All articles
ACX

Why Your ACX Submission Keeps Getting Rejected

By 7 min read
TL;DR
  • 01ACX measures your noise floor throughout the entire file, not just at the start. That pause between two sentences needs to hold at -60 dB RMS too.
  • 02Your DAW's peak meter and True Peak are two different things. If you're not using a True Peak meter, you might be failing without knowing it.
  • 03ACX checks each chapter individually. One quiet chapter can drag you out of the -23 to -18 dB RMS range even if your overall average looks fine.

You did everything right. Hours of recording, careful editing, a limiter on the master, clean exports. You uploaded to ACX and hit submit. Then the email came back: rejected.

The frustrating part is that ACX's rejection messages are often vague. "Audio quality does not meet requirements" could mean about six different things. This guide breaks down every technical reason submissions fail, explains exactly what ACX is actually measuring, and tells you how to fix each one before it costs you another round of edits.

What ACX Actually Checks

Every file you submit gets run through an automated QC process that measures four things. The values below come straight from the official ACX audio submission requirements:

ParameterACX Requirement
RMS Level-23 to -18 dB RMS
Peak-3 dB maximum
Noise Floor-60 dB RMS or lower
File FormatMP3, 192 kbps or higher, CBR, 44.1 kHz

Four numbers. But the way they're measured is where most people get tripped up.

The 6 Reasons Your File Is Getting Rejected

Noise Floor Measured in the Wrong Place

This is the most common one, and it catches a lot of experienced narrators off guard. Most people check the noise floor at the very start of the file, see a nice clean -65 dBFS reading, and move on. Then ACX rejects it anyway.

Here's why: ACX measures noise floor in any silence segment throughout the entire file. That includes the half-second gap between sentences, the breath pause before a new paragraph, and the room tone at the end. If your air conditioning kicks in mid-session, or your mic self-noise creeps up over a long recording day, those mid-file silences will fail even if your intro sounds perfect.

FixAfter editing, take a 1-second silence measurement from somewhere in the middle of the chapter, not just the top. A pause between two sentences works perfectly. That's the reading ACX is actually using.

Confusing True Peak with Peak

Your DAW's standard peak meter shows one number. ACX requires peaks at -3 dB or below, and the safe way to verify that is with a True Peak meter (dBTP). Sample peak and True Peak are not the same measurement, and the difference matters.

True Peak catches inter-sample peaks, which are clipping events that happen during digital-to-analog conversion. A file that shows -3.2 dB on your regular peak meter can easily exceed -3 dBTP once it's been processed by ACX's system. You're submitting something you think is clean, and it's failing a check you didn't know existed.

FixUse a limiter or meter that explicitly displays True Peak. In Reaper, ReaLimit shows it. In Audacity, install the ACX Check plugin. Fabfilter Pro-L2, iZotope Ozone, and Waves L2 all show True Peak on their output meters. If your current plugin doesn't mention "True Peak" anywhere, it's not measuring it.

Measuring Loudness Across the Whole Book Instead of Per Chapter

When you submit an audiobook, ACX checks each chapter file independently. If you measure your level across a full batch export of all chapters combined, you might hit -20 dB RMS overall while individual chapters vary anywhere between -17 and -24 dB RMS.

A quiet prologue, a slow chapter without much action, or a session recorded on a different day with slightly different gain settings: any of these can push an individual chapter out of range even when the average looks fine.

FixCheck every chapter separately before you submit. Tedious for a 25-chapter book, yes, but one bad chapter means a full rejection and another round of uploads.

Measuring LUFS Instead of RMS

Modern loudness workflows revolve around LUFS, based on the ITU-R BS.1770 standard, so a lot of narrators verify their chapters with a LUFS meter. But ACX specifies its target in RMS: -23 to -18 dB RMS. The numbers often look similar for spoken word, but they're calculated differently: LUFS applies frequency weighting and gating, while RMS is a straight signal power average.

If you're targeting the range with a LUFS meter, you can sit at -19 LUFS and still fall outside the RMS window - passing or failing by a margin that's invisible in your workflow.

FixVerify with an RMS meter, not (only) a LUFS meter. The free ACX Check plugin for Audacity measures exactly what ACX measures. If you master to a LUFS target, cross-check the final MP3's RMS value before uploading.

Edit Points Causing Micro-Distortion

This one shows up less often, but it's particularly sneaky because it sounds completely fine in your DAW. Hard cuts between takes can create tiny clicks or transient spikes when the waveform isn't at a zero crossing at the edit point. ACX's automated QC sometimes flags these as distortion.

Heavily edited chapters with a lot of punch-ins and comped takes are most vulnerable to this.

FixApply a very short crossfade (2 to 5 ms) to every edit point. It's completely inaudible and eliminates the discontinuity. Most DAWs let you set a default crossfade length that applies automatically to all new edits.

Wrong File Format or Export Settings

ACX accepts exactly one upload format: MP3 at 192 kbps or higher with CBR (Constant Bit Rate), at 44.1 kHz. Record and edit in WAV all you want, but the uploaded file must be MP3. Submitting variable bit rate MP3 or 48 kHz audio fails the technical check regardless of how good your levels are.

FixDouble-check your export settings before every batch. Specifically: confirm MP3 is set to CBR and not VBR, and 44.1 kHz, not 48 kHz. These settings can silently reset in some DAWs after updates. And run your final QC on the encoded MP3, not the WAV master - encoding shifts peaks.

A Pre-Submission Checklist Worth Bookmarking

  1. Measure RMS on each chapter individually (-23 to -18 dB RMS)
  2. Check True Peak with a meter that explicitly says "True Peak"
  3. Measure noise floor mid-file in a silence between sentences, not just the start
  4. Confirm export format: MP3, 192 kbps or higher, CBR, 44.1 kHz
  5. Check for 0.5 to 1 second of silence at the head and 1 to 5 seconds at the tail

Why This Gets Hard at Scale

For a single short chapter, running these checks manually is fine. For a 20-chapter audiobook, it takes a while, and the more you do manually, the more likely a missed step or a misread number becomes. Checking chapter 18 after four hours of editing is not the same as checking chapter 1 fresh.

The other issue is that ACX's automated system doesn't always behave exactly the way things look in your DAW. Subtle inter-sample peaks, noise sitting right on the -60 dB RMS boundary, or a single outlier chapter in a long book can mean a full rejection after days of work.

Running an automated check against the exact ACX spec before you upload removes that uncertainty. If it says pass, you submit with confidence. If it finds a failure, you know exactly which chapter and which parameter to fix before ACX ever sees the file.

Stop checking manually

DubCheck runs all of these checks automatically

LUFS, True Peak, Noise Floor, and LRA checked against the exact platform spec in one click. Pass/Fail PDF report included. Runs 100% locally on your machine.

Download free for macOS