Amazon gives this away and it works. That deserves saying first, because most reviews of free first-party tools are written to sell something else. Kindle Create takes a Word file or a PDF, applies a readable theme, builds a contents, and produces a file that looks right on a Kindle.
The question is not whether it works. It is what you give up by letting it hold your book.
What it is good at
- It is free, from the company you are uploading to, with no tier to upgrade to.
- It is easy. Import a manuscript, pick a theme, and the chapter detection is usually right.
- Chapter headings and drop caps come out looking deliberate without any work.
- The preview is accurate, because it is Amazon previewing an Amazon file.
- It handles front matter sensibly and builds the navigation for you.
Limitation one: the file only works at Amazon
Kindle Create saves a .kpf, which is Amazon's own package format. KDP accepts it. Apple Books, Kobo, Google Play and every other store do not.
| Where | Accepts .kpf | Wants |
|---|---|---|
| Amazon KDP | Yes | .kpf, .epub or .docx |
| Apple Books | No | EPUB |
| Kobo | No | EPUB |
| Google Play Books | No | EPUB |
| Your own storefront | No | EPUB and PDF |
So the moment you go wide, the formatting work does not travel — you reformat from the original manuscript in something else. That is not a small cost if you spent an evening getting the chapter openers right, and it is the cost people discover after publishing rather than before. Where to sell your ebook covers why most authors end up on more than one channel.
Limitation two: the formatting is not in your manuscript
Your book now exists in two places that disagree: the original document, which has the words, and the Kindle Create project, which has the words plus every decision you made about how they look.
Fix a typo in the manuscript and the project does not know. Fix it in the project and your manuscript is now the outdated copy. Over a year of corrections — and digital books get corrected, that is their advantage — the two drift apart and you stop being sure which is current.
This is the general problem with formatting inside an application rather than treating it as an export, and it is the reason a plain-text source is worth the switch for anyone who publishes more than once: correction, revision or second edition? is where it bites.
Limitation three: print is an afterthought
Kindle Create can produce a print-ready interior, and it is noticeably weaker there than at ebooks. Control over margins, gutter, running heads and trim size is limited compared with a dedicated formatter, and print is where those decisions are permanent.
If the book is going to paper, this is the point to use something else — print-ready PDF and page margins and line length cover what you need control over.
How it compares
| Cost | Output | Works beyond Amazon | |
|---|---|---|---|
| Kindle Create | Free | .kpf, limited print PDF | No |
| Vellum | One-off, high | EPUB + print PDF | Yes |
| Atticus | One-off, mid | EPUB + print PDF | Yes |
| Reedsy Studio | Free | EPUB + print PDF | Yes |
| Markdown + exporter | Free tier upward | EPUB + PDF from one source | Yes |
Reedsy Studio is the direct comparison worth making: also free, also easy, and it gives you a standard EPUB that every store accepts. If the appeal of Kindle Create is that it costs nothing, that alternative costs nothing and does not lock the file to one retailer. Vellum alternatives has the wider set.
The verdict
- Amazon exclusive, one book, no print — use it. It is free and it is fine.
- Going wide — do not. You will format twice.
- Print matters — do not. Use something with real control over the page.
- You will correct the book repeatedly — do not. Keep the formatting in the manuscript, not in a project file.
- You want a PDF to sell direct — do not. Its PDF is a by-product, not the point.
The underlying trade is the one that runs through every free first-party tool: it is genuinely free, and the price is that your work only fits where the company that gave it to you wants it to fit. Whether that is a good deal depends entirely on whether you intend to leave.
The way out, if you want one, is not a different application — it is not having the book live in an application at all. bukpress takes a Markdown manuscript and exports both the typeset PDF and a reflowable EPUB from that one source, so the same file serves Amazon, every other store and your own storefront, and a correction is one edit and one rebuild. Markdown to EPUB is that export in detail.
Common questions
Is Kindle Create really free?
Yes, with no paid tier. Amazon gives it away because it produces well-formatted books on its own store, which is worth more to them than a licence fee.
Can I convert a .kpf to EPUB?
Not cleanly, and not through any supported route. Plan to reformat from your original manuscript instead, which is the practical reason to keep that manuscript in a format you can re-export.
Does KDP prefer .kpf over EPUB?
No. KDP accepts a reflowable EPUB and converts it, and that path is well supported — how to turn a Markdown file into a Kindle book. Uploading an EPUB does not disadvantage the book.
Is it good enough for a paperback?
Adequate rather than good. It will produce an interior that prints, with less control than a dedicated formatter over the decisions that are permanent once printed.