File Naming Conventions: Best Practices, Examples, and Templates

IMG_4823.jpg, scan0003.pdf, Report FINAL (2).docx. None of these names tells you what is inside the file, what date it belongs to, or whether it is the latest version. A file naming convention fixes that with a few rules that everyone applies the same way.

This guide covers what a naming convention is, the three rules almost every guide agrees on, the full list of best practices, before-and-after examples, templates you can copy, and the filename rules of Windows, macOS, and Linux. If you are here to name a job application, jump to how to name a resume file. You can apply every rule by hand. The later sections show how to apply them automatically.

#What is a file naming convention?

A file naming convention is an agreed set of rules for naming files: which pieces of information go into the name, in what order, and how each piece is written. When everyone follows it, a filename tells you what the file contains and how it relates to other files without opening it. Files also sort into a predictable order in any folder.

A convention settles four things:

• Elements: which facts belong in the name, such as a date, client, project, document type, or version.
• Order: which element comes first. The first element decides how files sort.
• Format: how each element is written, for example 2026-03-08 for dates and v02 for versions.
• Characters and separators: what goes between elements, and which characters are not allowed.

Here is one filename taken apart:

Put together, that is 2026-03-08_acme-corp_proposal_v02.pdf. Underscores separate the elements and hyphens join words within an element. The reusable pattern behind it, YYYY-MM-DD_client_document-type_v01.ext, is what people mean by a naming format or filename template.

The extension is the part after the last period. It tells your computer which app opens the file. Changing it does not change the file itself: renaming report.docx to report.pdf does not turn it into a PDF.

#What are 3 file naming conventions?

There is no single official list. When a course, quiz, or style guide asks for three file naming conventions, it almost always means these three rules:

1. Be consistent and descriptive. Use the same elements in the same order for every file, and make the name say what the file is: 2026-03-08_board-minutes.pdf, not notes.pdf.
2. Write dates as YYYY-MM-DD. The ISO 8601 order (year, month, day) makes files sort chronologically and avoids confusion between the US 03/08 and the European 08/03. The compact YYYYMMDD form sorts just as well.
3. Avoid characters that have a special meaning to the operating system. Windows does not allow < > : " / \ | ? * in names, and Finder on a Mac does not allow a colon. Letters, numbers, hyphens, and underscores work on every system, in web addresses, and in scripts.

If the question is about capitalization styles instead, the three conventions are snake_case, kebab-case, and camelCase, with PascalCase as a common fourth:

For everyday files, snake_case, kebab-case, or a mix of the two (underscores between elements, hyphens inside them) is easiest to read because the separators are visible.

#File naming best practices

These rules come up again and again in university data-management guides, such as Harvard Medical School's, and in records-management policies. Not every folder needs all of them, but each one prevents a specific problem.

1. Be consistent. Use the same elements, order, and format for every file of a kind. A mediocre convention applied every time beats a perfect one applied half the time.
2. Put what you sort or search by first. Lead with the date for time-ordered records such as minutes, invoices, and logs. Lead with the client, project, or case number when you browse by account.
3. Use ISO 8601 dates, and agree which date. Write 2026-03-08 (or 20260308), never 3-8-26 or March 8. Year-first dates sort correctly as plain text. Decide which date each file type uses: the issue date for an invoice, the meeting date for minutes, the signing date for a contract. Never use the download date; your computer records that already.
4. Stick to safe characters for files you share. Letters, numbers, hyphens, and underscores work everywhere. Never use / \ : * ? " < > |, which Windows reserves. Also avoid # % & { } $ ! @ + = and apostrophes, which cause trouble in links, scripts, and some apps. Spaces and accented letters are allowed on Windows, macOS, and Linux, but a space turns into %20 in a link and needs quotes in a script.
5. Choose one separator scheme. A common one uses underscores between elements and hyphens inside an element: 2026-03-08_acme-corp_proposal. Whatever you pick, use it everywhere.
6. Keep names short but meaningful. Three to five elements are usually enough. You can drop what the folder already says, unless the file often leaves that folder as an email attachment or download. Long names inside deep folders also push the full path toward the 260-character limit that some Windows programs still enforce.
7. Pad numbers with leading zeros. Write 001, 002, and so on up to 010, so file 10 does not sort before file 2. Use as many digits as the largest number you expect.
8. Use version numbers, not "final". Write v01, v02, v03. Words like "final", "final2", and "latest" stop meaning anything after the second round of edits. Add a status word such as signed or approved only once that is true.
9. Pick one case style. All lowercase is the simplest. Linux treats Report.pdf and report.pdf as two different files, while Windows and macOS usually do not, which causes surprises when files move.
10. Leave out what a file does not have. A receipt without a printed reference number does not need an invented one. If a file has no reliable date, write an agreed marker such as MISSING and fix it before filing, instead of guessing.
11. Write the convention down. A short README in the shared folder with the pattern, the allowed abbreviations, and two or three examples is what keeps a team consistent. There is a template below.

Quick check against the most common mistakes:

#File naming convention examples

More examples, one per common file type:

In each case the date is the one that matters for the document (when it was signed, issued, or collected), not the day you saved the file. For photos, take the date from the camera's metadata or from what you know about the shoot. The picture itself rarely shows when it was taken.

#Copy-paste file naming templates

A template fixes the order and format of every element, so you only fill in the values. Pick the one that matches your work, copy it, and replace the sample values.

General business document: lead with the date, then the client and document type.

YYYY-MM-DD_client_document-type_v01.ext
2026-03-08_acme-corp_proposal_v01.pdf

Date-first records: for anything time-ordered, such as minutes, logs, or daily reports.

YYYY-MM-DD_description.ext
2026-03-08_board-minutes.pdf
logs/errors/2026-03-08_checkout-timeout.md

Add _v01 when a record goes through drafts: 2026-03-08_board-minutes_v02.pdf.

Client or agency work: lead with the client so every file for an account groups together.

client_project_YYYY-MM-DD_deliverable_v01.ext
acme_website_2026-03-08_homepage-copy_v03.docx

Invoices and receipts: lead with the issue date, then the vendor, the document type, and the printed reference.

YYYY-MM-DD_vendor_document-type_reference.ext
2026-02-28_acme-corp_invoice_4471.pdf

Project and version tracking: lead with the project and component, then the version.

project_component_v01.ext
apollo_checkout-flow_v03.fig

#How to name a resume file

Name your resume with your full name, the role you are applying for, and the document type, separated by hyphens or underscores. Save it as a PDF unless the employer asks for Word: Jane-Doe_Data-Analyst_Resume.pdf.

That name works because it starts with your name, so it stands out in a recruiter's downloads folder full of resume.pdf files. It names the role, which helps when you apply for more than one position. And it says what the document is, so your resume and cover letter are easy to tell apart. Leave out final, v7, (1), and dates.

If the job posting or application portal asks for a specific filename or format, follow its instructions exactly. That overrides everything here.

#Resume and cover letter filenames

Use the same pattern for every document in one application so they sort together. Use "CV" or "Resume", whichever word the job posting uses.

These examples assume PDF files. To send a Word document as a PDF, export it from your editor. Changing .docx to .pdf in the name does not convert it.

• Should you include the company name? Usually not. A reused file with the wrong company in its name is an easy, visible mistake. Put the company in your folder name instead.
• Keeping tailored versions apart: keep one master resume. For each application, make a folder such as 2026-09_acme_data-analyst, tailor a copy there (the working copy can carry _v03), and export the version you send with the clean name. After uploading, check that the portal kept your filename.

#File naming conventions for electronic documents and scans

Electronic documents in a shared drive, a records system, or an email thread get separated from their folders all the time. Their names should still make sense on their own:

• Include the record's own identifier when it has one, such as an invoice, case, policy, or purchase order number. It is usually the fastest thing to search for later.
• Keep sensitive personal data out of names. Filenames show up in file lists, sync logs, email previews, and search results. Use an ID or a short reference instead of a Social Security number or health details.
• Stay within the strictest system the file will touch. Cloud drives and sync apps can add their own rules to the operating system's, and long names in deep folder paths can exceed path limits.
• Name scans right after scanning. Scanners and phone apps produce names like scan0007.pdf, and a file that is not renamed on day one rarely gets renamed later.

This is where renaming by hand gets slow: you have to open every scan to read its date and sender. The guide to renaming PDFs based on their contents shows how to automate that step, and scanning documents with an iPhone covers the capture side.

Apply your pattern to your own documents

Save your convention as a Preset and test it on three copies. Try 30 free renames in the app. No email, no card. Add a card for 70 more and 14 days of your plan.

Joinhappy customers

Choose your downloadSee Preset setup

#File naming conventions by industry

The core rules stay the same in every field. What changes is which element goes first and which ones you can drop.

#Legal and case files

Lead with the matter or case number so every document for a matter groups together, then the date and a fixed document-type word: client-matter_YYYY-MM-DD_document-type_v01.ext, for example smith-2026-014_2026-03-08_motion_v01.pdf. Agree on the type words (motion, brief, exhibit, correspondence) so anyone can scan a folder without opening files.

Pitfall: client names or initials alone collide as soon as one client has two matters.

#Construction and job-site photos

Job-site photos arrive as camera codes like IMG_2231.jpg that lose their context once they leave the device. Lead with the project, then the date the photo was taken, then the location or phase and a sequence number: project_YYYY-MM-DD_location-or-phase_001.ext, for example riverside_2026-03-08_foundation-pour_014.jpg. The same pattern works for RFIs, submittals, and daily reports if you swap the last element.

Pitfall: without a project prefix, photos from several sites blur together the moment they leave the camera roll.

#Research data

Datasets go through revisions, so start with the collection date, then a study or project code, a sample identifier, and a version: YYYY-MM-DD_study_sample_v01.ext, for example 2026-01-12_study-b_sample-42_v02.csv. Keep a README next to the data that explains every code and sample ID.

Pitfall: duplicates like results(2).csv destroy provenance; version numbers preserve it.

#Invoices and receipts

Invoices and receipts reconcile fastest when the date leads. Use the issue date, the vendor, and the document type, then whatever you match against your statements. If that is the invoice number, use the invoice template above. If it is the amount, add it with its currency: YYYY-MM-DD_vendor_document-type_amount-currency.ext, for example 2026-02-28_acme-corp_invoice_450-00-usd.pdf. There are dedicated guides for naming receipts YYYY-MM-DD, naming bookkeeping receipts, and organizing invoices and receipts.

Pitfall: leaving out the currency causes mismatches the moment you deal with more than one. Write the amount with a hyphen instead of a decimal point (450-00) so the only period in the name is the one before the extension.

#Client and agency work

Agencies juggle many accounts, so lead with the client, then the date and the deliverable: client_YYYY-MM-DD_deliverable_v01.ext, for example acme_2026-03-08_landing-page_v03.fig. Grouping by client keeps each account's files together, and a version number tracks review rounds without labels like "latest".

Pitfall: generic names like homepage.psd exist for every client; the client prefix keeps accounts apart.

#Photography

Lead with the shoot date, then the client or event, then the camera's own frame number: YYYY-MM-DD_client-or-event_frame-number.ext, for example 2026-03-08_smith-wedding_0934.jpg. Take the shoot date from the camera's metadata or your booking. Keeping the original number lets you match an edited JPEG to its RAW file. For personal photo libraries, see renaming photos by date and location.

#Filename rules on Windows, macOS, and Linux

A name that works on your computer can still fail on a colleague's, in a cloud drive, or on a web server. These are the rules to design around:

The nine characters Windows reserves are <, >, :, ", /, \, |, ?, and *. Windows also treats NUL.txt as the device name NUL. Microsoft lists every rule in Naming Files, Paths, and Namespaces. On a Mac, Apple's rename guide says you cannot include a colon or start a name with a period. Case-sensitive Macs exist because Disk Utility offers an APFS (Case-sensitive) format.

Spaces and accented letters are allowed on all three systems. The set that works everywhere is the POSIX portable filename character set: the letters A to Z and a to z, the digits 0 to 9, the period, the underscore, and the hyphen. Use the period only before the extension, and do not start a name with a hyphen.

There is no single length limit to aim for: it depends on the file system and the app. On Windows, some programs still fail once the full path, folders included, passes the older 260-character limit. Microsoft explains when longer paths work on its path-length page.

For files that will live on a website, use lowercase and hyphens. Google recommends hyphens rather than underscores to separate words in URLs, and spaces turn into %20. That advice is about web addresses; underscores are fine in a private document library. For images, see the guide to image filename SEO.

#How to apply a naming convention automatically

A convention only helps if it is applied to every file, including the ones that arrive next week. Pick the tool based on where the information lives.

The information is already in the filename or metadata. Use a pattern renamer: Finder's Rename command on a Mac (batch renaming on Mac), PowerRename from Microsoft PowerToys or Rename-Item in PowerShell on Windows (renaming multiple files at once), and rename or mv in a Linux shell. They add prefixes, replace text, number files, and reformat dates that already appear in names. PowerRename can also insert a photo's date taken. The guide on how to rename a file has the shortcuts for each system.

Files arrive continuously in predictable layouts. Folder-rule tools such as Hazel on Mac run rules you write whenever a file lands in a folder, including rules that match text inside files. You define the pattern for each document layout.

The information is inside the file. A scan named scan0007.pdf has no date, sender, or document type anywhere a pattern tool can see. NameQuick is the app that renames files based on their content, for Mac and Windows. It reads the text of digital PDFs and documents; for scans and photos, the AI model reads the page image. A naming Preset holds your convention, and Smart Rename proposes names before you have written one. For codes that are not printed on the document, such as internal abbreviations, you can teach the AI the rule behind the name.

#Test your convention on three copies

Copy three real files into a test folder and keep the originals elsewhere. Include one that is missing a field you normally expect, such as a receipt with no reference number.

1. Set up AI. Choose your download and open Settings → AI. Choose Managed, your own cloud key, or a local model. Scans need a model that can read images.
2. Create the Preset. Open Presets → New Preset → Written instructions and paste the instruction below. To check one file without renaming it, use Test this Preset → Choose a sample file… → Test Preset.
3. Choose Review first. New installs rename automatically, so before you add the copies, open Settings → Renaming, select your Preset under Files processing mode, and set Apply suggestions from files you add to Review first.
4. Check and apply. Add the copies to Quick Rename. On a Mac, suggestions may start on their own; otherwise click Rename 3 files. Check each date, vendor, reference, and extension against the file, then click Apply 3 names.

Name each file as YYYY-MM-DD_vendor_document-type_reference. Use the issue date for invoices and receipts, and the signing date for contracts. Vendor means the business that issued the document, not the recipient. Use a short document type such as invoice, receipt or contract. Include a reference only when it is printed in the document. Use lowercase words, underscores between fields and hyphens within multi-word values. If the date, vendor or type is missing or unclear, write MISSING for that field. Do not infer a version number. Keep the original extension.

AI can misread a field, including whether it is missing at all. If a suggestion is wrong, leave it unapplied, click Clear (the files stay on disk), improve the Preset, and test fresh copies. History can undo applied renames where possible, but it is not a backup. For separate controls per part of the name, use a Filename template Preset, where each field's If not found setting can skip the file, leave the part out, or use stand-in text. Presets do not count versions for you.

#Name new files as they arrive

A watched folder, such as Downloads or your scanner's output, can apply the convention to new files. Start with an empty folder: add it in Settings → Folders, choose your Preset, and set the folder to Review first right away, because choosing the Preset turns naming on at once. NameQuick must be running, and files already in the folder are left alone. Rules can then move renamed files into their folders. Rules do not run on Quick Rename, and {year} and {month} in a Rule path are the processing date, not the document date.

With a local model (Ollama or LM Studio, or MLX on Apple Silicon Macs), the analysis stays on your computer; with your own cloud key, content goes to that provider; Managed uses NameQuick's EU-routed service (Data & Privacy). Managed starts with 30 free renames. No email, no card. Add a card for 70 more and 14 days of your plan. Self-Managed has its own 30-rename trial with no card and no time limit. See pricing.

Apply your pattern to your own documents

Save your convention as a Preset and test it on three copies. Try 30 free renames in the app. No email, no card. Add a card for 70 more and 14 days of your plan.

Joinhappy customers

Choose your downloadSee Preset setup

#How to create a file naming convention for your team

1. List the file types you actually handle and how people look for them: by date, client, case, or project.
2. Pick three to five elements and their order for each file type, with the search or sort key first.
3. Fix the formats: which date, date format, separators, case, version style, and a short list of approved abbreviations.
4. Write a one-page README and put it at the top of the shared folder.
5. Test on a few copies in the real destination, including any cloud drive or app that links to the files. Renaming a file that other documents link to can break those links.
6. Rename the existing backlog once, with the people who use it, so old and new files sort together. Then apply the convention to new files as they arrive.
7. Review it after a few months and adjust for the elements people keep adding or skipping.

A README can be this short:

NAMING CONVENTION: Finance shared drive
Pattern: YYYY-MM-DD_vendor_document-type_reference.ext
Example: 2026-02-28_acme-corp_invoice_4471.pdf
Date: the issue date printed on the document, written YYYY-MM-DD. Never the download date.
Fields: use the vendor that issued the document and its printed reference. Leave out a reference the document does not have.
Missing data: write MISSING and fix it before filing.
Separators: _ between elements, - inside an element
Case: lowercase; keep the original extension
Versions: v01, v02 ... never final
Abbreviations: po = purchase order, sow = statement of work
Collisions: stop and check. Never overwrite an existing file.
Changes: ask the drive owner before adding a new element

Names and folders work together: the digital filing system guide covers the folder side, and a shared company drive can start from the business folder structure template.

#FAQ

#What does file naming convention mean?

It means an agreed pattern for naming files: which details go in the name (such as a date, subject, and version), in what order, and in what format. The goal is that anyone can tell what a file contains from its name alone and that files sort in a predictable order.

#What is the best file naming convention?

There is no single best one, but a dependable general-purpose pattern is YYYY-MM-DD_subject_document-type_v01.ext, for example 2026-03-08_acme-corp_proposal_v01.pdf. Put a client, project, or case number first instead of the date if that is how you browse. The best convention is the one your whole team applies consistently.

#Should I use hyphens or underscores in file names?

Both work on every operating system. A readable scheme uses underscores between elements and hyphens inside an element, as in 2026-03-08_acme-corp_proposal.pdf. For files that will be published on the web, prefer hyphens, because Google recommends hyphens to separate words in URLs.

#What characters should be avoided in file names?

Avoid characters that have a special meaning to operating systems. Windows reserves / \ : * ? " < > |, Finder on a Mac does not allow a colon, and Linux does not allow a slash. For files you share, also avoid # % & { } $ ! and @, which can break links and scripts. Capital letters, numbers, and dates are fine.

#Are spaces allowed in file names?

Yes. Windows, macOS, and Linux all allow spaces. In a web link a space becomes %20, and in a script or command line a name with spaces needs quotes, so many teams use hyphens or underscores instead.

#Why put the date first in YYYY-MM-DD format?

So files sort chronologically. With the year first, then the month, then the day, alphabetical order and date order are the same, and the format means the same thing in every country. It does not make files smaller or open faster; it makes them sort and read correctly.

#How do I name files so they sort by date?

Start every filename with the date in YYYY-MM-DD format, always with a four-digit year and a two-digit month and day, for example 2026-03-08_board-minutes.pdf. Then sort the folder by name. Use the same kind of date for every file in the set, such as the issue date, and use leading zeros for any sequence numbers after the date (001, 002) so files from the same day stay in order.

#How do I put the time in a file name?

Add it after the date without colons, as HHMM or HH-MM-SS: 2026-03-08_1430_site-visit.jpg. Windows does not allow the colon in 14:30, and neither does Finder on a Mac. In PowerShell, Get-Date -Format "yyyy-MM-dd_HHmmss" gives a stamp such as 2026-03-08_143005, and Get-Date -Format FileDate gives 20260308 (Microsoft's Get-Date reference).

#How long should a file name be?

Long enough to say what the file is, and short enough to read at a glance in a file list. That usually means three to five elements. No single length limit covers every system; it depends on the file system and the app. On Windows, some programs still fail once the full path, folders included, passes 260 characters, so long names inside deep folders cause errors.

#Is there an ISO standard for file naming?

No ISO standard covers filenames as a whole. ISO 8601 standardizes date and time formats, which is where YYYY-MM-DD comes from. Organizations publish their own naming conventions on top of it.

#How should I name my resume file?

Use your full name, the target role, and the document type, separated by hyphens or underscores: Jane-Doe_Data-Analyst_Resume.pdf. Save it as a PDF unless the employer asks for Word, and export the PDF from your editor rather than changing the extension. Leave out the company name, words like "final", and version numbers, and follow any naming instructions in the job posting. The resume section above has templates for CVs, cover letters, and portfolios.