What Is PDF Metadata?

Every PDF you create, receive, or share carries an invisible passenger: metadata. This is structured information about the document rather than the visible content within it. It answers questions like: Who made this? When? With what software? Has it been edited since?

There are two primary metadata layers embedded inside modern PDF files:

  • DocInfo Dictionary — the original PDF 1.0-era standard. Stores basic key-value pairs like /Title, /Author, /Creator, /Producer, /CreationDate, and /ModDate.
  • XMP (Extensible Metadata Platform) — an Adobe-developed XML standard (introduced in PDF 1.4) that can store much richer, extensible metadata including copyright info, GPS data, edit history, camera settings, and custom namespace properties.

Both layers can coexist in the same file, sometimes with conflicting values — a common occurrence when PDFs are resaved through multiple tools.

/Title
The document title — used by search engines as a page title equivalent
/Author
The individual or organisation listed as the creator
/Subject
A summary or category description of the document
/Keywords
Comma-separated tags for search and classification
/Creator
The application that originally created the document (e.g., Microsoft Word)
/Producer
The PDF-generating software (e.g., Adobe PDF Library, macOS Quartz)
/CreationDate
Exact timestamp with timezone when the file was first created
/ModDate
Last modification date — updated each time the document is re-saved

Difference Between PDF Metadata and Document Properties

This is one of the most commonly confused distinctions in PDF handling. People use "metadata" and "document properties" interchangeably — but they are not the same thing.

Aspect Document Properties PDF Metadata
Definition The human-readable fields shown in your PDF viewer's File → Properties dialog The complete data layer — both DocInfo and XMP — embedded in the file structure
Visibility Visible in viewer Mostly hidden
Fields shown Title, Author, Subject, Keywords, Creator, Producer, dates All DocInfo fields + XMP namespaces (dc:, xmp:, pdf:, custom:)
Hidden data None — only displays what the viewer exposes Editing history, thumbnail previews, GPS coords, software serial data, embedded scripts
Editable in viewer? Yes (Acrobat Pro) Only partially
Cleared by "Clear" button Yes — visible fields No — XMP and thumbnail data usually survive
Risk level Low — intentionally authored data High — may contain unintentional or sensitive data
Key Takeaway Document properties are a subset of PDF metadata — the part intentionally exposed to users. Full metadata includes everything the application baked in during creation, much of which never surfaces in any dialog.

What lives in XMP that document properties don't show?

XMP metadata can contain a significantly broader scope of information than the DocInfo dictionary shows:

  • Revision/version history — lists of every time the document was edited, with author names and timestamps per revision
  • Embedded thumbnail — a base64-encoded JPEG preview of the first page, which can reveal document content even if the PDF itself is encrypted
  • Software identifiers — precise software name, version number, and sometimes licence serial number
  • Rights management data — copyright status, usage terms, licensing URL
  • GPS coordinates — from PDFs generated by mobile scanning apps that read device location
  • Custom enterprise properties — document classification labels, project codes, client reference IDs added by enterprise DMS systems

Can Metadata Track the PDF Owner or Creator?

Yes — and more precisely than most people realise. PDF metadata has been used in real investigations to identify whistleblowers, uncover anonymous authors, and attribute leaked documents.

Real-world risk: The NSA leak case (2017) Reality Winner's leaked NSA document was identified partly through printer tracking dots — but metadata in the PDF pointed directly to the printing user account and timestamp, narrowing suspects before forensic analysis even began.

Tracking vectors embedded in PDF metadata

  • Author field — auto-populated from the OS username or Microsoft Office registered user name at the time of creation
  • Creator field — reveals the precise application (e.g., Microsoft Word for Microsoft 365 MSO (Version 2401)), which can fingerprint the editing environment
  • CreationDate timezone offset — the timestamp includes a UTC offset (e.g., +05:30), which can geolocate the creator to a timezone
  • Revision author entries in XMP — every co-author who touched the document leaves a named entry in the revision history
  • GPS in scanned PDFs — mobile scanner apps like Adobe Scan or CamScanner embed device GPS coordinates by default
  • Enterprise classification tags — internal document numbers, project codes, and client names added automatically by document management systems
  • Embedded thumbnail — an image showing the document's first-page draft content, potentially revealing earlier confidential versions
Before sharing sensitive documents Always strip metadata from PDFs before distributing externally, especially for legal submissions, press releases, whistleblowing, academic anonymised submissions, or any file where authorship should remain private.

How Metadata Affects PDF SEO and Indexing

Google and other search engines actively crawl, index, and rank PDFs in their search results. Unlike HTML web pages where the <title> tag and meta description are your primary levers, PDFs rely on document metadata as the equivalent signal layer.

How Google reads PDF metadata

Google's crawler (Googlebot) parses the DocInfo dictionary of each PDF it indexes. The fields it uses most directly are:

  • /Title — This is the single most important metadata field for SEO. Google uses it as the clickable headline in search results, exactly like the HTML <title> tag. A missing or generic title (like "Untitled" or "Document1") forces Google to generate one from the body text, usually less effectively.
  • /Subject — Used as the meta description equivalent. A well-written Subject field improves the quality of the snippet shown under the search result title.
  • /Keywords — Has negligible direct ranking weight in modern search algorithms (analogous to HTML meta keywords since 2009), but can assist in correct document classification.
  • /Author — May appear in rich results for documents indexed with author attribution, improving click-through trust.
PDF Metadata Field HTML Equivalent SEO Impact
/Title <title> High — directly used as SERP headline
/Subject <meta name="description"> Medium — influences snippet text
/Keywords <meta name="keywords"> Low — largely ignored by modern search
/Author Schema.org author Low–Medium — E-E-A-T trust signal
/CreationDate <meta name="date"> Low — freshness signal

Best practices for PDF SEO metadata

  • Write a descriptive /Title that includes your primary keyword (e.g., "Annual Financial Report 2024 — Acme Corporation" rather than "Report Final v3")
  • Write a 120–160 character /Subject that summarises what the reader will learn — Google may use it as the search snippet
  • Set the /Author to your organisation name to reinforce brand attribution in search results
  • Make sure your filename also contains the keyword — Google uses the URL path (which includes the filename) as a secondary ranking signal
  • Do not leave the /Title blank or set it to a generic value — this is the most common PDF SEO mistake
Does removing metadata hurt PDF SEO? Only if you remove the /Title and /Subject fields. Stripping privacy-sensitive fields (Author, Creator, Producer, revision history) while keeping Title and Subject intact has no negative SEO impact. PDFMaster's Metadata Remover gives you full control over which fields to clear.

Does Removing Metadata Reduce PDF File Size?

This is a frequently asked question with a nuanced answer: yes, but the impact is usually modest. Understanding what actually contributes to metadata file size helps set realistic expectations.

What takes up space in PDF metadata?

  • DocInfo dictionary — typically 200–800 bytes for standard fields. Negligible.
  • XMP metadata packet — ranges from 1 KB to 8 KB for normal documents. Larger for PDFs with rich rights management or Adobe-specific namespaces.
  • Embedded thumbnail preview — a JPEG of the first page stored in the XMP stream. This is the biggest metadata contributor, typically 5–50 KB depending on resolution. Some tools embed high-resolution thumbnails reaching 150–200 KB.
  • Version history / revision annotations — incremental save operations (common in Acrobat Pro) append revision data that is technically part of the cross-reference structure, not pure metadata, but stripping it does reduce file size materially (sometimes by megabytes in heavily-revised documents).
Metadata Component Typical Size File Size Impact
DocInfo dictionary 200 – 800 bytes Negligible
XMP packet (no thumbnail) 1 – 8 KB Very small
Embedded thumbnail preview 5 – 200 KB Small to moderate
Revision history (linearised) 50 KB – several MB Moderate to significant
Embedded fonts (not metadata) 100 KB – 5 MB Most impactful for file size
Embedded images (not metadata) Varies widely Dominant file size factor

The bottom line: stripping all metadata from a typical 5 MB PDF usually reduces the file to roughly 4.97 MB — a difference of 20–30 KB. For PDFs with rich embedded thumbnails or long revision histories, savings of 100–500 KB are possible. If your goal is primarily file size reduction, image compression and font subsetting will deliver far greater gains than metadata removal alone.

Common misconception Many users think "removing metadata" includes deleting internal comment annotations, form data, or embedded file attachments. These are separate from document metadata — they are part of the PDF content stream and require different tools to address.

How to Inspect PDF Metadata Using Browser Tools

You don't need paid software to read PDF metadata. Several free approaches work directly in your browser with zero installs.

1

Chrome / Edge DevTools — Network Inspector

Open any PDF URL in Chrome or Edge. Press F12 to open DevTools, switch to the Network tab, and reload the page. Click the PDF request in the network log. Under the Headers tab, look for Content-Disposition and server-side response headers that may echo metadata fields like document title or content type hints.

2

PDF.js Console Inspection

Chrome and Firefox render PDFs using PDF.js. Open the browser console (F12 → Console tab) on a PDF page and run PDFViewerApplication.pdfDocument.getMetadata(). This returns a Promise that resolves to an object containing both the info (DocInfo dictionary) and metadata (raw XMP XML string) of the open document.

3

View Page Source — XMP Inspection

Since XMP metadata is stored as an XML packet inside the PDF binary, you can sometimes inspect it by opening the PDF in a text editor (like VS Code) and searching for <x:xmpmeta. The XML block between that tag and its closing counterpart is the complete XMP metadata. This works best for text-generated PDFs, not scanned image PDFs.

4

PDFMaster Metadata Remover (Recommended)

Upload your PDF to PDFMaster's free Metadata Remover tool. Before downloading, the tool displays a complete breakdown of all metadata fields found — Title, Author, Creator, Producer, dates, and XMP properties — entirely in your browser without uploading to any server.

5

ExifTool CLI (Advanced Users)

For technical users, ExifTool is the gold standard for metadata inspection. Run exiftool -a -u -g1 yourdocument.pdf to extract every metadata field across all groups. The -a flag shows duplicates, -u shows unknown tags, and -g1 organises by namespace group.

PDF.js console command reference

JavaScript — Browser Console 
// Run in Chrome/Firefox console while viewing a PDF
const meta = await PDFViewerApplication.pdfDocument.getMetadata();

// View DocInfo dictionary (standard fields)
console.log(meta.info);
// Returns: { Title, Author, Subject, Creator, Producer, CreationDate, ModDate... }

// View raw XMP XML
console.log(meta.metadata?._metadataMap);

// Check if document is encrypted
console.log(meta.info.IsEncrypted);

// Check PDF version
console.log(meta.info.PDFFormatVersion);

Remove PDF Metadata Instantly — Free & Private

No uploads. No server. Your files never leave your device. 100% browser-based processing.

Strip Metadata Now

Frequently Asked Questions

Answers to the most commonly searched questions about PDF metadata.

Document properties are the human-readable fields you see in a viewer's File → Properties dialog: title, author, subject, keywords. PDF metadata is the complete underlying data layer — encompassing both the DocInfo dictionary and the XMP packet — which can contain additional fields like GPS coordinates, revision history, embedded thumbnails, software version fingerprints, and custom enterprise namespace properties. Document properties are a partial view of the full metadata layer.

Yes, slightly. Standard DocInfo metadata is only a few hundred bytes. XMP packets add 1–8 KB. However, embedded thumbnail previews in the XMP stream can occupy 5–200 KB, and stripping those makes a more noticeable difference. For heavily-revised documents with incremental save history, the reduction can reach several hundred kilobytes. That said, embedded images and fonts dominate PDF file size — metadata removal alone will not significantly shrink most PDFs.

Google reads the /Title field and uses it directly as the search result headline — making it the most impactful SEO element in a PDF. The /Subject field functions as the meta description equivalent and can influence the snippet text displayed below the title in search results. The /Keywords field has minimal modern SEO value. An optimised title and subject field can meaningfully improve click-through rates from search results, especially for PDFs hosted on high-authority domains.

Yes. The /Author field is auto-populated from your OS username at creation time. The /Creator field identifies the exact software version used. Timestamps include timezone offsets that can geolocate a creator. XMP revision history logs every editor's name with timestamps. Mobile scanning apps embed GPS coordinates. Enterprise document systems can add project codes, client IDs, and internal document classification. PDFs shared externally without metadata stripping regularly expose this information.

Open the PDF in Chrome or Firefox, press F12 to open Developer Tools, navigate to the Console tab, and run PDFViewerApplication.pdfDocument.getMetadata(). This returns the full DocInfo dictionary and raw XMP XML. Alternatively, upload the PDF to PDFMaster's Metadata Remover — it displays all fields before processing, entirely client-side with no server upload.

No. Metadata is entirely separate from the visual content of a PDF — text, images, fonts, layouts, and page structure are untouched by metadata removal. The document will look, print, and behave identically to the original. The only observable change is that the File → Properties dialog in a PDF viewer will show empty or cleared fields.

Yes. PDFMaster's free PDF Metadata Remover processes your files entirely in your browser using pdf-lib — no file ever leaves your device. It strips both DocInfo fields and XMP packets, including embedded thumbnails, and gives you a clean download instantly.

Wrapping Up

PDF metadata is one of the most overlooked yet consequential aspects of document handling. It sits at the intersection of privacy, security, search engine performance, and file efficiency. Understanding it properly changes how you create, distribute, and protect documents.

The core principles to carry forward:

  • Document properties ≠ full metadata. What your PDF viewer shows you is only the surface of what's embedded.
  • Metadata tracks you. Author names, timezone offsets, GPS coordinates, and revision histories are all common metadata vectors for identifying document originators.
  • Metadata improves PDF SEO. The /Title and /Subject fields directly influence how your PDF appears in Google search results — optimise them.
  • Removing metadata doesn't significantly shrink files, but removing embedded thumbnails and revision history can help meaningfully.
  • You can inspect metadata today using your browser's developer tools — no software required.

Ready to clean your PDFs? PDFMaster's Metadata Remover handles it all for free, privately, and instantly — right in your browser.