Name It Like You Mean It: The Filename Convention That Opens Doors

A scout I know keeps a running list of submission filenames that made her pause. Not pause because the work looked bad—pause because the name looked like a warning label. final_final_v2.mov. untitled(3).mp4. Desktop Copy of MIX 7 REAL FINAL.mov. She has never opened one of those with high hopes. That is not a moral judgment on the artist. It is just what happens when a human being scans a list of forty links at 9:40 on a Tuesday morning and has to decide where to spend the next hour.

Your filename is not paperwork. It is the first frame of your submission. It runs before the cold open, before the room tone, before the one unbroken scene you worked so hard to protect. And in 2026, with portals and shared drives doing more of the sorting for scouts than ever, that first frame is often plain text.

What a Scout Sees Before the Play Button

Picture the actual interface. A submissions portal with a table of attachments. A shared Google Drive folder with a grid of thumbnails and names underneath. An email thread where your link sits between a catering invoice and a calendar hold. The scout is not studying your filename. They are absorbing it in about a second and a half, the same way you absorb a subject line.

A clean name does one quiet job: it tells the scout what they are about to watch, who made it, and which version they are looking at. A messy name does a louder job: it tells them the person who made this either does not know or does not care what happens on the receiving end. That may be unfair. It is also true. The good news is that this is the cheapest fix in your entire submission process. It costs about ten seconds and it never stops paying you back.

The Anatomy of a Filename That Works

You do not need a corporate records policy. You need a convention you can repeat without thinking. Here is the one I recommend to artists, filmmakers, and musicians sending tapes through Submit Your Tapes:

ArtistLastName_ArtistFirstName_ProjectTitle_Format_YYYY-MM-DD_v01

A few notes on why each piece earns its spot:

• Name first, in a stable order. Scouts often sort alphabetically or search by name. Put the person before the project so the file lands near the rest of your work.
• Project title, shortened but readable. Use hyphens or underscores between words. Do not use spaces if the portal might choke on them. Night-Shift-Short beats night shift short FINAL.
• Format or deliverable. master, roughcut, audition, scene1. This tells the scout what kind of tape this is without opening it.
• Date in ISO order. 2026-11-13 sorts correctly and reads clearly. 11-13-26 is fine in the US but confusing in an international portal. Nov13 is charming and useless for sorting.
• Version number. v01, v02, v03. Not final. Not finalfinal. A number is honest and it never lies to you at 2 a.m.

String it together and you get something like Okafor_Adaeze_Night-Shift-Short_master_2026-11-13_v02.mp4. Long, yes. But every character is doing a job, and none of them are apologizing.

Before and After: Three Renames That Change the Read

Before: final_final_v2.mov After: Reyes_Mateo_Concrete-Garden_roughcut_2026-10-28_v03.mov

The first name says “I have lost control of my own desktop.” The second says “I know what this is and so will you.”

Before: AUDITION TAPE.mov After: Whitfield_Jordan_Monologue-Chekhov_audition_2026-11-02_v01.mp4

Same file. Different level of respect for the person receiving it. One requires a follow-up email to explain. The other answers the question before it is asked.

Before: mix7real.mp3 After: Alvarez_Nina_Blue-Room-Demo_master_2026-09-15_v04.wav

Notice the format extension does some of the work too. A WAV tells a music scout “master.” An MP3 tells them “reference.” Both are fine. Only one is the thing they will want if they say yes.

The Metadata You Are Not Thinking About

Filename is the headline. Metadata is the fine print, and scouts read it more than you would guess. Duration, resolution, frame rate, audio channel count, file size, codec—these little fields populate portal previews and drive thumbnails. They shape expectation before playback.

If your tape is a three-minute short, a duration field that reads 00:47:12 will make a scout think they are being handed a feature. If your audition is a single monologue, a resolution of 4K at 60 frames per second is not impressive—it is a hint that the file is enormous and the export settings were left on default. A clean 1080p at 24 or 30 frames per second, stereo audio, sensible bitrate: that is the quiet professional move. It says you know what the tape is for.

One practical habit: before you upload, open the file’s properties or “Get Info” panel and read it the way a stranger would. Does the duration match what you claim in your cover note? Does the resolution match the platform’s recommendation? Is the audio mono when you meant stereo? Catching that in ten seconds is much cheaper than catching it in a scout’s first impression.

Build a Ten-Second Habit

None of this replaces the work. A beautifully named tape that stalls at minute five is still a tape that stalls at minute five. But the name and the package are the part you fully control, and they are the part a scout meets first. So before you hit submit, do this: rename the file, check the duration and resolution, confirm the version number is the one you actually mean, and read the whole string out loud once. If it sounds like a file you would be glad to receive, send it. If it sounds like a warning label, you already know what to fix.