Why a read-only PDF viewer matters more than you think
Most people think of "read-only" as a missing feature — the thing you give up when you do not buy the editor. It is more useful than that. It is a guarantee you can verify, and for a surprising number of documents that guarantee is worth more than the ability to edit.
Opening a file is not a neutral act
A PDF is a structured file with an object table, a cross-reference index, and metadata. Plenty of completely reasonable viewer behaviour touches it:
- Metadata rewrites. Some applications update
/ModDateon open, or add an application tag to/Produceron save. - Incremental updates. A save appends a new revision rather than rewriting the file. The document looks identical — and the byte count quietly grows.
- Re-serialisation. A repair pass on a slightly malformed file rewrites the object structure. Usually harmless, occasionally fatal to a digital signature.
- Annotation flattening. Comment in one tool, save, and your note is now part of the page content. There is no undo that leaves the file untouched.
- Accidental edits. A stray keystroke in a viewer with editing enabled is a stray edit. It happens.
None of this is malicious. It is all just software doing what software does. The problem is that afterwards you cannot easily prove the document is what it was.
Cases where "unchanged" is the whole point
- Signed contracts. An incremental update after signing does not always invalidate the signature, but it does complicate the story you have to tell about the file.
- Litigation and discovery. "Has this document been altered since you received it?" is a question you want a clean answer to.
- Evidence and chain of custody. A hash taken at intake should match the hash at review.
- Regulated records. Financial, medical and pharmaceutical workflows often require the received artefact to be preserved as received.
- Shared network drives. When five people open the same specification, you want to know nobody's viewer wrote to it.
How to verify a viewer really is read-only
Do not take a marketing claim for it — the test takes a minute and works with free tools:
certutil -hashfile "specification.pdf" SHA256
:: note the hash, open the file in the viewer, scroll every page,
:: rotate a page, add a highlight, close it
certutil -hashfile "specification.pdf" SHA256
:: compare
Two more things worth checking while you are at it:
- File size and modified date. Unchanged means byte-identical, not "looks the same".
- What appeared next to the file. A viewer that stores annotations in a sidecar (FlyPDF writes
.flymark) leaves the original alone; one that writes into the PDF does not.
If the second hash matches the first after a full read-through including annotations, the viewer is doing what it says.
Read-only is not the same as limited
This is the usual objection, and it rests on a false trade. A read-only viewer can still be genuinely capable — it just has to keep state somewhere other than your document:
| Capability | Where the state lives |
|---|---|
| Highlights, notes, arrows | Sidecar file beside the PDF (.flymark) |
| Search index for scanned pages | Memory, discarded on close |
| Reading position, zoom, theme | Application settings |
| Bookmarks and custom page labels | Session data |
The trade-off to be aware of is real but narrow: annotations stored outside the PDF are invisible to other readers unless you export them. If your workflow is "mark up and email the PDF to a colleague who uses Acrobat", a sidecar approach will frustrate you. If your workflow is "read, search, annotate, and keep the original intact", it is exactly what you want.
What read-only does not protect you from
Being straight about the limits:
- It does not stop you from copying the file and editing the copy. It only guarantees the original is untouched by the viewer.
- It does not detect prior tampering. Use a signature check or a known-good hash for that.
- It does not make a malicious file safe. Read-only refers to the document, not to the threats a hostile PDF carries — see PDF security risks.
- It does not help if your workflow genuinely requires editing. Then use an editor, on a copy.
The one-line summary
If your job is authoring PDFs, buy an editor. If your job is reading PDFs and being able to say they were not touched, use a viewer that structurally cannot touch them — and verify with a hash rather than a promise.
<!-- fd:hublink --> Related guide: see Using a portable PDF viewer for a detailed walkthrough.
FlyPDF does this locally. Read-only by design: OCR, search, annotations and text export all run on your machine, and the source file is never rewritten.
Try FlyPDF free for 30 days