Naming Conventions for Music Projects

Why Naming Matters

“cool idea 3.als” tells you nothing. “untitled 47.flp” is worse. When you have 200 projects and you’re trying to decide what to work on, file names are your first (and often only) clue about what’s inside.

Good naming doesn’t require discipline or creativity. It requires a simple system you follow every time.

The Formula

A good music project name has three parts:

[date]-[genre/mood]-[identifier]

Examples:

2026-03-deep-house-vocal-chop
2026-02-ambient-long-reverb-pad
2026-03-dnb-neuro-bass-experiment
2026-01-client-sarah-remix

Date

Use YYYY-MM format. This makes files sort chronologically when you view them alphabetically in Finder. You can also find projects from a specific time period instantly.

Genre or Mood

One or two words that describe the vibe. This is more useful than you think — when you’re looking for “that techno thing I started last month,” the genre tag narrows it down fast.

Identifier

Something unique about this specific project. A sound design element, a sample you used, a collaborator’s name, the purpose of the track. Keep it short but descriptive.

What NOT to Include in the Name

Status

Don’t put “IDEA,” “WIP,” “FINAL,” or “DONE” in file names. Status changes constantly, and renaming DAW projects can break internal references (especially in Ableton and Logic, where the session file name must match the folder name).

Track status in a separate system — Mixvisor, a spreadsheet, or even sticky notes.

Version Numbers

“track-v1,” “track-v2,” “track-v3-final,” “track-v3-final-ACTUALLY-final” — we’ve all been there. Instead of creating new versions, use your DAW’s built-in save mechanisms:

Ableton: File > Save a Copy for major milestones
Logic: File > Save As (or use Alternatives)
FL Studio: File > Save new version
Most DAWs: Rely on undo history for session-level changes

If you absolutely need version snapshots, keep them in a _versions/ subfolder inside the project directory. Don’t clutter the main project name.

Naming Bounces and Stems

Bounces and stems need their own naming convention:

Bounces (mixdowns)

[project-name]-bounce-[date].[format]

Example: 2026-03-deep-house-vocal-chop-bounce-0315.wav

Stems

[project-name]-stem-[instrument].[format]

Example: 2026-03-deep-house-vocal-chop-stem-drums.wav

Including the project name in bounce and stem file names makes them traceable back to the source project — even if they end up in a different folder.

Consistency Over Perfection

The specific format matters less than using it consistently. If you prefer genre-date-identifier instead of date-genre-identifier, that’s fine. Pick a format, write it down, and use it every time.

The worst naming convention is the one you abandon after a week. Keep it simple enough that you’ll actually follow it when you’re in a creative flow and just want to save quickly.

Quick-Start Rules

If you’re starting from scratch:

Never save a project as “untitled” or “new track.” Take 5 seconds to name it something real.
Always include the month and year. You’ll thank yourself later.
Use lowercase and hyphens. It’s easier to read and avoids cross-platform issues. deep-house-idea not Deep House Idea.
Don’t rename old projects. Apply the convention to new projects going forward. Renaming existing DAW projects risks breaking file references.