Resume File Name: What to Call the File Before You Upload It (2026)

By Roy6 min read

The filename is the only part of your resume that a recruiter reads before deciding whether to open it — and the only part that survives being downloaded into a folder alongside two hundred other applications.


Why the filename matters more than it should

When a recruiter downloads applications in bulk, the files land in one folder. Every candidate who uploaded resume.pdf collides into resume.pdf, resume(1).pdf, resume(2).pdf — and now nobody's name is attached to anything. The recruiter either renames them by hand or, more often, works from the ATS interface and never thinks about it again.

That second case is the important one. Most modern applicant tracking systems store your name from the parsed resume or the application form, so a bad filename rarely loses your application outright. The cost is narrower and more real: in the moments when a human is working with the raw file — forwarding it to a hiring manager, pulling it up months later, searching a shared drive — a file called resume-final-v3.pdf is invisible and Jordan-Ellis-Resume.pdf is not.

Treat it as free signal rather than a make-or-break rule. It costs ten seconds and it is one of the very few things about your application you fully control.


The format that works

Resume file naming: what to use and what to avoid
FilenameVerdictWhy
Jordan-Ellis-Resume.pdfBest defaultName first, purpose clear, no spaces.
Jordan-Ellis-Resume-Data-Analyst.pdfBest when tailoringSignals you customised it for this role.
Jordan_Ellis_Resume.pdfFineUnderscores are as safe as hyphens. Pick one and stay consistent.
Jordan Ellis Resume.pdfAcceptableSpaces work, but become %20 in some upload URLs.
resume.pdfAvoidCollides with every other applicant's file.
Resume-final-v3-USE-THIS.pdfAvoidShows your drafting process to a stranger.
Jordan-Ellis-Resume-Google.pdfRiskyOne paste error sends a rival company's name along.

Should you put the job title in the filename?

Only if the resume is genuinely tailored to that job. A role in the filename is a small claim that you customised the document, and it reads badly if the content underneath is generic. If you have tailored it — which you should be doing, see how to tailor a resume to a job description — then Jordan-Ellis-Resume-Data-Analyst.pdf is a clean, honest signal.

What to avoid is the company name in the filename. It creates exactly one failure mode, and it is a bad one: sending Jordan-Ellis-Resume-Google.pdf to a recruiter at Meta. The job title carries nearly all of the benefit with none of that risk.

If you are applying to many roles with tailored versions, the filename alone will not keep them straight for long. A job application tracker is the right place to record which version went where.

What to avoid, specifically

  • Version numbers and status words. v2, final, FINAL-final, USE-THIS, draft. These are notes to yourself that you accidentally published.
  • Dates. Jordan-Ellis-Resume-2026-08.pdf looks tidy in your folder and looks stale in a recruiter's inbox two months later. Keep dates out of the filename and in your tracker instead.
  • The word "CV" when applying in the US, or "resume" when applying somewhere that expects a CV. Match the local vocabulary of the posting.
  • Special characters beyond hyphens and underscores. Ampersands, slashes, hashes, and accented characters can be mangled by upload forms or rejected outright.
  • Very long filenames. Some portals silently truncate. Keep it under roughly 50 characters.
  • All lowercase or ALL CAPS. JORDAN-ELLIS-RESUME.PDF reads as shouting; jordan-ellis-resume.pdf reads as careless. Capitalise normally.

Does the file extension matter?

More than the name does. PDF is the right default for most applications because it preserves your layout exactly, and every mainstream ATS parses it. Send DOCX only when the posting explicitly asks for it — some staffing agencies do, because they edit resumes before forwarding them to clients.

Never upload .pages, .odt, or a Google Docs share link unless specifically requested. And export to PDF rather than printing to PDF or scanning, because a scanned resume is an image with no text layer for a parser to read. The full trade-off is in PDF vs DOCX for ATS resumes.

If you are unsure whether your exported file carries a clean text layer, run it through our free resume checker — it extracts the text the way a parser would, no signup required.


Frequently asked questions

What should I name my resume file?
Use FirstName-LastName-Resume.pdf, such as Jordan-Ellis-Resume.pdf. Leading with your name means the file identifies you when it sits in a folder with hundreds of other applications, and including the word Resume makes its purpose obvious at a glance. Skip version numbers, dates, and status words entirely.
Does the resume file name affect ATS scanning?
Not in any meaningful way. Applicant tracking systems parse the contents of the document and take your name from the resume text or the application form, so the filename is not a ranking factor. It matters at the human step instead — when a recruiter downloads, forwards, or later searches for the raw file.
Should I include the job title in my resume file name?
Only if the resume is genuinely tailored to that role, in which case Jordan-Ellis-Resume-Data-Analyst.pdf is a clean signal that you customised it. Avoid putting the company name in the filename — it adds almost nothing and creates a real risk of sending one employer a file named after a competitor.
Should my resume be a PDF or a Word document?
PDF by default, because it preserves your layout exactly and every mainstream ATS parses it reliably. Use DOCX only when a posting explicitly asks for it, which staffing agencies sometimes do because they edit resumes before passing them to clients. Always export to PDF rather than scanning, so the file keeps a readable text layer.
Can I use spaces in a resume file name?
Yes, spaces work on every major upload form, though hyphens or underscores are slightly safer because spaces become %20 in some URLs and can look untidy in a download link. Whichever you choose, stay consistent — mixing spaces and hyphens in one filename looks accidental.
Is it bad to name your resume file just 'resume.pdf'?
It is the one name genuinely worth avoiding. When a recruiter downloads a batch of applications, every generic resume.pdf collides and gets renamed to resume(1).pdf and resume(2).pdf, stripping your name from the file entirely. Your application still counts, but you have given up the small advantage of being identifiable.
Should I put the date in my resume file name?
No. A date makes the file look current the day you send it and stale a few months later, when a recruiter revisiting your application sees a filename from a previous quarter. Track which version you sent and when in a job application tracker instead of encoding it in the filename.
Optimize my resume