Every PDF you send carries two things: the pages people can see, and a small set of details people usually cannot. That second layer is PDF metadata — the file’s own description of itself: its title, its author, the date it was made, and a few other facts tucked inside the file rather than printed on any page.
Most of the time, nobody looks at it. That is exactly why it is worth checking before you send a PDF somewhere important — a CV, a contract, a report, a form. A file can quietly carry an old working title, a previous author’s name, or a date that tells a different story from the one you mean to tell.
What PDF metadata actually is
Metadata literally means “data about data.” In a PDF, it is descriptive information stored inside the file, rather than the document’s visible content. Open the PDF and you see text, images, and layout; look at its metadata and you see what the file says about itself — what it is called, who it is attributed to, what it is about, and when the software claims to have made it.
Think of it like the label on an envelope: the letter is the content, and the label — name, date, sender — is the metadata. It travels with the letter wherever it goes. Note the difference from your computer’s file properties (size, download date), which describe the file on your disk. PDF metadata lives inside the file itself, so it survives being emailed, copied, and downloaded.
The fields a PDF can carry
A PDF has a classic set of metadata fields, stored in a part of the file called the document information dictionary, or Info dictionary. It has been part of the PDF format since version 1.0 and holds eight entries — every one optional. A field can simply be empty, and an empty field is normal, not a fault.
| Field | What it records |
|---|---|
| Title | The document’s name, as set by its author or software. Some viewers show this in the tab instead of the file name. |
| Author | The person or organisation the document is attributed to — often copied from the account that set up the software. |
| Subject | A short description of what the document is about. |
| Keywords | Words associated with the document, usually separated by commas, meant to help with searching and cataloguing. |
| Creator | The application the document was written in before it became a PDF — for example, a word processor or design program. |
| Producer | The software that actually generated the PDF — a PDF library, a printer driver, or a scanner. |
| CreationDate | When the software says it first produced this PDF file. |
| ModDate | When the software says it last saved or changed the file. |
Two fields cause the most confusion. Creator is the program the document started in; Producer is the program that turned it into a PDF. A report written in a word processor and exported to PDF will often show the word processor as Creator and the PDF export engine as Producer. Both are just text the software wrote into the file, but together they sketch the document’s history.
Beyond this classic set, modern PDFs can also carry a second block called XMP, a packet of XML embedded in the file. XMP can repeat the same fields and add others, such as a document identifier. It also explains a puzzle you may meet: two viewers can show different titles or dates for the same file, because one reads the Info dictionary and the other reads the XMP packet. Neither is necessarily wrong.
Why so many fields are blank — and why dates can mislead
Check a few PDFs on your own computer and you will quickly find many fields empty. That is normal: most programs save PDFs without filling in the title, author, or keywords, because nobody asked them to. An empty author field usually means the export simply never filled it in, not that the document is anonymous by design.
Dates deserve a second look. CreationDate records when the software produced that particular PDF file — not when the content was first written. Convert or re-export a file and the dates can reset to the moment of that conversion while the content stays the same. A creation date from last week on a months-old report simply tells you when this copy was written. Metadata values are plain text any PDF editor can change, so a tidy set of fields proves nothing about authenticity — it is a clue, not a certificate.
How to check a PDF’s metadata
You do not need special software for a first look. Most PDF readers show the basics: open the PDF, find Document Properties (often under File), and read the Description tab, which typically lists title, author, subject, keywords, and the creation and modification dates.
That covers a quick check. A dedicated viewer gives a clearer read — including which fields are empty — because readers differ in which fields they display: some hide Creator and Producer entirely, and some prefer XMP values without saying so.
Manage My Tools’ free PDF Metadata Viewer reads exactly this: the stored title, author, subject, keywords, and creation date of a PDF. Choose a file, run it, and see the stored fields as the file carries them — or see plainly that a field is empty. The file is read in your browser and never sent to the site’s server, so nothing about it is recorded. It is a viewer, not an editor: it shows what is stored, invents nothing, and cannot change or remove metadata. If you also need a PDF’s size and page count, the site’s PDF File Size Inspector reports those alongside metadata.
Whichever route you use, check the final file you plan to send, not an earlier draft: editing, converting, or re-exporting can preserve, change, or add metadata. The copy you checked yesterday is not necessarily the copy you are sending today.
What to look for before you share a PDF
A short check before sending saves the awkward surprise you only discover when the recipient mentions it:
- A name you did not mean to share. Author is often filled in automatically from an account name — your full name on a CV, or a colleague’s name on a file you have since taken over.
- An old working title. Titles survive drafts: a report that began as “Draft v2 — DO NOT SEND” can keep that title in its metadata long after the cover page was rewritten.
- A subject line from another life. Subject and keywords never appear on the page, so a reused template can quietly carry a previous client’s name or project.
- Dates that contradict the story. A creation date from last week’s conversion, or a modification date older than the version you hold, is worth understanding before the file goes to someone who will notice.
- A software trail. Creator and Producer reveal your toolchain. Harmless for most sharing, but worth knowing about for a confidential tender.
None of this means metadata is dangerous by itself — most of it is boring, ordinary file information. The point is narrower: make sure the details travelling with the file are the ones you intend to share. As the University of Michigan’s Safe Computing guidance puts it, files can contain metadata that reveals more than you realise, so consider the impact before you send or post a file.
What checking can’t do: editing and removing metadata
Reading metadata is not the same as changing it — that is the honest limit of any viewer. If your check turns up a name or date you do not want in the file, you need a different step: your PDF editor’s document properties, or a dedicated metadata editor, where you can overwrite or clear the fields, save a new copy, and then check that new copy again, because that is the file that will actually travel.
Stripping metadata also does not make a document anonymous: the visible content — names, logos, signatures — still says what it says. And if a document must be verifiably authentic, such as a legal filing, changing its metadata can itself raise questions, so think before you edit.
PDF metadata vs photo metadata
If this idea feels familiar, it may be because photos carry their own version of it: a photo’s EXIF data records camera settings, dates, and sometimes location. The two are easy to confuse but not interchangeable — photo tools read EXIF, PDF tools read the Info dictionary and XMP. Our explainer on what EXIF data is and what your photos reveal covers the photo side, including its privacy angle.
Frequently asked questions
Does every PDF have metadata?
No. Every PDF can carry metadata, but many carry little or none: all eight classic fields are optional, and many programs export PDFs without filling them in. Blank fields are the common case, not a fault.
Does metadata change the document itself?
No. Metadata describes the document; it does not alter the pages, text, or layout. Changing a title field does not change the title printed on the cover page, and removing metadata removes nothing visible — which is exactly why it is so easy to overlook.
Is checking a PDF’s metadata private?
It depends on the tool. Some online tools upload your file to a server to read it. The Manage My Tools viewer reads the file in your browser, so it never leaves your device and nothing about it is recorded — a distinction worth checking before you use any tool.
Can I remove metadata with a metadata viewer?
No — a viewer only reads. Removing or editing metadata needs a PDF editor or a dedicated metadata tool, and you should always re-check the saved copy afterwards.
Check before you send
PDF metadata is small, boring, and easy to ignore — until the one time it is not. A title from an old draft, a name from an old account, or a date from a conversion can travel silently inside a file you thought was finished. Checking takes a couple of minutes, costs nothing, and tells you what your file says about itself before anyone else reads it.
Try it on the next PDF you are about to send: open the free PDF Metadata Viewer, choose the file, and read what it carries. If you work with PDFs regularly, the wider PDF Tools collection and the full all-tools directory cover the rest — merging, splitting, converting, and inspecting PDFs, all in your browser.
Sources and further reading
- Prepressure, “PDF metadata: how to add, use or edit metadata in PDF files” — https://www.prepressure.com/pdf/basics/metadata
- PDFCheck, “How to View PDF Metadata Online” — https://pdfcheck.online/blog/how-to-view-pdf-metadata-online
- University of Michigan Safe Computing, “Consider Metadata When Sending Files” — https://safecomputing.umich.edu/protect-privacy/consider-metadata