Your PDF carries more than its pages show

Where it hides

Three kinds of cargo ride in PDFs. Editing residue: author and company fields, the name of the tool that produced the file, earlier versions appended to the file’s tail, page thumbnails from before an edit, leftover objects nothing points at any more. Active content: JavaScript wired to run when the file opens, launch actions, whole other files embedded as attachments. And page content that paints nothing: text under a fill, off the page edge, white on white, or set to an invisible render mode — present in the file, absent from the view.

Before you send — and after you receive

The sending problem is the familiar one: a document leaves your hands carrying a name, a draft history, or a filled form value you never meant to share. The receiving problem gets less attention: a file someone sent you can carry scripts and attachments you can’t see on any page. Both call for the same first move — look inside before trusting what the pages show. For a whole folder of files at once, Verify reads a stack and reports each file’s findings, worst first.

Look first, then decide what goes

Nothing here is removed on a guess. The tool above inspects your file and shows every class of hidden data it found, each with a checkbox; you choose, the file is rebuilt without what you chose, and the output is re-inspected before it’s handed back. What can’t be removed safely says so, with the reason. The honest limit is stated up front, too: the result is “these classes, verified gone” — never a certificate that nothing else exists, because a PDF is open-ended and a fixed set of checks cannot promise absence.

Why no upload matters here in particular

A file you are cleaning is, by definition, a file with something in it you don’t want shared. The inspection and the rebuild run in your browser, on your own device — there is no server on the other end, so there is nowhere for the file, or for what it carries, to have gone.

Questions people actually ask

How do I see the hidden data in a PDF?

Drop the file on this page. It is inspected on your device and every class of hidden data found — metadata, attachments, scripts, hidden layers, form values, invisible text, and more — is listed with what it is and how much of it there is, before anything is touched.

Can I remove the author name from a PDF?

Yes — document identity fields like author, title and producing software are one of the classes the inspection surfaces, and clearing them is a checkbox. The rebuilt file is re-inspected afterwards so “removed” is a verified result.

Can hidden data be removed without uploading the file?

Yes — that is how this page works. The inspection and the rebuild are JavaScript running in your own browser tab; the file never travels. For a document being cleaned because it is sensitive, that matters more than convenience.

Is a PDF someone sent me safe to open?

A PDF can carry scripts set to run on open, launch actions, and embedded files — presence you can check here before trusting the document. The inspection reports what is in the file; it does not run any of it.

If nothing is found, is the file completely clean?

It means nothing was found in the classes checked — presence, not absence. A PDF is an open-ended container, so no fixed set of checks can honestly certify that nothing else exists. You get the finding list, stated exactly that carefully.