The short answer
Name it "Firstname-Lastname-Resume.pdf". Keep version numbers and dates out of the file you send, keep them in the copies you keep, and never send anything called "resume final v3 USE THIS ONE".
What matters most
- Firstname-Lastname-Resume is the convention that works in every system.
- Never send a filename containing version numbers, dates or draft notes.
- Hyphens or underscores rather than spaces, and no special characters.
- Keep your own version control in folder names, not in the name of the file you attach.
The convention, and why it is shaped that way
Your name first, then the word "Resume", then the extension. That order exists because files get sorted alphabetically in whatever folder they land in, and sorting by your surname or forename is how a person finds you again. A file beginning with "Resume" sorts into a block with every other applicant's, which is precisely the opposite of what you want.
| Filename | Verdict | Reason |
|---|---|---|
| Priya-Raman-Resume.pdf | Ideal | Sorts by name, states what it is, safe characters, no noise. |
| Priya_Raman_Resume.pdf | Equally fine | Underscores behave the same as hyphens in every system that matters. |
| Priya-Raman-Resume-Data-Analyst.pdf | Good for direct email | Helpful when applying to one named role; slightly long for bulk portals. |
| PriyaRamanResume.pdf | Acceptable | Readable, if less so at a glance. No separator makes long names harder to parse. |
| resume.pdf | Poor | Anonymous. Has to be renamed by hand, and collides with every other file in the folder. |
| Resume_final_v4_NEW.pdf | Bad | Advertises a chaotic process, and the reader wonders what was wrong with the first three. |
| Priya Raman Resume (2).pdf | Bad | The "(2)" is an accidental download artefact, and brackets plus spaces can break some upload handlers. |
| CV Priya 2024 UPDATED.pdf | Bad | A stale year on a current application is the worst possible detail to volunteer. |
Characters to avoid and why
This is not pedantry. Each of these causes a real, occasional, entirely avoidable failure somewhere in the chain between your machine and a recruiter's screen.
- Spaces. Mostly fine now, but they become %20 in URLs and occasionally trip older upload handlers. Hyphens cost you nothing and never misbehave.
- Brackets, ampersands, hashes, slashes, quotes. Some are reserved characters in web addresses and file systems. A slash in particular can be rejected outright.
- Accented and non-Latin characters. Keep them in your name inside the document, where they belong, and use plain Latin characters in the filename to avoid encoding problems on systems that handle them badly.
- Very long names. A few systems truncate at a fixed length, and a truncated name can lose the extension. Keep it under about fifty characters.
- The word "final". It is never true, and it tells the reader something about your process that you did not intend to share.
What goes inside the file, not just on it
A filename is one of three places your identity is stored, and the other two are invisible until they are not.
- The filename
- What a human sees in a mailbox or folder listing. Get this right first because it is seen most.
- The document title property
- Stored inside the file and used by some PDF readers as the browser tab label. If it says "Microsoft Word - Document1" or the name of whoever built the template, that is what shows above your resume in a browser.
- The author property
- Often carries the name of the account that created the original document. If you started from a template a friend sent you, their name may still be in there.
Managing tailored versions without losing track
If you are applying properly you have several versions of your resume, each aimed at a different kind of role, and the risk is sending the wrong one. The way to avoid that is to put all your version information in the folder structure and none of it in the filename.
- 1One folder per application
Named for the employer and the role, for example "Northgate-Health-Data-Analyst". Everything for that application lives in it β resume, cover letter, the job posting saved as a PDF, and any notes.
- 2The same clean filename inside every folder
Every folder contains "Priya-Raman-Resume.pdf". The folder tells you which application it belongs to; the file arrives at the employer with a clean, professional name.
- 3Save the job posting alongside it
Postings are taken down, sometimes before you are interviewed. Having the original text is genuinely useful when you prepare, and it lets you re-check what you tailored toward.
- 4Keep a master version in its own folder
A single long document containing everything you have ever done, which is never sent anywhere. Each tailored version is a cut-down copy of it, which makes tailoring subtraction rather than recall.
- 5Match the cover letter naming
"Priya-Raman-Cover-Letter.pdf" in the same folder. Two files with a consistent convention look like a considered application; two files named differently look like they came from different places.
The last check before you attach it
Most wrong-file incidents happen at the final step, when you are tired and attaching something at eleven at night. Three habits prevent nearly all of them: attach the file before you write the email, so you cannot forget it and cannot rush it; open the attachment from within the sent-mail draft rather than trusting the filename, because the name is exactly what you would get wrong; and read the first two lines of the document you just opened to confirm it is the version tailored to this employer and not the one aimed at a different sector.
The other frequent failure is a mismatch between the name on the file and the name on the document. If your resume header says "Priyanka Raman" and the file says "Priya-Raman-Resume", a recruiter searching their system for one will not find the other. Pick the form of your name you want to be known by, and use it identically on the resume, the cover letter, the filename and your professional profiles.
- The filename is Firstname-Lastname-Resume with the correct extension.
- No version numbers, no dates, no "final", no "(2)".
- Hyphens or underscores instead of spaces, and no reserved characters.
- The PDF title property shows your name, and the author property is yours or empty.
- The name on the file matches the name printed on the document.
- The cover letter follows the same convention.
- The attachment was opened and checked after being attached, not before.
Exports from our free resume builder use this convention automatically and set the document title from your name, so the properties problem does not arise. If you are also sending a letter, our template gallery includes matching letter layouts so the pair looks like one application rather than two.
Questions people actually ask
What should I name my resume file?
Firstname-Lastname-Resume followed by the file extension, for example Priya-Raman-Resume.pdf. Your name comes first so the file sorts usefully in a folder of applications, and the word "resume" tells the reader what it is before they open it.
Should I put the job title in the filename?
It is a nice touch when you are emailing a specific person about a specific role, and it helps them file it. For bulk uploads through an application portal it adds length without benefit, since the system already knows which requisition you applied to.
Should I include the date or a version number?
Never in the file you send. A version number tells the employer how many drafts there were, and a date becomes stale the moment the year turns over. Keep version information in your own folder names instead.
Do spaces in a filename cause problems?
Rarely now, but they become percent-encoded in web addresses and can still trip older upload handlers. Hyphens or underscores are just as readable and never misbehave, so there is no reason to use spaces.
Does the filename affect ATS ranking?
No. Applicant tracking systems score the content of the document, not what it is called. The filename matters because a human sees it in a mailbox and in a folder, and because a file that has to be renamed by hand starts your application with a small favour asked.