PDF Metadata

The formula

• PDF metadata lives in the document info dictionary embedded in the file.
• Creation / modification dates are stored in PDF date format (D:YYYYMMDDHHmmSS).
• Page count is the number of page objects in the PDF catalog.
• File size is the total number of bytes in the file on your device.

A worked example

A report PDF shows Title: Not set, Creator: Microsoft Word, Pages: 12, Created: 3/4/2026, 9:14:22 AM, and File size: 184.5 KB, all revealed without uploading the file anywhere.

More about the PDF Metadata

The story this data tells about you

Here is the scenario that surprises people: you export your CV from Word and email it to a recruiter. The PDF quietly carries Author: your full name, Company: your current employer, and a creation date from three weeks ago. None of it is secret, any recipient can see it, but most senders have no idea it is there.

Checking first takes ten seconds and lets you decide what goes out with your name on it. For client deliverables and job applications, it is a small professionalism habit with an outsized payoff.

Reading the fields like a pro

Title, Subject and Keywords are often blank, 'Not set' is completely normal and just means the PDF does not contain that field. Creator is the app that made the document (Microsoft Word, for example); Producer is the PDF engine that wrote the file. Dates use the PDF date format, and the page count and file size are measured straight from the file.

A mismatch can be informative too: a 'contract' whose creation date is yesterday but whose content claims to be from 2019 deserves a second look. Metadata will not prove fraud, but it is a reasonable first question.

What this viewer does not do

It is deliberately view only, it reads your file and changes nothing, so there is no risk of corrupting a document by inspecting it. If you want to edit or strip metadata, you need a dedicated metadata editor; this tool will not do that job.

It also cannot reveal what is not there, and encrypted files that need a password may refuse to show their metadata at all. Those are limits of the format, not the tool.

The pre send checklist

Before emailing anything sensitive, run through this: check the author field (is it you, or a colleague whose template you borrowed?), the creation date (does it match the story?), and the file size (is it reasonable for the content?). Ten seconds, three fields, zero surprises.

For job applications specifically: export to PDF, check the metadata, and if the author field shows something odd, fix it in the source document and re export. Recruiters do notice, or rather, they notice when something looks off.

Metadata in received documents

The same reading skills work in reverse. A supplier invoice with a producer field showing a free online converter and a creation date of this morning is worth a closer look than one exported from accounting software last month.

Do not over read it, though: metadata is circumstantial, not proof. Use it to decide which documents deserve verification, not to convict anyone.

Cleaning metadata before sharing

This viewer only reads, but knowing what is there is the first step to controlling it. To actually remove metadata, open the source document (Word, InDesign) and clear the author, company and comments fields in document properties, then export a fresh PDF.

For sensitive documents, some organizations run all outgoing PDFs through a metadata scrubber. If you handle client data regularly, ask your IT team. It is a solved problem, and far more reliable than remembering to check each file manually.

The nuclear option for maximum privacy: print to PDF from a viewer, which creates a fresh file with minimal metadata. You lose some fidelity (it re renders), but for a final share copy, it is the cleanest slate.

Metadata in legal discovery

In litigation, document metadata (author, creation date, edit history) can be evidence. This viewer shows you what is there, but for legal purposes, the metadata must be preserved forensically, not just viewed.

Never edit and re save a document that might be evidence; even opening and saving can alter metadata timestamps. Work from copies, keep the original untouched, and let your legal team handle the chain of custody.

For everyday business, though, the lesson is simpler: assume everything you put in a document's properties is visible to recipients. Type accordingly.

A worked check on a contract you are about to sign

Suppose a supplier sends you a 12 page agreement as a PDF. The viewer shows the Creator as a word processor, the creation date as 4 March, and the modification date as 18 March, exactly 14 days later. The Title field reads Not set, the Author field carries a personal name you do not recognise, and the file size is modest. Nothing here is alarming by itself, but together the fields tell you this file was drafted, revised over two weeks, and exported at least once after its first draft.

Read a modification gap the careful way. A later modification date does not prove deception, because innocent exports, signature tools, and page merges all rewrite that date. What it does justify is one calm question about which version you hold. If the other side insists the file was finalised on 4 March, yet the record shows changes on 18 March, ask what changed in between and request the final signed copy for comparison before you rely on it.

Mistakes people make when reading metadata fields

The commonest mistake is treating the Author field as proof of who wrote the document. That field usually comes from the name registered in the software or the computer account, so it can name an assistant, a template designer, a previous employee, or nobody meaningful at all. It is a clue about the file’s history, never a verdict about authorship, and any serious dispute needs far stronger evidence than one editable field.

The opposite mistake is assuming that blank fields mean a file is clean. A PDF can show almost no document information yet still carry comments, form entries, attachments, layers, or earlier content tucked inside its structure. This viewer reports the document information dictionary and the XMP stream, which covers what most recipients can casually see. For a sensitive release, treat a tidy result as a good first pass, not as a forensic guarantee.

Document information versus XMP: which record should you trust?

A PDF can store descriptive details in two places. The older document information dictionary holds the familiar Title, Author, Subject, and Keywords fields, while an XMP stream can carry a richer, more structured record that publishing and photography workflows prefer. Many applications update one store and neglect the other, so the two can disagree, one title in the document information, a slightly different title inside the XMP data for the very same file.

When the two records conflict, neither is automatically the liar. Prefer the record that matches how the file will actually be used: browsers and search tools lean on the document information title, while archive and asset systems often read XMP. Before publishing or filing an important document, make both records agree, because a mismatch you leave behind becomes a confusing discrepancy that someone else has to explain later.

Why PDF metadata deserves a look

The classic fix takes thirty seconds. Open report.pdf and look at the pre filled form: title says "Untitled", author is blank. Type "Q3 Sales Report" as the title, add your company as the author, maybe "quarterly results, sales" as keywords. Press Apply Metadata, download the file. The pages are pixel identical; the properties panel now shows a document that looks like someone competent made it.

When does this actually matter? Publishing: whitepapers, ebooks and portfolios with proper titles get found and look professional. Sharing: scrubbing author names before a file goes to people who should not see them. Archiving: future you searching a hard drive for "Q3 Sales Report" will thank present you. And compliance: some organisations require correct document properties on official publications. This is the five minute way to comply.

What the editor changes, and what it leaves alone

A few field by field tips. Title should describe the document, not the filename. "Q3 Sales Report" beats "report_final_v2". Author can be a company rather than a person. Keywords are comma separated phrases, not a paragraph; five honest ones beat fifty stuffed ones. Leave any field blank and it keeps its current value, so you only change what needs changing. And always re open the downloaded file's properties to confirm, trust, then verify.

One more thing worth knowing: this edits only the standard document information fields (title, author, subject, keywords, creator). It does not touch the visible pages, does not remove watermarks, and does not strip everything the way a dedicated sanitiser might, some PDFs carry additional XMP metadata blocks that this tool does not rewrite. Encrypted files are refused. Free, unlimited, and private by design.

A worked clean up: one resume PDF, five fields

Suppose you are about to send your resume to an employer. You open it here and the pre filled form tells an embarrassing story: the title reads “Microsoft Word, resume_final2”, the author is a nickname from your laptop account, the subject is blank, and the creator names the app you built it in. A recruiter who opens document properties sees all of that before your work history. Two minutes of editing fixes the file’s first impression without touching a single visible word.

Here is the cleaned version, field by field. Title becomes your name plus the role. “Ayesha Khan, Marketing Manager Resume”, because the title is what appears in browser tabs and saved file lists. Author becomes your full professional name. Subject carries one honest line: “Application for Marketing Manager position”. Keywords hold five or six terms a searcher would actually type, such as the role title, your city and your strongest tools. Creator can stay as it is; it merely records which program produced the file.

Verification takes thirty seconds and should never be skipped. Download the edited copy, open it in your usual reader, and check the document properties panel against what you typed. Confirm the pages look untouched. They will, because only the property fields changed, and then send the new file, not the original sitting next to it. Sending the unedited twin by mistake is the most common way this whole exercise gets wasted.

Three layers people confuse: content, filename and metadata

A PDF presents itself in three separate layers, and this tool edits exactly one of them. The content layer is the visible pages, the words, tables and images a reader sees. The filename is the label your operating system shows in folders. The metadata layer is the document’s internal property card: title, author, subject, keywords and creator, written inside the file itself. Renaming the file changes layer two only; the “Untitled” a browser tab shows comes from layer three, which is why renaming never fixes it.

The distinction decides real tasks. A document management system, a shared drive or a recruiter’s inbox search may index the metadata title and keywords rather than the filename, so a file named perfectly can still surface badly if its internal title is junk. Conversely, scrubbing the author field for privacy does nothing to a filename that gives you away, “khan resume confidential.pdf” announces its owner no matter what the properties say. Check all three layers before any file leaves your hands.

Knowing the layers also tells you what this editor cannot do. It does not rewrite the visible pages, so a name printed in a header stays printed. It does not rename the file on your disk. And as the existing guide notes, it edits the standard property fields rather than every extended metadata block a file might carry. Match the tool to the layer that is actually wrong and the fix takes minutes; attack the wrong layer and the problem survives your effort completely.

Mistakes that leave private details behind

The classic failure is editing the copy and sending the original. Both files sit in the same folder with near identical names, and the email gets the wrong attachment. Give the edited version a clearly different filename, add “-clean” or the new title to it, and open the exact file you attached before pressing send. Ten seconds of checking beats explaining to a client why their competitor’s name was in the author field of your proposal.

A second mistake is checking only the title. Authors are leaked by the fields nobody reads: the creator string revealing internal software, keywords carried over from a template naming a previous client, a subject line written for a different recipient. Read every pre filled field the tool shows you, including the boring ones, and clear or replace anything that belongs to another context. Metadata hygiene is a whole panel habit, not a single field fix.

Finally, remember that a PDF is often converted from something else, and the source can leak back in. If you edited the PDF but later re export from the original Word or design file, the fresh PDF inherits the old application’s metadata all over again, nickname and all. For documents you publish repeatedly, fix the properties in the source application’s settings too, then use this editor as the final check on every exported copy before it goes out.

How to use the PDF Metadata

1. Choose a PDF file from your device.
2. Click "Analyze PDF" to read its metadata.
3. Review the title, author, dates, page count and file size.
4. Use Reset to clear the results and check another file.