How to annotate a PDF without changing the file
The usual way to mark up a PDF is to write the markup into the PDF. That works, and it is also why the file you got back is not the file you sent. There is a cleaner way: keep the annotations in a separate file and anchor them to the document by content rather than by position.
Three places your annotations can live
Inside the PDF. Standard PDF annotation objects written into the file. Universally readable by other viewers, and the only option if you must send marked-up documents to people who use different software. Cost: the document is modified, the file grows, and an incremental update is appended every time you save.
In the application's own database. Some readers keep all annotations in a central store keyed by file path or hash. Convenient until you move the file, rename it, or open it on another machine — then the notes vanish or attach to the wrong document.
In a sidecar beside the file. A small companion file (FlyPDF uses .flymark) that lives next to the PDF and holds highlights, notes, shapes and reading position. The PDF itself is never opened for writing. Move both files together and your annotations travel; email only the PDF and the recipient sees a clean document.
Why anchoring matters more than storage
Any annotation scheme has to answer one hard question: where exactly does this highlight belong?
- Page + rectangle is easy and brittle. Change the zoom, print at a different paper size, or open a re-flowed version, and the rectangle is pointing at the wrong pixels.
- Page + character range is better. The annotation follows the text even if the page is rendered differently — but it breaks if the document is re-exported with different pagination.
- Page + character range + context hash is what survives in practice. Store the surrounding text with the offset, and if the range no longer matches, search the neighbourhood for the context string and re-anchor. When even that fails, fall back to the rectangle and tell the user the anchor was lost rather than silently moving their note.
That last point is the difference between annotation storage you can trust and storage that quietly corrupts your notes. A viewer should be honest about an anchor it could not resolve.
A workflow that keeps the original intact
- Put the PDF where it lives permanently — the sidecar is written next to it, so a file on a read-only share or a write-protected archive directory will not accept annotations.
- Highlight, underline, strike out, add sticky notes, rectangles and arrows as usual.
- Save (or let it autosave). Only the sidecar is touched; verify with a hash if you want proof.
- Keep the pair together when you archive. A sidecar without its PDF is meaningless; a PDF without its sidecar is simply the original.
- Back up both. If your backup tool filters by extension, make sure the sidecar extension is included.
When you should flatten anyway
Sidecars are not universally right. Use in-PDF annotations when:
- The marked-up document has to be read by someone else's software. A colleague on Acrobat will not see your
.flymark. - You need a single artefact for submission, filing, or a formal record.
- The annotation must be part of the legal document — a signature, a stamped approval, a redaction.
The safe pattern here is: annotate on a copy, then flatten the copy. Do your reading and marking in the read-only viewer on the original, then — only when you actually need to send something — export a flattened version. You keep an untouched source and still get a shareable marked-up file.
What FlyPDF does
- Six annotation types (highlight, underline, strikeout, sticky note, rectangle, arrow), stored in a
.flymarksidecar next to the document. - Anchoring to text wherever a text layer exists, falling back to rectangles on scans.
- No save path that writes to the PDF — the viewer does not hold the file open for writing at all.
- A list panel for jumping between annotations, and export of annotation text for pasting into a report or email.
What it does not do: write annotations into the PDF, or read annotation types it does not support from files annotated elsewhere. Because annotations are not burned in, other readers will not see them — that is the trade, and it is deliberate.
Practical tips
- Agree a convention with your team. If you exchange marked-up PDFs, sidecars will confuse people; if you exchange clean originals plus separate notes, they are ideal.
- Name the sidecar after the document, not the other way round. If you rename the PDF, rename the sidecar to match or the pairing breaks.
- For review cycles, export the notes as text. A reviewer list of "page 12, paragraph 3: typo" is often more useful than a coloured rectangle the recipient has to hunt for.
- Check your sync client. Some cloud sync tools ignore unknown extensions; confirm the sidecar actually uploads.
Marking up a document and preserving a document are different jobs. Keep them in different files and you stop having to choose.
<!-- fd:hublink --> Related guide: see Redacting a PDF before sharing 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