Understanding ACX Technical Specifications

ACX (Audiobook Creation Exchange) enforces strict technical standards to ensure consistent playback quality across Audible, Amazon, and iTunes. Every file you upload must conform to these specifications or risk rejection during the review process. Beyond the basic MP3 format, the platform requires a constant bitrate of 192 kbps, a sample rate of 44,100 Hz, and mono or stereo channels — with stereo being the preferred choice for most producers. The file naming convention must be clear and sequential, typically following a pattern like AuthorName_Title_Chapter01.mp3. Understanding these requirements is the first step to a smooth submission.

ACX’s quality standards exist because audiobook listeners expect a consistent, professional experience across thousands of titles. A file that plays perfectly on one device might skip, distort, or fail to load if its encoding deviates from the platform’s baseline. Every technical parameter — from bitrate to sample rate to channel layout — directly affects how the audio behaves during streaming, download, and playback on devices ranging from high-end headphones to car stereos to budget smart speakers.

Why Each Specification Matters

Bitrate: 192 kbps Constant

ACX mandates a constant bitrate (CBR) of 192 kbps, not variable (VBR). Constant bitrate ensures predictable data flow during streaming and download, which is critical for audiobook players that rely on consistent decoding. If you export with VBR, the file size fluctuates and can cause playback glitches on certain devices. Always double-check your export settings to confirm CBR 192 kbps is selected.

The reason ACX insists on CBR comes down to how audiobook playback systems work. Unlike music streaming, where buffering can smooth out VBR fluctuations, audiobook players often skip forward and backward by specific time stamps. VBR files can introduce timing inconsistencies that make chapter markers drift or cause audible pops when the player jumps between sections. Producers who attempt to use VBR at 192 kbps to save a few megabytes often end up with rejected files and delayed releases.

Some DAWs label CBR options differently. In Audacity, you select “Constant” from the Bit Rate Mode dropdown. In Adobe Audition, you choose “CBR” from the Bitrate Type menu. In Reaper, you set Mode to “Constant bitrate.” If your DAW does not explicitly label the option — as with GarageBand — you must verify the output file manually. A file showing “VBR” in its metadata will not pass ACX validation, regardless of the average bitrate value.

Sample Rate: 44,100 Hz

This is the standard CD-quality sample rate. It captures the full frequency range of the human voice without unnecessary data overhead. Higher sample rates like 48,000 Hz or 96,000 Hz introduce aliasing artifacts when downsampled by ACX’s processing pipeline. Stick to 44,100 Hz throughout your entire production chain — from recording to final export.

The human voice typically occupies the range of 80 Hz to 8,000 Hz, with most intelligible speech falling between 300 Hz and 3,400 Hz. A 44,100 Hz sample rate gives you more than enough headroom to capture every nuance of a narrator’s performance without wasting bandwidth on frequencies that neither the human ear nor typical playback equipment can reproduce. Higher sample rates like 48,000 Hz, common in video production, force ACX’s encoding pipeline to downsample, which can introduce unwanted artifacts if not handled carefully.

A common mistake is recording at 96,000 Hz and then downsampling to 44,100 Hz during export. This process can generate ultrasonic noise that folds back into the audible range, creating subtle distortion that may not be obvious until the file is played on high-quality equipment. The safest approach is to set your project sample rate to 44,100 Hz at the very beginning and never change it.

Channel: Stereo Preferred

While ACX accepts mono files, stereo is recommended. Even though most audiobooks are narrated in a single voice, stereo preserves spatial consistency and avoids phase issues that can occur when mono files are played on stereo systems. If your recording setup uses a single microphone, pan your track to centre and export as stereo. This gives you maximum compatibility across all listening environments.

The stereo versus mono decision affects more than just soundstage. Mono files processed through ACX’s distribution pipeline can sometimes be incorrectly mapped on devices that expect stereo audio. Some smart speakers and car audio systems apply stereo widening or spatial audio processing to all content, and a true mono file can trigger unintended phase cancellation or comb filtering effects. Exporting as stereo with identical left and right channels avoids these edge cases entirely.

Producers recording with a single microphone should still capture in mono, then pan the track to centre before exporting as a stereo file. This preserves the bitrate efficiency of a mono recording while ensuring the final output meets ACX’s stereo recommendation. The file size difference between a 192 kbps mono MP3 and a 192 kbps stereo MP3 with identical channels is negligible — typically less than 5 percent — so there is no practical reason to choose mono over stereo.

Step-by-Step Export Workflows by DAW

Audacity

Audacity remains the most popular free DAW for audiobook production. To export properly:

  1. Open your project and ensure the track is set to stereo. Go to Tracks > Stereo Track if needed.
  2. Set the project sample rate to 44100 Hz in the bottom-left corner of the interface.
  3. Select the entire track or the region you want to export.
  4. Go to File > Export > Export as MP3.
  5. In the export dialog, set Bit Rate Mode to Constant and Quality to 192 kbps.
  6. Name your file using the ACX naming convention and click Save.

A common pitfall in Audacity is forgetting to set the sample rate before editing. If you change the sample rate after editing, the audio will be resampled and quality may degrade. Always set your project rate at the start.

Audacity users should also note that the default MP3 encoding uses the LAME encoder, which must be installed separately on some systems. If the export dialog does not show bitrate options, download and install the LAME library from the official Audacity website. Once installed, the encoder provides full CBR support at any bitrate from 32 kbps to 320 kbps.

Adobe Audition

Audition offers robust batch processing, ideal for multi-chapter projects:

  1. Open your multitrack session or waveform editor.
  2. Ensure the file is stereo and set to 44100 Hz. You can check in Edit > Edit Sample Rate.
  3. Go to File > Export > Multitrack Mixdown > Entire Session (or use the waveform export option).
  4. In the export dialog, choose MP3 format.
  5. Click Options and set Bitrate to 192 kbps and Bitrate Type to CBR.
  6. Name your file sequentially and export.

Adobe Audition allows you to save export presets. Create an ACX-specific preset to avoid repeating these steps for every chapter. To save a preset, configure all export options, then click the preset dropdown and select Save Preset. Name it something like ACX Audiobook and it will appear in every future export dialog.

Audition’s batch processing is particularly powerful. Open the Batch Process panel from the Window menu, add all your chapter files, configure the output format to MP3 with ACX-compliant settings, and run the batch. The tool can also apply effects like EQ, compression, or normalisation across all files simultaneously, saving hours of manual processing.

GarageBand

GarageBand is less commonly used for audiobooks due to its limited export options, but it works with a workaround:

  1. Complete your recording and ensure the project tempo is irrelevant — set it to any value.
  2. Go to Share > Export Song to Disk.
  3. In the export window, set Quality to Custom.
  4. Choose MP3 Encoder with Stereo Bitrate: 192 kbps and Sample Rate: 44.100 kHz.
  5. Name the file and export.

GarageBand does not allow you to explicitly set CBR versus VBR, so always verify the final file using a tool like MediaInfo or the ACX Checker. In practice, GarageBand’s MP3 encoder defaults to CBR at the selected bitrate, so most exports pass validation. However, if you update the operating system or GarageBand version, the encoder behavior can change. Verify every file until you are confident in your specific setup.

One limitation of GarageBand is the inability to export multiple regions as separate files. For multi-chapter audiobooks, you must either export each chapter individually or switch to a more capable DAW like Audacity or Reaper.

Reaper

Reaper is gaining traction among audiobook producers for its flexibility and low cost:

  1. Set your project sample rate to 44100 Hz in File > Project Settings > Audio Settings.
  2. Ensure the track is stereo.
  3. Go to File > Render.
  4. In the render dialog, choose MP3 (LAME) as the output format.
  5. Set Mode to Constant bitrate and Quality to 192 kbps.
  6. Name the file and render.

Reaper’s render queue is excellent for batch exporting multiple chapters. Set up one chapter, add it to the queue, adjust the file name pattern, and render all at once. To use the render queue effectively:

  • Create regions for each chapter using the Region/Marker Manager.
  • Name each region with the chapter number and title.
  • Open the render dialog, select Region render matrix, and configure the file name pattern to use $region as the output name.
  • Add the job to the queue and repeat for all regions.
  • Render the entire queue in one pass.

Reaper also supports wildcards in file naming. Use patterns like $track-$region ($year-$month-$day) to generate consistent, descriptive file names automatically.

Logic Pro

Logic Pro users have more control than GarageBand but must still be careful with export settings:

  1. Set your project sample rate to 44,100 Hz in File > Project Settings > Audio.
  2. Ensure the output is stereo by checking the channel strip configuration.
  3. Go to File > Export > All Tracks as Audio Files.
  4. In the export dialog, choose MP3 as the file type.
  5. Click Options and set Bit Rate to 192 kbps and Bit Rate Mode to CBR.
  6. Name the file and export.

Logic Pro’s bounce function also works for single-file export. Use File > Bounce > Project or Section, choose MP3, and configure the settings. The bounce dialog provides a preview of the estimated file size, which can be helpful for confirming the bitrate is correct.

Compressing Files for Upload

ACX accepts individual MP3 files or a single ZIP archive containing all chapters. Compressing into a ZIP file is not required but simplifies uploads, especially for books with 20+ chapters. A ZIP archive preserves your folder structure and file order, reducing the chance of misaligned chapters.

How to Create a Proper ZIP Archive

  1. Gather all MP3 files into a single folder. Name the folder using the book title or project identifier.
  2. Ensure files are named sequentially and consistently. Avoid special characters like #, &, or parentheses — use underscores or hyphens instead.
  3. On Windows: right-click the folder and select Send to > Compressed (zipped) folder.
  4. On macOS: right-click the folder and select Compress.
  5. Name the resulting ZIP file clearly, such as Author_Title_Chapters.zip.
  6. Upload the ZIP to ACX. The platform will automatically extract and process the files.

Do not compress the files further with lossy codecs inside the ZIP. The ZIP container should only hold your 192 kbps MP3s. Double compression degrades audio quality unnecessarily. Also avoid using compression formats other than ZIP — ACX only supports standard ZIP archives, not RAR, 7z, or TAR files.

When ZIP Archives Are Problematic

ZIP files simplify uploads but can introduce issues if your files are incorrectly named or if the ZIP is corrupted. ACX expects files in alphabetical order when extracted, so pad chapter numbers with zeros (Chapter01, Chapter02, etc.). If your chapters are misordered, the audiobook will play out of sequence. Always test your ZIP by extracting it locally before uploading.

Another common ZIP issue is file path length. On Windows, the maximum path length for extraction is 260 characters by default. If your folder hierarchy is too deep or your file names are too long, the ZIP may extract incorrectly. Keep folder names short and flat — avoid nesting folders inside the ZIP archive. Put all MP3 files directly in the root of the ZIP, not in subdirectories.

If you experience ZIP corruption, try recreating the archive with a different tool. Built-in compression in Windows and macOS works reliably for most users, but third-party tools like 7-Zip or WinRAR can produce archives that are more resilient to upload errors. If you use third-party software, select the Store compression method to avoid recompressing the already-compressed MP3 files.

Validating Your Files Before Upload

ACX provides a Checker Tool that scans your MP3 files for compliance. Run every file through this tool before uploading. The checker verifies bitrate, sample rate, channel count, and file naming. It also checks for audio issues like clipping, DC offset, and excessive silence.

The ACX Checker Tool is available as a free download from the ACX website. It runs on Windows and macOS and provides a detailed report for each file. The tool highlights any specification violations with specific error codes, making it easy to identify and fix issues before submission. Run the checker on your ZIP archive as well — some producers forget that the tool can scan compressed archives directly.

Manual Validation with MediaInfo

MediaInfo is a free, open-source tool that displays detailed metadata about your audio files. Use it to confirm:

  • Format: MPEG Audio
  • Bit rate: 192 kbps (constant)
  • Sampling rate: 44,100 Hz
  • Channel(s): 2 (stereo) or 1 (mono)
  • Codec ID: 55 (MP3 constant bitrate)

If you see VBR in the bit rate mode field, re-export the file with CBR selected. MediaInfo also shows the exact bitrate value — sometimes a file labelled as 192 kbps actually encodes at 191 kbps or 193 kbps due to encoder rounding. ACX tolerates minor deviations, but values outside the 190–194 kbps range can trigger rejection.

MediaInfo offers a tree view and a text view. The text view is easier to parse for quick checks. On macOS, the MediaInfo command-line tool is available via Homebrew for users who prefer terminal-based workflows.

Loudness and Dynamic Range

ACX also has loudness guidelines. The average loudness should be between -23 dBFS and -18 dBFS, with a maximum peak of -3 dBFS. Use an LUFS meter in your DAW or a dedicated tool like Youlean Loudness Meter to check. If your audio is too quiet or too loud, apply compression or limiting before export. Consistent loudness across all chapters prevents the listener from constantly adjusting volume.

The loudness standard for spoken-word content differs from music. Music tracks are often mastered to -14 LUFS or even louder, but audiobooks need headroom for dynamic range — the natural variation in a narrator’s volume. A narrator who whispers during quiet passages and raises their voice during emotional moments should still stay within the -23 dBFS to -18 dBFS range overall. Use an integrated LUFS measurement over the entire chapter, not short-term peaks.

Many DAWs include built-in loudness meters. Audition has a Loudness Radar effect, Reaper offers the integrated Loudness Meter JSFX, and Audacity supports loudness measurement through the Contrast Analyzer. For precise control, use a dedicated plugin like Orban Loudness Meter or DPA Meter during the mastering stage.

Common Pitfalls and Troubleshooting

File Rejection Due to Bitrate

The most common rejection reason is incorrect bitrate. Even if you set 192 kbps in your DAW, some export dialogs default to VBR. Always verify with the ACX Checker or MediaInfo before uploading.

Another bitrate pitfall involves sample rate conversion. Some encoders change the bitrate when downsampling from a higher sample rate. For example, exporting from a 48 kHz project to 44.1 kHz can cause the encoder to recalculate the bitrate, resulting in a value slightly below 192 kbps. The fix is simple: set the sample rate to 44.1 kHz at the project level, not during export.

Sample Rate Mismatch

If your project sample rate is set to 48,000 Hz and you export to MP3, the file may still show 48,000 Hz in the metadata. ACX will reject it. Convert your project to 44,100 Hz before editing, not after. Resampling after compression introduces artifacts.

Some DAWs allow you to change the sample rate in the export dialog without changing the project rate. This creates a mismatch between the project rate and the output rate, which can cause the encoder to produce distorted audio. Always match the project sample rate to the export sample rate before rendering.

Stereo vs. Mono Confusion

Exporting a mono track as stereo without panning creates a centre-panned stereo file that is technically two identical channels. This is acceptable, but if you accidentally export a true mono file, ACX will still accept it — however, listeners on stereo systems may experience a narrower soundstage. For consistency, always export as stereo.

A related issue is exporting a stereo track with one silent channel. Some producers accidentally record in mono, then duplicate the channel to create stereo, but leave one channel muted or at a different level. The resulting file passes ACX validation but sounds unbalanced on systems that process left and right channels independently. Use a phase correlation meter to verify that both channels contain identical audio.

File Naming Errors

ACX expects files to be named in a way that clearly indicates chapter order. Avoid names like Chapter 1 (final).mp3 — the parentheses and spaces can cause sorting issues in the ZIP extraction. Use underscores: Chapter_01.mp3.

ACX’s extraction system sorts files alphabetically by file name. If you use single-digit chapter numbers (Chapter1, Chapter2, ..., Chapter10), the system sorts Chapter1, Chapter10, Chapter2 — causing the audiobook to play in the wrong order. Always pad numbers with leading zeros: Chapter01, Chapter02, ..., Chapter10. For books with more than 100 chapters, use three digits: Chapter001, Chapter002, etc.

Optimizing Your Workflow for Multi-Chapter Projects

For audiobooks with 20, 50, or even 100 chapters, manual export of each file is tedious and error-prone. Build a batch processing workflow to save time and reduce mistakes.

Using Audacity’s Label Tracks

Record the entire book as a single long file, then use label tracks to mark chapter boundaries. Export each label region as a separate MP3 with a single command. Go to File > Export Multiple, choose Split files based on labels, and set your export preferences. This automates file naming and ensures consistent settings across all chapters.

Label tracks in Audacity also support metadata. You can add chapter titles, track numbers, and album information directly into the label track, and the Export Multiple function embeds this metadata into each MP3 file. This is especially useful for audiobooks that will be distributed through multiple platforms, as consistent metadata improves discoverability.

Adobe Audition’s Batch Process

Audition’s Batch Process panel lets you apply the same export settings to multiple files. Drag in all your raw chapter files, set the output format to MP3 with 192 kbps CBR and 44,100 Hz, and run the batch. The tool also applies effects like normalisation or compression if needed.

Audition’s batch processor includes a match loudness feature that automatically normalises all files to a target LUFS level. This is extremely useful for multi-chapter audiobooks where each chapter was recorded in different sessions or with different microphone setups. Set the target loudness to -20 LUFS (midpoint of the ACX range) and let Audition handle the rest.

Reaper’s Render Queue

Reaper allows you to create a render queue with different regions. Set region start and end points for each chapter, add them to the queue, and render all at once. You can use the region name as the file name pattern. This approach is fast and reliable for large projects.

Reaper also supports wildcard file naming with metadata fields. You can embed the project name, region number, total region count, and date into each file name automatically. A pattern like BookTitle_Chapter_$regionnumberof$totalregions produces clean, consistent file names that sort correctly in any file system.

Using Scripts for Automation

For producers working with extreme numbers of files — 200 or more chapters — manual batch processing still involves too many clicks. Consider using scripts to automate the entire export pipeline. Reaper supports Python, Lua, and EEL scripting, while Audacity supports Nyquist plugins. Simple tasks like trimming silence, normalising loudness, and exporting with ACX-compliant settings can be scripted into a single button press.

Third-party tools like FFmpeg can also process entire directories of audio files with a single command. For example, a bash script that runs ffmpeg -i input.wav -codec:a libmp3lame -b:a 192k -ar 44100 -ac 2 output.mp3 on every WAV file in a folder converts an entire audiobook to ACX-compliant MP3s in seconds.

Final Quality Control Checklist

Before uploading to ACX, run through this checklist:

  • All files are MP3 format
  • Bitrate is constant 192 kbps
  • Sample rate is 44,100 Hz
  • Channel is stereo
  • File names are sequential and use underscores or hyphens
  • No files exceed the maximum individual file size (if any — ACX generally accepts files up to 2 GB)
  • ZIP archive is not corrupt
  • Loudness is between -23 dBFS and -18 dBFS
  • Peak level does not exceed -3 dBFS
  • No audible clipping or distortion
  • All chapters play in correct order
  • Metadata is consistent across all files (album name, artist, track numbers)
  • No silent gaps or missing audio at chapter boundaries

Taking the time to validate every file will save you from a rejection that could delay your audiobook’s release by weeks. ACX’s review process typically takes 10–14 business days, and a rejection resets the clock. Investing 30 minutes in quality control can prevent a two-week delay.

External Resources

For further reading, refer to the official ACX submission guidelines at ACX Audio Submission Requirements. The ACX Checker Tool is available for download from ACX’s website. For technical details on MP3 encoding standards, consult the MP3 Tech resource. If you need loudness measurement tools, Youlean Loudness Meter offers a free version that works with most DAWs. Finally, the MediaInfo tool is indispensable for verifying file metadata before upload.

For producers who want deeper technical knowledge, the Hydrogenaudio LAME Wiki provides comprehensive documentation on MP3 encoding parameters, including the exact command-line switches for CBR encoding at 192 kbps. Understanding the encoding process at this level makes it easier to troubleshoot issues when DAW presets behave unexpectedly.

Conclusion

Exporting and compressing files for ACX compatibility is a straightforward process when you understand the technical requirements and follow a repeatable workflow. Pay attention to bitrate, sample rate, and channel configuration in every export. Validate your files with the ACX Checker and MediaInfo before uploading. For large projects, batch processing saves time and ensures consistency. By adhering to these standards, you minimise the risk of rejection and deliver a high-quality audiobook that meets the expectations of both ACX and your listeners.

Building a reliable workflow takes time, but the effort pays off with every successful submission. The producers who avoid rejection are not the ones with the most expensive equipment — they are the ones who test every file, check every setting, and follow a consistent process from start to finish. Adopt these practices early, and your audiobook production will run smoothly from the first chapter to the final upload.