{"id":48,"date":"2026-08-11T14:18:00","date_gmt":"2026-08-11T14:18:00","guid":{"rendered":"https:\/\/easyextract.online\/blog\/what-metadata-is-stored-in-a-pdf\/"},"modified":"2026-10-07T17:00:56","modified_gmt":"2026-10-07T17:00:56","slug":"what-metadata-is-stored-in-a-pdf","status":"publish","type":"post","link":"https:\/\/easyextract.online\/blog\/what-metadata-is-stored-in-a-pdf\/","title":{"rendered":"What Metadata Is Stored in a PDF?"},"content":{"rendered":"<p><strong>A PDF stores metadata in two primary structural locations: the Document Information Dictionary (Info dict) and an Extensible Metadata Platform (XMP) XML data stream. Together, these data structures contain core document descriptors\u2014including Title, Author, Subject, Keywords, Creator software, Producer engine, CreationDate, and ModDate\u2014as well as rights management, font subsets, revision histories, and device identifiers.<\/strong><\/p>\n<p>Every Portable Document Format (PDF) file generated by word processors, desktop publishers, or virtual printer drivers carries embedded administrative and technical metadata. While visual page content consists of vector graphics, image layers, and glyph positioning instructions, PDF metadata resides outside the visual canvas within dedicated dictionary tables and XML streams. Standardized under ISO 32000-1 (PDF 1.7) and ISO 32000-2 (PDF 2.0), this attribute payload enables operating systems, search engines, and enterprise indexers to categorize and manage files. However, because metadata is written automatically during creation, PDF documents frequently persist confidential authorship handles, local workstation file paths, editing durations, and software toolchain signatures without the sender&#8217;s explicit awareness.<\/p>\n<h2>Key Definitions: PDF Metadata, Document Info Dict, XMP Stream, and ISO Standards<\/h2>\n<p>To analyze the internal structure of a PDF file, technical definitions must be established for the standards and containers governing embedded metadata payloads.<\/p>\n<ul>\n<li><strong>PDF Metadata:<\/strong> Non-visual attribute data stored within a PDF binary container. PDF metadata defines document properties, authorship identity, creation software, security parameters, and modification histories independently of visual page layouts.<\/li>\n<li><strong>Document Information Dictionary (Info dict):<\/strong> The legacy key-value dictionary table defined in early PDF specifications (PDF 1.0\u20131.7). Positioned near the trailer cross-reference table, the Info dict maps predefined keys (such as <code>\/Author<\/code> or <code>\/CreationDate<\/code>) to literal string objects.<\/li>\n<li><strong>XMP (Extensible Metadata Platform) Data Stream:<\/strong> An ISO-standardized framework (ISO 16684-1) created by Adobe that embeds an XML metadata payload formatted according to W3C Resource Description Framework (RDF) syntax. Referenced in the PDF Document Catalog (<code>\/Root<\/code> catalog object), the XMP stream supports custom namespaces, nested properties, and granular editing histories.<\/li>\n<li><strong>PDF 1.7 \/ ISO 32000-1 and PDF 2.0 \/ ISO 32000-2:<\/strong> International specifications governing PDF file construction. ISO 32000-1 allows dual metadata storage in both the Info dict and XMP stream, whereas ISO 32000-2 formally deprecates legacy Info dict fields in favor of synchronized XMP packets.<\/li>\n<\/ul>\n<h2>Information Dictionary (Info Dict) Fields: Standard Keys and Syntax<\/h2>\n<p>The Document Information Dictionary represents the original metadata store defined in ISO 32000-1 Section 14.3.3. Attributes shown under basic viewer properties are retrieved from this dictionary. The specification defines eight standard fields:<\/p>\n<ul>\n<li><strong>Title (<code>\/Title<\/code>):<\/strong> A text string specifying the actual document title, often derived from manuscript headers rather than the physical file name.<\/li>\n<li><strong>Author (<code>\/Author<\/code>):<\/strong> A text string identifying the document creator, automatically populated with the operating system username, login profile, or software registration handle.<\/li>\n<li><strong>Subject (<code>\/Subject<\/code>):<\/strong> A text string summarizing the document subject matter or topic abstract.<\/li>\n<li><strong>Keywords (<code>\/Keywords<\/code>):<\/strong> A string of comma-separated or space-separated search keywords for enterprise indexers.<\/li>\n<li><strong>Creator (<code>\/Creator<\/code>):<\/strong> A text string identifying the original authoring software (e.g., <code>Microsoft\u00ae Word for Microsoft 365<\/code>, <code>Adobe InDesign 19.0<\/code>, or <code>Google Docs<\/code>).<\/li>\n<li><strong>Producer (<code>\/Producer<\/code>):<\/strong> A text string naming the underlying rendering library, virtual printer, or conversion tool that compiled the final PDF file (e.g., <code>Acrobat Distiller 24.0<\/code>, <code>Skia\/PDF m122<\/code>, or <code>Quartz PDFContext<\/code>).<\/li>\n<li><strong>CreationDate (<code>\/CreationDate<\/code>):<\/strong> An ASN.1-formatted date string recording when the PDF was compiled, formatted as <code>(D:YYYYMMDDHHmmSSOHH'mm')<\/code> with UTC time zone offsets (e.g., <code>D:20260918083000-04'00'<\/code>).<\/li>\n<li><strong>ModDate (<code>\/ModDate<\/code>):<\/strong> A date string recording the timestamp when the PDF was last modified or resaved.<\/li>\n<\/ul>\n<p>Within the underlying binary stream, the Info dict is serialized as an indirect object table:<\/p>\n<pre><code>12 0 obj\n&lt;&lt;\n  \/Title (Quarterly Audit &amp; Risk Assessment 2026)\n  \/Author (Elizabeth Vance)\n  \/Subject (Enterprise Security Compliance)\n  \/Keywords (audit, compliance, security, 2026)\n  \/Creator (Microsoft Word for Office 365)\n  \/Producer (Acrobat Distiller 24.0)\n  \/CreationDate (D:20260918083000-04'00')\n  \/ModDate (D:20260918114522-04'00')\n&gt;&gt;\nendobj<\/code><\/pre>\n<h2>XMP Metadata Data Stream: XML Schemas, Namespaces, and Data Payload<\/h2>\n<p>Modern PDF documents rely on XMP streams to store structured metadata payloads. Standardized under ISO 16684-1, XMP embeds XML data packets directly inside a stream object linked from the Document Catalog (<code>\/Catalog<\/code> dictionary under <code>\/Metadata<\/code>).<\/p>\n<p>Wrapped inside XML processing instructions (<code>&lt;?xpacket begin=\"...\" id=\"W5M0MpCehiHzreSzNTczkc9d\"?&gt;<\/code>), XMP packets can be read by external asset management systems without full PDF binary parsing. XMP organizes attributes into standardized XML schema namespaces:<\/p>\n<ul>\n<li><strong>Dublin Core Schema (<code>dc:<\/code> namespace <code>http:\/\/purl.org\/dc\/elements\/1.1\/<\/code>):<\/strong> Contains universal descriptors including <code>dc:title<\/code>, <code>dc:creator<\/code> (author array), <code>dc:description<\/code>, <code>dc:subject<\/code>, <code>dc:publisher<\/code>, <code>dc:rights<\/code>, and <code>dc:format<\/code> (<code>application\/pdf<\/code>).<\/li>\n<li><strong>Adobe PDF Schema (<code>pdf:<\/code> namespace <code>http:\/\/ns.adobe.com\/pdf\/1.3\/<\/code>):<\/strong> Encapsulates PDF-specific properties such as <code>pdf:Keywords<\/code>, <code>pdf:PDFVersion<\/code>, <code>pdf:Producer<\/code>, and <code>pdf:Trapped<\/code>.<\/li>\n<li><strong>Photoshop &amp; Basic Schemas (<code>photoshop:<\/code>, <code>xmp:<\/code>):<\/strong> Stores creation dates (<code>xmp:CreateDate<\/code>), modification timestamps (<code>xmp:ModifyDate<\/code>), and editing tool states.<\/li>\n<li><strong>Media Management Schema (<code>xmpMM:<\/code> namespace <code>http:\/\/ns.adobe.com\/xap\/1.0\/mm\/<\/code>):<\/strong> Tracks file lineage through GUIDs (<code>xmpMM:DocumentID<\/code>, <code>xmpMM:InstanceID<\/code>) and an <code>xmpMM:History<\/code> resource array logging every save, tool invocation, and export step.<\/li>\n<li><strong>Rights Management Schema (<code>xmpRights:<\/code>):<\/strong> Encodes copyright status, legal statements, and licensing terms.<\/li>\n<\/ul>\n<p>Compliant PDF 1.7 and PDF 2.0 parsers give authoritative precedence to XMP streams when values conflict with legacy Info dict entries.<\/p>\n<h2>Hidden &amp; Invisible Metadata Risks in PDF Files<\/h2>\n<p>PDF documents contain non-visual data structures that introduce privacy exposures beyond standard fields:<\/p>\n<ul>\n<li><strong>Incremental Update Trailers &amp; Revision History:<\/strong> PDF specifications support append-only saving, where edits are appended to the file end alongside a new cross-reference (<code>xref<\/code>) table. Deleting text or pages in standard editors leaves original unedited bytes and earlier metadata states intact in prior byte offsets.<\/li>\n<li><strong>Embedded Font Subsets &amp; PostScript Metrics:<\/strong> Embedded fonts contain descriptors (<code>\/FontDescriptor<\/code>) with system font names and glyph metrics that can reveal local workstation font paths.<\/li>\n<li><strong>Annotations, Markup Layers, and Deleted Comments:<\/strong> Reviewer notes, highlights, and sticky notes reside in the <code>\/Annots<\/code> array. Even when hidden on screen, annotation objects retain author handles, edit timestamps, and full comment strings.<\/li>\n<li><strong>Workstation Usernames and Local File Paths:<\/strong> Creator strings and OLE links frequently retain absolute workstation file paths (e.g., <code>C:\\Users\\jdoe\\Documents\\Confidential\\Tender.docx<\/code>), exposing network directory structures and user identity handles.<\/li>\n<li><strong>Embedded File Attachments &amp; Printer Identifiers:<\/strong> PDF containers can embed source files within <code>\/EmbeddedFiles<\/code> dictionaries or store application data in <code>\/PieceInfo<\/code> tables, alongside device printer identifiers and trapped rendering flags.<\/li>\n<\/ul>\n<h2>How to View and Inspect PDF Metadata in Your Browser<\/h2>\n<p>Inspecting metadata before distributing files is critical to prevent accidental data leaks. The safest method uses client-side, browser-based tools that process document structures in memory without remote server uploads.<\/p>\n<p>You can view every hidden attribute inside any document using the <a href=\"https:\/\/easyextract.online\/pdf-metadata-extractor\/\">PDF metadata extractor<\/a>. When a file is loaded, client-side JavaScript reads the PDF binary buffer (<code>Uint8Array<\/code>), locates the trailer <code>\/Info<\/code> dictionary, and parses the <code>\/Metadata<\/code> object stream to render the XMP RDF\/XML payload. Because all processing occurs locally within your browser sandbox, sensitive reports and legal documents never leave your local device memory.<\/p>\n<h2>How PDF Metadata Differs from Office (DOCX\/XLSX) Metadata<\/h2>\n<p>Comparing PDF metadata to Microsoft Office metadata highlights structural differences across file formats:<\/p>\n<ul>\n<li><strong>Container Architecture:<\/strong> Office files (DOCX, XLSX, PPTX) follow the Open Packaging Conventions (OPC)\u2014a zipped container of structured XML files (<code>docProps\/core.xml<\/code>, <code>docProps\/app.xml<\/code>, <code>docProps\/custom.xml<\/code>). PDF files store metadata in binary dictionaries and XMP streams within a continuous binary stream.<\/li>\n<li><strong>Revision History Tracking:<\/strong> Word documents record Revision Save Identifiers (RSIDs) inside <code>word\/document.xml<\/code> to track editing sessions. PDF files track history through incremental trailer revisions and XMP media management history arrays (<code>xmpMM:History<\/code>).<\/li>\n<li><strong>Conversion Persistence:<\/strong> Exporting an Office file to PDF extracts metadata from <code>docProps\/core.xml<\/code> to populate the PDF <code>\/Info<\/code> dict and XMP payload, while stamping the conversion engine name into the <code>\/Producer<\/code> field.<\/li>\n<\/ul>\n<p>To inspect hidden attributes in office documents, use the <a href=\"https:\/\/easyextract.online\/office-metadata-extractor\/\">Office metadata extractor<\/a>.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<p><strong>What metadata is stored inside a standard PDF document?<\/strong><br \/>\nA standard PDF contains Document Information Dictionary fields (Title, Author, Subject, Keywords, Creator software, Producer engine, CreationDate, and ModDate) and an XMP XML stream holding Dublin Core descriptors, software licenses, font metrics, and modification histories.<\/p>\n<p><strong>Where is metadata located within the PDF file structure?<\/strong><br \/>\nPDF metadata is stored in two locations: the Document Information Dictionary (located near the PDF trailer xref cross-reference block) and the XMP metadata stream (an XML stream object referenced under the <code>\/Metadata<\/code> key in the Document Catalog).<\/p>\n<p><strong>What is the difference between the PDF Info dictionary and an XMP metadata stream?<\/strong><br \/>\nThe Info dictionary is a legacy key-value string container defined in PDF 1.0\u20131.7. The XMP metadata stream is an ISO 16684-1 standard RDF\/XML data packet introduced in PDF 1.4 supporting complex nested schemas, custom namespaces, and media management histories.<\/p>\n<p><strong>Can PDF metadata reveal the identity of the author or software user?<\/strong><br \/>\nYes. The <code>\/Author<\/code> field frequently embeds operating system usernames or software registration handles, while <code>\/Creator<\/code> and <code>\/Producer<\/code> fields record software builds, rendering engines, and local workstation file paths.<\/p>\n<p><strong>What are PDF incremental updates and how do they expose deleted metadata?<\/strong><br \/>\nIncremental updates append modifications to the end of a file without rewriting existing binary objects. Editing sensitive text or metadata standardly leaves original content fully readable in earlier byte offsets of the binary file.<\/p>\n<p><strong>Is PDF metadata visible when printing or viewing the document page?<\/strong><br \/>\nNo. Metadata resides within non-visual structural containers in the PDF file code. It is never drawn onto the visual page canvas during screen rendering or physical printing unless explicitly converted into visual text header elements.<\/p>\n<p><strong>How can I extract and inspect PDF metadata without uploading my document to a server?<\/strong><br \/>\nYou can inspect PDF metadata securely using an in-browser tool like the <a href=\"https:\/\/easyextract.online\/pdf-metadata-extractor\/\">PDF metadata extractor<\/a>, which parses binary byte arrays in local device RAM without sending files over remote web networks.<\/p>\n<h2>Related Reading &amp; Tools<\/h2>\n<ul>\n<li><a href=\"https:\/\/easyextract.online\/blog\/remove-hidden-metadata-before-sharing-pdf\/\">How to Remove Hidden Metadata Before Sharing a PDF<\/a><\/li>\n<li><a href=\"https:\/\/easyextract.online\/pdf-metadata-extractor\/\">Browser PDF Metadata Extractor<\/a><\/li>\n<li><a href=\"https:\/\/easyextract.online\/office-metadata-extractor\/\">Office Metadata Extractor<\/a><\/li>\n<li><a href=\"https:\/\/easyextract.online\/blog\/what-is-file-metadata\/\">What Is File Metadata? Types, Examples, and How to View It<\/a><\/li>\n<\/ul>\n<h2>Sources &amp; References<\/h2>\n<ul>\n<li><strong>ISO 32000-1:2008:<\/strong> <em>Document management \u2014 Portable document format \u2014 Part 1: PDF 1.7<\/em>. International Organization for Standardization. Technical specifications for document information dictionaries and metadata stream structures.<\/li>\n<li><strong>ISO 32000-2:2020:<\/strong> <em>Document management \u2014 Portable document format \u2014 Part 2: PDF 2.0<\/em>. International Organization for Standardization. Deprecation of legacy Info dictionary entries and XMP synchronization rules.<\/li>\n<li><strong>ISO 16684-1:2019:<\/strong> <em>Graphic technology \u2014 Extensible Metadata Platform (XMP) specification \u2014 Part 1: Data model, serialization and core properties<\/em>. Standardized RDF\/XML metadata data model and namespace definitions.<\/li>\n<li><strong>Adobe Technical Note #5144:<\/strong> <em>PDF Reference, Version 1.7 (Sixth Edition)<\/em>. Adobe Systems Incorporated. Implementation guidelines for document catalog metadata, incremental updates, and dictionary objects.<\/li>\n<\/ul>\n<p><em>Last updated: 18 September 2026.<\/em><\/p>\n<p><script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What metadata is stored inside a standard PDF document?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"A standard PDF contains Document Information Dictionary fields (Title, Author, Subject, Keywords, Creator software, Producer engine, CreationDate, and ModDate) and an XMP XML stream holding Dublin Core descriptors, software licenses, font metrics, and modification histories.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Where is metadata located within the PDF file structure?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"PDF metadata is stored in two locations: the Document Information Dictionary (located near the PDF trailer xref cross-reference block) and the XMP metadata stream (an XML stream object referenced under the \/Metadata key in the Document Catalog).\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is the difference between the PDF Info dictionary and an XMP metadata stream?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"The Info dictionary is a legacy key-value string container defined in PDF 1.0\u20131.7. The XMP metadata stream is an ISO 16684-1 standard RDF\/XML data packet introduced in PDF 1.4 supporting complex nested schemas, custom namespaces, and media management histories.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Can PDF metadata reveal the identity of the author or software user?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Yes. The \/Author field frequently embeds operating system usernames or software registration handles, while \/Creator and \/Producer fields record software builds, rendering engines, and local workstation file paths.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What are PDF incremental updates and how do they expose deleted metadata?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Incremental updates append modifications to the end of a file without rewriting existing binary objects. Editing sensitive text or metadata standardly leaves original content fully readable in earlier byte offsets of the binary file.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Is PDF metadata visible when printing or viewing the document page?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"No. Metadata resides within non-visual structural containers in the PDF file code. It is never drawn onto the visual page canvas during screen rendering or physical printing unless explicitly converted into visual text header elements.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How can I extract and inspect PDF metadata without uploading my document to a server?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"You can inspect PDF metadata securely using an in-browser tool like the PDF metadata extractor, which parses binary byte arrays in local device RAM without sending files over remote web networks.\"\n      }\n    }\n  ]\n}\n<\/script><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A PDF stores metadata in two primary structural locations: the Document Information Dictionary (Info dict) and an Extensible Metadata Platform (XMP) XML data stream. Together, these data structures contain core document descriptors\u2014including Title, Author,\u2026<\/p>\n","protected":false},"author":2,"featured_media":374,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"slim_seo":{"title":"What Metadata Is Stored in a PDF?","description":"A PDF carries hidden metadata \u2014 author, title, the software that made"},"footnotes":""},"categories":[3],"tags":[],"class_list":["post-48","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-guides"],"_links":{"self":[{"href":"https:\/\/easyextract.online\/blog\/wp-json\/wp\/v2\/posts\/48","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/easyextract.online\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/easyextract.online\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/easyextract.online\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/easyextract.online\/blog\/wp-json\/wp\/v2\/comments?post=48"}],"version-history":[{"count":2,"href":"https:\/\/easyextract.online\/blog\/wp-json\/wp\/v2\/posts\/48\/revisions"}],"predecessor-version":[{"id":223,"href":"https:\/\/easyextract.online\/blog\/wp-json\/wp\/v2\/posts\/48\/revisions\/223"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/easyextract.online\/blog\/wp-json\/wp\/v2\/media\/374"}],"wp:attachment":[{"href":"https:\/\/easyextract.online\/blog\/wp-json\/wp\/v2\/media?parent=48"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/easyextract.online\/blog\/wp-json\/wp\/v2\/categories?post=48"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/easyextract.online\/blog\/wp-json\/wp\/v2\/tags?post=48"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}