Every PDF carries an Info dictionary at the document root that stores Title, Author, Subject, Keywords, Creator (the source application like Word or InDesign), Producer (the library that wrote the file, e.g., Adobe PDF Library, pdf-lib, ReportLab), CreationDate, and ModDate. Modern PDFs may additionally carry an XMP metadata stream — an XML packet with the same fields plus extensions for Dublin Core, IPTC, and tool-specific data. Both are invisible in the main view but exposed by every PDF reader's Properties dialog and by command-line tools like pdfinfo.
PDF Metadata reads and rewrites the document Info dictionary using pdf-lib, in the page itself, never on a server. The fields are surfaced in a form, edits are written back into the dictionary, and the file is re-serialized — page content, fonts, vector graphics, and images are not touched. Whatever you type into the Producer and Creator fields is written verbatim, so you stay in control of those values. Note that the separate XMP metadata stream some PDFs carry is preserved as-is and is not edited here — if a file was authored in Office, InDesign, or Acrobat, identifying data in its XMP packet will survive these edits.
Stripping metadata is a privacy hygiene step before publishing. Author fields often contain real names, Creator fields can leak internal tooling (e.g., "Confidential Internal Build"), and timestamps reveal when a document was prepared. The Clear All button blanks every field at once. To go further, the PDF Flatten tool can also remove embedded annotations and form data that may carry comments or filled-in personal information.
Conversely, accurate metadata makes PDFs findable. Document management systems (SharePoint, M-Files, Box) and search platforms (Google Scholar, internal Confluence search) rely on Title and Keywords for indexing. A PDF with no Title falls back to its filename, which is often unhelpful ("final-v3.pdf").
Dates are picked with a calendar-and-time control and written in the PDF's standard date format (D:YYYYMMDDHHmmSS) on save. Leaving CreationDate empty is allowed; some archival systems treat that as a flag that the document is metadata-cleansed.
There are limits: encrypted PDFs cannot be parsed by pdf-lib until they are unlocked, so password-protected files must be cleared with the PDF Password tool first. Existing digital signatures will be invalidated by any modification, including metadata edits — this is part of the PDF signing standard. And custom metadata schemas embedded in the XMP packet are preserved on read but not exposed for editing in this UI.
All processing is local. The file is loaded into a Blob in your tab's memory, parsed by pdf-lib, modified, and offered as a download. There is no upload endpoint behind this tool.