PDF Metadata Editor Online Free
Open any PDF to read its Info dictionary (Title, Author, Subject, Keywords, Creator, Producer), edit the fields you need and download a rewritten document with the new metadata baked in. Ideal for fixing blank titles before upload, scrubbing author names for anonymity, or correcting keywords for archival systems — all inside the browser with pdf-lib.
PDF Metadata Editor In-Browser Workspace
Input data or select files to begin. 100% private, client-side execution with zero server transmission.
How to Use PDF Metadata Editor
- Step 1: Drop a PDF onto the dropzone; the tool loads it into memory and parses document info fields.
- Step 2: Edit Title, Author, Subject, Keywords (comma-separated), Creator or Producer in the form.
- Step 3: Compare against original values — reverted fields show a revert link when dirty.
- Step 4: Click Save & Download PDF to write the Info dictionary and trigger a download of edited-metadata.pdf.
- Step 5: Use Change File to load another document, or Reset All to restore the original field values.
About PDF Metadata Editor
PDF document metadata lives primarily in the Info dictionary referenced from the trailer, with keys /Title, /Author, /Subject, /Keywords, /Creator and /Producer as text strings (often PDFDocEncoding or UTF-16BE with BOM). Metadata can also exist as XMP packets in an XML metadata stream; this tool updates the classic Info dictionary, which most viewers read first. The workflow uses lazy-loaded pdf-lib: load() parses the cross-reference table and object graph, setTitle/setAuthor/setSubject/setKeywords/setCreator/setProducer mutate the info map (keywords accept a string array), and save() rewrites the file structure with a new xref. Password-protected files fail fast with a clear error because decryption keys are unavailable. Dates such as ModificationDate are refreshed on save to reflect the edit time. Because loading happens in RAM, original bytes never leave the machine — download produces a local blob. Limits: encrypted PDFs, severely broken xrefs and portfolios with custom schemas may not round-trip perfectly; embedded XMP is left untouched so dual metadata sources can disagree until an XMP-aware editor is used.
Frequently Asked Questions
Is the PDF uploaded anywhere?
No. Parsing and rewriting use pdf-lib entirely in browser memory; the edited file downloads directly from a local blob.
Can I remove password protection first?
No — encrypted PDFs cannot be opened without the password. Decrypt with a tool you trust, then edit metadata here.
Does this change the visible pages or text?
No. Only Info dictionary strings (and modification date) change; page content streams and fonts stay as they were.
Why do some readers still show old metadata?
A few apps cache properties, and XMP packets can override Info. Open the downloaded file fresh or clear the viewer cache.
Is there a file size limit?
The dropzone defaults to 50 MB; very large files depend on available browser memory since the PDF is held in RAM.