Your Resume PDF Is Telling on You: The Metadata Recruiters Actually See

A recruiter opens her inbox on a Monday morning. Forty-seven new applications for a marketing manager role. She clicks the first attachment and before she reads a single word on the resume itself, the filename tells her everything she needs to know: NASTY_ANGEL.DOC.

That is a real story. Recruiters have been sharing these gems for years — the applicant who forgot to rename their file before sending it out into the professional world. But here is the thing: the filename is just the beginning. Your resume PDF is carrying a surprising amount of baggage that you probably never meant to pack.

What Recruiters See Before They Read Your Resume

Every PDF carries metadata — invisible properties embedded in the file that describe when it was created, who made it, and what software produced it. Most people never look at this information. Recruiters do. Not all of them, but enough that it matters. Right-click a PDF, select "Properties" or "Get Info," and there it is: a dossier about your job search that you did not write.

Here is what a typical resume PDF reveals:

Every line in that box is telling a story you did not intend to share. Let us walk through what each one says to the person deciding whether to call you.

The Author Field: Who Actually Wrote This?

When the "Author" field says "ResumeFactory.com" or "TopResumeBuilder" or any professional resume writing service, the recruiter now knows you paid someone to write your resume. That is not necessarily disqualifying — plenty of strong candidates use resume services. But it does raise a question: if the polished language on this page is not yours, what will the interview sound like?

Worse, sometimes the author field shows a completely different person's name. Maybe you started from a friend's resume as a template. Maybe you downloaded a sample resume and edited it. Either way, the recruiter is now looking at a document attributed to "Michael Chen" submitted by someone named Sarah Williams — which can raise questions before the recruiter reads a word.

The Creation Date: A Three-Year-Old Resume

A resume created in 2023 and modified in 2026 tells the recruiter that this is a recycled document. You have been updating the same file for three years. That might mean you have been job-hunting for three years. It might mean you update your resume regularly as a career habit. But the recruiter does not know which one, and in a stack of forty-seven applications, ambiguity does not work in your favor.

The modification date is equally revealing. If you are applying for a job posted yesterday and your resume was last modified six months ago, the recruiter can see that you did not tailor this version for their specific role. You sent the same document you have been sending to everyone.

The Title Field: Your Internal Filing System, Exposed

The PDF title property often inherits the original document's filename from when it was first created. So even if you carefully rename the file to "Sarah_Williams_Marketing_Manager.pdf" before attaching it, the title metadata might still read "Resume_SALESJOB_highersalary.docx" or "Copy of Copy of Mike_template_2.docx" or whatever you originally saved it as. Some PDF viewers display this title in the tab bar instead of the filename, so the recruiter sees it immediately.

Recruiters have reported seeing title fields like "Resume for companies that pay more than 80k" and "Application backup — if Google rejects me." These are real. People do not realize this field exists.

Tracked Changes: The Salary Negotiation You Left In

This one is rarer with PDFs but devastating when it happens. If you exported your resume from a Word document that had tracked changes enabled, and those changes were not fully accepted before export, the revision history can sometimes survive in the PDF. Recruiters have found drafts where the applicant had different salary expectations written for different companies — visible as edited text in the document properties or comments.

Even without tracked changes, the "Comments" or "Subject" metadata fields occasionally contain notes the applicant left for themselves: "Need to remove the gap year" or "Exaggerated the project lead role — fix if they ask." Notes like these, if spotted, can undermine an otherwise strong application.

How to Clean Your Resume PDF in 60 Seconds

The good news is that this takes less than a minute to fix. Before you send your resume to anyone, clean the metadata:

1. Open the Metadata tool. Go to pdfb2.io/metadata in your browser.
2. Upload your resume PDF. The file is processed in your browser — it is not uploaded to any server. (Ironic, given the topic, but it means your resume does not end up in yet another database.)
3. Review the metadata. You will see every property embedded in your PDF: author, title, subject, creator, creation date, modification date, and any custom properties.
4. Edit or remove the fields. Set the author to your actual name. Clear the title field or set it to your name and the role. Remove any comments or subject lines. The creation and modification dates can be updated to today.
5. Download the clean PDF. Save the updated file and use this version for all your applications.

The Quick Checklist Before You Hit Send

Run through this every time you submit a resume, cover letter, or any professional document as a PDF:

• Filename: FirstName_LastName_Role.pdf — clean, with no version numbers or internal notes.
• Author field: Your name. Not your resume writer. Not the person whose template you borrowed.
• Title field: Your name, the role title, or blank.
• Creation date: Recent. A document created today for a job posted yesterday shows you made the effort.
• Comments and subject: Empty. No internal notes, no salary ranges, no strategy memos to yourself.
• Creator software: Less critical, but "ResumeBuilder Pro Trial Version" is a detail some recruiters notice.

A resume is a first impression. The content, the formatting, the language — applicants spend hours getting all of that right. Metadata is a sixty-second fix that keeps file properties from telling a different story than the resume itself.