Inspect the document
The browser reads visible document properties and reports what it can identify.
Rebuild the pages without the original metadata or text layer.
Clean
One file at a time, up to 25 MB and 40 pages.
No file scanned yet.
Context
The cleaned copy becomes image only Search, selectable text, links, forms, attachments, scripts, and digital signatures are not copied. Review every page before sharing the result.
A contract exported from an office suite can name the person who wrote it, the machine it came from, and the software version in use. None of that appears on the page, and all of it travels with the file.
Run the tool on the copy you intend to send. It renders every page, then writes a new PDF using only those pixels. The output keeps the visible pages while leaving the source document structure behind.
Metadata is not the only thing a document can leak. Hidden text, comment threads, and revision history are separate problems. A scan reports what it finds in the file structure; it cannot tell you whether a name is visible on page three.
The browser reads visible document properties and reports what it can identify.
Each page is rendered into fresh pixels, leaving the source metadata and active structures behind.
Open the downloaded image-only PDF and review every page before you share it.
No. The file is read by this page in your browser. There is no upload request, so the document never reaches the server.
Yes. The browser rebuilds a new image-only PDF, so the source metadata and active document structures are not copied. The new file identifies the browser tool as its producer.
No document script is executed. PDF.js renders page appearance with scripting disabled, and the output contains page images rather than the source actions.
A scan of a paper document has no author properties to leak, but the image inside it can still carry details. Use the image tools to strip metadata from a picture before you build a PDF around it.
You are offline. Changes will retry when the connection returns.