home-studio-setup
The Importance of Proper File Naming and Organization for Acx Submission
Table of Contents
Why Proper File Naming and Organization Is Critical for ACX Submission
Submitting an audiobook to ACX (Audiobook Creation Exchange) may seem straightforward, but the reality is that ACX enforces strict technical and naming guidelines. Improperly named or disorganized files are one of the most common reasons for submission rejections, which can delay your audiobook’s release by days or even weeks. ACX relies on automated systems to parse filenames, match them to metadata, and validate consistency. A single misplaced hyphen or an extra space can cause a file to be flagged as invalid. Beyond submission, consistent naming conventions help you, your narrator, and your project manager keep track of dozens or hundreds of audio files, especially when revisions are required. This article walks through every facet of file naming and organization so you can submit with confidence.
Understanding ACX’s Technical Requirements
Before diving into naming conventions, you must understand the file specifications that ACX expects. All audio files must be:
- MP3 format, 192 kbps, 44100 Hz sample rate, joint stereo
- Constant bitrate (CBR) — variable bitrate (VBR) is not accepted
- Normalized to -3 dB peak and -23 dB RMS loudness (per ACX guidelines)
File names themselves must adhere to ACX’s naming structure. For retail samples, use AUTHOR_TITLE_SAMPLE.mp3. For full chapters, use AUTHOR_TITLE_ChapterXX.mp3 (where XX is a two‑digit number). Cover art must be named AUTHOR_TITLE_cover.jpg or .png. The same basic pattern extends to metadata files such as ACX review copies or supplementary text files. Consistency across every part of the submission reduces friction and helps ACX’s internal tools auto‑match your files to the correct project.
The Consequences of Poor File Naming
Even if your files sound perfect, bad naming can cause immediate rejection. Common problems include:
- Mismatched labels – ACX compares filenames to the metadata you enter in the submission form. If the chapter number in the filename doesn’t match the actual chapter sequence, the system may reorder your files incorrectly. For example, if Chapter03 is accidentally saved as Chapter02, the order becomes garbled and the listener hears content out of sequence.
- Upload errors – Special characters like &, %, #, or spaces are frequently the culprit behind stalled uploads or “file not found” errors. A simple space between words can be interpreted as a delimiter, causing the system to treat the intended filename as two separate entries.
- Lost revisions – When narrators or editors send updated files, confusing filenames (e.g., “new_final_v2_revision.mp3”) can lead to the wrong version being uploaded, forcing additional QC cycles. Without a clear naming convention, you might accidentally submit an unmastered draft instead of the polished final.
- Cover‑art mismatch – ACX requires cover art filenames to follow the same pattern. If the cover is named “cover_final.jpg” but the metadata says AUTHOR_TITLE_cover.jpg, the system won’t link them, and your submission will be flagged. This forces you to re-upload and resubmit, wasting hours.
- Duplication and missing files – In a disorganized folder, it’s easy to overlook a chapter or accidentally upload the same file twice. ACX’s validator will catch duplicates, but you’ll still need to re-upload the entire set or risk rejection.
Best Practices for File Naming: A Detailed Guide
Standardise on a Single Format
Choose one separator character — either an underscore (_) or a hyphen (-) — and stick with it for every file. Most ACX‑friendly naming uses underscores because they avoid the confusion that hyphens can cause when file names already include dashes in author or book titles. Example: Jane_Doe_TheGreatStory_Chapter01.mp3. Avoid periods or spaces; they are easily misinterpreted by file systems and ACX’s validator. If your project involves multiple authors or co-writers, agree on a consistent separator before recording begins.
Include Only Essential Information
The filename should contain: Author name, Book title, and Chapter number (or a descriptor like “Sample” or “Cover”). Keep each segment short but unique. For non‑fiction books with many parts, you may also add a part number:
John_Smith_Leadership2023_Part2_Chapter04.mp3. Avoid extra words like “final,” “approved,” or “revised” inside the main filename — use a separate version‑tracking system instead. If a book has a subtitle, either omit it or abbreviate it with care. The goal is to create filenames that are instantly human-readable and machine-parsable.
Use Leading Zeros for Chapter Numbers
ACX expects two‑digit chapter numbers (Chapter01, Chapter12). This ensures correct alphabetical sorting. If you have a prologue, use Chapter00. For appendixes or author notes, use ChapterXX and include a note in the project metadata. Leading zeros also prevent Chapter10 from appearing before Chapter09 when sorted alphabetically.
Avoid Special Characters Completely
The following characters are known to cause problems in ACX systems: / \ : * ? " < > | & % # @ ! $ ^ ~ ` { } [ ]. Stick only to letters, numbers, underscores, and hyphens. If your book title contains a colon (e.g., “The Story: A Memoir”), replace the colon with a hyphen or simply omit it: Jane_Doe_The_Story_A_Memoir_Chapter01.mp3. If an ampersand appears in the title, spell out “and” to avoid ambiguity. For example, “Science & Nature” becomes “Science_and_Nature”.
Set a Character Limit
Some operating systems and ACX’s upload tool may truncate very long filenames. Keep each segment short — ideally under 50 characters total, not including the extension. If the author and title are lengthy, abbreviate using clear, consistent rules (e.g., “The” becomes “The”, “And” becomes “&”, but avoid ambiguous abbreviations). Test a few sample filenames by uploading them to a test project before you rename the entire library.
Organising Your Files for a Smooth Submission Workflow
Build a Clear Folder Hierarchy
Create a main project folder named after the book. Inside, create subfolders:
- 01_Recordings – all raw .wav or .flac files provided by the narrator
- 02_Edited – noise‑reduced, clipped, and time‑aligned files
- 03_Masters – the final MP3 exports ready for ACX
- 04_CoverArt – high‑resolution cover image files
- 05_Metadata – any ACX metadata files, proof copies, or revision logs
- 06_Assets – optional folder for sound effects, music, or intro/outro files if applicable
Never mix stages in one folder. If you need to run QC checks, duplicate the entire master folder as a snapshot before making changes. Use numeric prefixes to force operating systems to sort folders logically.
Label Folders with Project Identifiers
Use a naming pattern that matches your filenames. Example:
Jane_Doe_The_Great_Story_ACX (main folder),
Jane_Doe_The_Great_Story_03_Masters (subfolder). This way, if you share the folder with anyone, they immediately recognise the project and file stage. For teams working remotely, consider adding a date stamp in the folder name (e.g., Jane_Doe_The_Great_Story_ACX_20250315) to make rollbacks easier.
Use a Centralised Reference Document
Maintain a simple spreadsheet or checklist that lists every expected file, its intended filename, and its status (recorded, edited, mastered, QC’d). As you export each MP3, rename it according to the standard and tick it off. This prevents missing a chapter or submitting a duplicate. A sample row might look like:
“Chapter 01 | Jane_Doe_TheGreatStory_Chapter01.mp3 | Recorded ✔ | Edited ✔ | Mastered ✔ | QC ✔”.
Share this document with your narrator and proof listener so everyone is aligned from the start.
Version Control Without Cluttering Filenames
Instead of adding “v2” to the filename, keep versions in a separate “Versions” subfolder or use a naming suffix that indicates revision round (e.g., “Chapter03_r02.mp3”). Only the final, QC‑approved version should be placed in the 03_Masters folder. This approach keeps your submission folder clean and prevents accidental upload of a draft. For collaborative projects, use a cloud-based version control system (like Google Drive version history) to track changes without filename pollution.
File Naming for Different Submission Components
Retail Sample
Filename: AUTHOR_TITLE_SAMPLE.mp3. The sample should be 2–5 minutes long, from any chapter, and already mastered to ACX loudness specs. Use the same naming convention for any audition or marketing files you send outside ACX. If you produce multiple sample versions, add a descriptor like “SAMPLE_A” or “SAMPLE_B” before the extension, but only one should be named exactly as prescribed for submission.
Chapter Files
Each chapter file must be a single continuous track of that chapter. Do not split chapters into multiple files. Name them sequentially: AUTHOR_TITLE_Chapter01.mp3, AUTHOR_TITLE_Chapter02.mp3, continuing to the last chapter. If the book includes a dedicated “Acknowledgments” or “About the Author” section, include it as the final chapter file, e.g., AUTHOR_TITLE_Chapter20.mp3. If a chapter is very long (over an hour), ACX allows breaking it into parts but you must use the same base name with a part suffix (e.g., A_B_Chapter08_Part1.mp3, A_B_Chapter08_Part2.mp3) and label them clearly in the metadata. Check current ACX guidelines for part splitting rules.
Cover Art
ACX accepts JPEG or PNG, minimum 2400×2400 pixels, 300 dpi. The filename must be AUTHOR_TITLE_cover.jpg. Do not add extra words like “front” or “final.” The cover art file must exist in the same folder as the master MP3s when you upload. If you have multiple cover variations (hardcover, paperback, audiobook), keep only the ACX-specific cover in the submission folder.
Metadata and Support Files
Some projects require a PDF of the manuscript or a separate text file for corrections. Use the same base pattern: AUTHOR_TITLE_manuscript.pdf. For any file that ACX doesn’t automatically ingest, keep the naming consistent so your own records stay straight. If you include a readme file, name it AUTHOR_TITLE_readme.txt.
Common Mistakes That Derail Submissions
- Case sensitivity confusion – ACX treats filenames as case‑sensitive. JANE_DOE_TITLE.mp3 is different from jane_doe_title.mp3. Standardise on uppercase for author and title — but choose one style and apply it everywhere. Lowercase is easier to type but uppercase stands out; pick one and stick with it across all files.
- Mixed separators – If you use underscores in chapter files but hyphens in the cover art file, the automated matching may fail. Inspect all filenames before submission to ensure a single separator is used consistently.
- Spaces in filenames – Jane Doe Title Chapter 01.mp3 will likely cause upload errors. ACX’s system may interpret the space as a delimiter and split the filename incorrectly. Replace spaces with underscores.
- Omitting the author name – Filenames like Chapter01.mp3 cannot be linked to any specific project. Always include author and title. Even if you’re submitting only one project, ACX’s automated matching still requires the full pattern.
- Using the wrong extension – Submitting .wav or .aac files will cause immediate rejection. Always export as .mp3 with the ACX preset. Double-check that your export settings produce a .mp3 file, not a .m4a.
- Cover art too large or too small – Even if the filename is perfect, ACX will reject cover art that does not meet pixel, resolution, or format requirements. Always verify dimensions and DPI before uploading.
- Chapter number mismatch with metadata – The chapter numbers in filenames must match the chapter titles you enter in the ACX submission form. If your book has a “Chapter 1: The Beginning,” the filename should still be Chapter01.mp3, not “The_Beginning.mp3”. ACX links by number, not by chapter name.
Tools to Automate and Validate File Naming
Manually renaming dozens of files is tedious and error‑prone. Consider using these tools to enforce consistency:
- Bulk Rename Utility (Windows) – free tool that can replace text, add leading zeros, and enforce character restrictions. Allows you to preview changes before applying.
- Renamer (macOS) – similar functionality with an intuitive interface. Supports regex patterns for advanced transformations.
- Advanced Renamer (cross‑platform) – supports scripting and presets for complex naming patterns. You can save a preset called “ACX Master” that automatically applies your naming convention.
- ACX‑specific checkers – several third‑party websites and scripts let you drag‑and‑drop your folder to check that every filename matches the required format. Search for “ACX filename validator” to find current options. Some popular ones include “ACX Checker” and “Audiobook Naming Validator”.
- Spreadsheet formulas – Use Google Sheets or Excel to generate filenames from author, title, and chapter list. Copy the generated filenames into a batch rename tool to eliminate manual typing errors.
Always verify the output of any renaming tool against your reference document. Take extra care that file extensions remain unchanged and that no accidental renaming of cover art occurs. After using a tool, open a few random files in an audio editor to ensure they still play correctly.
Step‑by‑Step Final Pre‑Submission Checklist
- Open your master folder — confirm that every expected file is present. Use a diff tool or folder comparison if you have one.
- Check filenames against the ACX template: AUTHOR_TITLE_ChapterXX.mp3 for all chapters, AUTHOR_TITLE_SAMPLE.mp3 for retail clip, AUTHOR_TITLE_cover.jpg for cover art.
- Verify that no two files share the same name unless they are intentionally identical (rare). Look for duplicate names or near-duplicates like Chapter01_v1.mp3.
- Ensure chapter numbers are sequential with no gaps. Missing chapter 07? Something is wrong. If your book skips a number for stylistic reasons (e.g., no chapter 13), note it in the ACX metadata so the system doesn’t flag it as missing.
- Open a few random MP3s in an audio editor (Audacity or similar) and confirm bitrate, sample rate, and loudness match ACX specs. Use the ACX loudness analysis tool if available.
- Double‑check the cover art meets pixel and resolution guidelines. Use an image viewer that shows DPI and dimensions.
- Zip the entire master folder (or upload files individually as ACX allows). Never submit a compressed archive if ACX requires individual file uploads — read the submission page carefully. Some updates may require you to upload individual files rather than a zip.
- After uploading, review the automatic validation report. If any files are flagged, correct the issue (likely a bad filename or incorrect audio specs) and re‑upload only the affected files. Do not resubmit the entire project unless instructed.
Why This Matters Beyond Submission
Good file management pays off long after your audiobook is live. If ACX requests corrected chapters due to a minor audio glitch, you can quickly locate and re‑export the exact file without sifting through a messy folder. If you partner with a distributor or want to republish on other platforms, well‑named and well‑organized files make the transition seamless. Many authors and producers build a template that they reuse for every project, dramatically reducing setup time and mental overhead. The same naming convention can be applied to promotional clips, bonus content, or future audiobooks in a series, creating a consistent library that is easy to maintain.
External Resources
For the most current ACX technical specifications and naming requirements, refer directly to the official documentation: ACX Audio File Submission Guidelines and ACX Audio Requirements. For advice on batch renaming and folder structuring, see the PCMag guide to bulk renaming (Windows) and Apple Support article on renaming files (macOS). Additionally, the Audio Production Tips blog offers real-world examples from experienced producers.
Final Word
Proper file naming and organization for ACX submission is not busywork — it is a best practice that directly impacts your audiobook’s approval speed and the sanity of everyone involved. By adopting a consistent, minimal naming convention, building a logical folder hierarchy, and validating every file before submission, you eliminate the most common causes of rejection. Spend an hour setting up a system now; it will save you days of troubleshooting later. Your listeners (and your future self) will thank you.