PDF metadata is the document information stored inside every PDF — separate from the visible pages but reachable through any viewer's Properties dialog — and it includes eight standardized fields: Title, Author, Subject, Keywords, Creator, Producer, CreationDate, and ModDate. Editing PDF metadata means reading those entries, changing the values you want to update, and saving a new PDF copy with the new information attached. The page artwork, text, and layout stay exactly the same; only the hidden document information dictionary changes. The operation leaves the original file untouched on the device and produces a separate copy that can be reviewed before sharing. Because the Info dictionary sits in a fixed location of the PDF specification, the read/write process is predictable across operating systems and reader apps.
PDF metadata is not the same thing as the visible filename, the words printed on the page, or the file's location in your file system. The dictionary is read by PDF software and indexed by document management systems, while users typically see only a subset of those fields through Properties panels. Keeping these distinctions in mind is what makes metadata edits both useful and predictable.
Inside the PDF: How Metadata Is Structured
Every PDF carries two parallel descriptions of itself. The visible description is the page artwork — text, images, charts, and headings laid out across a sequence of pages. The hidden description sits in a separate part of the file called the document information dictionary, often shortened to the Info dictionary. This dictionary stores key-value pairs that any PDF reader knows how to interpret: Title, Author, Subject, Keywords, Creator, Producer, CreationDate, and ModDate. A second, XML-based description called XMP metadata sometimes appears alongside it, but the Info dictionary is the most widely supported layer and the one standard viewers expose in their Properties dialog.
Because the Info dictionary is stored separately from the page content stream, editing it does not redraw any artwork, repaginate the document, or alter images. The original PDF remains valid and openable; only the descriptive entries change. That separation is also why metadata edits are safe to try — any change can be inspected before the file is shared.
The Standard Fields and What Each One Stores
The eight common entries each carry a different kind of information. The table below summarizes what each one records and where the value usually comes from in a freshly exported document.
| Field | What it stores | Typical source |
|---|---|---|
| Title | Document title shown in viewer headers, browser tabs, and search results. | Often blank or copy-pasted during export. |
| Author | Original creator's name as listed in Properties. | Application user or export settings. |
| Subject | Short summary or topic line for the document. | Often blank. |
| Keywords | Comma-separated tags for search and categorization. | Often blank; used by archival systems. |
| Creator | Application that authored the document content. | Word, InDesign, Pages, or similar. |
| Producer | PDF conversion library used to finalize the file. | pdf-lib, Acrobat Distiller, Skia/PDF. |
| CreationDate | Calendar date of original creation. | Export time. |
| ModDate | Last modification date. | Re-save time. |
Looking at the table, the first four entries are user-facing — they describe what the document is about. The next two describe the toolchain that produced it. The last two are time stamps. A routine metadata edit usually touches only one or two of these columns; the rest stay at whatever the original export recorded.
Editing PDF Metadata in Three Steps
The full read/write flow is a single browser session. The PDF Metadata Editor loads the PDF locally, reads its Info dictionary, and writes back a separate copy whose only difference from the source is the entries you changed.
- Choose a PDF file from your device. The file picker loads the PDF inside the browser. The tool reads common entries from the Info dictionary without uploading the file to a server. The detected values appear in the editor for Title, Author, Subject, Keywords, Creator, Producer, CreationDate, and ModDate. Read through each one before deciding what to change.
- Edit the entries you want to change. Type new text into Title, Author, Subject, Keywords, Creator, or Producer to replace the current value. Leave a box empty on purpose to write an empty value for that text field into the saved copy. Dates must be entered in YYYY-MM-DD format and the editor checks the actual calendar date, including leap years, before saving. A blank date is treated as leave unchanged, since standard PDF date removal is not a dependable public operation in this local workflow.
- Save the metadata and verify the download. Click save to produce a separately named PDF copy on your device. The original file is not overwritten. Open the downloaded copy in your preferred viewer and check the Properties or Document Information panel to confirm the new entries. This verification step matters because some viewers display only a subset of fields.
Where Metadata Appears Across Viewers and Archives
Different programs show different slices of metadata. A desktop PDF viewer usually displays Title, Author, Subject, Keywords, Creator, Producer, and both date fields in its Properties dialog. Some viewers prioritize Title over the filename when labeling open tabs, while a file browser only ever shows the operating-system filename. Search systems inside larger organizations often index Title and Keywords for fast retrieval. Document management platforms tend to focus on Author and CreationDate for sorting and audit trails.
There is no single rule about which fields matter most — the right viewer or system is always the one that matches the workflow. Because of this, the recommended last step after saving is to open the downloaded PDF in the exact reader or archive destination that matters, then confirm the values there. A field that looks correct in Adobe Reader may not appear at all in a lightweight viewer, and an archive system may read Keywords while ignoring Producer entirely.
Limits and Cautions When Editing Metadata
The editor's scope is intentionally narrow. It updates the standard document information and leaves the page content stream, form fields, bookmarks, links, annotations, attachments, and passwords alone. Saving a metadata change does not redraw a cover page, change a heading, add a watermark, alter the filename, or remove hidden content. PDF metadata is descriptive information, not visible text on a page.
Three practical cautions often come up in real workflows.
Text entries clear on purpose. If a Title, Author, Subject, Keywords, Creator, or Producer box is empty when the file is saved, the downloaded copy receives an empty value for that field. This is helpful for removing legacy bylines or anonymizing a publication record. Keywords are entered as a comma-separated value and are preserved in the saved document-information entry.
Dates are handled differently from text. A blank date preserves the source date rather than removing it, because public date removal is not dependable for every viewer. Review any date change before saving — recipients that rely on document timestamps for legal filings, regulatory submissions, or archival logs will see exactly what was typed. If the recipient system only renders a subset of fields, choose the date carefully.
Existing digital signatures can break. Editing metadata rewrites bytes inside the PDF, which means a hash-based signature tied to the original file content no longer matches even though the visible page artwork looks unchanged. Keep the original signed file and use a signature-aware workflow whenever signature validity matters. The editor never touches the signature itself; it only changes the Info dictionary around it.
The editor also rejects protected or unreadable files safely. A password-locked PDF will not load, and a damaged file is not repaired. Starting with a known-good, unprotected PDF is the safest workflow.
Practical Reasons to Update Each Field
People edit metadata for very different reasons, and the field they touch usually reveals the goal.
Title. A clearer title improves how the document shows up in browser tabs, downloads folders, and search results. Internal reports often arrive with a generic "Document1" or with a long system path captured during export. Replacing the Title entry makes the file recognizable at a glance without changing the filename. For readers focused on title edits specifically, the how-to guide for editing a PDF title in your browser covers the same operation with extra detail.
Author. Correcting a byline before delivery is one of the most common edits. Many authoring tools record the operating system login, a temporary username, or a shared team account. Setting Author to a real person or a department name keeps the record consistent across a set of files.
Subject. A one-line description acts as an internal summary that appears in Properties panels. It helps reviewers and archive indexes when many files are open at once.
Keywords. Comma-separated tags drive search inside document management systems. A consistent vocabulary across reports (for example, "2026, Q2, audit, finance") makes those reports easy to find later.
Creator and Producer. Setting a predictable Creator and Producer convention — for example, the team or pipeline that produced the file — helps internal analytics and lets teams audit which toolchain generated which document. The metadata edit writes a value that survives subsequent openings of the file in any standard reader.
CreationDate and ModDate. These dates are useful when an archival system relies on timestamps for sorting or retention rules. Errors in these dates (a clock set to the wrong year, an unchanged export timestamp, or a clock-skew on a virtual machine) often need correction, and the editor validates the calendar date before saving.
The full tool reads all eight fields at once and writes only the ones changed. The PDF Metadata Editor runs entirely in the browser — the file stays on the device until the download step. Behind the scenes, the operation uses the pdf-lib PDFDocument API to load the file, edit the Info dictionary, and write a separate local copy.