Resume PDF File Name: What Should You Use?

What should you name your resume PDF file?

Use FirstName-LastName-Resume.pdf for your resume PDF file name — for example, Ana-Reyes-Resume.pdf. Keep the .pdf extension visible, avoid spaces and special characters, and add the job title for tailored versions (Ana-Reyes-Marketing-Manager.pdf). Never submit a file named resume.pdf or anything with the word "final" in it.

PDFs deserve their own naming rules because they travel differently than Word docs. A PDF is a finished artifact — it locks your layout, carries your fonts, and often gets parsed by an ATS before any human opens it. The filename is metadata the machines read too. Get it right once and the habit pays off across every application. Run through the filename checklist before each upload.

The format that works everywhere

FirstName-LastName-Resume.pdf is the universal default. It's searchable in a recruiter's downloads folder, sortable, and unambiguous. For role-specific versions, append the title: FirstName-LastName-Title-Resume.pdf — Ana-Reyes-Marketing-Manager.pdf tells everyone exactly what this version is for without opening it.

Two technical rules matter more for PDFs than for other files. First, keep the extension lowercase and visible: ".pdf" not ".PDF" — some Linux-based ATS parsers are case-sensitive about extensions. Second, export directly to PDF from Word or Google Docs rather than printing and scanning; a scanned PDF is an image, and many parsers can't read it at all. Test your PDF before applying to catch this.

ATS-safe characters only

Applicant tracking systems ingest your filename along with the file. Stick to letters, numbers, hyphens, and underscores. Characters like #, %, &, /, and parentheses can choke older parsers or get URL-encoded into gibberish when the file passes through email and portals. "Ana Reyes (Final) Resume.pdf" might arrive as "Ana%20Reyes%20%28Final%29%20Resume.pdf" — still readable, but why risk it?

Accented characters deserve a thought too. If your name has accents (José, François), the unaccented version in the filename (Jose-Garcia-Resume.pdf) avoids encoding issues while your resume header keeps the correct spelling. The filename is plumbing; the resume is the presentation.

Version control without the embarrassment

Everyone iterates. The trick is keeping the mess private. Work in files named "Resume-DRAFT-2026-10-22.pdf" all you want — just rename the winner to the clean format before sending. Never let a version number, the word "draft," or "FINAL" reach a recruiter. I've seen "Resume-FINAL-really-final-v9.pdf" submitted to a detail-oriented accounting firm. You can guess how that went.

A simple system: one folder per job search, filenames with dates for drafts (Ana-Reyes-Resume-draft-2026-10-22.pdf), and the clean name reserved for the exact file you attach. When you tailor for a role, save the tailored PDF with the job title in the name so next month you know which version went where.

The 60-second naming ritual before every upload

Make this a habit and you'll never send a bad filename again. One: confirm the content is final — open the PDF and skim it, because renaming a file you'll edit tomorrow wastes the effort. Two: rename to the clean format with the role appended if tailored. Three: check the file size (under 2MB is safe for every portal; compress images if it's bloated). Four: verify it's a real text PDF, not a scan — select a line of text with your cursor; if you can't select it, re-export.

Five: attach it to a draft email to yourself and download it back, checking the name survived intact. This sounds paranoid until the first time a portal renames your file to "upload_7391.pdf" and you realize you can't control everything — but you can control what you submit. Sixty seconds, five checks, zero filename regrets.

When the posting names the format, obey it

Sometimes a posting specifies: "Name your file LastName_FirstName_Resume.pdf" or "upload as DOCX." When it does, follow the instruction exactly — it's often a compliance filter, and deviating can auto-reject you. Only when no format is specified do you default to FirstName-LastName-Resume.pdf. And if they ask for DOCX instead of PDF, send DOCX (see when each format wins) but keep the same clean naming logic.

Frequently asked questions

Should the PDF file name include my phone number or email?

No — keep personal contact details inside the resume, not in the filename. A filename with your phone number looks odd, travels through systems you can't control, and adds nothing. Name plus "Resume" plus optional role is the complete recipe.

Does capitalization in the file name matter?

For readability, yes: Ana-Reyes-Resume.pdf scans better than ana-reyes-resume.pdf. For systems, mostly no — but keep the .pdf extension lowercase as noted above. Consistency between the filename's name and your resume header's name matters more than case.

Can I use the same file name for every application?

For the generic version, yes — that's the point of a clean default. But when you tailor a resume for a specific role, save it with the role in the name. Six months later, "Ana-Reyes-Resume.pdf" won't tell you which of your five versions went to which company.

What if my builder exports with a weird default name?

Rename it immediately after export — most resume builders default to something like "resume-2026-10-22.pdf" or your account username. Thirty seconds in your file manager fixes it. Make renaming part of your export ritual, right alongside the PDF pre-send checklist.

Should I rename old resume PDFs sitting in my folders?

Only the ones you'll actually send. Archive the old drafts as-is (rename the folder, not each file) and give your current master copy the clean name. Going forward, the 60-second ritual above keeps every new export tidy from birth — no more archaeological digs through "Resume-old-good-one.pdf."

Using a resume PDF file name can make this task easier and more efficient when you need a simple online solution.

A resume PDF file name is especially useful when you want a quick browser-based workflow.