Every freelancer has sent a draft to a prospect and felt the same small worry: what if this work gets used without the project going ahead? A proposal, a design mockup, a sample chapter — once it leaves your inbox, you cannot control where it goes next. A watermark does not solve that problem completely, and anyone who tells you it does is overselling it. But as one step in a sensible sharing workflow, it is cheap, quick, and genuinely useful.
Add Watermark stamps translucent text — DRAFT, CONFIDENTIAL, or your own words — across a PDF's pages, in your browser, with controls for opacity, angle, size and tiled layout. This post builds a sharing workflow around it for freelancers, using a fictional example, and is honest throughout about what the watermark can and cannot protect.
Why watermark a draft at all
A watermark serves two purposes, and they are different. The first is signalling: a document marked DRAFT tells the reader, unambiguously, that this is not the final version. That matters when a prospect forwards the draft internally, because the third person who opens it may never see your covering email. The watermark carries the status with the document itself, wherever it travels.
The second purpose is deterrence. A visible mark across a page makes casual reuse awkward: a prospect who wanted to quietly use your draft as a finished deliverable must now explain the word DRAFT stamped across every page, or do the work of removing it. Deterrence is not prevention — a determined person can remove or crop a watermark — but most misuse is casual, not determined, and a watermark raises the effort of casual misuse above zero. That is often enough.
What a watermark does not do is prove ownership in a dispute, prevent screenshots, or stop someone from retyping your ideas. If those are your concerns, you need different tools: contracts, dated records, and selective sharing. A watermark is a label and a speed bump, not a lock.
The workflow: mark, check, send separately
A reliable workflow has four steps. First, finish the draft as a PDF and save an unmarked original. Never watermark your only copy: you will need the clean version when the project goes ahead, and re-creating it from a watermarked file is unnecessary work.
Second, watermark a copy. Choose text that states the document's status plainly: DRAFT, DRAFT — NOT FOR DISTRIBUTION, or your business name plus DRAFT. Diagonal placement across the centre of the page is the usual choice, because it is visible on every page without hiding any single paragraph entirely. Set the opacity so the mark is unmistakable but the text beneath remains readable — the readability question deserves its own attention, and it is covered in the next post in this series.
Third, check the watermarked copy page by page. Open it and confirm the mark appears on every page, that it does not obscure a key figure or heading, and that the document still reads sensibly. A watermark that hides the price in your proposal has cost you more than it protects. This check takes two minutes and catches the errors that embarrass.
Fourth, send the watermarked copy, and keep the covering email separate from the document's status. Do not rely on the email to say "this is a draft" — say it in the email too, but let the watermark carry the message for anyone who receives the file second-hand.
Worked example: a fictional proposal
Elena, a fictional freelance designer at example.org, has prepared a twelve-page brand proposal for a prospective client, a small bakery chain. The proposal includes logo concepts, colour palettes, and a price breakdown. She is excited about the project, but the client has not signed anything, and the concepts are her work until they do.
Elena saves the clean proposal as her original, then creates a watermarked copy marked "DRAFT — Elena Design Studio" diagonally across each page, at a moderate opacity. She checks every page: the logo concepts are still clearly visible, the price breakdown is readable, and the watermark is unmistakable on each page, including the cover. She sends the watermarked copy with an email explaining that the concepts are drafts for discussion, and that final files follow on agreement.
Two outcomes are possible, and the watermark helps in both. If the client goes ahead, Elena sends the clean final files, and the draft's watermark becomes irrelevant history. If the client goes quiet and later uses a concept, Elena has a document that was visibly marked as a draft, a dated email sending it as such, and a clean original proving the work's provenance. None of that promises a good outcome, but it puts her in a far stronger position than sending an unmarked file and hoping for the best.
For a related guide on preparing documents for sharing, see merging and splitting PDFs.
What to watermark, and what not to
Watermark drafts, proposals, samples and anything sent before payment or agreement. Watermark documents shared with people who will forward them internally, since you cannot control the onward journey. Consider watermarking portfolio samples sent to strangers, where the relationship is new and untested.
Do not watermark final deliverables a client has paid for, unless they ask for it — a paying client has bought the clean file, and a watermark on it reads as distrust. Do not watermark documents where readability is the whole point, such as a reference manual the reader must consult quickly; there, a watermark on every page is a constant irritation. And do not watermark instead of a contract: if a document genuinely must not be shared, a written agreement and selective sharing protect it better than a translucent word ever will.
Honest limitations
A watermark is a deterrent and a label, not a security measure. It can be cropped out if it sits near an edge, covered with a shape, or removed by anyone with modest PDF editing skill. It does not survive a screenshot being retyped, a photograph of a screen, or a determined attempt to clean the file. It also does not identify who leaked a document, unless the watermark itself carries a recipient's name — a technique that works for controlled distributions but is overkill for an ordinary proposal. Use watermarks as part of a workflow that also includes contracts, dated records, and care about who receives what.
FAQs
Should I watermark every draft I send?
For new prospects and unsigned work, yes — it costs minutes and marks the document's status wherever it travels. For established clients and paid deliverables, a watermark is usually unnecessary and can read as distrust.
Does a watermark prove the work is mine?
No, not on its own. It shows the document was marked as a draft, but proof of ownership comes from dated originals, contracts, and records of the work. Keep the clean original and the sending email as your evidence.
What text should a draft watermark carry?
The document's status, plainly: DRAFT, or your business name plus DRAFT. Avoid aggressive wording like "STOLEN WORK" or legal threats — a calm, factual mark is more professional and just as effective as a deterrent.
Will a watermark annoy the prospect?
Not at a sensible opacity. A translucent diagonal mark is standard practice in creative work, and most clients expect drafts to be marked. If the mark obscures the content, lower the opacity or reduce the size until the document reads comfortably.
When a draft also needs real access control, Protect PDF adds a password, and Sign PDF places a signature on a finished document.
human review pending client designation