File Naming Sort Order: How to Make Files and Folders Sort the Way You Work

A file name is also a sort key. The order of its parts, how numbers are padded, and how dates are written decide where a file lands in a folder list. Write names so that a plain sort by name puts versions in order, dates in time order and related files side by side, and the folder starts doing the organizing for you.

Why does sort order matter in a file name?

Most people find files by looking, not searching. You open a folder, sort by name and scan for the right one. If the latest version sits in the middle of the list, or a client's files are scattered between three other clients, every look takes longer and the wrong file is easier to grab.

Sorting by Date Modified seems like a shortcut, but that date describes the file, not the work. It changes when a file is re-saved or re-exported, and some copy, sync and download tools change it too. A name you control is a steadier way to keep order.

How do macOS Finder and other apps sort file names?

There are two common ways to sort names:

• Alphabetical (character by character). The computer compares names one character at a time. Because 1 comes before 2, v10 lands before v2.

• Natural (number-aware). Runs of digits are read as whole numbers, so v2 comes before v10, the way a person would expect.

Sorted by name, macOS Finder uses natural sorting. Apple's developer documentation for localizedStandardCompare describes this number-aware comparison as "Finder-like sorting." Finder's name sort also ignores upper and lower case. Windows works the same way. File Explorer sorts numbers in names naturally by default (this can be changed in system settings).

The catch is that your files don't only live in Finder. The ls command in Terminal, many scripts, web server listings and some apps, file panels and online storage views sort character by character. The same files can appear in two different orders:

The goal is a name that sorts correctly under both methods, so it doesn't matter which tool is doing the sorting.

Why should version numbers be zero-padded?

Zero-padding gives every number the same width, so character-by-character and natural sorting agree. Write v01, not v1.

Pick a width you won't outgrow on a project. Two digits ( v01 to v99 ) covers most work. Shot numbers and image sequences often need three or four ( shot010, frame_0001 ). The same rule applies to numbered prefixes: 01_, 02_ … 10_, not 1_, 2_ … 10_. Mixing widths, such as v1 next to v01, makes the order hard to predict, so choose one width and use it everywhere.

How should dates be written so files sort chronologically?

Put the year first, then the month, then the day, with zero-padded months and days. This is the order used by the ISO 8601 date standard. Two common forms:

• YYYY-MM-DD, such as 2026-10-23. Easy to read and unambiguous in every country.

• YYMMDD, such as 261023. Shorter, popular in edit and production folders. It sorts correctly as long as every date in the project uses it.

Month-first dates like MM-DD-YY sort by month, not by time. Natural sorting doesn't fix this, because the problem is the order of the parts, not the padding:

On the left, a January 2027 file sits at the top and a December 2025 file at the bottom. On the right, the list reads oldest to newest. Day-first formats like DD.MM.YY have the same problem, and both month-first and day-first dates read differently depending on where your client is.

Which part of the name should come first?

Sorting by name groups files by the first field, then the second, and so on. So put the grouping you use most at the front. For a studio that works by client and project, that usually means the client or project code comes before the date.

Neither is wrong. A photographer filing shoots by day, or a team that mostly asks "what came in this week?", may want the date first. Ask what you look for most, and lead with it.

Where should an owner ID go, and how does field order change the sort?

Many teams add an owner field, usually the artist's initials, such as _rh or _jd. It answers "who has this?" without opening the file. Where you put it decides how the folder sorts, because each field only breaks ties in the fields before it.

Here are the same six files from two artists, named both ways and sorted by name.

Version before owner sorts each shot by version, so the newest pass is always at the bottom of its shot, whoever made it:

Owner before version groups each shot by artist, then by version within each artist:

In the second list, the latest version of shot010 ( v04 ) is the second file, not the last, and you have to read every name to find it. That suits a team where each artist works their own branch of a shot. It slows down a team that just needs "the latest." Choose the order that matches the question you ask most, then keep it.

A mixed folder is the version you want to avoid:

Why don't "final," "final2" and "FINAL_real" work?

Status words don't sort. final, final2, FINAL_real and final_USE-THIS carry no order a computer can read, and case-insensitive sorting in Finder only adds to the guesswork. They also stop being true the moment someone makes another pass.

Let the version number carry the order. If you need to mark status, add a separate status field after the version, such as approved or review, or move approved files into a delivery folder. The version tells you which pass it is. The status tells you where it stands.

How do numbered folder prefixes control folder order?

Folder names sort alphabetically too, which rarely matches how a project flows. A number prefix sets the order to match the work, from what comes in, to what you work on, to what goes out.

A few habits keep prefixes useful:

• Pad the numbers ( 01_, not 1_ ) so 10_ doesn't jump ahead of 02_ in tools that sort character by character.

• Leave gaps if you expect to add stages later, such as 10_, 20_, 30_.

• Use the same prefixes in every project, so 02_Out always means delivery.

• Keep prefixes for folders that follow a sequence. Folders without a natural order, such as a list of clients, can stay alphabetical.

A short sort order checklist

• Assume some tool will sort your names character by character, even if Finder doesn't.

• Zero-pad every number to a fixed width: v01, shot010, 01_.

• Write dates year first: YYYY-MM-DD or YYMMDD, one format per project.

• Lead with the grouping you look for most, usually client or project code.

• Put version before owner if you want "latest" at the bottom; owner before version if you want each artist grouped.

• Replace "final" with a version number and, if needed, a separate status field.

• Number folders by stage: 00_In, 01_Work, 02_Out.

For the wider principles, see our file naming best practices guide. Fictional example codes: ACM and BRV are made-up client codes used for illustration only and do not refer to any real company. Your studio defines its own rules.

How does Prisma Scanner help?

Prisma Scanner gives you a quick read on how your current names and folders hold up. Paste a filename, a path or a folder tree into the free Prisma Scanner to see where they break good naming practice. The Prisma plugins for your creative apps suggest names that follow your rules for you to copy. One-click Apply rename is on the paid Creator and Studio plans.

Whichever tool you use, the rules are yours. Decide your field order, padding width and date format once, write them down, and use them on every file.

How can I check my file names for free?

Paste a few names from a busy project folder into Prisma Scanner and see how they score. It is free and needs no signup. The score is a heuristic read of the text you paste, not a full audit, but it is a quick way to see which names could use a clearer pattern.

Finder is a trademark of Apple Inc. Windows is a trademark of Microsoft.