Removing annotations from a PDF means deleting the interactive objects associated with each page — links, comments, stamps, and form widgets — without disturbing the painted text and images that make up the document's visible content. PDF annotations live in a separate array on each page dictionary called the Annots entry, which is distinct from the content stream that holds drawn artwork. A page can look identical to a regular PDF page and still carry dozens of invisible link regions, popup notes, or fillable widgets on top of it. The local annotation tool at Remove PDF Annotations walks every page dictionary in your file, counts those entries, removes the entire Annots array from each page that has one, and writes a new PDF whose page count, page order, page boxes, rotation, and existing content streams remain in place. Everything happens in the browser, so the original file stays on your device and nothing is sent to a server.
What Counts as a Page Annotation
PDF annotations are a defined category in the PDF specification. They are objects attached to a page through the Annots array and they carry their own appearance, behavior, and metadata. Common members of this group include clickable link annotations, text comments and sticky-note popups, highlight and underline markup, stamps, file-attachment annotations, and form-field widgets. The category is broader than most readers expect — even a small sticky note in the margin counts as a page annotation, as does an invisible rectangle drawn over a heading that turns the word into a clickable link.
What is not an annotation is equally important. Anything that has been flattened or painted directly into the page's content stream is no longer an annotation, even if it looks like one. A bright yellow bar across a sentence might be a real highlight annotation, or it might be a flat yellow rectangle drawn with the same color as a highlight. Only the first kind is reachable through the Annots array. The second kind has become part of the page artwork and stays put when annotations are removed. This is why the tool's removal rule is narrow and auditable rather than visual.
How to Strip Annotations from a PDF
Follow these steps to use the annotation tool and produce a new local PDF with page annotation arrays removed.
- Choose a non-empty PDF no larger than 25 MiB. Open the Remove PDF Annotations page and select your file. The tool loads the PDF locally in your browser; nothing is uploaded. Empty files, non-PDF selections, files over 25 MiB, encrypted PDFs, and files with damaged cross-reference data produce a visible error rather than a silent failure.
- Review the detected annotation count and number of affected pages. The tool resolves each page's Annots array and reports two numbers: the total annotation entries across the document and the count of pages that hold at least one entry. If both numbers are zero, the tool tells you that no page annotations were found and does not create a pointless replacement file. Selecting another file clears the previous inspection.
- Remove the page annotations and download the new PDF. Click the action to remove annotations. The tool deletes the Annots key from every page dictionary that has one and serializes a new PDF. The page count, page order, page boxes, rotation, and existing content streams remain in place. The original file is never overwritten. The generated filename adds -annotations-removed to the original base name.
- Open the downloaded PDF and verify both visible and interactive behavior. Check that the page artwork still looks right, that highlights and stamps you wanted to keep still appear if they were flat content, and that links, popups, and form widgets no longer respond. Different PDF viewers interpret the remaining interactive objects differently, so use the viewer or workflow that matters to you.
What the Tool Strips vs. What It Leaves Alone
The table below summarizes the page-level behaviors this annotation tool can remove and the page-level behaviors it cannot. Read the third column carefully: removal depends on whether the object still lives in the page's Annots array, not on whether it looks like an annotation in the viewer.
| Behavior or Object | Page Annotation? | Removed by This Tool? |
|---|---|---|
| Clickable link regions | Yes (Link annotation) | Yes |
| Sticky-note popups and text comments | Yes (Text annotation) | Yes |
| Highlight, underline, strike-through markup | Yes (Markup annotation) | Yes |
| Stamps still bound to the Annots array | Yes | Yes |
| File-attachment annotations | Yes | Yes |
| Form-field widgets (text boxes, checkboxes, signatures) | Yes (Widget annotation) | Page presence removed |
| Flattened highlight painted into content stream | No | No — it lives in the artwork |
| Completed form value already drawn into the page | No | No — it lives in the artwork |
| Blue underlined link text after link removal | n/a | Text remains, click target gone |
| Document metadata, embedded files, scripts, hidden layers | Not page annotations | Not affected |
The key rule is that removing the page annotation array disables interactivity but does not erase visible marks that were never annotations to begin with. Form widgets are removed as page annotations, but the document catalog can still contain form-related structures; the tool makes no claim that it repairs, flattens, or fully deletes an AcroForm definition. If field structure must remain valid for downstream workflows, use a dedicated form editor instead.
What This Tool Does Not Do
This tool performs a narrow, auditable operation. It is not a security redaction or sanitization product. Deleting page references does not prove that referenced objects, prior revisions, metadata, attachments, scripts, hidden layers, embedded files, or recoverable source information have been purged from every byte. Do not use it to remove confidential information. For sensitive disclosure, use a purpose-built redaction workflow that permanently removes content and validates the final file. Scripted workflows that need finer control over the page dictionary can call pdf-lib's PDFDocument load and save API directly, but that path is for developers, not for casual redaction.
Password protection is not bypassed. If the PDF is encrypted, the tool reports the error and does not produce an output. The 25 MiB size limit and the no-empty-file rule also stop processing at the input stage. A stale asynchronous job cannot replace a newer selection, and an earlier object URL is revoked when the input changes, so you always download the file generated from your current selection. If you want to confirm the final page count before and after removal, a quick pass through PDF Page Counter gives you the exact figure without modifying the document.
When Stripping Annotations Makes Sense
Removing page annotation arrays is useful in several recurring situations. Sending a final draft of a contract for signature where previous review comments should not appear in the recipient's copy. Disabling every URL on a printed handout so that a printed page does not produce clickable links when reopened on a screen. Clearing demo widgets from a sample form so that the structure can be re-tested with a clean slate. Removing a layer of markup notes that accumulated during collaboration but is no longer needed in the archived version.
In each case, the rule is the same: the visible artwork stays, the interactive layer goes. If your scenario instead calls for removing visible content along with interactivity, this is not the right tool. You would need to delete pages with Delete PDF Pages, crop the regions with Crop PDF, or use a redaction workflow for confidential text. Combining those tools with annotation removal is fine; using annotation removal alone for any of those jobs will leave the visible marks in place.
When to Flatten First, Remove Second
Sometimes the goal is to preserve the current appearance of form fields as page artwork while disabling their interactive presence. In that case, run Flatten PDF before running annotation removal. Flattening paints the current field appearance into the page content stream, so the form value survives even after the Annots entry is deleted. If you only need to disable interactivity and do not care about preserving field appearance for future edits, run the annotation tool alone.
If you are working on a Mac and want a platform-specific walkthrough of the same operation, see How to Remove PDF Annotations on Mac for the equivalent steps in macOS Preview and other native tools. The browser-based annotation tool covers every operating system with a modern browser and keeps the original file on your device throughout. For per-page insight into the links a document carries, run PDF Link Extractor first to get a downloadable report of every link annotation by page — that lets you confirm what you are about to strip before you commit.