There’s a particular kind of anxiety that comes with sending a document into the world. Not the content anxiety — you’ve checked the numbers, reviewed the language, approved the layout. The distribution anxiety. Once it leaves your hands, it goes everywhere. And there’s no recall button.
Watermarks exist to solve this. Or at least to make the problem visible.
A watermarked document carries its provenance. “DRAFT” stamped diagonally across every page tells anyone who sees it that this isn’t final. “CONFIDENTIAL” tells them it shouldn’t have been shared. “COPY — JOHN SMITH” tells them exactly where it leaked from.
The first two are protective. The third is forensic. And the third is the one that actually changes behaviour.
When people know a document can be traced back to them specifically, they treat it differently. They don’t forward it casually. They don’t screenshot it and share it. They don’t leave it open on a screen in a coffee shop. The watermark isn’t a lock — it’s a name tag. And name tags make people careful.
This is why film studios send screener copies with unique watermarks to each recipient. It’s why law firms watermark discovery documents with the receiving party’s name. It’s why financial institutions watermark draft reports before board review.
PDFs have equivalent printing mysteries. A document that looks correct on screen prints with white borders that weren’t there in the preview. Colours shift — the deep blue that looked perfect in Chrome looks grey on the printed page. Fonts disappear and are replaced by the printer’s fallback. Images that were sharp on screen appear blurry on paper.
Each of these is a different problem with a different cause. White borders mean the page dimensions in the PDF don’t match the paper size. Colour shifts mean the document was created in RGB (for screens) and not converted to CMYK (for print). Font substitution means the PDF doesn’t embed the font — it references it by name and relies on the printer having it installed. Image blur means the resolution was set for screen (72 or 96 DPI) rather than print (300 DPI minimum).
The mechanics of fixing them are simple. But the tools that perform the fixes are scattered across expensive software or require uploading your document. For a file you’re preparing for a print run, uploading it to a third-party server to fix the margins is a step that shouldn’t be necessary.
The obvious answer: fix it locally. On your machine. Without the document ever touching a server.