About Edit PDF metadata
Edit PDF metadata rewrites the six descriptive fields in a PDF's Info dictionary: title, author, subject, keywords, producer and creator. The current values are read the moment you drop the file in — with pdf-lib's own load-time rewriting switched off, so what you see is genuinely what is in your file — and a before-and-after diff shows only the fields you changed. Use it to put a real title on a document still called Microsoft Word - draft3.docx, to remove a colleague's name before sending a file outward, to tag an archive so desktop search finds it, or to fix a producer string a converter got wrong. Also searched as change PDF author, edit PDF properties or remove PDF metadata.
Edit PDF metadata specs
| Price | Free ($0) — no paid tier |
|---|---|
| Account | Not required |
| Watermark | None |
| Where it runs | In your browser, on your device |
| File upload | No file is uploaded |
| Input | PDF (1 file) |
| Output | |
| File size limit | Limited only by your device's memory |
| Works offline after the page loads | Yes |
How to use Edit PDF metadata
Load the PDF
Drop one file on the upload area. The six fields fill immediately with whatever the document already contains, and any field the document leaves empty stays blank.
Edit the fields you care about
Title, Author, Subject, Keywords (comma-separated), Producer and Creator are all free text. The keywords placeholder shows the expected shape: invoice, 2026, finance.
Check the diff
The What will change pane lists only the fields you touched, old value on the left and new on the right, marking a missing value as empty. Restore original puts everything back.
Download with new metadata
Press Download with new metadata to save a copy with a -metadata suffix. Every field is written, including the ones you cleared, which go out as empty strings.
Frequently asked questions about Edit PDF metadata
Which fields can I edit, and where do they show up?
Six fields are editable: Title, Author, Subject, Keywords, Producer and Creator. They live in the PDF's Info dictionary, and every desktop reader surfaces them somewhere — Acrobat under File, Properties, Description; macOS Preview under Tools, Show Inspector; Windows Explorer in the Details tab of a file's properties. Title has the widest reach: many viewers show it in the window or tab bar instead of the file name, cloud previews use it as a heading, and search engines will use it when a PDF is indexed on a public site. Producer and Creator are the software fingerprints — Creator names the program that authored the original, Producer the one that wrote out the PDF.
If I clear a field, is the old value really gone from the file?
Clearing a field writes an empty string in its place, and the download is a complete rewrite rather than an appended revision, so the old Info value is not carried along inside it. That distinction matters: PDFs can be saved incrementally, tacking changes onto the end while the previous version survives further up the file, and a document edited that way can still be mined for its earlier values. This tool does not save incrementally. What it cannot promise is that the same string appears nowhere else in the document — inside an XMP packet, an annotation's author entry or the visible page text — which is the subject of the next answer.
What can this tool not remove?
Edit PDF metadata touches the Info dictionary and nothing else, so several other carriers of identifying data survive untouched. XMP metadata, a separate XML packet many producers embed alongside the Info dictionary, is left exactly as it was, which is why an XMP-aware reader may still display an old author name. Annotation and comment author names, embedded file attachments, EXIF data inside embedded photographs, form field values and the visible text of the pages themselves are all outside this tool's scope. The document's File ID is regenerated on save, but other producer fingerprints inside object streams are not touched. Where hidden data genuinely matters, use Redact PDF in Wipe mode, which rebuilds the file and leaves those structures behind on purpose.
Why can't I change the creation and modification dates?
The creation and modification dates are deliberately preserved rather than exposed, so the tool does not turn into a convenient way to backdate a document. The PDF is loaded with pdf-lib's automatic metadata updating switched off, which stops the library stamping its own producer string and a fresh modification date over the originals simply because the file was opened — that would have made the mutated values appear as the before side of the diff and then be written straight back out. The result is that the dates you had going in are the dates you have coming out. To see what a file currently records, dates included, open it in PDF info viewer.
Why does my PDF fail to load here?
Encryption is the usual reason a PDF will not load in Edit PDF metadata. The tool has to parse and rewrite the document, and it will not do that through a security handler, so a password-protected file simply reports that it could not be read. Unlock it with Remove PDF password first, edit the fields, and re-protect it with Add password to PDF afterwards if you still want it encrypted — the encryption step has to come last, since rewriting metadata requires an unencrypted file. The other cause is genuine damage: a truncated download, or a file that is not really a PDF despite its extension, fails the same way, and there is no reliable browser-only repair for that. In both cases the tool says the file could not be read rather than writing out a document it never parsed properly.
Is it free, and is my document uploaded to read its metadata?
Edit PDF metadata is free, unlimited and watermark-free, and nothing is uploaded to read or write the fields. Parsing and rewriting both happen in your browser with pdf-lib, so the document — and whatever its metadata says about who wrote it and when — stays on your machine. That is the point for this tool in particular: sending a file to a server in order to strip an author name from it would defeat the exercise. The saved copy is a standard PDF with no added branding, and your original stays untouched on disk while the result is written alongside it with a -metadata suffix. Nothing you type into the six fields is recorded anywhere either, so a title you tried and discarded leaves no trace.
Why in-browser processing matters
Every PDFChamp tool runs inside this page: the file you choose is read by JavaScript in your own browser and is never sent to a server, so nothing is uploaded, queued, or stored anywhere. That removes the upload wait, the processing queue, and the question of what happens to your file afterwards — the about page compares this architecture with server-side PDF tools.
Last updated