Submitting a finished audiobook to ACX (Audiobook Creation Exchange) is more than just uploading a batch of audio files—it is a rigorous process that demands precision, consistency, and thorough preparation. ACX has specific technical requirements and expects a clean, professional product. Without a solid system for managing and organizing your audio files, you risk rejection, late delivery, or loss of work. This guide expands on essential organization strategies and introduces advanced practices to help you navigate the ACX submission process efficiently, reduce errors, and maintain a high-quality production workflow.

1. Create a Clear Folder Structure

A well-defined folder structure is the backbone of any organized audio project. It prevents confusion, speeds up file retrieval, and ensures that everyone involved (narrator, editor, reviewer) can work from the same logical layout.

Why a Dedicated Project Folder Matters

Mixing audio files from different projects or scattering them across your desktop is a recipe for mistakes. A single project folder keeps everything in one place. Inside this folder, create subfolders for each logical unit of your audiobook—typically chapters, but also for the introduction, copyright notice, and any bonus content.

Consider a structure like this:

  • Project_Root (named Author_Title_ACX)
  • 01_Recordings – Raw, unedited takes
  • 02_Edits – Processed files ready for review
  • 03_Mastered – Final versions aligned to ACX specs
  • 04_Approved – Files that have passed quality check
  • 05_Backups – Copies of critical stages

Inside each stage folder, create chapter subfolders labeled Chapter_01, Chapter_02, and so on. This way, you can quickly find the third mastered version of Chapter 12 without digging through hundreds of files.

Naming Subfolders

Use leading zeros for single-digit chapters (Chapter_01 instead of Chapter_1) so they sort correctly in any file browser. Avoid generic names like “final” or “new” unless you include a date stamp. Consistency in naming your subfolders is as important as naming the audio files themselves.

2. Adopt Consistent File Naming Conventions

ACX recommends filenames that clearly identify the content and version. A standardized naming system makes it easy to track files during editing, quality control, and final submission.

Elements to Include

  • Author last name (or a short code)
  • Title abbreviation (short enough to avoid truncation)
  • Chapter number (padded with zeros)
  • Version indicator (e.g., v1, v2, _edit, _master)
  • File extension (.wav or .aiff)

Example format: Smith_GreatGatsby_Ch01_v1.wav

Avoid Common Pitfalls

  • Do not use spaces—use underscores or hyphens instead.
  • Avoid special characters like &, #, %, or /.
  • Keep filenames short but descriptive. Long names may be truncated in some systems or cause errors during upload.
  • Be consistent with capitalization. ACX is case-insensitive but for human readability, use TitleCase or lowercase.

A standardized naming convention also simplifies automated processing. If you use batch processing tools (e.g., to normalize audio or add metadata), consistent filenames allow you to sort and operate on the correct files programmatically.

3. Maintain High Audio Quality—Meeting ACX Specifications

ACX has published strict audio specifications that your files must meet. Simply recording in a quiet room is not enough; you must verify your files against these standards before submission.

Key Technical Requirements

  • Format: Uncompressed WAV or AIFF; 16-bit or 24-bit sample rate; 44.1 kHz sample rate (most common). Avoid MP3 or other lossy formats.
  • RMS Level: Between -23 dB and -18 dB. Too quiet or too loud may trigger an automatic rejection.
  • Peak Level: Not exceeding -3 dB (true peak). Clipping will cause immediate failure.
  • Noise Floor: Below -60 dB (no audible hum, clicks, or background noise).
  • Headroom: Consistent dynamic range—avoid sudden volume jumps between chapters.

Tools to Check Your Audio

Use a free audio editor like Audacity or Reaper. Most have metering plugins that display RMS and peak levels. For batch validation, consider the ACX Check plugin (for Audacity) or third-party tools like Piral (audioproofing).

Your Pre-Submission Audio Checklist

  • All files are in WAV/AIFF, 44.1 kHz, 16-bit.
  • No clipping, no DC offset.
  • RMS level hovers around -21 dB (within the -23 to -18 range).
  • No audible room tone variations between chapters.
  • No plosives, mouth noises, or sibilance after editing.

Maintaining a high-quality recording from the start saves you from having to re-record or heavily process files later.

4. Implement a Thorough Quality Control Routine

Even the most experienced narrators produce imperfect takes. A dedicated QC process catches errors before they reach the listener—or the ACX reviewer.

Step-by-Step QC Workflow

  1. Listen in a quiet environment using closed-back headphones that reveal flaws.
  2. Check for technical issues: clipping, hum, pops, clicks, and background noise. Use a frequency analyzer to look for 60 Hz hum.
  3. Verify volume consistency across the entire chapter and then across the whole audiobook. The RMS should not jump by more than 1 dB between consecutive chapters.
  4. Proof the spoken word against the manuscript to catch misread lines, missing paragraphs, or repeated phrases.
  5. Mark errors with track markers or a time-stamped log so the editor knows exactly where to fix.

Batch Processing for Efficiency

If you have many files, use software like Audacity’s Chains or Reaper’s Actions to apply normalization, noise reduction, and compression consistently. This reduces manual labor but still requires a final listening check.

Common QC Red Flags

  • Audio levels that are too low or too high.
  • Long silences at the beginning or end of a file (ACX expects between 0.5 and 1 second of silence at the start, and no more than 5 seconds at the end).
  • Clicking between edited splices.
  • Room tone changes due to different recording sessions.

A rigorous QC routine ensures your audiobook meets ACX standards and minimizes the chance of a revision request.

5. Track Your Progress Meticulously

Managing dozens or hundreds of audio files requires a tracking system. Without one, you risk sending a file that hasn’t been approved, or worse, missing a file entirely.

What to Track

  • File name and version number.
  • Status: Recorded, Edited, QC Passed, Final, Uploaded.
  • Date of each status change.
  • Notes about any issues or special instructions.
  • Retakes – track when a file needed re-recording.

Tools for Tracking

A simple spreadsheet (Google Sheets or Excel) works wonders. Create columns for Chapter, File Name, Status, QC Notes, and Upload Date. Color-code cells: red for problems, yellow for in progress, green for approved.

If you collaborate with an editor or proof listener, consider project management tools like Trello, Asana, or Airtable. They allow you to assign tasks, add comments, and see the entire project pipeline at a glance.

Version Control

Keep every version of a file—never overwrite. If you re-record a chapter, save the new take with a higher version number (e.g., Ch12_v2.wav). This gives you a fallback if something goes wrong during mastering.

6. Backup Your Files Regularly

Data loss can happen at any time—a crashed hard drive, corrupted SD card, accidental deletion. Backups are non-negotiable for a professional production.

Follow the 3-2-1 Rule

  • 3 copies of your data (one primary, two backups).
  • 2 different media types (e.g., external hard drive + cloud storage).
  • 1 copy offsite (cloud, or a drive stored at a different location).

Cloud Options

Dropbox, Google Drive, and OneDrive offer sync and version history. For large WAV files, consider services like Backblaze or dedicated backup plans. Always encrypt sensitive files before uploading if privacy is a concern.

Automate When Possible

Use time-saving automation: set your audio editing software to auto-save regularly, and configure your cloud storage to sync the project folder automatically after each session. This ensures you never have to remember to manually backup.

7. Additional Best Practices for a Smooth Submission

Beyond the basics, these extra strategies can elevate your organization and prevent last-minute surprises.

Metadata Tagging

ACX does not require metadata in the audio files, but adding tags (title, author, chapter number, narrator name) inside the WAV file can be helpful for internal reference and for distributors who later process the files. Use tools like MetaFlac (for FLAC) or Audacity’s Metadata Editor. Keep tags consistent.

Use a Submission Checklist

Create a document that lists every step before you hit “upload” on ACX. Include: file format check, RMS check, file naming compliance, no special characters, all chapters present, cover art ready, and the final zip package. Print it out or keep it as a pinned note.

Template Directory Structure

Save your folder and subfolder setup as a blank template. When starting a new audiobook, copy the template and rename it. This saves time and ensures you never miss a folder.

Collaborate with a Proof Listener

Fresh ears catch errors you miss. Have someone else listen to the final mastered files against the manuscript. Give them a strict deadline and a clear log template for feedback. This external review can be the difference between a first-pass acceptance and a revision request.

Prepare for ACX’s Review Process

After submission, ACX performs an automated check for audio specs and often a human review. If a problem is found, you’ll receive a revision request with specific file references. Having a well-organized project makes it trivial to locate and fix the flagged file.

8. Summary of Key Actions

  • Folder structure: Consistent hierarchy with padded chapter numbers.
  • File naming: Uniform convention—author, title, chapter, version, extension.
  • Audio quality: Meet ACX specs for RMS, peak, noise floor, sample rate, format.
  • Quality control: Listen to every file, check for errors, use batch processing.
  • Tracking: Use a spreadsheet or project tool to monitor status, version, and notes.
  • Backups: 3-2-1 rule with cloud + external drives.
  • Extra polish: Metadata tagging, submission checklist, proof listener feedback.

Managing audio files for an ACX submission is as much about process as it is about technical skill. By establishing clear folder structures, adopting consistent naming conventions, maintaining eagle-eyed quality control, and backing everything up, you reduce stress, minimize errors, and deliver a professional audiobook that meets ACX standards on the first try. The time you invest in organization will pay off—not only in a smoother submission but also in the confidence that your work is ready for listeners.