Audio Folder Structure: A Simple System for Studio Projects

By /

A good audio folder structure is one you can open in six years and find the right mix in under a minute. Keep one top-level folder per client or project, split it into numbered stages (sources, sessions, mixes, masters, deliverables, documents), name everything without spaces or special characters, and never let a DAW’s default layout be the only organization you have. This guide gives you a layout you can copy today, the naming rules behind it, and the habits that keep it from rotting.

It is written for people who handle other people’s audio: mixing and mastering engineers, podcast producers, post-production editors and studio owners. (If you are looking for how to arrange a personal music library or audiobook collection for a media player, that is a different problem. Those tools read tags and their own folder rules.)

Audome
Keep Project Files and Feedback Together
Audome organizes audio projects, versions, and timestamped client feedback in one secure workspace, alongside the folders you use for files.

Visit Audome

TL;DR

  • Use one root folder per project, with numbered subfolders that follow the order of the work: sources, sessions, mixes, masters, deliverables, documents.
  • Name files and folders with underscores or hyphens, no spaces and no special characters, and keep names well under 255 characters.
  • Put the version in the filename, never in a folder called “final” or “new.”
  • Keep session notes, track sheets and recording maps in the project folder. Audio files do not document themselves.
  • Your folders hold the files. Client feedback and approvals need their own home, or they end up in email threads.

Table of Contents

Why folder structure matters more than it seems

The point of any structure is predictability. A layout that still makes sense months or years later means nobody guesses when a client returns for a revision or a project has to be archived, and that saves hours of searching for misplaced files.

The Audio Engineering Society makes a related point about metadata. Audio files are not self-documenting, and a complete project folder should include auxiliary documentation such as session notes and recording maps so the material stays usable for reuse or restoration. That is the part most home-grown systems skip.

So a folder structure does two jobs. It tells you where a file goes today, and it tells a stranger (or you in 2032) what happened to the project.

Know what a project actually contains

Before designing folders, list what a typical job generates. Most audio projects produce the same five kinds of material:

  1. Source audio. Recorded tracks, files received from the client, samples, reference tracks.
  2. The session or project file. The DAW document itself, plus whatever media folders the DAW creates around it.
  3. Bounces and mixes. Rough mixes, revisions, alternates (instrumental, TV mix, a cappella).
  4. Masters and deliverables. Final files in the formats the client or distributor asked for.
  5. Paperwork. Session notes, track sheets, invoices, contracts, emails saved as text, lyric sheets, cue sheets.

Every folder structure is a way of keeping these five apart. The mistakes come from mixing them, for example saving a bounce inside the audio folder the DAW manages, then wondering why it vanished after a “consolidate” or a clean-up.

A top-level layout you can copy

Here is a structure for a single song, mix or mastering job. The numbers force the folders to sort in workflow order on both macOS and Windows.

ClientName_ProjectTitle/
  01_Sources/
    Client_Uploads/
    Recorded_Tracks/
    References/
  02_Sessions/
    ProjectTitle_Mix_v01/
  03_Bounces_Mixes/
    Rough/
    Revisions/
    Alternates/
  04_Masters/
  05_Deliverables/
  06_Documents/
    Session_Notes/
    Invoices_Contracts/
  07_Archive/

What goes in each folder

  • 01_Sources is read-only in spirit. Whatever arrives from the client goes into Client_Uploads untouched, so you can always prove what you were originally given. Keep your own tracked material separate in Recorded_Tracks.
  • 02_Sessions holds the DAW sessions. One subfolder per session version if your DAW makes a folder per session (Pro Tools does).
  • 03_Bounces_Mixes holds anything you rendered for listening. Splitting rough, revision and alternate versions keeps the client-facing ones easy to spot.
  • 04_Masters holds the approved masters only. If it is not approved, it does not belong here.
  • 05_Deliverables is what actually leaves the building: the formats, sample rates and bit depths the client asked for.
  • 06_Documents is where the AES advice lands. Notes, maps and paperwork live next to the audio.
  • 07_Archive is for superseded sessions and anything you want to keep but never see again.

The point is not these exact names. It is that anyone can tell, from the folder alone, whether a file is raw, in progress, or finished.

How your DAW fits into the structure

Each DAW creates its own subfolders, and you should work with them rather than against them. In a Pro Tools session, for example, the program creates a folder named for the session containing the session file, and the audio normally lives in an Audio Files folder inside it. Sound on Sound explains that audio used in a session does not have to be in that folder, so it is easy to end up with a session pulling audio from several locations. That is how sessions come back from a hard drive swap with missing media.

The Pro Tools Reference Guide lists the standard pieces: the session file, an Audio Files folder, a Fade Files folder, a Bounced Files folder and a Rendered Files folder. Other DAWs use similar ideas with different names, such as audio files, rendered files and clip groups.

Two habits prevent most trouble:

  • Copy media into the project when importing. Choose the copy option rather than adding files by reference, so the session is self-contained. Before you archive or send a session, use your DAW’s save-a-copy or collect-all-files feature to gather everything into one folder.
  • Treat the DAW’s own folders as off limits. Do not hand-sort files inside them, and do not drop unrelated files in. Put your own organization around the session folder, as in the layout above.

For handoffs between facilities, the Recording Academy’s Producers & Engineers Wing publishes guidance on session organization. Its one-page Pro Tools guidance on master sessions says the master session is the central session where all the tracks intended for the final mix end up. If your studio hands sessions to mix engineers, label that master session clearly.

File naming rules that keep the structure working

Folders are only half of it. Bad filenames wreck a good tree.

The Audio Engineering Society’s recommendation for delivering recorded music projects relies on a hierarchical naming approach with underscores separating fields, and a suggested pattern of artist, song title, version or mix type, sample rate, bit depth and revision number. It also advises avoiding spaces and special characters and keeping names under 255 characters, so they behave on different operating systems and asset management systems. An example of that pattern looks like this:

Six fields in an audio project filename

ArtistID_SongTitle_MixType_SampleRate_BitDepth_RevisionNumber.wav

The Academy Digital Preservation Forum also notes that every studio and facility does it a little differently, but a general paradigm has emerged. In other words, pick a convention, write it down, and apply it every time.

Practical naming rules

  • No spaces. Use underscores or hyphens, or camelCase.
  • No special characters such as !, $, & or ;. They break scripts, cloud sync and some DAW media management.
  • Zero-pad numbers. v01, v02, v10 sort correctly. v1, v10, v2 do not.
  • Put the sortable part first. Client or project, then song, then version.
  • Keep the date in ISO order (2026-10-22) when you use one, so dates sort chronologically.
  • Never use “final.” There is always a “final_v2.” Use version numbers and let the approved one move to the Masters folder.

Example filenames

Purpose Filename
Rough mix Harbor_Lights_RoughMix_v01.wav
Revision after client notes Harbor_Lights_Mix_v04.wav
Instrumental alternate Harbor_Lights_Instrumental_v04.wav
Approved master, streaming Harbor_Lights_Master_44k1_24bit_v01.wav
Podcast episode ShowName_Ep042_Edit_v03.wav

If version naming is where your projects go wrong, our guide to a six-step mix version naming system goes deeper than this section can.

Adapting the structure by job type

The same logic works across disciplines. Change the middle folders, keep the pattern.

Mixing and mastering

Add a Stems folder under 01_Sources if clients send stems separately from multitracks. In mastering, keep Pre_Master (the mix you received) and Post_Master clearly apart so you never process a file twice. Put reference tracks in their own folder so they never get bounced into a deliverable by mistake. If you compare against references often, see our notes on reference track management.

Podcast production

Organize by episode, not by calendar:

ShowName/
  Ep042_GuestName/
    01_Raw_Recordings/
    02_Edit_Session/
    03_Music_SFX/
    04_Mixes/
    05_Final_Episode/
    06_Show_Notes/

Keep show-level assets (intro music, sponsor reads, logos) in a _Shared folder at the show level so each episode does not carry duplicate copies.

Post-production and film

Post work lives or dies by consistency across many hands. Organize by reel or scene, keep dialogue, effects and music in separate folders, and record frame rate and sample rate in the project notes. When several editors share a project, a single document explaining the conventions is worth more than an elaborate tree.

Composers

Composers deal with many cues per project. Name cues with a number first (1M01_Opening_v03), keep a Mockups folder apart from Approved, and save the cue sheet in documents.

Versioning without chaos

Versions are where folder structures usually fail. Three rules help:

  1. The filename carries the version. Folders do not.
  2. Old versions are not deleted during the project. Move them to Archive or a Superseded subfolder once a newer one is approved.
  3. One place is the source of truth. If the client has v04 and you have v05, someone has to know which is current.

For the tooling side, read our overview of audio version control, its pitfalls and best practices.

Backups and archiving

A tidy tree on one drive is one failure away from no tree. The setup we recommend is one working copy and two archives, described in our guide to backing up client projects.

When a project closes:

  • Collect all media into the session folder.
  • Save the final session, the approved masters and the deliverables.
  • Add a short text file listing the DAW and version, sample rate, plugins used and any known issues.
  • Move the project to long-term storage and note it in your project log.

You should also decide how long you keep client files and what you charge to bring them back. Our post on a studio file retention policy covers that.

Our perspective: folders organize files, not conversations

We build Audome for people who run audio businesses, and we see the same pattern repeatedly. Studios get their folder trees right and still lose time, because the folder only holds the files. The real mess is around it: a note in a text message, a revision request in an email, a link to a file that was moved last week, an approval buried in a Discord thread.

A clean structure solves “where is the file.” It does not solve “which version did the client approve, and what exactly did they ask me to change at 2:14 in the second chorus.” That is why we think of the folder structure as the studio’s internal system, and the client collaboration space as a separate, deliberate layer. Your folders stay yours, with your naming, your archive and your backups. What clients see is a project page with the current versions, timestamped comments on the waveform and a clear record of revisions.

In practice, that means mirroring your structure lightly. Your 03_Bounces_Mixes folder maps to what you share for review. Your 04_Masters and 05_Deliverables folders map to what a client downloads after approval, and, if you choose, after payment. If you want a deeper look at how the pieces fit together, our project collaboration workflow guide walks through it.

One more opinion: do not over-engineer. A structure with four levels of nesting will be ignored by your tired self at 1 a.m. Six numbered folders and a naming rule you can recite are enough.

— Kreg

Where Audome fits in

Once your files are organized, the next question is how clients hear them and respond. Audome gives you unlimited uploads of high-resolution audio (up to 96kHz/24-bit), project pages clients can open without creating an account, timestamped feedback on the waveform, automatic version tracking, and optional revision limits and payment before final downloads unlock through Stripe. Plans are listed on the pricing page: Studio is $12.50 per month or $150 per year, and Pro is $48 per month or $576 per year. You can also see the full platform on our homepage.

For a comparison of the approaches to sending mixes, see our guide to the best way to share audio files with music clients.

A one-week plan to adopt the structure

You do not need to reorganize your whole archive. Do this instead:

  1. Day 1. Create a template folder with the layout above and save it somewhere you can duplicate in one click.
  2. Day 2. Write a one-page naming convention: separators, version format, date format. Pin it where you work.
  3. Day 3. Start the next new project from the template. Do not touch old ones yet.
  4. Day 4. Add a notes template to 06_Documents with fields for DAW, sample rate, bit depth, plugins and open issues.
  5. Day 5. Set up your backup routine and test restoring one project.
  6. Day 6. When a client reopens an old project, migrate it into the new structure at that moment.
  7. Day 7. Review what slowed you down and adjust the template once.

Migrating only when a project is reopened keeps the cost low and puts effort where it matters. For more on the surrounding workflow, our guides on recording studio workflow and producer file management cover the next layers, and our post on exporting audio deliverables helps with the output side.

Common mistakes to avoid

  • Folders named by date only. You will not remember what happened on 10-14.
  • “Final,” “final2,” “final_REAL.” Use version numbers.
  • Mixing client files with your own. Keep the originals untouched.
  • Relying on the DAW’s default location. Sessions saved to the desktop or a downloads folder get lost.
  • No notes. Audio without documentation is the first thing to become unusable.
  • Cloud sync on the active session. Some sync tools lock or partially upload files mid-session. Work locally, then sync or back up when you close.
  • Special characters in names. Ampersands and exclamation marks cause errors in scripts and transfers.

FAQ

What is the best folder structure for audio projects?

The best one is the one you apply the same way every time. A numbered layout that follows the workflow (sources, sessions, mixes, masters, deliverables, documents) works for most mixing, mastering, podcast and post jobs. Adjust the middle folders to your discipline and keep the pattern.

Should I organize audio by client, by date, or by project type?

Start with the client, then the project. Dates alone are hard to search by memory, and project type works better as a tag or a top-level split once you have many clients. Put the date in the filename or notes when it matters.

Can I use spaces in audio file and folder names?

You can, but you should not. Spaces and special characters can cause compatibility problems between Windows, macOS, cloud storage and DAW asset management, which is why the AES recommends avoiding them. Underscores and hyphens do the same job safely.

Where should session notes and track sheets go?

Inside the project folder, in a documents subfolder, so they travel with the audio. The AES stresses that audio files do not describe themselves, so notes and recording maps are part of a complete project.

Sources

Scroll to Top