Guide · 31 August 2026
PDF Metadata vs XMP
PDF metadata vs XMP is a split inside the file, not two names for the same box. Document Info is a document-level key-value dictionary. XMP is RDF/XML metadata that can hang off the document catalog or off some objects, including pages. A PDF can have both, either, or neither, and the same title or author can disagree between them.
Document Info and XMP, side by side
Adobe’s PDF reference describes the Info dictionary and a separate document Metadata stream. Adobe’s XMP specifications describe that stream as RDF/XML. The PDF Association notes that object-level Metadata streams can exist as well. The table below is the practical split those sources imply, plus what this site actually reads or writes.
| Aspect | Document Info | XMP |
|---|---|---|
| Storage location | A document-level Info dictionary referenced from the PDF trailer. | A Metadata stream, commonly on the document catalog, and sometimes on pages or other objects. |
| Data model | Named keys with simple strings or dates, such as Title and Author. | An RDF/XML packet with namespaced properties that can nest and repeat. |
| Field mapping | Eight standard keys this site reads: Title, Author, Subject, Keywords, Creator, Producer, CreationDate, ModDate. | Documented counterparts exist, such as dc:title for Title. The two stores are not kept in lockstep. |
| Extensibility | A small standard set, plus occasional extra keys a writer may add. | Designed to grow through namespaces rather than a fixed key list. |
| Object-level scope | One dictionary for the document. It does not describe a single page or image. | Can describe the document, a page, or another object that carries its own stream. |
| Common viewing methods | Properties dialogs and this site’s field list. | Often invisible in a properties dialog. This site reports presence, not every nested property. |
| Cleanup impact | The editor changes the eight standard keys. The remover deletes the whole Info dictionary. | The editor leaves existing XMP in place. The remover unlinks detectable catalog and page Metadata streams, then rechecks those locations. |
Both stores can exist, and they need not match
A properties dialog usually shows Document Info. That view can look empty while an XMP packet still names a person, a tool, or a date. The reverse also happens: Info can carry a public title while XMP still holds an older draft. Do not assume that editing one location rewrites the other.
This site’s editor is explicit about that boundary. It updates standard Document Info and preserves existing XMP. If you change Author in the form, any Author-like value inside XMP stays. The PDF metadata fields reference lists the eight Info keys and their common XMP counterparts without claiming that this viewer displays those XMP properties.
Why PDF metadata vs XMP conflicts happen
A PDF metadata vs XMP conflict often starts with an ordinary export. An authoring application can write a title and author to Document Info while also creating an XMP packet. A later tool may update only the familiar properties fields, preserve the older XMP, or create a new packet from its own defaults. The PDF format allows both stores, so matching values depend on the applications that read and write the file.
Templates are another common source. A document can inherit an old subject, author, project code, or keyword before anyone exports it. Renaming the file does not rewrite either metadata store. Copying pages into a new document can also leave object-level Metadata streams on individual pages even when the new document-level fields look correct. This is why a PDF metadata vs XMP review should cover the copy being delivered, after the final export or merge.
A difference is not automatically an error. A publishing system might intentionally keep a richer XMP description while a reader shows a shorter Info title. The useful question is whether the receiving workflow reads one store, both stores, or merely needs sensitive labels removed. Treat the PDF metadata vs XMP result as evidence for that decision, rather than assuming every duplicate value must be synchronized.
How to tell which store your file actually uses
Start with a read-only pass on the exact copy you plan to share. Use the view PDF metadata report, then decide. The viewer does not rewrite the file.
- Read the eight standard Info fields. Empty means this reader found no value, not that a hidden XMP property is absent.
- Note whether document XMP is detected. That flag means a Metadata stream is attached to the catalog, not that every XMP property was parsed.
- Note how many pages carry their own XMP stream. Page-level packets can remain when a cleanup changes only Document Info.
- If a signature field is present, stop writing. A rewrite can invalidate the signature.
- If standard Info needs correction and XMP can stay, edit PDF metadata. If Info and detectable catalog or page XMP should go, remove metadata from PDF.
A worked PDF metadata vs XMP example
Imagine a proposal called Final board pack.pdf. Its properties dialog shows the Title “Board review v3” and Author “Casey.” The viewer also reports document XMP and two pages with XMP. This PDF metadata vs XMP example illustrates the limits below.
| Observation | What it supports | What it does not establish |
|---|---|---|
| Title and Author are visible | The reader found those values in standard Document Info. | It does not show whether dc:title or dc:creator inside XMP matches them. |
| Document XMP is detected | A Metadata stream is attached at the catalog location this viewer checks. | Presence alone does not reveal the packet’s properties or whether they are sensitive. |
| Two pages have XMP | Two page dictionaries reference their own Metadata streams. | It does not prove that other objects, attachments, or embedded images contain no metadata. |
| No signature field is detected | This site can offer its normal edit or removal path if the PDF is otherwise supported. | It is not a general authenticity or forensic finding. |
The filename suggests a final copy, while the Info title suggests a draft. That mismatch is enough to review the public-facing title. The XMP presence flags create a second question, not an answer about their values. If your delivery rule requires those values to agree, inspect the packet with a dedicated XMP tool before changing anything. A responsible PDF metadata vs XMP check keeps those two conclusions separate.
Choose an action after a PDF metadata vs XMP check
A PDF metadata vs XMP check is useful when it leads to a scoped action. Choose the smallest operation that satisfies the real sharing or publishing requirement, then inspect the saved output again.
| Your task | Appropriate next step | Boundary to keep in mind |
|---|---|---|
| Inventory standard fields and XMP locations | Use the read-only viewer on the exact PDF you plan to send. | It reports XMP presence at supported locations, not a full RDF property dump. |
| Correct Title, Author, or another standard field | Use the editor when existing XMP can remain unchanged. | The saved Info value can still differ from an XMP counterpart. |
| Remove supported document labels before sharing | Use the remover for the Info dictionary plus detectable catalog and page XMP references. | Attachments, annotations, image EXIF, custom objects, and external copies stay outside that promise. |
| Reconcile XMP properties or validate PDF/A | Use a dedicated XMP editor, validator, or controlled publishing workflow. | This site does not expose arbitrary namespaces or certify conformance. |
Save changes as a new copy so the source remains available for comparison. Reload the output in the viewer: confirm each expected Info value, the document and page XMP indicators, and the signature warning. The site performs its own supported-scope verification before enabling a download, while your final PDF metadata vs XMP review confirms that the result fits the wider workflow.
Limits of this PDF metadata vs XMP check
There is no online XMP property editor here. The viewer does not dump nested RDF. The remover does not search attachments, images, comments, or custom objects for XML. If two structures share one Metadata object, the remover unlinks the catalog and page references it knows about; it does not claim to erase every other pointer.
PDF/A validation, forensic imaging, and EXIF inside embedded pictures are different jobs. If your workflow requires those, use software that states that scope and verify the output against that workflow. The PDF metadata guides index keeps this comparison with the field list and the removal tutorial.
For a repeatable handoff, keep the original PDF and record the goal of the change: corrected Info, removed supported metadata, or XMP reconciliation in another application. Note which tool created the output and inspect that output instead of relying on the settings used. A short record helps another reviewer understand why XMP remains after an Info edit, or why a removal report covers catalog and page references while excluding attachments and embedded media. This makes the PDF metadata vs XMP decision auditable without turning a limited check into a broader guarantee.
Sources and scope notes
Product behavior is grounded in this site’s PDF code and verified-output tests. External storage facts come from the pages below, checked on 31 August 2026.
- Adobe XMP Specifications
Defines XMP as RDF/XML metadata that applications can embed in files.
- Adobe PDF Reference 1.5, metadata section
Documents the Info dictionary and the document-level Metadata stream.
- PDF Association: use of object metadata streams
Notes that Metadata streams can attach to objects other than the catalog.
Questions this guide answers
What is XMP metadata in a PDF?
XMP is an XML packet based on RDF. In a PDF it usually lives in a Metadata stream attached to the document catalog. Some files also attach a Metadata stream to individual pages or other objects. It is a separate store from the Document Info dictionary.
What is the difference between Document Info and XMP in a PDF?
Document Info is a document-level key-value dictionary for familiar fields such as Title and Author. XMP is RDF/XML that can describe the document or some objects, using namespaced properties. They can both exist, and they can disagree.
Do I need XMP in a PDF?
Only if a later workflow needs it. Some publishing and archival pipelines read XMP. Many sharing tasks only care about Title, Author, and whether leftover XMP still names a person or a tool. Inspect the file before you decide to keep, ignore, or remove it.
Does editing Title or Author update XMP?
Not on this site. The editor writes standard Document Info and preserves existing XMP. If the two stores already differ, correcting Info leaves the XMP packet as it was.
Can I edit arbitrary XMP properties here?
No. This site does not offer an XMP editor, a full XMP property dump, or PDF/A compliance checking. Use the viewer to see whether document or page XMP is present, the editor to change standard Info, or the remover to clear Info plus detectable catalog and page XMP references.
How should I resolve a PDF metadata vs XMP conflict?
First decide which store the receiving workflow reads. Correct standard Document Info when that is the only required output and XMP can remain. Remove the supported Info and detectable catalog or page XMP locations when the shared copy should omit both. Use a dedicated XMP or PDF/A tool when you must inspect, edit, reconcile, or validate individual XMP properties.