The PDF fields that out your author name

The Info dictionary: a business card you didn't mean to attach

Nearly every PDF carries an Info dictionary — a set of key-value fields written by whatever software created the file. The standard fields are Title, Author, Subject, Keywords, Creator (the application that authored the content), Producer (the software that generated the PDF), CreationDate, and ModDate. Many documents also carry an XMP metadata stream, an XML block duplicating and extending the same information.

Word processors typically fill Author from the account or licence name on the machine. That means a report exported from a personal laptop can carry a real name; one exported from a work machine can carry a corporate username. Documents shared 'anonymously' — complaints, tips, bids, drafts — are routinely de-anonymized by a right-click on Properties.

What each field can reveal

Individually small, together these fields profile the document's origin:

• Author / Creator: personal names, usernames, and organisation names
• Producer: exact software and version — which can date the document, identify the employer's toolchain, and occasionally flag conversion tools with known quirks
• CreationDate / ModDate: when the document was really made versus when it claims to be — including timezone offsets that hint at location
• Title: often the original filename or draft title ('layoffs_v3_FINAL') even when the visible first page says something neutral
• Keywords / Subject: workflow tags and internal categorization

What metadata cleaning does not fix

Clearing the Info dictionary and XMP stream removes document-level identity. It does not touch content-level information: visible text, headers and footers with names, comments and annotations, form field values, or attachments. A PDF whose third page contains 'Prepared by Jane Doe' needs editing or redaction, not metadata cleaning. Treat the two as separate passes: content first, metadata last.

It's also worth knowing that assembling documents can carry metadata forward in surprising ways — which is why tools that build new PDFs should write fresh, empty metadata rather than inheriting a source file's fields.

How to do this locally

Our PDF Metadata tool parses the Info dictionary in your browser and shows every field with its value — the document itself never uploads, which matters when the document is exactly the sensitive thing. Exporting a cleaned copy writes a fresh document with identity fields emptied and timestamps normalized, then reopens its own output and reads every field back; verification passes only when the fields are actually gone, and a failed check blocks the download rather than being labelled clean.

If you're combining documents first, our Merge PDF tool builds its output as a fresh document that doesn't inherit source metadata — run the metadata check on the merged result as your final pass before sharing.