How to Publish an Audiobook on Google Play Books

To publish an audiobook on Google Play Books, open a free Play Books Partner Center account, then either use Google's free auto-narrated program to generate a synthetic voice from your ebook or upload your own produced audio files. Both paths pay a 52% royalty on the list price, and both require disclosing AI narration during the listing.

Google Play Books gives self-published authors two distinct routes to an audiobook, and choosing between them is the first real decision. The auto-narrated program converts an existing Google Play ebook into a synthetic-voice audiobook at no cost. The self-uploaded route lets you supply your own finished audio files, which gives you control over the voice and quality the auto-narrator does not offer. This guide walks through account setup, both production paths, file specifications, royalties, supported languages, and the step-by-step listing process.

How much does Google Play Books pay in audiobook royalties?

Google Play Books pays self-published authors 52% of the list price on each audiobook sale, after Google deducts applicable transaction or device fees. The 52% rate is among the more generous in the aggregator market — higher than ACX's 30% non-exclusive royalty and Kobo Writing Life's 45% audiobook rate. Importantly, the royalty is the same whether you use Google's free auto-narration or upload your own produced audio, so the choice between the two paths is about quality and control, not earnings per sale. For a full breakdown of how platforms pay, see audiobook royalties explained.

Is the Google Play auto-narrated audiobook program free?

Google's auto-narrated audiobook program is free to use and adds no upfront production cost. The program generates a synthetic voice from a Google Play ebook you already have in your catalogue, lets you preview and tune pronunciation, and then lists the result as an audiobook. Google requires the source ebook to be in your Play Books account and in a supported language before the auto-narration feature becomes available. The appeal is obvious: zero cost and a few hours of setup turn an ebook into an audiobook.

The auto-narrated program's limits are equally real. Voice selection is restricted to Google's preset synthetic voices, fine control over pacing and emphasis is minimal, and the output is locked into the Google Play ecosystem — it does not give you portable files you can distribute elsewhere. For a single title where reach on Google is the only goal, the free program can be a reasonable starting point. For authors who want a consistent voice across a series, or who plan to sell the same audiobook on Spotify, Apple Books, and library networks, the self-uploaded route is the better fit.

Auto-narrated program vs uploading your own audio

The core trade-off on Google Play Books is between Google's free auto-narration and uploading your own produced audio. The table below compares the two paths on the factors that matter most to an indie author deciding which route to take.

The key takeaway from the comparison is that the auto-narrated program wins on cost and simplicity for a Google-only release, while uploading your own audio wins for authors who want voice control, consistent series narration, and files they can sell across every platform. Because the royalty is identical, the decision comes down to how much reach and control you need. Authors weighing this against fully synthetic platform tools may also find the best AI audiobook tools comparison useful before committing.

What languages does Google Play Books support for audiobooks?

Google Play Books supports audiobook publishing in dozens of languages and territories, and its auto-narration feature covers a growing subset including English, Spanish, French, German, Italian, Portuguese, Dutch, Japanese, and several others. The supported-language list for auto-narration is narrower than the list for self-uploaded audio, because the synthetic voices have to be trained per language. If you upload your own audio, you can list an audiobook in any language Google sells in, provided the files and metadata are accurate. Authors producing in a single non-English language — for example a Spanish-language edition — should produce that book as a single-language audiobook rather than mixing languages in one file.

What audio file specs does Google Play Books require?

Google Play Books requires uploaded audiobook files to meet professional audio specifications so the listing passes review. These specs mirror the broader audiobook industry standard, so files prepared correctly for Google also work on Spotify, Apple Books, and INaudio. The specifications below are the targets to hit for a clean approval.

Meeting Google Play Books audio specs by hand means measuring loudness, normalizing peaks, splitting chapters, and tagging metadata — manageable but time-consuming. TomeVox generates M4B plus per-chapter MP3 files meeting all of these specifications automatically, within 48 hours, and every audiobook is automatically checked for technical quality before delivery. If a chapter needs a different read, you can re-generate any chapter at no extra cost. For the full workflow from manuscript to finished files, see the AI audiobook production guide.

How do you publish an audiobook on Google Play Books step by step?

Publishing an audiobook on Google Play Books follows a clear sequence whether you use auto-narration or upload your own audio. The numbered steps below cover the self-uploaded route, with notes on where the auto-narrated path differs.

Step 1: Open a Google Play Books Partner Center account

Start by signing up for the Google Play Books Partner Center, accepting the audiobook content policies, and completing your payment and tax profile. Google cannot pay out royalties until the tax forms are on file, so completing this profile first avoids a delay later when your title is ready to publish.

Step 2: Choose auto-narration or upload your own audio

After your account is active, decide on your production path. If you want the free auto-narrated route, open the existing ebook in Partner Center and start the auto-narration flow, then preview and tune the synthetic voice. If you want full control, prepare your own produced audio files for upload instead — this is the route most authors choose when they care about voice and want portable files.

Step 3: Prepare your audio files

For the self-uploaded route, prepare per-chapter audio files that meet Google's specs before you create the listing. Producing the audio with TomeVox gives you M4B plus per-chapter MP3 output that already meets Google's 44.1 kHz, 192 kbps requirements, so the files are ready to upload without further editing. Authors converting an existing manuscript can follow the guide to where to sell an AI audiobook to plan distribution beyond Google as well.

Step 4: Create the audiobook listing

Once your audio is ready, create the audiobook listing in Partner Center by adding the title, author, description, a square cover image, an ISBN if you have one, and the language. During this step Google asks you to disclose synthetic or AI narration — select that option accurately, because disclosure is both an ethical and a contractual requirement on Google Play.

Step 5: Set price and territories, then publish

After the listing details are complete, set your list price and choose the territories where the audiobook should sell, then submit for review. Google reviews the submission and the title goes live on Google Play once approved, at which point you begin earning the 52% royalty on every sale. Review times vary, so plan your launch with a few business days of buffer.

Which Google Play path should an indie author choose?

For most indie authors, uploading your own produced audio to Google Play Books is the stronger long-term choice, even though the auto-narrated program is free. Auto-narration is genuinely useful for a quick, Google-only release or for testing whether an audiobook edition sells at all. But because the 52% royalty is identical either way, the only thing the free program saves is the production cost — and at $49–$99 early bird with TomeVox, that cost is small relative to the value of owning files you can sell on Spotify, Apple Books, Kobo, INaudio, library networks, and your own website.

Owning portable, distribution-ready files also protects you against being locked into one retailer. An author who auto-narrates on Google and later wants the same title on Apple Books has to produce the audio again, while an author who uploaded produced files can list everywhere from one set of files. Voice cloning to narrate in your own voice is coming soon to TomeVox; for now, you choose from American and British, male and female, Classic and Playful voices across 13 languages. The honest summary: use auto-narration to experiment, but produce your own files when you are ready to publish widely and keep control of your catalogue.