All tools
Archival cleanup
PROSanitize a PDF for long-term storage by flattening annotations, stripping JavaScript, and rewriting the file's internal structure so it stays clean and portable. This is honest cleanup, not strict PDF/A.
Files stay local
Pro tool. Try it once free (the output gets a watermark), or get every tool for $19. Get Pro for $19
Drop PDF files here
or click to browse
Archival cleanup prepares a PDF to sit in storage for years without surprises. It bakes annotations into the page, removes any JavaScript so the file can't run code, and rewrites the internal object structure so the result is tidier and more self-contained. Reach for it before you hand a document to a records system, attach it to a legal file, or back it up somewhere you won't open it again for a long time. Everything runs in your browser, so the file never leaves your device.
How to use Archival cleanup
- 1Drop your PDF into the upload area or pick it from your files.
- 2Run the cleanup. The tool flattens annotations, removes JavaScript, and normalizes the structure.
- 3Compare the result against the original if you want to confirm the look is unchanged.
- 4Download the cleaned PDF for your archive.
Why use Archival cleanup
- Removes embedded JavaScript, so the stored file can't execute code when someone opens it later.
- Flattens annotations into the page content, so comments and stamps stay put instead of relying on a viewer that supports them.
- Rewrites the internal object structure for a cleaner, more portable file that's less likely to confuse old or strict readers.
Common uses for Archival cleanup
- You're filing a signed contract or invoice into a records system and want it stripped of active scripts and loose annotations first.
- You're backing up documents you won't touch for years and want them as self-contained and tidy as you can get without a server tool.
- Someone sent you a PDF with sticky notes and a JavaScript form, and you want a flat, inert copy to keep on file.
Frequently Asked Questions
Is this a real PDF/A converter?
No. Valid PDF/A needs a bundled ICC color profile plus OutputIntent and XMP metadata, which we can't write reliably from the browser. This tool sanitizes a PDF for storage by flattening annotations, removing JavaScript, and normalizing the structure. It's useful, but not strict PDF/A. For verified output, use a server tool like veraPDF or Acrobat.
What does the tool actually do?
It bakes annotations into the page content, removes JavaScript so the document can't run code, and rewrites the file's object streams so the structure is cleaner and more portable. The output is still a regular PDF. Fonts aren't re-subset, so the archived copy relies on whatever fonts were already embedded.
Why not produce real PDF/A?
PDF/A requires an embedded ICC color profile, an OutputIntent dictionary, and XMP metadata that declares the conformance level. Doing all of that locally in a browser without bundling a color profile is hard to get right. We chose honest sanitization over fake compliance.
Will the visual appearance change?
It should look the same. The changes are all under the hood to keep the file self-contained. Flattening moves annotations into the page itself, so they show up identically without depending on the viewer.
Does my file get uploaded anywhere?
No. The cleanup runs entirely in your browser, so the PDF never leaves your device. That's a good fit for archival work, since the documents you store long-term are often the ones you most want to keep private.
What happens to form fields and JavaScript in the document?
JavaScript is removed, so the file can't execute code when opened later. Interactive behavior tied to that script will stop working. If you need the document to stay fillable, keep your original; the cleaned copy is meant to be an inert archive.
Why does file size sometimes change after cleanup?
Rewriting the internal object structure can shrink or slightly grow the file depending on how the original was built. The goal is a cleaner layout, not the smallest size. If you want a smaller file, run a compression tool instead.
Can I trust the cleaned file to open in old or strict PDF readers?
Normalizing the structure helps, since a tidy file is less likely to trip up older or stricter viewers. It isn't a guarantee, and it isn't certified compliance. For a hard requirement, validate the result with a tool like veraPDF.