Login

— 6 minutes — Mark Eckert

Naming Conventions for Sync Tracks: File Names That Get Found

Short answer: Name every file so a stranger can tell what it is without opening it: artist, title, version, length, and sometimes tempo, in the same order every time, with no special characters. A simple pattern such as Artist_Title_Version_Length.wav works for most libraries. Consistent names stop files being mixed up, help editors find the right version fast, and keep your details matched across every catalog. Always follow a library's own rules if it has them.

Why file names matter in sync

Editors and librarians handle thousands of files. When a supervisor needs the 30 second instrumental of your track at the last minute, the file name is often the only thing they look at. A confusing name can mean the wrong version is used, or your track is skipped for one that is easier to find. File names also connect your audio to its metadata, so mistakes can cause payment and clearance problems later.

A simple naming format

Use the same parts, in the same order, for every file:

PartExampleNotes
Artist or writer nameJaneRiversNo spaces, or use underscores between words
Track titleMorningLightSame spelling as in your metadata
VersionFull, Inst, NoVox, Clean, StemUse a fixed set of codes
Length60s, 30s, 15sOnly for edits
Optional tempo or key92bpmOnly if your library asks
File type.wavUsually WAV for delivery

Example: JaneRivers_MorningLight_Inst_30s.wav

Version codes to standardize

Pick codes once and use them everywhere:

CodeMeaning
FullFull mix with vocals
InstInstrumental, no vocals
NoVoxLead vocal removed, backing vocals kept
CleanExplicit lyrics removed or replaced
60s, 30s, 15sEdits of that length
StingVery short ending or logo hit
LoopSeamless loop
StemIndividual stem, followed by its name, such as Stem_Drums

Before and after

BeforeAfter
final final v3 MASTER.wavJaneRivers_MorningLight_Full.wav
morning light no vox (1).wavJaneRivers_MorningLight_NoVox.wav
ML 30 sec edit.wavJaneRivers_MorningLight_Full_30s.wav
drums.wavJaneRivers_MorningLight_Stem_Drums.wav

Rules that prevent problems

  • No special characters. Avoid slashes, colons, ampersands, accents, and emoji. Some systems reject them.
  • No vague words. Drop "final", "new", "master", and version numbers from delivery files.
  • Keep it short. Long names get cut off in many systems.
  • Match your metadata. The title in the file name should match the title field exactly.
  • Be consistent. The same order, codes, and capitalization in every file.
  • Follow library rules first. If a library gives a format, use theirs.

File names and metadata work together

A file name tells people what the file is. Metadata tells systems everything else: writers, splits, publishers, codes, mood, genre, and descriptions. Both must agree. If your file says "Morning Light" but your metadata says "Mornin Light", libraries and performance rights organizations may treat them as different works. Metadata requirements for music libraries lists the fields most libraries expect.

Embed key details in the file where you can, such as title, artist, and writer, so they travel with the audio. Keep a master spreadsheet that lists every file name and its metadata. Metadata templates for sync licensing has a starting layout.

Organizing folders

Group files by track, with versions and stems inside:

  • One folder per track, named Artist_Title
  • Inside it, full mix, instrumental, edits, and clean versions
  • A Stems subfolder for individual stems
  • A text or spreadsheet file with the track's metadata

Organizing stems and versions goes into more detail.

Titles that work for sync

The title itself matters too:

  • Keep it short and easy to spell
  • Avoid titles that match famous songs
  • Avoid symbols and numbers that look like version labels
  • Do not change a title once it is registered and distributed

Common mistakes

  • Different titles in the file name, metadata, and registrations
  • Sending files called "final" or "mix 2"
  • Using spaces and special characters that break uploads
  • Labeling an instrumental as the full mix
  • Renaming files after they are registered

Common metadata mistakes in sync licensing covers related errors.

A hypothetical example

This example is made up. A producer delivers twelve files for one track to a library: full mix, instrumental, clean, three edits, and six stems, each named with the same pattern. Months later, an editor needs the 15 second instrumental. She searches the library, finds JaneRivers_MorningLight_Inst_15s.wav in seconds, and uses it. The cue sheet lists the same title, so the producer's royalties match too.

A quick naming checklist

  • Artist, title, version, length, in that order
  • Fixed version codes
  • No special characters or vague words
  • Title matches metadata exactly
  • One folder per track, with a metadata file
  • Library rules followed where they exist

Naming stems

Stems need extra care because there are many of them per track. Use the track's base name, then Stem, then the part, such as Drums, Bass, Keys, Vocals, or FX. Keep the same start point and length for every stem so they line up in an editor's session. If you deliver stems for a short edit, add the length too, such as JaneRivers_MorningLight_Stem_Drums_30s.wav.

Naming for different libraries

Some libraries ask for their own format, a catalog number, or no artist name in the file. Keep your master files in your own standard format, and make delivery copies in each library's format when needed. Your spreadsheet should map each library's file name back to your master name, so you can always find the original.

When you change your system

If you change your naming system, do not rename files already delivered or registered. Use the new system for new tracks only, and record both formats in your spreadsheet so older files still match their metadata.

Why naming affects payment

File names are not just tidy housekeeping. When a library licenses your track, its records, the buyer's records, and the cue sheet all refer to the track by name. If the names do not match your registrations, a performance rights organization may fail to link the use to your song, and royalties can go unclaimed. A consistent name from the first file onward is one of the cheapest ways to protect your income.

Where That Pitch fits

That Pitch takes your tracks and details once and places them in 100+ non-exclusive sync libraries, so consistent names and metadata pay off across every catalog. Your music is matched to library briefs automatically, and you keep 100% of your sync placement earnings. Get started free on Lite with unlimited uploads into 1 library per track, sync briefs included, and upgrade to 100+ anytime.

Join That Pitch free

FAQ

How should I name my sync files?

Use the same parts in the same order, such as Artist_Title_Version_Length.wav, with no special characters, and follow a library's own rules if it has them.

Should the file name match my metadata?

Yes. The title in the file name should match the title in your metadata and registrations exactly.

What version codes should I use?

Pick a fixed set, such as Full, Inst, NoVox, Clean, 60s, 30s, 15s, Sting, Loop, and Stem, and use them everywhere.

Can I use spaces in file names?

It is safer to use underscores or no spaces, because some systems handle spaces and special characters badly.

Should I rename a track after it is registered?

No. Changing titles after registration can cause payment and matching problems.

Do libraries have their own naming rules?

Many do. Always follow a library's format when it gives one.

How should I name stems?

Use the track's base name, then Stem, then the part, such as Stem_Drums, and keep every stem the same length and start point.

Last updated

Related reading