Back to blog
pdf8 min read

PDF Metadata Fields Explained: Title, Author, Creator, Producer, and Dates

Learn what PDF metadata fields such as title, author, creator, producer, keywords, and dates can reveal before you send or publish a PDF.

By Metadata Remover Editorial TeamReviewed by Metadata Remover Product TeamPublished May 9, 2026

Guides are written by the team building Metadata Remover's browser-based metadata inspection and cleaning tools.

Quick answer

PDF metadata is hidden document information such as title, author, subject, keywords, creator, producer, creation date, and modification date. These fields are separate from the visible pages, so a clean-looking PDF can still reveal who made it, which software exported it, when it changed, or how it was classified.

Metadata risk by file type

File typeCommon metadataPrivacy riskCleaner
TitleHidden document title, internal draft name, project name, or exported page titleCan reveal a client, deal name, legal matter, private draft label, or subject that is not visible in the filename.PDF metadata remover
AuthorPerson name, account profile, organization identity, or app profileCan expose the real creator, employee account, contractor name, or source organization behind the PDF.PDF metadata remover
Subject and keywordsDocument topic, search tags, internal taxonomy, client labels, category termsCan disclose classification notes, internal wording, campaign names, confidential topics, or project context.PDF metadata remover
Creator and producerOriginal application, export workflow, PDF library, conversion tool, production softwareCan fingerprint your toolchain, automation setup, document source, or conversion process.PDF metadata remover
Created and modified datesCreation timestamp, modification timestamp, export date, revision timingCan reveal when work happened, whether a file changed recently, or how a document moved through a workflow.PDF metadata remover

What PDF metadata is

PDF metadata is document information stored outside the visible page content. It helps PDF readers, search tools, document systems, and operating systems describe the file, but it can also preserve context that the sender did not mean to share.

The important privacy detail is separation. Changing a filename does not necessarily change the PDF title. Removing text from a page does not necessarily remove the author field. Exporting from another app can also add creator, producer, and date fields of its own.

  • Document info fields can include title, author, subject, keywords, creator, producer, creation date, and modification date.
  • Some PDFs may also contain XMP metadata or app-specific fields depending on the export path.
  • A recipient may be able to inspect PDF properties even when the visible pages look finished and polished.

Title, subject, and keywords

The title field is often confused with the filename, but they are not the same thing. A PDF named final-report.pdf can still have a hidden title such as an old draft name, client name, internal project label, or copied browser page title.

Subject and keyword fields are meant to describe and classify the document. That makes them useful inside a team, but risky when a PDF leaves that team. They can reveal internal taxonomy, campaign wording, matter names, customer labels, or private search terms.

  • Check title when a PDF was exported from Word, PowerPoint, Google Docs, a design app, or a browser.
  • Check subject and keywords before publishing reports, decks, invoices, legal drafts, resumes, or client files.
  • Do not assume a renamed PDF has clean document properties.

Author metadata

The author field can store a person, account, organization, device profile, or application identity associated with the PDF. In a casual file this may not matter. In a public, professional, legal, recruiting, or client delivery workflow, it can identify someone who should not be attached to the shared copy.

Author metadata is especially easy to miss because it may come from the source document rather than the final PDF export step. A proposal exported by one person can still carry another editor's name if the original document properties were never cleaned.

  • A resume can expose a template author or previous editor.
  • A proposal can reveal a staff account, contractor, or internal author.
  • A public PDF can carry a personal name even when the visible byline is a company or brand.

Creator vs producer

Creator and producer sound similar, but they usually describe different parts of the PDF workflow. Creator often points to the original application or document workflow that made the source content. Producer often points to the software library, print driver, converter, or export engine that wrote the PDF file.

These fields are not always sensitive, but they can disclose more than expected. A producer value can reveal a specific conversion service, automation library, desktop app, or server-side pipeline. A creator value can show whether a PDF came from a word processor, browser, design tool, scanner, or internal system.

  • Creator can reveal the source application or workflow.
  • Producer can reveal the PDF writer, conversion library, or export engine.
  • Together, they can fingerprint how the PDF was generated.

Created and modified dates

PDF date fields can store when a document was created, exported, or last modified. Date metadata can be harmless for public brochures, but sensitive for contracts, client work, legal drafts, press material, research notes, invoices, or files tied to private timelines.

Dates are also easy to misread. A file system modified date can differ from the PDF's internal modification date. A PDF exported today may still carry a source document date from earlier in the workflow, and a cleaned copy may have new internal dates depending on the tool that rewrites it.

  • Creation date can reveal when the PDF or source workflow began.
  • Modification date can reveal recent edits or revision timing.
  • Export and file system dates are related signals, but they are not always the same.

How to check and remove PDF metadata

Before sending an important PDF, inspect its document properties and create a cleaned copy. Metadata Remover checks common PDF document info fields locally in the browser, shows what it found, clears supported title, author, subject, keywords, creator, and producer fields, and cleans supported date metadata in the downloaded copy.

This browser workflow is useful when you want a focused PDF metadata check without uploading the file for server-side processing. It is also a good final step after exporting from Word, PowerPoint, a design tool, a scanner app, or a browser print-to-PDF workflow.

  • Open the PDF metadata remover.
  • Select a PDF from your device.
  • Review title, author, subject, keywords, creator, producer, and date fields.
  • Clean supported metadata locally in the browser.
  • Download and share the cleaned PDF copy instead of the original.

What PDF metadata removal does not protect

PDF metadata removal is not the same as redaction. It does not remove visible text, page images, annotations, form field content, comments, attachments, layers, hidden page objects, or information that someone can see by opening the file.

It also does not guarantee forensic sanitization. Signed PDFs may lose signature validity when rewritten, encrypted PDFs may not be readable by a browser tool, and complex PDFs can contain structures that need specialist review. For sensitive legal, compliance, or high-risk publishing workflows, use metadata cleanup as one step in a broader review process.

  • Redact visible sensitive content before cleaning metadata.
  • Review annotations, comments, form fields, attachments, and page layers separately.
  • Keep the original private and send a cleaned copy.
  • Do not treat metadata removal as a guarantee that a PDF is safe in every forensic context.

PDF sharing checklist

The safest order is content review first, metadata cleanup last. That way you do not clean a PDF and then accidentally add new metadata by editing, exporting, or recompressing it again.

Use this checklist when a PDF is going to a client, court, recruiter, marketplace, public folder, press list, vendor, customer, or external partner.

  • Review visible pages for names, account numbers, addresses, signatures, and private text.
  • Check comments, annotations, form fields, attachments, and redactions.
  • Inspect title, author, subject, keywords, creator, producer, and date fields.
  • Remove supported PDF metadata in the browser.
  • Download the cleaned copy and share that file, not the working original.

Frequently asked questions

What metadata can a PDF contain?

A PDF can contain hidden document properties such as title, author, subject, keywords, creator, producer, creation date, and modification date. Some PDFs can also include XMP or application-specific metadata depending on how they were created.

Is the PDF title the same as the filename?

No. The filename is what you see in the file system. The PDF title is a separate hidden document property, so renaming a PDF does not necessarily remove or change the internal title field.

What is the difference between PDF creator and producer?

Creator usually describes the application or workflow that made the source document. Producer usually describes the PDF writer, converter, library, or export engine that generated the PDF file.

Does removing PDF metadata redact the PDF?

No. Removing PDF metadata clears supported hidden document properties. It does not remove visible text, images, annotations, comments, form fields, attachments, layers, or redacted-looking content.

Are PDFs uploaded when I use Metadata Remover?

No. Supported PDF inspection and metadata removal run locally in your browser. The cleaned PDF copy is generated on your device before download.