You can edit or remove PDF metadata in the browser: the file is opened locally, the title, author, subject, keywords, creator and producer values are read into a form, you change or clear them, and a new copy is saved as a download. Nothing is uploaded.
Metadata is the block of document properties that travels invisibly with a PDF. It usually names the person or team who wrote the file, the software that produced it, the original document title, and any keywords the author typed in. Readers and search engines can both read it, and so can anyone you send the file to. This page covers what each field reveals, why that matters when a file leaves your desk, and the honest limits of what a browser tool can clear: it rewrites the document information dictionary, but an XMP packet and custom keys are not guaranteed to go.
A PDF looks like a finished document, but behind its pages it carries a small set of properties that describe the file itself. Most people never open that panel, and most programs that save a PDF fill it in without asking. The result is that files sent to clients, uploaded to job portals and posted on public sites routinely name the person who wrote them and the software that made them.
PDF Metadata
Read and rewrite the title, author, subject, keywords, creator and producer inside a PDF, or clear all six in one click. The file is parsed and rebuilt in your browser, so it never leaves your device.
What PDF metadata is and where it hides
Metadata is stored in the PDF's document information dictionary, a short block of text that sits alongside the pages rather than inside them. It exists so that readers, file managers and document management systems can identify a file without rendering it first. In most PDFs the values are stored as readable text, which means anything that parses the file can read them. That includes the person you send it to, their document portal, and a search engine that indexes the file.
The six fields this tool reads and writes
This tool works on the six standard entries of that dictionary. The current values are shown before you change anything, so you can see exactly what is already in the file rather than guessing.
| Field | What it usually holds | Why it matters |
|---|---|---|
| Title | The document name a reader shows in its window and tab | Exported files often keep a working name such as Document1 or final_v3 |
| Author | The person or account credited with the document | Often the template author, not the person sending the file |
| Subject | A short description of the contents | Can restate a confidential matter or project name |
| Keywords | A comma separated tag list | May carry a client name, a case number or an internal code |
| Creator | The application that wrote the original document | Names the software and sometimes its version |
| Producer | The library or driver that generated the PDF | Can reveal a scanner model or an internal build string |
Where those values come from
Most people never type any of this in. An office suite writes its own name into Creator and the signed-in account name into Author. A scanner writes its brand and model into Producer. An export to PDF stamps Title with the name of the file you saved. That is why two documents that look identical can carry completely different trails, and why a file with no visible byline can still name its author.
How to edit or remove PDF metadata
The whole job takes three steps and no account. The file is read and rebuilt inside the browser tab, so it is never uploaded.
- Add the PDF. Drop one file into the tool or click to browse. The page count and all six current properties are read on your device and listed in the Result panel.
- Change or clear the values. Type new text into Title, Author, Subject, Keywords, Creator or Producer. To remove everything at once, click Strip all metadata, which empties all six fields.
- Save and download. Click Save metadata. The tool writes the new values, rebuilds the file and downloads it as a copy named after your original with -metadata added.
Your original file is never modified. Only the downloaded copy carries the new values, so you can open both files and compare their properties side by side.
Why PDF metadata is a privacy problem
A PDF's properties are a trail that follows the file, and it is rarely the trail you would choose to leave.
It names people who did not expect to be named
Templates get shared, so the Author field often holds the name of whoever built the template rather than the person sending the file today. A former colleague, an old account, a contractor who has since left: the name travels with the document and is invisible on the page. Creator and Producer add a second layer by naming the specific application or scanner that produced it.
It can expose an internal file name or a working title
Title is often copied from the name of the exported file, which may be an internal reference rather than a public one. A draft named after a client still in negotiation, a matter number, or a working title you would never use in public can sit in that field and be read by anyone who opens the properties dialog.
It survives when the page looks clean
This is what makes metadata worth thinking about. A PDF can look fully anonymised, with no logo and no byline, and still name its author in the document properties. Some portals and search tools index those properties, so a field you never noticed can surface in a listing next to a title you did not write.
What this tool can and cannot clear
A clear statement of the limits is more useful than a promise of a total wipe. This tool rewrites one specific part of a PDF and leaves the rest untouched.
| What you want to remove | Does this tool do it | What to do instead |
|---|---|---|
| Title, Author, Subject, Keywords, Creator, Producer | Yes, it reads and rewrites all six | Nothing else needed |
| An XMP metadata packet | Not reliably | Treat the file as still carrying it |
| Custom keys and private application data | No | Not covered by this tool |
| Page content, stamps, letterheads, signatures | No, and it should not | Edit or redact the pages separately |
| The password on an encrypted file | No | Unlock the PDF first, then edit metadata |
Only the document information dictionary
The six fields live in the document information dictionary, and that dictionary is what the tool reads and writes. Values stored elsewhere in the file are out of scope. In practice you should treat the tool as a reliable fix for the standard properties, not as a universal metadata eraser.
XMP packets and custom keys are not guaranteed to go
Many scanners and Adobe products embed a second, richer block of metadata called an XMP packet, which is separate from the document information dictionary. Because this tool rewrites the dictionary rather than the entire file, an XMP packet is not guaranteed to be removed. The same applies to custom keys added by third-party software. If a file came from a scanner or a production pipeline, assume that some metadata remains even after you clear the six fields.
Encrypted files must be unlocked first
A password protected PDF cannot be parsed, so the tool reports that the file could not be opened and notes that it may be password protected or damaged. Remove the password with the Unlock PDF tool, then edit the unlocked copy here. If the file has to stay locked, do the metadata edit first and apply protection last.
Clearing properties is not deleting content
Strip all metadata empties the six fields and nothing else. Pages, text, images, links and bookmarks are copied through unchanged, which is why the output stays safe to print or sign. If a signature image, a letterhead or a footer with a name is visible on the page, clearing the properties does not remove it. Removing visible content is a different job, done on the pages themselves.
When to keep metadata instead of removing it
Removing metadata is not always the right move. A publishing workflow, a document management system and a records archive all rely on Title and Keywords to file and find files, and stripping them makes a document harder to manage. The same is true for signed records where Creator and Producer help establish provenance.
The sensible rule is to match the audience. For a file going to a client, a public portal or a job application, correct or clear the identifying fields. For a file going into your own archive, or one where the authoring details are part of the record, leave them in place. The tool lets you change one field instead of all six, so you can keep the useful values and remove only the sensitive ones.
Browser editing versus uploading a file
Most metadata editors are server applications: you upload the document, their machine rewrites it and you download the result. That works, but for the exact files people most want to clean, contracts, applications, medical records and ID scans, handing the original to a third party is the risk you were trying to reduce.
| Approach | Where the file goes | What you give up |
|---|---|---|
| Aihangsoft PDF Metadata | Stays on your device | Nothing. No account, no upload, no watermark |
| A typical server editor | Uploaded to their servers | Retention and privacy policies you have to trust |
A local edit also means the file does not depend on a connection from the moment the page has loaded. You can clean a batch of documents on a train with no signal, and the originals on disk are never altered, so a run you are unsure about costs you nothing.