How to Format a Book for Google Play (2026)

If you only publish on Amazon, a huge slice of the ebook market never sees your book. Google Play Books comes preinstalled on virtually every Android phone — hundreds of millions of potential readers, including in countries where Amazon has no storefront. To format a book for Google Play correctly, know this: Google is stricter than Amazon about file validity, more flexible about where else you publish, and different on covers, pricing, and territories. This guide covers the 2026 workflow end to end — file rules, EPUBCheck validation, cover specs, fixed versus reflowable layout, pricing and territories, and the direct-versus-aggregator decision — flagging where it diverges from our Apple Books formatting guide so one master file can serve both.

By the end, you will know which files Google accepts, how to pass validation on the first upload, what your cover must look like, how to price across 70+ territories, and whether to upload directly or use an aggregator — plus a pre-publish checklist for every title.

Why Google Play Books Deserves a Place in Your 2026 Plan

Every Android phone ships with Google Play Books installed — the largest ebook audience most self-publishers ignore, serving 70+ countries including many where Amazon has no store. Sell only on Amazon and you are invisible across large parts of Asia, Africa, Latin America, and Eastern Europe, where Android dominates and Google Play is the default bookstore.

Google also demands no exclusivity: Amazon’s KDP Select requires 90 days of exclusivity for Kindle Unlimited reads, while Google lets you stay wide everywhere else without breaking a rule. For wide authors, Google is free distribution to hundreds of millions of devices.

The trade-off is stricter ingestion: Google validates your EPUB against the EPUBCheck test suite and bounces files that fail. That is a favor in disguise — a file that passes EPUBCheck renders reliably everywhere.

How to Format a Book for Google Play: The Core File Rules

The first rule when you format a book for Google Play is to start from a finished EPUB, not a Word document. Google accepts EPUB (version 2 or 3) and PDF, and it will not convert anything else for you.

The second rule is that everything inside the EPUB must be well-formed: every XHTML file valid XML, every referenced file listed in the OPF manifest, UTF-8 encoding, and the declared EPUB version matching the actual markup. A stray unclosed tag or an undeclared image triggers errors — and Google rejects on errors, not warnings. JavaScript and MathML are hard rejections, so strip them before uploading.

Finally, keep the file lean — interior images at 800–1200 pixels wide, photos compressed to JPEG quality 80 — and follow Google’s filename conventions (1234567890_frontcover.pdf, 1234567890_interior.pdf), which is how ingestion matches covers to interiors.

EPUB vs PDF: Which File to Upload (or Both)

Google’s official recommendation is to upload both an EPUB and a PDF for every title. The EPUB is the reflowable version readers resize and restyle on any screen; the PDF is the fixed-layout version preserving your exact page design.

Upload only a PDF and you limit your audience to fixed-flow readers, because a PDF cannot reflow on a phone — text stays tiny and readers pinch and zoom. For text-heavy books, EPUB-only is the better single choice; for cookbooks, photography books, picture books, and workbooks where layout is the product, the PDF matters — upload both.

Google processes the files independently: re-upload a fixed EPUB and the old version is overwritten and archived under Past Files. Keep your own source files versioned locally.

Passing EPUBCheck on the First Try

EPUBCheck is the official validation tool for the EPUB standard, and Google runs it — or an equivalent — on every upload. It reports errors (fatal, must fix) and warnings (advisory, should fix); Google bounces files with errors. Validate locally before submitting to save days of back-and-forth — our EPUBCheck validation guide covers setup and the most common error codes.

The errors that fail Google uploads are mundane: files referenced in the XHTML but missing from the OPF manifest (or vice versa), malformed XHTML like an unclosed tag or stray ampersand, spine order not matching reading order, and a missing or broken toc.ncx (EPUB 2) or nav document missing properties=”nav” (EPUB 3).

The workflow: build the EPUB in a dedicated tool — Vellum, Jutoh, Sigil, or Atticus, not a Word export — run EPUBCheck until it reports zero errors, then upload. Clear the warnings too: a file with warnings usually still ingests, but warnings about missing fallbacks or deprecated markup predict rendering quirks on real devices.

Cover Art Requirements for Google Play

Google handles covers differently from every other retailer: the cover is a separate required upload — PDF, TIFF, PNG, or JPEG — alongside the interior, not embedded in the EPUB. This is where most first uploads stumble.

For resolution, Google asks for a high-resolution image without publishing a hard pixel minimum. Use the industry norm: at least 1600 × 2400 pixels at a 2:3 ratio, RGB, as a high-quality JPEG or PNG. Never upscale a small cover — the storefront shows every blurry edge at full size.

Design for the thumbnail. Google shows your cover small in search results and carousels, so the title must stay legible at roughly 150 pixels wide: large high-contrast type, no tiny subtitle text, nothing critical near the edges. Keep the same art across retailers so readers recognize your book anywhere.

Because the cover uploads separately, refreshing it later is one of the cheapest marketing tests in publishing — upload the new file, wait for processing, compare sales. Keep your layered source file and export settings saved.

Fonts, Images, and Navigation: TOC and NCX Details

You may embed fonts, and subsetting — including only the characters your book uses — keeps the file small. But never design as if a custom font were guaranteed: Google’s apps can substitute their own fonts, so the book must read perfectly in a fallback serif or sans-serif. Never use an image of text where real text works, and never convey meaning through styling alone.

Declare every image in the OPF manifest with the correct media type, use relative paths, and keep dimensions sensible: 800–1200 pixels wide is plenty for phone screens. Print-resolution images bloat the file and strain low-end Android devices. Compress photos to JPEG quality 80, reserve PNG for line art, and add alt text to meaningful images.

Navigation is non-negotiable: every EPUB needs a working table of contents openable from the reader menu — a nav document marked properties=”nav” with epub:type=”toc” (EPUB 3), or a valid toc.ncx referenced from the spine (EPUB 2). Every chapter heading should be a linked entry resolving to a real anchor; a TOC entry that jumps nowhere is a validation error and a reader complaint. Generate the TOC from heading styles automatically and test every link.

Fixed Layout vs Reflowable on Google Play

For novels, memoirs, narrative nonfiction, and business books, reflowable EPUB is the only sensible choice: text adapts to every screen and reader preference — font size, spacing, margins, day and night themes — and Google’s apps are built around that flexibility.

Fixed layout fits a narrow set: children’s picture books, cookbooks, photography books, comics, and workbooks where element position matters. Google supports fixed-layout EPUB 3, and the PDF upload serves these readers too. But fixed layout is harder to validate, renders badly on small phones, and excludes readers who need large text. Do not choose it for a text book just to control the look — on Google Play, that control belongs to the reader.

The middle path for illustrated nonfiction is a reflowable EPUB with well-anchored images that scale to screen width: most of the design control, none of the fixed-layout fragility.

Pricing, Sales Territories, and Royalties Basics

You can price as low as $0.00 — genuinely free books are allowed, making Google ideal for permafree series starters. Choose your payout currency; Google converts it everywhere the book sells. For finer control, set per-country prices and schedule promotions with start and end dates.

Territories default to worldwide — leave that alone unless a rights limitation says otherwise. Individual territories can be included or excluded in the Partner Center, and price changes take effect after Google’s processing delay, so plan promotions days ahead, not the morning they start.

On royalties, Google pays a revenue share that varies by country and payment processor; direct publishers historically receive around 70 percent of list price in most major markets — well above the 35 percent Amazon pays outside its $2.99–$9.99 band. With no KDP Select equivalent, there is no exclusivity trade-off: stay wide and collect Google’s share on top.

Direct Upload vs Distributing Through an Aggregator

You have two routes onto Google Play Books: direct upload through the Partner Center, or delivery via an aggregator such as Draft2Digital, PublishDrive, or StreetLib.

Direct upload means maximum control: per-territory pricing, instant updates, no middleman, the full revenue share. The cost is administrative — another dashboard, slow review queues, and troubleshooting that is entirely yours. If Google is a meaningful slice of your income, or you publish often, direct is worth it.

Aggregators trade control for convenience: they validate your EPUB first, deliver to Google Play plus dozens of retailers from one upload, and absorb per-retailer quirks. The price is a revenue cut (typically ~10 percent of net on top of the retailer’s share), slower updates, and less granular pricing. For a first book this is completely reasonable — you can switch to direct later. The same control-versus-convenience math applies on Kobo, as our Kobo formatting guide explains.

One caution for either route: never run the same book on Google Play through both channels at once. Duplicate listings split reviews and sales rank, confuse Google’s systems, and can trigger content flags. Pick one channel per title.

Pre-Publish Checklist: Google Play Books

Run this list on every title before you touch the Partner Center.

• EPUB validates with zero EPUBCheck errors (clear warnings too if you can)
• No JavaScript or MathML anywhere in the package
• All XHTML well-formed with UTF-8 encoding declared
• Every image and font declared in the OPF manifest with correct media type
• Working linked TOC: nav document (EPUB 3) or valid toc.ncx (EPUB 2)
• Cover as separate high-resolution file (PDF/TIFF/PNG/JPEG, at least 1600 × 2400 px)
• Interior images 800–1200 px wide, compressed; alt text on meaningful images
• Fonts embedded and subset; clean reading in a fallback system font
• Metadata complete: title, author, description, language, categories, ISBN or GGKEY
• Price set ($0.00 allowed), payout currency chosen, territories reviewed
• Filenames follow Google’s convention (identifier_frontcover / identifier_interior)
• Live through ONE channel only — direct or aggregator, never both

Conclusion: One Master File, Two Hundred Storefronts

Google Play Books is the largest ebook audience most self-publishers ignore: hundreds of millions of Android readers, no exclusivity demands, worldwide territories by default, free pricing allowed, and a revenue share that beats Amazon’s worst tier. The price of admission is a clean, valid EPUB — zero EPUBCheck errors, no JavaScript, a working table of contents, a separate high-resolution cover — plus a few minutes of pricing and territory setup. Build one good master EPUB and it serves Google Play, Apple Books, Kobo, and every other wide retailer. Format once, publish everywhere.