Name your resume file with your full name, the word Resume, and, if you tailor it, the target role, joined by hyphens or underscores rather than spaces, for example jordan-lee-resume-product-manager.pdf. The file name is the first thing a recruiter sees before opening the document, and many applicant tracking systems store and display it against your record. A clear name makes you findable and reads as organised; a generic name like resume.pdf collides with every other applicant and disappears into a folder.
The overlooked detail
The detail almost everyone skips
The name you save your resume under is the first thing a recruiter sees, before they open a single line of it. It shows up in an email attachment list, in a download folder, in an applicant tracking system, and on the tab of whatever opens it. Most people never think about it. They export whatever the software suggested and send it, which is how thousands of inboxes end up holding a dozen files all called resume.pdf or document1.docx.
That is a missed opportunity, and occasionally a real cost. A recruiter handling fifty applications saves attachments into a folder. If yours arrives as resume.pdf, it collides with every other resume.pdf, gets renamed or overwritten, and becomes hard to find by name later. A file called jordan-lee-resume.pdf sits in that folder as a small, quiet piece of professionalism, easy to locate and clearly yours.
None of this decides whether you get the job. But hiring is a game of small signals, and a clean file name is one you fully control. It costs nothing, takes ten seconds, and it is the kind of detail that a careful reader notices and a careless one benefits from without knowing why.
The touchpoints
Where your file name actually gets read
The file name is not a formality that lives on your own machine. It travels, and it is read at several points where you want to look organised rather than generic.
Inbox
The recruiter attachment list
In an email client, the attachment shows its file name before anyone opens it. A clear name reads as organised; a generic one reads as one of many. It is the first impression before the first impression.
ATS
The applicant tracking system
Many systems store and display the original file name against your record. A descriptive name makes you findable in a search of hundreds of candidates; a name like final2.pdf makes you a needle in a haystack.
Folder
A shared hiring folder
When a team downloads candidates into a shared drive, file names sit side by side. Yours competes for clarity against everyone else. A name with your full name in it never gets confused with another applicant.
Search
A later keyword search
Weeks after applying, a recruiter may search their files for your name to reopen you. If your name is in the file name, you surface instantly. If it is not, you may as well not be there.
Tab
The open document title
When someone opens your resume, the file name often shows in the window or tab. A tidy name is a tidy final impression as they read; a name like untitled-1 is a small distraction at the worst moment.
Version
Your own drafts
A clear convention helps you too. When you keep several tailored versions, a naming pattern stops you attaching the wrong draft to the wrong application, which is a genuine and common mistake.
The convention
A resume file-naming convention that works
A good convention is boring on purpose. It should be predictable, human-readable, and free of anything that trips up software. This one works everywhere.
Lead with your full name.
Start the file name with your first and last name. That is the single most useful thing in it, because it is what a recruiter searches for and what makes the file unmistakably yours.
Say what the document is.
Add the word Resume, or CV if that is the term in your field. A name like jordan-lee-resume tells anyone exactly what they are looking at without opening it.
Add a role only if you tailor.
If you send different versions, append the target, such as jordan-lee-resume-product-manager. It helps you attach the right file and shows the reader the document was made for them, not mass-mailed.
Use hyphens or underscores, not spaces.
Spaces can turn into awkward codes in a link or break an upload on older systems. Join words with hyphens or underscores so the name stays clean everywhere it travels.
Keep it short and plain.
Avoid dates, version numbers, and words like final or draft in the sent file. Skip special characters entirely. A reader should see a finished, confident document, not your editing history.
The failure modes
The naming mistakes that cost you
Every one of these is common, and every one is fixable in the ten seconds before you hit send. Rename the file, then attach it.
Generic
resume.pdf and document1
A generic name collides with every other applicant and vanishes into a folder. It is the single most common naming error and the easiest one to fix.
Versions
resume-final-v3-final
Version tags and the word final look unprofessional and reveal your process. Strip them before you send. The recipient does not need to see that this was your fourth attempt.
Spaces
Spaces and odd characters
Spaces, slashes, ampersands and accents can break uploads or turn into unreadable codes in a link. Stick to letters, numbers, hyphens and underscores.
Dates
Burying it under a date
A date stamp at the front buries your name and dates your application the moment it is out of season. If you must track dates, do it in a folder, not the file name.
Extension
The wrong or hidden extension
Sending a format the reader cannot open, or a name with the extension hidden, forces them to work to read you. Export to a format that opens on any machine and keep the extension visible.
The extension
The extension counts too: PDF, DOCX and the label
The last part of the file name is the extension, and it carries a decision of its own. For most applications a PDF is the safe default: it looks the same on every machine, it cannot be edited by accident, and it preserves your layout exactly as you designed it. The file name ending in .pdf tells the reader they will see what you intended.
Some employers, and many applicant tracking systems, still ask for an editable document, in which case a .docx is what they want. When a posting specifies a format, follow it exactly; a file in the wrong format can be set aside before a person ever reads it. When it does not specify, PDF is the conventional choice, with a DOCX kept ready in case it is requested.
Whichever you send, make the extension honest and visible. A file named jordan-lee-resume.pdf that is actually a Word document, or a file with the extension hidden by an operating system, creates friction at exactly the moment you want none. The extension is part of the name, and it should say plainly what the file is.
The takeaway
Save it the way a recruiter would want to find it
File naming is the smallest item on any resume checklist, which is exactly why it is worth getting right: almost no one does, so the ones who do stand out for free. Lead with your name, say what the document is, keep it clean, and match the format the employer asked for. That is the entire convention, and it will serve you for every application you ever send.
If you would rather not think about export settings at all, a builder can handle the format and a sensible file name for you. Folio exports your resume to both PDF and DOCX for free, with no watermark, named from your details so it arrives as something like your-name-resume.pdf rather than a generic download. The free plan also gives you a portfolio page at portfolio.wrxstack.com/yourname with a small Made with Folio badge, and while the wider theme gallery is a paid feature, the resume export never is.
Save the file the way a recruiter would want to find it, in the format the posting asked for, and you have removed one more tiny reason for anyone to set your application aside. The work is in the resume; the file name just makes sure it lands cleanly.
Frequently asked questions
What should I name my resume file?
Use your full name, the word Resume, and, if you tailor it, the target role, joined by hyphens or underscores. A name like jordan-lee-resume.pdf or jordan-lee-resume-product-manager.pdf is clear, findable, and unmistakably yours. Avoid generic names like resume.pdf, and skip dates, version numbers, and words like final or draft.
Why does the resume file name matter?
It is read before the resume is opened, in the recruiter inbox, in the applicant tracking system, and in a shared hiring folder. A clear name makes you easy to find and reads as organised; a generic one collides with every other applicant and can be renamed, overwritten, or lost. It is a small signal you fully control at no cost.
Should a resume file name include the date or version number?
No. Dates and version tags like v3 or final belong in your own folders, not in the file you send. A date at the front buries your name and makes the application look stale later, and a version number reveals your editing process. The recipient should see a finished document, not its history.
Should I send my resume as a PDF or a Word document?
PDF is the safe default: it holds your layout on any machine and cannot be edited by accident. Send a .docx only when the posting or the applicant tracking system asks for an editable file. When a format is specified, follow it exactly, since the wrong format can be rejected before anyone reads it. Keep a DOCX ready either way.
Can a bad file name get my resume rejected by an ATS?
A name alone rarely triggers a rejection, but it can hurt you. Some systems store and display the original file name, so a descriptive name helps a recruiter find you in a later search, while a generic one leaves you invisible. The bigger risk is the extension: an unusual or wrong file format can fail to parse, which does cost you.