Blog
Where document workflows go wrong
Not instructions — each tool explains itself. These are the things that catch people out, mostly learned by getting them wrong first.
What "runs in your browser" actually means
Local processing is a real guarantee about one specific thing. It is worth understanding which thing, and what it does not cover.
Extracted text is text, not layout
A PDF stores where each piece of text was drawn, not what order it should be read in. That is why extraction sometimes comes out scrambled.
Getting good OCR out of a bad scan
Recognition quality is decided before the recogniser runs. Most of the win is in what you feed it.
Why real redaction costs you the text layer
Every honest redaction method destroys something. Understanding which trade you are making is the difference between a redacted document and an embarrassing one.
Blank page detection is a threshold problem
A page with one line of text covers less than a tenth of a percent of the sheet. Which makes 'is this page blank' much harder than it sounds.
Front matter that agrees with itself
Covers, contents pages, bookmarks and page numbers all move each other. The order you add them in decides whether they end up consistent.
Keeping a Bates sequence honest across a set of files
Bates numbering is a convention, not a certification. What it guarantees depends entirely on how carefully you run it.
The duplex scan that comes out backwards
Your scanner produced two files: fronts, and backs in reverse order. Here is why, and how to reassemble them without re-scanning.
What PDF compression can and cannot do
Most 'compress PDF' buttons do nothing measurable to a text document. Here are the numbers, and what actually moves them.
Cropping a PDF doesn't remove anything
A crop changes what a reader displays, not what the file contains. If you crop to hide something, it is still there.
What merging quietly loses
Combining PDFs keeps every page and drops several things that are not pages. Knowing which ones saves rebuilding a packet twice.
A filled-in form is not a finished document
Form values live in fields, not on the page. Until you flatten them, what you see is not necessarily what anyone else sees.
Printing bigger than your printer
A poster split across ordinary sheets works well, provided you get one setting right and do not let the driver help.
Why booklet page order looks wrong until you fold it
On the outermost sheet, the last page sits beside the first. The arithmetic is simple once you have folded one piece of paper.
Why your document prints inconsistently
A PDF assembled from several sources usually contains several page sizes. That is the cause of most unpredictable printing.
Checksums, signatures, and what each actually proves
One tells you a file has not changed. One tells you who stood behind it. Confusing them is the common and expensive mistake.
What a PDF can and cannot stop someone doing
Passwords, permissions and watermarks offer very different guarantees, and only one of them is a real one.
The metadata most tools leave behind
Clearing a PDF's document properties usually clears half of them. The other half is a second store that many tools never touch.
Why a rotated PDF sometimes prints the wrong way round
Rotation in a PDF is a note attached to the page, not a change to it. That distinction explains a whole family of printing surprises.
Two documents wearing the same file extension
Almost every frustrating PDF problem comes down to one question: is this a document, or a photograph of one?