H
HidePDF
Redact PDFs in your browser. Nothing uploads.
100% local · zero uploads

How to Redact a Freelance Contract Before Sharing It

Freelancers reuse old contracts as portfolio samples—but past client rates, names, and proprietary details weren't meant to travel with them.

PDF
Drop a PDF here, or click to choose
Your file never leaves your device.
Burning in redactions…

Freelancers end up sharing old contracts more often than people expect. A designer wants to show a past agreement as a portfolio piece to prove they've handled a project of a certain scope. A consultant references a past contract in a proposal to demonstrate the kind of engagement they typically run. A hiring manager asks for a work sample, and the cleanest proof of past work happens to be an actual signed contract rather than a case study. In all of these situations, the goal is to demonstrate experience or process — not to hand over a past client's confidential rate, internal business details, or personal information along with it. A contract written for one client relationship was never meant to circulate beyond it, so before reusing one as a sample or reference, it's worth going through and removing anything that belonged specifically to that past relationship.

What Typically Needs Redacting

A handful of things come up in almost every freelance contract that shouldn't travel with it once it's repurposed as a sample.

The client's name or company name is often the first thing to consider, especially if the original agreement included any confidentiality or non-disclosure language. Even without a formal clause, many clients simply expect their name won't show up in someone else's portfolio without being asked first.

Payment terms and exact rates are almost always worth removing. Rates are frequently treated as private by both freelancers and clients, and showing a specific number tied to a specific client can create friction — either because it reveals what that client was willing to pay, or because it sets an expectation with whoever you're sharing the sample with that may not reflect your current rates.

Scope-of-work sections sometimes reference proprietary details about the client's business — internal tools, product names, unreleased plans, or specific processes — that were fine to include in a private agreement but shouldn't be visible in a document you're now showing to someone unrelated to that client.

Signatures and contact information for the other party are also worth removing. A signature block with a name, title, email, and phone number is personal information that doesn't need to travel along with a document you're using to show off your own work.

When You Legally Need to Redact vs. When It's Just Good Practice

Some contracts include an explicit confidentiality or non-disclosure clause that legally restricts what you can share externally — including the terms of the contract itself, the client's identity, or specific details discussed in the scope of work. If your contract has language like this, redaction isn't optional; you need to remove anything the clause covers before showing the document to anyone outside that engagement, and in some cases you may need to avoid sharing it at all.

In other cases, there's no formal confidentiality requirement, but redacting rates, personal contact information, and identifying details is simply professional courtesy — the kind of discretion most clients would expect even if it isn't spelled out contractually. Before sharing any version of an old contract externally, it's worth actually reading back through the confidentiality section (if there is one) rather than assuming a document is safe to share just because nothing bad has happened yet.

How to Do It

Open the contract directly in your browser using HidePDF and work through it methodically: black out the signature blocks, every dollar figure and payment term, the client's name and company wherever it appears, and any contact details for the other party. Leave the scope-of-work and deliverables sections visible where they don't reference proprietary client details — that's usually the part that actually demonstrates your work. Because the redaction happens locally, the contract never has to leave your device just to prepare a version you can share elsewhere.

Common Mistakes

The most common mistake is redacting information the first time it appears but missing it the second time — client names and rates often show up again in an appendix, a change order, or an exhibit attached to the main contract, and it's easy to redact the body while forgetting those extra pages. Going too far the other direction is also a problem: redacting so heavily that the sample no longer demonstrates anything useful defeats the purpose of sharing it in the first place. And it's worth stating plainly: don't assume a version is safe to share just because you removed a few obvious details — actually check the contract's confidentiality clause, if one exists, before treating any redacted version as fully cleared for external use.

Related guides

Explore more ways to redact PDFs privately, or use the redaction tool above:

Frequently asked questions

Can I share a redacted contract even if it has a confidentiality clause?

It depends on exactly what the clause restricts. Some clauses prohibit sharing the existence of the engagement at all, not just specific terms, so read the language carefully or check with the client before sharing any version.

Should I redact my own rate, or just the client's information?

That's a personal call. Many freelancers redact their own historical rates too, since past pricing can create awkward comparisons with current rates.

What's the safest way to redact a contract I plan to reuse for multiple future proposals?

Create one thoroughly redacted master version, double-check every page including appendices, and reuse that same file rather than redacting a new copy each time you need it.

Does redacting a contract this way affect the original file?

No. Redaction with HidePDF creates a new, separate file — your original signed contract stays intact and unaffected, since everything happens locally in your browser.