Your Resume Reveals More Than You Think: PDF & Word CV Metadata

The Scenario Nobody Warns You About

Picture this. You're at your desk on a Tuesday afternoon, your current employer's laptop open in front of you. You've spent lunch updating your resume — tightening the bullet points, tweaking the summary — and you export it to PDF. Then you upload it to three job boards and email it directly to a recruiter. Done.

What you don't realize: that PDF just told the world exactly where you work, what laptop created it, and that you edited it at 1:47 PM on a Tuesday. The Author field says your name from your company's Active Directory profile. The Company field says your current employer's name. The ModDate timestamp shows today. The revision count shows you've saved this version 14 times this week.

None of that is in your resume's text. All of it is in your resume's metadata.

This isn't hypothetical. Resume metadata revealing current employer details is a documented issue that career coaches flag with senior executives — people whose job searches carry the highest confidentiality stakes. But it affects anyone who edits a resume on a work computer, uses a corporate Office license, or builds on a company-provided template. That's a lot of people.

What Metadata Actually Lives Inside Your Resume

Open any PDF in Adobe Acrobat and hit Ctrl+D (or Cmd+D on Mac). You'll see a Document Properties dialog. Most people have never looked at it. Here's what can be sitting there, fully readable, in the resume they just sent out.

Author: The person registered to the software that created the document. If you wrote your resume in Microsoft Word on a work computer, this field often pulls from your corporate Windows account or Active Directory profile — sometimes even your manager's name if the template was originally theirs. If you're applying under a different name than your legal name, this field may out you immediately.

Company: Microsoft Office has always had an Organization field in its user profile. When you create a document using a company-licensed copy of Word, the Company field in the resulting PDF often reflects your employer's registered name. This is automatic. You didn't type it. You probably don't even know it's there.

Creation Date and Modification Date: These are timestamps that show exactly when the document was first created and when it was last saved. The ModDate is particularly revealing for confidential job searches — a resume modified yesterday afternoon, during work hours, signals active searching to anyone paying attention.

Revision Number: Word increments a revision counter every time you save the document. A resume sitting at revision 40 after two weeks of edits paints a very specific picture of how intensively you've been working on your applications.

Creator and Producer: The application used to create the file ("Microsoft Word 16.88") and the PDF conversion engine ("Acrobat PDFMaker 23.0"). This reveals your software stack, which is often enough to identify the organization — large enterprises tend to use standardized, licensed versions of Office and Acrobat.

Template Origin: Documents built on corporate templates can embed the template's file path — including folder names that reveal organizational structure. A path like C:\Users\jsmith\AppData\Roaming\Microsoft\Templates\Acme_HR_Resume_Template.dotx tells you the company, the employee's username, and the internal template naming convention in one string.

DOCX vs PDF: Different Formats, Same Problem

A lot of people assume that exporting from Word to PDF strips the metadata. It doesn't — not by default.

When you save a Word document as PDF using "Save As" or "Export," the PDF inherits metadata from the DOCX source. The Author, Company, Creator, and timestamp fields transfer. The revision count becomes embedded in the PDF's metadata stream. What you get is a new file format containing the same identifying information as the original.

The DOCX file itself carries even more. Word's Open XML format stores metadata in a docProps/core.xml file inside the document package. This includes the document's creator, last modifier, revision count, creation time, and last modification time. Word also maintains a Revision History — a log of every editor who's touched the file — in docProps/app.xml. And Track Changes, if it was ever enabled, stores every deletion and insertion with the author name attached.

Sending a DOCX directly (which some job postings request) gives the recipient access to everything a PDF would contain plus the full edit history if Track Changes was ever on. A recruiter opening a DOCX in Word can navigate to Review → Track Changes and see every sentence you cut, every phrasing you reconsidered, every version you abandoned.

What Recruiters and HR Actually See

Here's where it's worth being realistic about who looks at this and how.

Most ATS (Applicant Tracking Systems) — Greenhouse, Lever, Workday, iCIMS — are primarily parsing your resume's visible text to extract name, email, work history, and skills. The automated parsing layer isn't specifically hunting for Author metadata. But these systems store the original file you uploaded. And the people on the other end of those systems download that file.

HR coordinators, recruiters, and hiring managers who download your resume from an ATS receive the original file you uploaded — metadata intact. Checking Document Properties on a candidate's PDF takes about three seconds. Some recruiters do this routinely when vetting executive candidates for confidentiality reasons. Some hiring managers do it out of curiosity. Some HR departments do it as part of due diligence. The point isn't that everyone checks. The point is that anyone can, at any time, effortlessly.

For currently-employed job seekers, the specific risk scenario looks like this: you apply through a job board, the company downloads your PDF, an HR coordinator notices the Company field says "[Your Current Employer]" — now they know you're searching from inside that company. If they have any connection to your organization, that information could travel. If your company's HR department searches for their employee resumes on job boards (this happens), your metadata makes the connection explicit even if your resume's text is deliberately vague about your current role.

For our deeper dive into what's hidden in professional PDF documents beyond resumes, the hidden data in PDFs and business risk guide covers the full range of scenarios where document metadata creates exposure.

The Specific Risk for Currently-Employed Applicants

Let's be direct about the worst-case scenario, because it's real and it happens.

You're employed. You want to explore other opportunities — a reasonable professional decision. You've been careful: you haven't mentioned your search to colleagues, you're using your personal email, you've set your LinkedIn activity to private. You've done everything the career advice articles recommend.

But your resume was created on your work laptop using your company's licensed copy of Microsoft Office. The Author field contains your name from the corporate directory. The Company field contains your employer's name. The ModDate shows you saved it at 2:15 PM on a Thursday — during work hours. The revision count is 22, indicating heavy recent editing over the past two weeks.

That document just told a story. Not the story you intended — the story of an employee actively looking to leave, editing their resume on company equipment during business hours. If that resume lands with a recruiter who knows your industry and has contacts at your firm, if your HR department runs an employee resume search, if a hiring manager at the target company has any LinkedIn connection to your current employer — the metadata is the thread that connects you to your current job in a way your carefully worded resume text doesn't.

Career coaches who work with executives specifically flag this risk. One career consultant noted publicly that executive resume document properties reveal information that candidates would be "surprised" to see exposed — and that's for people whose job searches carry the highest professional stakes and who presumably have the most resources to manage them carefully.

How to Clean PDF Resume Metadata

There are a few paths here, and they have different trade-offs.

The fastest method for PDFs is using MetaClean's PDF metadata tool. Drop your PDF into the tool, click Remove Metadata, download the clean version. Everything is processed in your browser — your resume never leaves your device. The tool removes Author, Company, Creator, Producer, creation timestamps, modification timestamps, subject, keywords, and all other standard PDF metadata fields. It takes under a minute, and you can verify the result by re-opening the cleaned file in the same tool to confirm all fields are empty.

The manual path in Adobe Acrobat (full version, not Reader): File → Properties → Description tab — clear all visible fields. Then File → Properties → Custom tab — remove any custom fields. This gets the visible metadata but doesn't always reach XMP streams embedded deeper in the file structure. For a complete removal, a dedicated tool is more reliable.

The print-to-PDF method works in a pinch: open your PDF and print it to a PDF printer (Mac's built-in "Save as PDF," Windows' Microsoft Print to PDF). This creates a new file without inheriting most source metadata. The downside is it can slightly affect formatting and it won't always strip everything from complex PDFs.

How to Clean Word (DOCX) Resume Metadata

Word has a built-in tool called Document Inspector, and you should run it every time you export a resume you intend to share externally.

In Microsoft Word: File → Info → Check for Issues → Inspect Document. Run it with all categories checked. The Inspector will flag: comments, revisions and tracked changes, document properties and personal information, hidden text, headers and footers data. Click Remove All next to every category that returns results. Save the document. Then export to PDF.

A few things to do before running Document Inspector:

• Accept all tracked changes (Review → Accept All Changes). Once you remove them, they're gone — so confirm the final text is right first.
• Delete all comments.
• Disable Track Changes if it's currently on.
• Check that your personal Author info in Word's preferences is what you want it to be (or blank it out): File → Options → General → Personalize — the name and initials here stamp every document you create.

After running Document Inspector and exporting, run the resulting PDF through MetaClean's PDF tool as well — it's worth the extra 30 seconds to confirm the export didn't reintroduce anything.

For DOCX files you need to submit directly (rather than as PDF), the Office metadata remover handles the full Open XML metadata package. Our Office metadata tool strips the hidden properties from DOCX, XLSX, and PPTX files in the browser, no upload required.

How to Verify Your Resume Is Actually Clean

Don't just trust that the cleanup worked. Verify it.

For a PDF: open it in Adobe Acrobat Reader (free), press Ctrl+D or Cmd+D. The Document Properties dialog will show the Description, Custom, and Initial View tabs. Everything in the Description tab should be blank or show only generic software information — no names, no company names, no meaningful timestamps. The Author, Subject, Keywords, Title fields should all be empty.

Alternatively: drop the cleaned PDF back into MetaClean's PDF viewer. The metadata panel will show exactly what's in the file. If the Author, Company, and Creator fields are empty, you're clean. If they still show values, run the cleanup again.

For a DOCX: right-click the file in Windows Explorer → Properties → Details tab. This shows the document's properties as Windows sees them. Every name field should be blank. On Mac, Get Info (Cmd+I) on the file and expand the More Info section.

Also check the filename itself. A filename like "Smith_Resume_v14_FINAL_REVISED.pdf" tells its own story. Use something clean: "[FirstName]_[LastName]_Resume.pdf" with no version numbers or draft indicators.

Cover Letters, Portfolios, and References

The same metadata risks apply to everything else you send. Cover letters created from corporate templates often carry the same Author and Company fields as your resume — sometimes worse, because cover letters are often created fresh for each application and never go through any cleanup workflow.

Portfolio PDFs assembled from multiple source documents can carry metadata from every source. A design portfolio built from client project files might embed the client's name, your work email, and project-internal document identifiers. For consultants or contractors who've worked across multiple organizations, this is a meaningful confidentiality exposure.

Reference lists are a lower risk (usually just a simple document) but still worth checking if created from company templates. Writing samples, if you're submitting them for editorial, writing, or research roles, are the highest-risk documents of all — these are often actual work product created on company time, with full company metadata intact.

For a broader look at how PDF metadata creates risk across professional contexts, our complete guide to removing PDF metadata covers all document types and use cases. And if you need to understand precisely what's hiding inside a given file before you clean it, the guide to removing author names from PDFs walks through the field-by-field anatomy of what's stored and where.

For the LinkedIn-specific dimension — what happens when your resume metadata is visible to the platform itself and to everyone who downloads your document from your profile — our piece on LinkedIn document metadata and resume privacy covers that scenario in detail.

Frequently Asked Questions

Can recruiters actually see my resume's metadata?

Yes — anyone who downloads your PDF or Word file can view its metadata in seconds. In Adobe Acrobat Reader, it's Ctrl+D (or Cmd+D on Mac) to open Document Properties. In Windows Explorer, it's right-click → Properties → Details. No special tools required, no technical skill needed. HR coordinators and recruiters who download files from an ATS receive your original uploaded document with all its metadata intact.

Does exporting from Word to PDF remove the metadata?

No — by default, exporting or saving as PDF in Microsoft Word transfers the document's metadata fields (Author, Company, Creator, timestamps, revision count) directly into the PDF. You need to run Word's Document Inspector and clear personal information before exporting, and then optionally run the resulting PDF through a tool like MetaClean to confirm all fields are clean.

What does the Company field in my resume reveal?

The Company field is pulled from your Microsoft Office user profile and often reflects the organization name registered to your software license. If you're using a company-licensed copy of Office, this field typically contains your current employer's name — which is embedded in every document you create with that installation, including your resume, without any action on your part.

Does ATS software read resume metadata?

Modern ATS platforms like Greenhouse, Lever, and Workday primarily parse the visible text of your resume to extract structured information. They don't typically flag or process document metadata as part of candidate screening. However, the original file you uploaded — metadata included — is stored and accessible to every human recruiter or HR coordinator who downloads it from the system.

I created my resume on a personal computer. Do I still need to clean metadata?

It's still worth cleaning. A personal computer's Office installation can have your full name as Author, timestamps revealing when you created and edited the document, and revision counts that reflect your editing history. The privacy concern is lower than for company hardware, but the Author field will still identify you and the modification date will show exactly when you last updated your resume.

Does MetaClean upload my resume to a server?

No — MetaClean processes all files entirely in your browser. Your resume is never uploaded to any server, logged, or retained. This is by design: a metadata removal tool that uploads your resume to clean it would create the exact kind of privacy exposure it's supposed to prevent.