Format Once, Publish to Kindle, Kobo, and Apple Books
Wide publishing should not require duplicate formatting work. Use this workflow to prepare one clean source and publish across major ebook retailers.
Publishing “wide,” selling on Kobo, Apple Books and Google Play as well as Amazon, is one of the best things an indie author can do for their reach. It’s also where a lot of authors quietly lose whole weekends. A file that works on Amazon gets rejected by Kobo. The Apple edition needs different links. Before long there are three slightly different copies of the same book, each edited by hand, and nobody is quite sure which one is current.
It doesn’t have to work like that. The authors who publish wide without the headaches all do roughly the same thing: they keep one clean source for each book and produce a fresh file for every store from it. Here’s how that works and why it saves so much time.
Why wide publishing gets messy
Each retailer treats your EPUB a little differently. Amazon converts your file into its own format and forgives a lot along the way. Kobo checks the file far more strictly. Apple has its own expectations about how a book is packaged. On top of that, each store wants your back matter to send readers to its shop, not a competitor’s.
The natural reaction is to fix each problem in the file for that store. The trouble is that every fix lives in a different copy, so a correction made for Kobo never reaches the Kindle edition, and a change to your bio has to be made three times. Worse, a fix for one store can quietly break another. You end up maintaining three books, not one.
The format-once approach
The alternative is to treat your formatting project as the single source of truth and the files you upload as disposable outputs.
1. Keep one clean master project
Everything that should be the same everywhere lives in one place: the text, the chapter headings, the styling, the front and back matter, and the book’s details. When you need to change something, you change it here and nowhere else.
2. Fix structure before anything store-specific
Most rejections come from structure, not from anything unique to a store: inconsistent headings, a table of contents that doesn’t match the chapters, images that are missing, or incomplete metadata. Get these right in the master project first, and most store-specific problems never appear.
3. Export a fresh file for each store
Instead of editing finished files, produce a new export for each retailer from your master project every time something changes. This is exactly what Libba’s per-store exports do: one project, and a separate EPUB for Kindle, Apple Books, Kobo, Nook and Google Play, each built fresh with the right links for that store.
4. Spot-check each edition
Before uploading, open each file and check the parts most likely to differ: the back matter links, the cover, and the opening chapters. Each store’s own previewer is the final word on how your book will look there.
Back matter is where it usually goes wrong
If one part of a wide-published book causes more trouble than any other, it’s the back matter. This is where your “buy my next book” links, series links and newsletter sign-up live, and it’s where store rules matter most, because Amazon doesn’t want links to Apple Books and Apple doesn’t want links to Amazon.
The cleanest solution is to store a link for each retailer once and let each export include only the right one. Your newsletter and website links can appear everywhere; your store links shouldn’t. Authors who manage this by hand often end up with an Amazon link in the Kobo edition or a broken link in all three, which is exactly the sort of thing that gets a book flagged.
Making it a routine
If you publish or update books often, a simple, repeatable routine helps. Make your changes in the master project, check the structure, export every edition in one go, spot-check each one, and upload. If a store flags a problem, fix it in the master and re-export, so the fix carries over to every edition next time. Over a few books this becomes second nature, and your editions stop drifting apart.
Common questions
Do I need a separate manuscript for each store? No. One clean source for each book is enough. The differences between stores belong in the export, not in separate copies of the book.
Should I ever edit the final EPUB for a particular store? Only as a last resort. Any change you make to a finished file disappears the next time you export, so it’s almost always better to fix the source.
What causes most of the extra work in wide publishing? Inconsistent structure and one-off manual fixes. A source-first approach removes most of both.
You don’t need three separate formatting workflows to publish wide. You need one clean source and a fresh export for each store. If a store does reject your file, Why Your EPUB Gets Rejected by Kobo (But Not KDP) and Why Your EPUB Gets Rejected by KDP explain the usual causes.
