How to remove highlight annotations from a pdf document
- Step 1Decide whether you need a markup-free copy — This tool removes all annotations, not just highlights. If you want a clean reading copy with no markup at all, continue. If you need to keep comments but drop highlights, this tool can't do that — use a full editor instead.
- Step 2Keep your highlighted original — Removal is permanent on the output. If the highlights mark passages you still need to find later, save the highlighted version separately before you run the tool.
- Step 3Open the highlight remover — Go to the PDF Annotation Remover. It runs locally in your browser; the document is never sent anywhere.
- Step 4Drop the highlighted PDF in — Drag the file onto the dropzone. The tool takes one PDF and starts immediately on drop — there is no settings step.
- Step 5Let the single pass run — Every page's
/Annotsarray is deleted, removing highlights, underlines, strikethroughs, and any other annotations together, then the file is re-saved. - Step 6Verify and download — Reopen the output and confirm no coloured quads remain over any text. The downloaded file is named
yourdoc.annotation-remover.pdf.
Text-markup annotations and how this tool treats them
All three text-markup subtypes live in the page /Annots array and are removed when the array is deleted. There is no way to target only one subtype.
| Markup | Annotation subtype | Removed? | Underlying text after removal |
|---|---|---|---|
| Highlight (coloured span) | Highlight | Yes | Fully intact |
| Underline | Underline | Yes | Fully intact |
| Strikethrough | StrikeOut | Yes | Fully intact (the text is not deleted) |
| Squiggly underline | Squiggly | Yes | Fully intact |
| Sticky notes / callouts on the same page | Text / FreeText | Yes — removed too, no opt-out | n/a |
Free vs Pro limits
Enforced before the file is processed. The free tier checks both size and page count.
| Tier | Max file size | Max pages | Files per job |
|---|---|---|---|
| Free | 2 MB | 50 pages | 1 |
| Pro | 50 MB | 500 pages | 5 |
| Pro + Media | 500 MB | 2,000 pages | 50 |
Cookbook
Before/after scenarios for highlight-heavy review PDFs, and what this all-or-nothing pass actually produces.
A study guide highlighted yellow throughout
You highlighted half the page while studying and now want a clean copy to print. Every Highlight quad is removed; the text beneath is untouched.
Before page 4: Highlight x14 (yellow), Underline x3 page text: 612 words After (auto-run): /Annots empty → 0 highlights, 0 underlines page text: 612 words (identical) → notes.annotation-remover.pdf
Strikethrough does NOT delete the text
A reviewer struck through a sentence to suggest deletion. Removing the StrikeOut annotation removes the line through the text — but the text itself stays, because strikethrough is markup, not an edit. If the deletion was intended, edit the source document.
Before: "This clause is obsolete" ← StrikeOut over it After annotation remover: "This clause is obsolete" ← still present, no line To actually delete it, change the source then re-export.
Highlights and comments together — both go
The page has highlights you want gone and comments you wanted to keep. There is no per-type selection, so the single pass clears everything. Keep the annotated original if the comments still matter.
Before page 2: Highlight x5 + Text comment x2 After: empty /Annots → highlights AND comments removed No highlight-only mode exists in this tool.
Coloured highlights from different reviewers
Two reviewers used different highlight colours. Subtype and colour are irrelevant to the tool — it deletes the whole array, so every colour disappears at once.
Before: green Highlights (Reviewer A)
pink Highlights (Reviewer B)
After: all Highlight objects removed
regardless of colour or authorConfirming a clean reading copy
The result panel shows counts, not a per-annotation breakdown. Verify visually that no quads remain.
Result panel: Input pages: 28 Input size: 1.1 MB Output size: 0.97 MB Processing: Browser Open reading-copy.annotation-remover.pdf → scroll: no coloured spans on any page
Edge cases and what actually happens
No highlight-only option exists
Not supportedThe tool deletes the entire /Annots array per page; it cannot remove highlights while keeping comments or vice versa. For surgical, type-by-type removal use a full editor such as Adobe Acrobat. Keep your annotated original if you need any annotation back.
Strikethrough left the text in place
By designA StrikeOut annotation draws a line over text — it does not delete the text. Removing the annotation removes the line; the words remain because they are page content, not part of the markup. To actually remove struck-through text, edit the source document and re-export.
Highlighted text in a scanned (image) PDF
SupportedIf the highlight is a real Highlight annotation over a scanned page image, it is removed normally. The page image underneath is untouched. (The 'text' in a scan is pixels, not characters — to make it searchable, run PDF OCR afterward.)
Form fields disappear too
ExpectedRemoving annotations also clears interactive AcroForm fields, since form widgets are annotations. If the document is a form whose values you need, flatten it first with PDF Flatten, then strip the highlights.
Free-tier file over 2 MB or 50 pages
BlockedBoth limits are enforced before processing. A long, heavily highlighted document hits one or the other quickly. Upgrade to Pro (50 MB / 500 pages) or shrink the file with lossy compression first.
Highlight 'baked into' the page, not an annotation
PreservedIf a previous tool flattened the highlights into the page content (coloured rectangles drawn into the content stream), they are no longer annotations and this tool cannot remove them. Once flattened, highlight colour is part of the page and stays.
Password-protected PDF
Often worksThe tool loads files with encryption ignored, so many protected PDFs process fine. If a strongly encrypted file won't open, unlock it first with PDF Unlock, then remove the markup.
PDF has no annotations
By designPages with no /Annots array are skipped and you get a valid, re-saved copy with nothing changed. No error is raised.
Corrupt PDF
ErrorA damaged or non-PDF file fails to parse and the run errors rather than producing partial output. Repair it first with PDF Repair.
Frequently asked questions
Will removing highlights delete the highlighted words?
No. A highlight is a Highlight annotation — a coloured quad drawn over the text, stored separately in the page's /Annots array. Removing it takes away the colour, not the characters. Every highlighted word stays exactly where it was; you simply get a clean, unmarked version of the same text.
Can I remove highlights but keep my comments?
No. The tool removes the entire annotation layer in one pass — highlights, underlines, strikethroughs, comments, and callouts all go together. There is no per-type or per-subtype switch. If you must keep comments while dropping highlights, use a full editor like Adobe Acrobat, and keep your annotated original as a fallback.
Does removing a strikethrough delete the text it crossed out?
No. A StrikeOut annotation draws a line through text to suggest a deletion; it does not perform the deletion. Removing the annotation removes the line, but the text underneath remains because it is real page content. If the strikethrough represented an intended edit, change the source document and re-export the PDF.
Are underlines and squiggly lines removed too?
Yes. Underline, StrikeOut, and Squiggly are text-markup annotations in the same /Annots array as highlights, so they are all removed when the array is deleted. As with highlights, the underlying text is untouched — only the markup overlay is gone.
Will the highlight colour come back if I reopen the file?
No. Once the annotation is deleted and the PDF re-saved, the highlight is permanently gone from the output file. Reopening it in any viewer shows clean text. Your original highlighted file is unaffected, though, so you can always return to it.
Is the document uploaded to remove the highlights?
No. All processing happens in your browser using pdf-lib. The file never leaves your device — the result panel confirms Local browser processing · 0 bytes uploaded. Only an anonymous usage counter is logged if you are signed in.
Why are my form fields gone after removing highlights?
Because interactive form fields are annotation widgets, and the tool clears the whole annotation layer including the AcroForm. If your document is a fillable form and you need the entered values, run PDF Flatten first to bake the values into the page, then remove the highlights.
What if the highlights were flattened into the page already?
Then they are no longer annotations — they are coloured shapes in the page content stream — and this tool cannot remove them. Annotation removal only affects objects in /Annots. Flattened highlights are permanent and would need a content-level editor to undo.
How big a file can I process?
Free tier: 2 MB and 50 pages, both enforced before the run. Pro: 50 MB and 500 pages. Pro + Media: 500 MB and 2,000 pages. A long, heavily highlighted PDF can exceed the free limits, so compress with lossy compression first or upgrade.
Do I need to choose 'highlights' from a menu before running?
No. There is no menu and no options panel. The tool processes automatically the instant you drop a PDF in, removing the whole annotation layer. You don't pick markup types because there is no per-type filtering.
Does this work on highlights made in any app?
Yes. Whether the highlights came from Adobe Acrobat, macOS Preview, Microsoft Edge, or another viewer, they are stored as standard Highlight annotations. The tool removes the entire array, so the originating app is irrelevant — all highlights are cleared the same way.
Will the file get smaller after removing highlights?
A little. Each highlight carries geometry and an appearance stream, so deleting many of them trims some bytes. The saving is modest because the page content is unchanged. For meaningful size reduction, follow up with lossless or lossy compression.
Privacy first
All PDF processing runs locally in your browser using PDF-lib and pdf.js. No file is ever uploaded — only metadata counters are saved for signed-in dashboard stats.