Annotate a PDF: markups everyone can see, because they are in the page
Reviewing a draft lives or dies on whether the marks survive the journey. A highlight made as a floating annotation can vanish in the wrong reader, hide behind a layer setting, or strip out on a forward. Annotate PDF takes the other road: you mark up the page preview — highlight, underline, box, sticky note, text note, in your colour — and when you press the button, the markups are burned into the page. They become part of the document every reader renders, every printer prints, every forward carries. This article is about the review craft that follows from that permanence: mark boldly, because the marks will be seen; mark finally, because they will stay.
The five tools, and the review grammar they form
Highlight (drag) — the highlighter pen: this passage matters. Underline (drag) — the editor's pencil: this phrase, precisely, is the problem or the point. Box (drag) — the figure framer: this chart, this table, this region — look here. Sticky note (click) — a pinned comment marker at a spot. Text note (click) — the comment itself, written on the page where it belongs. Together they form the grammar of a good review: marks locate, notes explain. A highlight without a note says “something here”; a note without a mark floats unanchored. The colour choice is your voice in that grammar — one colour per reviewer is the meeting-room convention, and it works in files too: the reader can follow whose marks are whose across a long document.
The workflow honours how reviewing actually happens: choose a page and a tool, drag or click on the preview, accumulate marks (the counter keeps count, Undo last forgives the slips), and only when the review is complete, bake them in. Until the bake, the session is a draft; the bake is the publishing of your review into the document itself.
Burned in vs floating: the permanence bargain
Floating annotations are editable, hideable, filterable — and losable. Burned-in markups are none of those: they show everywhere, print everywhere, and cannot be toggled off or peeled away by the recipient. Choose per audience. A collaborative draft, where the author must work through comments and resolve them one by one, wants floating comments in a full editor. A review of record — the marked proof sent to a client, the commented draft archived with a decision, the annotated exhibit — wants the marks inseparable from the pages. The tool in front of you is built for the second genre, and its one discipline follows: annotate a copy. The clean original stays clean; the marked file is the review, named as such.
Annotate a PDF, step by step
Step 1 — drop a copy of the PDF onto Annotate PDF. The review copy, not the master. Nothing uploads — drafts under review are usually unreleased for a reason.
Step 2 — pick your colour and your first tool. One colour per reviewer; highlight for passages, underline for phrases, box for figures.
Step 3 — mark page by page. Drag for highlights, underlines and boxes; click for notes, and type the note text that makes the mark make sense.
Step 4 — undo freely, count honestly. The markup counter is your review's table of contents; a page with forty marks is a conversation, a page with two is a verdict.
Step 5 — bake in the markups and send the marked file. Open it once as the recipient will: marks present in a plain reader, printing as expected. That check is the whole point of burned-in — verify it once, trust it everywhere.
Annotation vs editing: marks talk about the text; they do not change it
Nothing here alters a word of the document — deliberately. The reviewer's authority is commentary; the author's is the text. When a “review” discovers the document needs an actual correction — a wrong figure, a typo — that is editing's job, done by whoever owns the text, ideally before the annotated copy becomes the record. Keep the genres separate and both stay honest.
Mark it so it survives the forward.
Highlights, underlines, boxes and notes — drawn on the preview, burned into the page, visible in every reader.
Open Annotate PDFSources
- Adobe — Comment on PDFs: Adobe's reference for highlights, sticky notes and comment markup — the standard annotation behaviour this guide explains how to keep readable in every reader.
- Tool behaviour — the steps and limits in this guide are from PDFJadoo's own Annotate PDF tool page, checked 18 November 2026; the file never leaves your device, so the result you preview is the file you save.
A worked example: the contract review
A draft services agreement circulates for comment. The reviewer works the copy: highlights on the three clauses that matter (liability, term, exit), underlines on two phrases whose wording carries risk, a box around the pricing table, and text notes at each mark saying why — the note at the liability clause is four words: “cap missing — see v2”. Baked in and returned, the marked file opens identically for the drafter, their partner and the client-side reader on a phone: forty marks, zero “I can't see your comments” emails. The drafter works from the marks; the clean master absorbs the agreed changes; the marked file is archived as the review of record. Permanence was not a feature — it was the medium the conversation needed.
Edge cases
Marks on the wrong layer of history. Annotating version 6 while the author edits version 7 strands the review. Name the version in the marked file's name, and freeze the reviewed draft.
Note text length. A text note is a comment, not an essay; the essay belongs in the covering message, with the note pointing at its passage.
Scanned pages. Markups burn into scanned pages as happily as text pages — the preview is the page, whatever the page is made of.
Before you finish: the 60-second check
- The annotated file is a copy — the clean master stays clean
- One colour per reviewer, used consistently
- Every significant mark carries a note saying why
- The bake happened once, after the review was complete
- The marked file was opened in a plain reader to prove the marks travel
Fair questions
How do I annotate a PDF for free?
Drop the PDF onto Annotate PDF, choose a tool — highlight, underline, box, sticky note or text note — mark up the page previews, and press Bake in my markups. The marks are drawn into the pages themselves, in your browser.
Will my annotations show in every PDF reader?
Yes — that is the point of baking them in. Floating annotations depend on the reader's annotation support; burned-in markups are page content, rendered and printed by every reader.
Can the recipient remove my markups?
Not as annotations — they are part of the page. That permanence suits reviews of record; for collaborative drafts the author must resolve one by one, a full editor's floating comments are the better medium.
Can I undo a markup before baking?
Yes — Undo last removes marks during the session, and the counter tracks how many you have placed. The bake is the point of no return, so review before pressing it.
Does annotating change the document's text?
No. Markups comment on the text; they never alter it. Corrections belong to editing, done on the master by its owner.
Is my draft uploaded?
No — marking and baking happen in your browser; the file never leaves your device.
Tool behaviour — the five markup tools, colour and note text, the markup counter with undo, and the bake-in permanence model — is from PDFJadoo's own Annotate PDF page. Checked 18 November 2026.
Keep reading
How editing PDF text works
When the review finds a real error — the correction craft, in place.
Flatten a PDF
Permanence's other form: fields baked into the page for filing.
Compare two PDF versions
The author revised it — which pages actually changed?
Electronic vs digital signatures
Review complete and agreed? The signing step, and which kind you need.