Managing audio files during the review and feedback phase of an ACX audiobook project can determine whether your production stays on schedule or spirals into endless revisions. The platform’s built-in tools are powerful, but they only work as well as your file management, communication, and editing practices. This guide outlines best practices for handling audio files from submission through final approval, helping you avoid common pitfalls and deliver a polished audiobook.

Understanding ACX Audio Specifications and Workflow

Before any file touches the review stage, you must confirm that every recording meets ACX’s technical requirements. ACX mandates a sample rate of 44.1 kHz, 16-bit depth, mono channel, and a constant bitrate of 192 kbps or higher for MP3 uploads. The file must also comply with volume specifications: RMS of -23dB to -18dB, peak not exceeding -3dB, and noise floor below -60dB. Submissions that fall outside these parameters are returned for correction, wasting time for both narrator and author.

Familiarize yourself with ACX’s official audio submission guidelines before you export your first file. Keep a checklist next to your recording station so no technical detail is overlooked.

Preparing Audio Files for Submission

A clean, well-organized submission makes the review process far smoother. Editing should remove all mouth clicks, breath noises (unless stylistically desired), plosives, sibilance, and background hum. Truncate silences between sentences to a natural rhythm — typical gaps range from 0.5 to 1 second. Between chapters, aim for a 3–4 second pause.

File Naming Conventions

Every file should carry a meaningful name that identifies its content and version. For example:

  • Chapter-05_FirstRead_v1.wav
  • Chapter-05_Revised_nov15.wav
  • Chapter-05_Final_Approved.wav

This system lets anyone on the team instantly understand what they are listening to. Avoid ambiguous names like audio5final2.wav that invite confusion.

Embedding Metadata

Most professional audio editors allow you to embed metadata into WAV or MP3 files. Include the title, chapter number, narrator name, and date. This metadata survives file transfers and prevents mix-ups when multiple files are re-uploaded.

Sharing Audio Files for Feedback

ACX provides a secure upload and playback system, but many producers prefer to supplement it with cloud storage for temporary drafts. When using Dropbox, Google Drive, or a similar service, set permissions to “view only” or “comment.” This prevents accidental overwrites. Send a shareable link directly to the reviewer, along with a brief message explaining what you are seeking feedback on — pacing, emotional tone, pronunciation, or something else.

For large projects, consider using a dedicated collaboration tool like Wipster or Frame.io (which now supports audio). These platforms allow time-coded comments directly on the waveform, making it easy to pinpoint issues without writing lengthy descriptions.

Setting Clear Expectations

Before sending files, agree with the author or producer on what type of feedback is expected. Does the author want to review only for content accuracy, or are they also critiquing performance? Clarify whether they will listen to every chapter or only a sample. This prevents unnecessary revisions and keeps the project moving.

Incorporating Feedback Effectively

When feedback arrives, resist the urge to re-record whole sections piecemeal. Instead, follow a systematic approach:

  1. Log every comment in a spreadsheet or project management tool, noting the file name, timecode, and the nature of the issue (pronunciation, background noise, pacing, etc.).
  2. Batch similar edits. If multiple chapters need a noun pronunciation corrected, record those replacements in one session instead of jumping between chapters.
  3. Use punch-and-roll recording. Re-record only the affected phrase while keeping the original take as a reference. This preserves the natural room tone and voice consistency.
  4. Check crossfades. Edits should be seamless. Listen for pops, clicks, or abrupt changes in background noise that appear after splicing.

Tools for Precision Editing

Professional software like Audacity (free), Adobe Audition, or Reaper gives you control over spectral editing, noise reduction, and normalization. For ACX-specific workflows, plugins like Apterea StylePlus can automatically match loudness and dynamic range to ACX specs.

Version Control Best Practices

As files evolve, a version control system prevents nightmare scenarios like sending the wrong take to the author or losing a perfectly good master.

Folder Structure

Create a root folder for the audiobook project. Inside, maintain subfolders:

  • Raw recordings – untouched takes straight from the mic.
  • Edited masters – cleaned, leveled, and retouched versions ready for review.
  • Approved finals – confirmed submissions that also serve as your backup archive.

Within each folder, use a consistent naming scheme as described earlier. Never delete old versions; keep them in a “backup” subfolder in case you need to revert.

Using Git-LFS for Audio

If you are comfortable with developer tools, Git Large File Storage (LFS) can track changes to binary audio files and let you roll back to any point in time. This is overkill for most solo producers but invaluable for teams with multiple engineers.

Managing Multiple Review Rounds

ACX allows for up to three rounds of review. Each round should have a clear objective. The first round might focus on overall performance and content errors, the second on details like sound quality and volume, and the third as a final QA pass. Document what was requested and fixed in each round so that neither party forgets what was already approved.

Communicating Changes to the Author

After you finish editing based on feedback, send a quick summary: “Chapter 3: Replaced two mispronunciations at 2:15 and 5:40. Reduced background noise in the first 30 seconds. No other changes.” This builds trust and reduces the need for the author to re-listen to the entire file.

Final Review and Quality Assurance

Before uploading to ACX for official approval, perform a comprehensive QA check. Listen to every file from start to finish on good headphones or studio monitors. Check for:

  • Consistent volume across chapters (use loudness metering to verify RMS within -23dB to -18dB).
  • No audible editor cuts or sudden noise floor changes.
  • Correct chapter titles and gaps.
  • Proper adherence to ACX’s upload protocol (MP3 file at correct bitrate, WAV master preserved).

If the project includes multiple narrators (e.g., a dual-narrator book), ensure their audio matches in level, tonality, and perceived distance from the microphone. You may need to apply EQ or compression to one voice to make them sound cohesive.

Using ACX’s Built-In Validation

Before submitting, run your files through ACX’s Check My Audio tool. It will flag volume or format issues immediately. Correct any errors before sending to the author for approval.

Common Pitfalls and How to Avoid Them

  • Inconsistent room tone: Always record in the same space with the same microphone position. If you must re-record later, try to match the original environment.
  • Over-editing: Removing every single breath makes the narration sound unnatural. Leave enough to preserve performance.
  • Ignoring background noise: A low hum that is inaudible on monitors may become obvious on consumer earbuds. Use noise reduction sparingly but thoroughly.
  • Poor communication: If feedback is ambiguous, ask for clarification. Guessing at a vague comment leads to wasted effort.

Conclusion

Handling audio files during the review and feedback process with ACX requires discipline, but the payoff is a streamlined workflow and a high-quality audiobook that passes technical inspection on the first try. By preparing files meticulously, communicating clearly with reviewers, implementing feedback methodically, and maintaining rigorous version control, you reduce stress and avoid costly delays. Adopt these best practices as your standard operating procedure, and your ACX projects will move from recording to publication with fewer hiccups and stronger outcomes.