More about the Watermark PDF
Text or image: picking the right watermark
Here is the standard workflow. Open contract.pdf, six pages, type DRAFT, choose diagonal centre at 25% opacity, press Add Watermark. Half a minute later you download watermarked.pdf: all six pages carry a light diagonal DRAFT stamp, the contract text reads fine underneath, and the original file on your device is untouched. That untouched original is the whole point, watermark the copy, archive the clean version.
The situations that call for a watermark are remarkably consistent. Sending a proposal to a client before terms are agreed: stamp DRAFT so nobody mistakes it for final. Sharing internal figures: CONFIDENTIAL across every page. Publishing a sample chapter: your company name, so screenshots credit you. Photographers and designers watermark proofs for the same reason. In each case the watermark is doing legal ish work, signalling status, so make it unambiguous rather than decorative.
Batch stamping and honest limitations
Two mistakes we see constantly. First, cranking opacity to 80% because the preview looked faint, on paper it prints as a grey slab over your text. Stay under 35% for body pages. Second, watermarking the only copy. The stamp cannot be cleanly removed afterwards, so if a client later asks for the clean version and you overwrote your original, you are retyping a contract. Keep originals in a separate folder; watermark only copies.
Limits, stated plainly: text watermarks only, stamped on all pages at once, and the tool refuses password protected PDFs (remove the password first). The watermark is drawn with an embedded bold font, so it looks the same on every device, but it is a visual stamp, not a security feature. Anyone determined can cover it with a white box in an editor. For real document protection, combine a watermark with a password via our Protect PDF tool.
Sizing a diagonal stamp: the page geometry nobody does
A diagonal watermark has to span the longest line on the page, the corner to corner diagonal. On A4 paper, 210 by 297 millimetres, that diagonal works out to about 364 millimetres, roughly 1.7 times the page’s width. On US Letter it is about 13.9 inches against a width of 8.5 inches. This is why a size that looks generous on a horizontal footer stamp looks lost on a diagonal: the same word must stretch across a far longer distance to reach both corners, and short words like DRAFT need the larger sizes to get there.
Work it through on a real document. Suppose you are stamping a 12-page proposal before it goes to a client for review. You type “DRAFT - FOR REVIEW”, choose diagonal centre, and set opacity at 25 percent. At a medium size the phrase may only cross the middle third of each page, leaving clean corners a screenshot could crop around. Raising the size until the text spans most of that 364-millimetre diagonal is what makes the stamp survive cropping — the status of the document stays visible in any excerpt anyone shares.
Page shape matters as much as page size. The same stamp behaves differently on a landscape slide page, where the diagonal is flatter, and on a tall phone shaped document, where it is steeper. If your PDF mixes orientations or sizes, check a page of each type in the result before sending, the tool stamps every page with the same settings, and the page that reveals a problem is never the standard portrait one you tested first.
Opacity in practice: screens flatter, paper tells the truth
Every screen shows your watermark at its gentlest. Backlit displays and bright office lighting wash a 25 percent stamp out until it looks barely there, which tempts people to push the slider up before downloading. Print the first page before you judge. On paper, under flat light, the same stamp prints visibly darker and heavier than the screen suggested, and a stamp that looked tasteful on a monitor can sit on the text like a grey blanket. One test print is the cheapest quality control in the whole watermarking process.
Match opacity to purpose rather than to taste. A status stamp on a working document, DRAFT, CONFIDENTIAL, FOR REVIEW, wants the 20 to 30 percent band: unmistakable at a glance, silent underneath the reading. A deterrent stamp on a paid sample or proof can justify going somewhat stronger, because its job includes surviving screenshots and making casual misuse obviously visible. A subtle ownership line, like a company name in a footer position, can sit a little higher at small size because it does not cross the text at all.
If two audiences need two strengths, make two files rather than compromising one. Watermark the client copy at review strength and the internal copy lighter, name them clearly, and keep both beside the clean original. The tool runs in seconds per file, so versioning costs almost nothing, far less than the confusion of one stamp that is somehow both too faint for the client and too heavy for your own team.
Stamping a workflow, not just a file
A watermark earns more when it carries version information. “Draft v2” tells a client exactly which iteration they are reading and quietly expires every older copy in circulation; adding a date does the same job in plainer language. When feedback arrives referencing page numbers, ask which stamped version it belongs to before acting on it, half of all document confusion in collaborative work is two people annotating different drafts that share one filename.
Recipient specific stamps are the professional upgrade for sensitive documents. Instead of one generic CONFIDENTIAL copy for everyone, stamp each recipient’s copy with their company name alongside the status word. If a copy ever surfaces where it should not, the stamp names its route out. The effort is a minute per copy because the tool is quick, and the deterrent effect is real: people handle documents that carry their own name with noticeably more care.
Build the habit at the right moment in your process. Watermark the copy at the moment of sending, never during drafting, because a document still being edited will be re exported repeatedly and every re export needs the stamp reapplied. Keep the clean file in your working folder, produce the stamped file in the same motion as attaching it to the email, and the workflow protects itself, no checklist required, and no unstamped final ever escapes by accident.
