Resume Formatting · 4 min read
Your file name is the first thing a recruiter sees — before a single word of your resume. Make it count with these proven formats.
What should you name your resume file?
Name your resume file FirstName-LastName-Resume.pdf — for example, Maria-Garcia-Resume.pdf. Include your full name so recruiters can find it, add the target role for tailored applications (Maria-Garcia-Project-Manager-Resume.pdf), and never use vague names like resume-final-v2.pdf. Always use PDF unless the posting asks otherwise.
This tiny detail punches above its weight. Recruiters download hundreds of files into one folder, and yours sits there labeled whatever you called it. "Resume.pdf" disappears into a sea of identical names; "resume_FINAL_v2(1).pdf" quietly signals disorganization before they've read a word. Thirty seconds of naming discipline is the cheapest professionalism upgrade in your whole application. Our resume filename checklist covers the full pre-upload routine.
The gold-standard formats (copy these)
These three cover nearly every situation:
FirstName-LastName-Resume.pdf — the default. Clean, searchable, professional. Example: David-Okafor-Resume.pdf.
FirstName-LastName-JobTitle-Resume.pdf — for tailored applications. Example: David-Okafor-Data-Analyst-Resume.pdf. It tells the recruiter instantly which role this version targets, which matters when you're applying to several openings at one company.
LastName-FirstName-Resume-Year.pdf — some prefer surname first for alphabetical sorting: Okafor-David-Resume-2026.pdf. Any consistent, readable order works.
Use hyphens or underscores between words — never spaces, which some older systems mangle into %20 strings. Capitalize each word for readability. And keep the extension: PDF beats DOCX for preserving your formatting across devices.
When to add the job title or company
Add the target job title when you're customizing a resume for a specific role — it keeps your versions organized and signals relevance at a glance. Adding the company name (David-Okafor-Resume-AcmeCorp.pdf) is smart when emailing applications directly; it shows intention and helps the hiring manager file it.
Skip the extras for one-click portal applications where the system renames files anyway — but even then, a clean original name costs nothing. Never include salary expectations, dates of birth, photos, or anything personal in the filename. The filename is a label, not a billboard.
Mistakes that make you look careless
The hall of shame, all real examples I've encountered: "resume.pdf" (which one of 400?), "Resume_Final_FINALv3.pdf" (indecision as a filename), "CV 2023" (outdated and vague), and my personal favorite, "Document1.pdf." Special characters — #, %, &, / — can break uploads or display weirdly in an ATS, so strip them out.
Also watch the version-number habit. If your file says v7, the recruiter wonders what was wrong with v1 through v6. Finalize the content first, then name it once, confidently. And double-check the actual file you're attaching — the number of people who've sent "Resume-DRAFT-do-not-send.pdf" is higher than anyone admits.
What recruiters actually see on their end
Picture the recruiter's screen: a downloads folder or ATS attachment list with 300 files. Yours appears as one line of text next to everyone else's. A clear name — "Priya-Nair-UX-Designer-Resume.pdf" — lets them find you with Ctrl+F in two seconds flat. A vague one forces them to open the file just to learn whose it is, and every extra click is friction working against you.
There's a subtler effect too. Hiring managers forward resumes internally — "take a look at this candidate" — and the file name travels with it. A professional filename keeps looking professional through three rounds of forwarding. A sloppy one becomes a quiet joke in a Slack channel. You can't control what happens after you hit send, but you can control the label on the package.
Don't forget the cover letter
Apply the same logic: FirstName-LastName-Cover-Letter.pdf, or add the role for targeted versions. When submitting both files, matching name formats look deliberate and organized — a small coherence signal that hiring managers notice subconsciously. Keep both files in the same folder so you never attach the wrong version in a rush.
Frequently asked questions
Should I include the year in my resume file name?
Optional but harmless — FirstName-LastName-Resume-2026.pdf works fine and helps you track versions across years. Just don't let an old year linger; a "2023" in the filename on a 2026 application suggests a stale, mass-sent resume.
Is it okay to use spaces in the file name?
It usually works, but don't risk it. Some applicant tracking systems and email clients replace spaces with %20 or underscores unpredictably. Hyphens are universally safe and more readable than underscores on screen.
What file format should my resume be?
PDF in almost all cases — it locks your layout so what you see is what they see. Only send DOCX if the posting explicitly requests it (some older ATS portals do). See the resume PDF checklist for the full pre-send verification.
Does the file name really affect hiring decisions?
Not directly — no one hires you for a filename. But it's part of the first impression: a clean, professional name signals attention to detail, while "resume_final_FINAL.pdf" plants a seed of doubt. In a stack of equally qualified candidates, small signals compound.
Should the file name match the name on my resume header?
Yes, keep them consistent — if your resume header says "Priya Nair," the file should be Priya-Nair-Resume.pdf, not P-Nair-CV.pdf. Consistency avoids confusion when a recruiter searches their files for your name later, and it looks deliberate rather than thrown together.
Using a best resume file name examples can make this task easier and more efficient when you need a simple online solution.
A best resume file name examples is especially useful when you want a quick browser-based workflow.