Document privacy
PDF metadata viewer
PDF metadata viewer?
PDF metadata viewer, in three steps. Drop an unlocked PDF. Read author, creator app, producer, title, and dates from the Info dictionary, plus XMP when the packet text can be read. Leave the file here, or open the remover only if you want those Info fields cleared.
Gmail Help: Send attachments with your Gmail message; WhatsApp Help: media and documents; WhatsApp Help: longer videos; Telegram FAQ
Last updated
PDF metadata viewer, in three steps. Drop an unlocked PDF. Read author, creator app, producer, title, and dates from the Info dictionary, plus XMP when the packet text can be read. Leave the file here, or open the remover only if you want those Info fields cleared. Encrypted PDFs stay locked. Words on the page are not metadata.
The PDF stays in this tab. Property values are not uploaded.
Choose a file
Waiting for a file.
What fields a PDF can carry
A PDF can carry an author, a creator app name, a producer, a title, a subject, keywords, a creation date, and a modification date in the document information dictionary. It can also carry an XMP packet. This page reads those values when they are stored in a form it can open. It does not read annotations, attachments, forms, JavaScript, signatures, or the words printed on the pages.
Why the fields matter
Creator is the application name stored in the Info dictionary. Producer is the tool name stored next to it. Author and the two dates are the strings the file saved. This page shows those strings. It does not edit the PDF.
What this viewer reads
| Format | What is read |
|---|---|
| Info dictionary, page count, encryption flag, uncompressed XMP |
What stays on your device
pdf-lib reads the Info dictionary in the page. This viewer does not unlock encrypted files.
Viewer and remover
This page reads. The PDF metadata remover clears supported Info fields and leaves XMP, forms, attachments, and visible page text. The Info and XMP remover deletes the catalog Metadata stream as well and then reads the file again. This viewer does not edit the file.
Supported standard Info-dictionary fields can be cleared in the PDF metadata remover.
Limits
- Encrypted PDFs are reported as encrypted and are not unlocked.
- XMP values are listed when the packet text is uncompressed. A compressed packet may only show as present.
- A blank row means this reader did not find that value. It does not mean the page has no name on it.
One PDF where Info and XMP disagree, 27 October 2026
On 27 October 2026 this site built one synthetic PDF, 1744 bytes, SHA-256 f6280b3790a2ee349a0294ee7f4c5e47a5a96ac4c43d482994a7eb28d33f6df9. The header is %PDF-1.4. One page is 200 by 200 points. The catalog Metadata entry is uncompressed object 5. The Info dictionary is indirect object 6. An inline Info dictionary made ExifTool 12.76 refuse -Author= with “Error: Info dictionary is not an indirect object”, so this file uses an indirect object. qpdf 11.9.0 --check reported PDF 1.4, not encrypted, not linearized, and no syntax errors. The file was not uploaded, and the button on this page was not clicked. inspectPdfBytes in src/metadata-viewers/pdf-inspector.js read the bytes with pdf-lib 1.17.1.
The Info dictionary stores Title Info Title Fixture, Author Info Author Fixture, Subject Info Subject Fixture, Keywords Info Keywords Fixture, Creator Info Creator Fixture, Producer Info Producer Fixture, and CreationDate and ModDate D:20261027120000Z. The XMP packet stores dc:title XMP Title Fixture, dc:creator XMP Creator Fixture, dc:description XMP Description Fixture, pdf:Producer XMP Producer Fixture, xmp:CreatorTool XMP CreatorTool Fixture, and xmp:CreateDate 2026-10-27T08:00:00Z. The two sides disagree on purpose.
pdfinfo 24.02.0 printed the Info strings. Keywords stayed Info Keywords Fixture, with the spaces and without added commas. CreationDate and ModDate printed Tue Oct 27 20:00:00 2026 CST on this host, which is UTC+8. That line is this host’s local rendering of the Z time. It is not a claim about every pdfinfo build. Encrypted was no. Metadata Stream was yes. Custom Metadata was no. Page size was 200 x 200 pts. PDF version was 1.4.
ExifTool 12.76 with no -a flag preferred XMP on several unsuffixed rows: Title XMP Title Fixture, Creator XMP Creator Fixture, Description XMP Description Fixture, Producer XMP Producer Fixture, Creator Tool XMP CreatorTool Fixture, Create Date 2026:10:27 08:00:00Z. Author stayed Info Author Fixture. Subject stayed Info Subject Fixture. Keywords printed Info, Keywords, Fixture. Modify Date printed 2026:10:27 12:00:00Z. ExifTool -a -G1 showed both groups. [PDF] Title, Author, Creator, Producer, and Create Date 2026:10:27 12:00:00Z sat next to [XMP-dc] Title and Creator, [XMP-pdf] Producer, and [XMP-xmp] Create Date 2026:10:27 08:00:00Z. The comma-separated Keywords line matches the list behavior on ExifTool’s PDF tag page. The stored Info string has spaces and no commas.
inspectPdfBytes returned status ok, encrypted false, xmpPresent true, version 1.4, and pageCount 1. Info fields are the Info strings, including keywords Info Keywords Fixture. creationDate and modificationDate are 2026-10-27T12:00:00Z. It also returned xmpAuthor XMP Creator Fixture, plus xmpTitle, xmpDescription, xmpProducer, and xmpCreatorTool. It did not return xmp:CreateDate. This reader shows Info and XMP side by side. It does not replace the Creator row with the XMP creator the way ExifTool’s unsuffixed Creator line did.
One write used exiftool -Author="Info Author After Write" -overwrite_original. The file went from 1744 bytes to 5813, SHA-256 465805ab4fbb7e9b96e6b5f0dada65891c65d7fea88d366d8bce4f369efa4fda. The old literal Info Author Fixture still occurs once. Info Author After Write occurs twice. ExifTool -a -G1 then showed [XMP-pdf] Author and [PDF] Author both set to the new string. [XMP-dc] Creator was still XMP Creator Fixture. [PDF] Creator was still Info Creator Fixture. [PDF] Modify Date was still 2026:10:27 12:00:00Z. pdf-lib read the new Info author and the old XMP dc:creator, with dates still 2026-10-27T12:00:00Z. qpdf --check still reported PDF 1.4, not encrypted, not linearized, and no syntax errors. This is one write. It is not a test of the Password option or of every write flag.
One encrypted copy used qpdf 11.9.0 with a user password and a 256-bit key. The password is not published. The file is 2723 bytes, SHA-256 18dce514b0afbee0e940fd2cd246a956fc79a6242e3bf9fad6cb3df00f2893cf. qpdf rewrote the header to PDF 1.7. pdfinfo with no password printed no Title and reported Command Line Error: Incorrect password. qpdf --show-encryption without the password printed Incorrect password supplied, then R = 6, P = -4, and AESv3 for streams, strings, and the file. pdfinfo with the password printed Encrypted yes, algorithm AES-256, PDF version 1.7, file size 2723, Author still Info Author Fixture, and Metadata Stream yes. inspectPdfBytes returned status encrypted, encrypted true, version 1.7, pageCount null, and only the pdfVersion field. The viewer does not unlock it.
pdfquiz.com/pdf-metadata-viewer, read on 27 October 2026, says that when Info and XMP disagree, most readers show the Info dictionary, and that its own tool reports Info first. The same page says the file is uploaded. It does not publish this file’s 1744 bytes, the hashes, the four-reader rows, an author write that leaves the old literal in the file, or an encrypted file this viewer refuses. On this file, ExifTool’s unsuffixed Title and Creator were the XMP values, while pdfinfo and this reader kept the Info title and author. ExifTool’s tag page, fetched the same day, still described incremental updates and a Password option. A revision date was not in that fetched text. The earlier “last revised 29 May 2026, as read on 21 October 2026” sentence is from that earlier read. This site did not run pdfquiz.
Which value shows when PDF Info and XMP disagree?
On this 1744-byte file, pdfinfo 24.02.0 and this page’s pdf-lib 1.17.1 reader kept the Info title and the Info author. This reader also listed xmpAuthor XMP Creator Fixture beside them. ExifTool 12.76 with no -a flag printed the XMP title and the XMP creator on the unsuffixed rows, and it kept the Info author. Keywords printed as Info, Keywords, Fixture in ExifTool and as Info Keywords Fixture in pdfinfo and pdf-lib.
Questions
How do I view PDF metadata?
Open this PDF metadata viewer and drop the file. It reads the Info dictionary in this browser: author, title, subject, keywords, creator app, producer, and dates when those values are stored. The file is not uploaded.
How do I read PDF metadata without uploading?
Use this page. pdf-lib reads the file in the tab. An encrypted PDF is reported as encrypted and stays locked. This viewer does not ask for a password.
What PDF metadata fields can this page show?
Author, creator app, producer, title, subject, keywords, creation date, modification date, page count, PDF version, the encryption flag, and XMP when the packet text is readable. Page text is not a metadata row.
Can I see XMP as well as the Info dictionary?
Uncompressed XMP can show author, title, description, producer, and creator tool. A filtered metadata stream may only show as present. Clearing Info fields later does not delete that XMP packet.
How does this PDF metadata viewer read the file?
Choose a file, or drop the PDF. The file stays in this tab. pdf-lib opens it with encryption checking left on and metadata updating left off. An encrypted file is reported as encrypted and is not unlocked. There is no password box.
How is this different from ExifTool?
ExifTool’s PDF tag page, last revised 29 May 2026 as read on 21 October 2026, says it reads and writes PDF through version 2.0, including RC4 and AES, with a Password option, and that its writes are incremental and reversible unless the file is linearized afterward. On 27 October 2026 the same URL still described incremental updates and a Password option; a revision date was not in that fetched text. This page only reads a smaller set of Info fields and uncompressed XMP. It does not write. The same day, ExifTool 12.76 read one synthetic PDF on this site: the default listing preferred several XMP values, and one -Author= write left the old author literal in the file. That read is not a test of the Password option or of every write flag.