All articles
Audiobooks

Audible ACX vs Findaway Voices vs Spotify Audiobooks: Three Specs, One Master

By 9 min read
TL;DR
  • 01All three platforms accept a master at -20 LUFS integrated, -3 dBTP true peak, -60 dBFS noise floor, 44.1 kHz / 16-bit WAV. That single render passes ACX, Findaway and Spotify Audiobooks without re-export.
  • 02The specs disagree most on file format and chapter structure, not loudness. ACX accepts MP3 192 CBR or WAV. Findaway prefers WAV. Spotify accepts WAV and FLAC. Master to WAV and the conversion is downstream.
  • 03Rejection reasons differ by platform. ACX = automated QC on loudness, noise floor, true peak. Findaway = human QC, broader tolerance, stricter on metadata. Spotify = automated QC similar to ACX with different loudness target.

Five years ago, "publish an audiobook" meant ACX. Now it means three platforms minimum if you want full coverage, and each one publishes a different spec sheet with different numbers. The natural assumption is that you need three different masters. You do not. The platforms disagree on policy, not on what a clean audiobook master looks like.

Here is exactly what each platform requires in 2026, where the specs differ, and the single master that satisfies all of them.

The Three Platforms in 2026

  • Audible / ACX: The original platform. Exclusive or non-exclusive distribution through Amazon's ACX portal. Automated QC. Royalty share or per-finished-hour models.
  • Findaway Voices (Spotify): Spotify-owned wide-distribution platform. Distributes to 40+ retailers including Apple Books, Google Play, libraries, Storytel. Human QC. Per-unit royalty.
  • Spotify Audiobooks: Direct distribution to Spotify's in-app audiobook catalog. Accessed either via Findaway Voices distribution or directly by qualifying publishers. Automated QC similar to ACX.

Most independent narrators and small publishers ship to all three, either directly or via Findaway's downstream distribution. The question is what master to make.

Side-by-Side: The Numbers

ParameterACXFindaway VoicesSpotify Audiobooks
Integrated Loudness-18 to -23 LUFS-18 to -23 LUFS (recommended)-14 to -20 LUFS (target -18)
True Peak Ceiling-3 dBTP-3 dBTP-1 dBTP
Noise Floor-60 dBFS or lower-60 dBFS or lower-60 dBFS or lower (recommended)
Sample Rate44.1 kHz44.1 kHz44.1 or 48 kHz
Bit Depth16-bit16 or 24-bit16 or 24-bit
File FormatMP3 192 CBR or WAVWAV preferred, MP3 acceptedWAV or FLAC
ChannelsMono or stereoStereo preferredStereo
Head Silence0.5 to 1 sec1 sec recommended1 sec recommended
Tail Silence1 to 5 sec2 to 5 sec recommended2 to 5 sec recommended
Chapter StructureOne file per chapter, max 120 minOne file per chapterOne file per chapter
QC TypeAutomatedHumanAutomated

Specs sourced from ACX audio submission requirements, Findaway Voices delivery documentation, and Spotify Audiobooks publisher specs current as of 2026.

Where the Specs Actually Differ

Loudness Target Window

ACX and Findaway publish the same -18 to -23 LUFS window. Spotify Audiobooks targets a hotter range, centered around -18 LUFS, with normalization that lifts quieter material on playback. A master at -20 LUFS passes all three: comfortably inside the ACX/Findaway window, comfortably inside Spotify's lift range.

True Peak Ceiling

ACX and Findaway require -3 dBTP. Spotify requires -1 dBTP. The conservative choice is to master to -3 dBTP. It passes all three. Mastering to -1 dBTP saves 2 dB of headroom but fails ACX and Findaway. There is no upside to that on a voice-only master.

File Format and Bit Depth

ACX is the outlier: it accepts MP3 192 CBR as a primary delivery format, while the other two strongly prefer WAV. The cleanest workflow is to master and deliver in 44.1 kHz / 16-bit WAV for all three. ACX accepts this natively. Findaway prefers it. Spotify accepts it. The MP3 encoding for ACX happens downstream of you or in their pipeline. Do not master to MP3.

QC Type

ACX and Spotify run automated checks. A file that misses the numbers gets bounced by a machine inside 24 hours. Findaway uses human QC, which means broader tolerance on numbers but stricter checking on perceptual things: mouth clicks, breath consistency, room tone matching across chapters, performance issues. A file that scrapes through ACX's loudness check by 0.5 dB will likely also pass Findaway, but Findaway is the platform most likely to flag a chapter that sounds inconsistent with the rest of the book.

The Single Master That Passes All Three

Master to this:

  • Integrated loudness: -20 LUFS (±0.5 LU)
  • True peak ceiling: -3 dBTP
  • Noise floor: -60 dBFS or lower at every silence inside the file, not just the head
  • Sample rate / depth: 44.1 kHz / 16-bit WAV
  • Channels: stereo (dual mono is fine if you record mono; duplicate the channel)
  • Head silence: 0.75 seconds
  • Tail silence: 3 seconds
  • One WAV file per chapter

That render goes to all three platforms as-is. No re-export, no re-encode, no per-platform variant. The conversions each platform needs (ACX's MP3, Spotify's streaming codec, Findaway's retailer-specific formats) happen on their side.

Common Rejection Patterns by Platform

PlatformMost Common RejectionWhat It Means
ACXNoise floor above -60 dBFS mid-fileHVAC or breath in a silence segment. See our ACX guide
ACXTrue peak above -3 dBTPLimiter not in true-peak mode. See true peak guide
ACXLoudness outside -18 to -23 LUFSSingle chapter out of range, not the average
FindawayChapter-to-chapter inconsistencyRoom tone or level drift across recording days
FindawayMouth noise / clicksEditing pass missed transients human QC catches
FindawayMetadata mismatchChapter titles, track numbers, ISBN inconsistencies
Spotify AudiobooksTrue peak above -1 dBTPIf delivering directly to Spotify, this is stricter than ACX
Spotify AudiobooksFormat mismatchMP3 delivered instead of WAV or FLAC

The Findaway Wide-Distribution Question

Findaway Voices distributes to retailers (Apple Books, Google Play, Kobo, Storytel) and library systems (OverDrive, hoopla) with their own internal specs. Findaway's job is to take your master and conform it to each retailer's requirements, which is why their preferred input is 44.1 kHz / 16-bit (or higher) WAV. They re-encode downstream. If you deliver MP3, they cannot recover the quality before sending to retailers who expect lossless input.

This is the main reason every modern audiobook workflow should master to WAV regardless of which platform is the primary destination. Even if ACX is the only platform you ship to today, a WAV master is the input every other platform will eventually ask for.

One Master, Two Common Variants

There are two reasons to deviate from the universal master:

  1. Spotify-direct delivery at hotter loudness. If you publish directly to Spotify Audiobooks (not via Findaway), you can master to -18 LUFS / -1 dBTP and gain a small competitive loudness advantage in the catalog. Costs you the ACX-compatible master. You have to render twice.
  2. High-end retail (Apple Books premium). If you are delivering to a premium retail program that accepts 24-bit / 48 kHz, render a higher-res master alongside the universal one. The universal master still goes to ACX, Findaway and standard Spotify.

For everyone else: one master, three platforms, no re-render.

Pre-Delivery Checklist

  1. Every chapter measured individually: -20 LUFS ±0.5 LU
  2. True peak verified per chapter at -3 dBTP or lower
  3. Noise floor checked at multiple points inside each file, not just the head
  4. 44.1 kHz / 16-bit WAV confirmed in export dialog (CBR/VBR does not apply to WAV)
  5. Head silence 0.5-1 sec, tail silence 1-5 sec, consistent across all chapters
  6. Room tone consistent between chapters (see our room tone guide)
  7. One file per chapter, named consistently, under 120 minutes each
  8. Metadata complete and consistent (chapter title, track number, ISBN)

Why This Gets Hard at Scale

For a single book on a single platform, dialing in the spec and running manual checks is fine. For a catalog going to all three platforms, every chapter has to pass three different QC processes (two automated, one human) and a miss on any of them means a redelivery weeks after you thought the project was done.

Running every chapter through an automated check against the universal master spec, before any of the three platforms see it, removes the platform-specific failure modes. If the report says pass, the file goes to all three without modification. If it finds an issue, you fix one chapter against one spec instead of three.

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 7-day Pro trial