Publicado
What KPF Is, and Why It Only Opens Inside the Kindle App
KPF shows up in every list of ebook formats, usually with no explanation. It isn't something you read — it's the file Kindle Create exports for KDP, and the app that actually opens it isn't the one on your phone.
What KPF Is
KPF stands for Kindle Package Format. It's the file Kindle Create produces when an author exports a finished manuscript for submission to KDP, Amazon's self-publishing platform. An author builds the book in Kindle Create — a Word document for a reflowable novel, say, or a PDF for something image-heavy like a comic — then sets chapter themes, drop caps, and image placement before clicking Export. That step produces two files: a .kcb project file the author keeps for future edits, and a .kpf file, the finished package that actually goes to KDP.
Here's the part that trips people up, including the framing in most format roundups: a .kpf file doesn't open in the Kindle app on your phone or e-reader. The application that opens it is Kindle Previewer — a separate, free desktop tool authors use to check formatting before anything is published. Never seen a .kpf? That's by design. It was never meant to reach you.
Why It Matters
KPF exists to solve one unglamorous problem: making sure a book's fonts, drop caps, and chapter themes render the same way across every Kindle device before it goes live. It's Amazon's recommended format for reflowable ebooks specifically, partly because it can guarantee embedded fonts in a way some other export paths can't.
That's narrower than it sounds, and it points at a pattern you'll recognize if you've read about why some ebooks won't open outside the store they came from. Publishing pipelines tend to build their own closed, purpose-built formats rather than lean on something universal. KPF isn't a DRM format itself — it's a pre-publishing package — but it comes from the same instinct: keep the whole process inside one company's tools, from formatting through preview through submission.
How KPF Fits the Kindle Format Family
From AZW to KFX
KPF isn't what a reader ends up with. What you actually download when you buy a Kindle book comes from a different lineage entirely: AZW, introduced in 2007 and built on the older Mobipocket format; AZW3 (also called KF8), which added HTML5 and CSS3 support in 2011; and KFX, which arrived in 2015 with better typography. KPF sits earlier in the pipeline than any of these. It's what an author submits, not what a reader receives. For the reading-format side of this story, we've covered it separately in MOBI vs. AZW.
Proprietary by design
The whole Kindle lineage is closed, built with DRM in mind from the start — a real structural difference from an open standard like EPUB. Amazon loosened that a little in 2022 by accepting EPUB uploads directly, converting them internally to KF8. But the destination format is still Amazon's own. Still closed.
Where You'll See It
As a reader, you'll almost never run into a .kpf file yourself. The one place it might cross your path: you're the one publishing, exporting from Kindle Create, or someone accidentally sends you a project export instead of a finished book.
Worth separating KPF from Send to Kindle, too — a completely different, reader-facing workflow for getting a personal document onto a Kindle device. They share a company and a name, not much else. We've written about how Send to Kindle actually works, and where it stops, if that's the workflow you were actually looking for.
How Margina Handles It
Margina reads the documents you already have — PDF, EPUB, Word, plain text, Markdown — directly, without routing them through a publishing tool first. None of that needs a packaging step like KPF, because none of it is being prepared for a storefront. To be plain about the boundary: Margina doesn't open .kpf files, since it isn't a reading format, and it doesn't work around DRM-protected Kindle books either. If your library is already in an open format, Margina is on the App Store and Google Play.
Frequently Asked Questions
Can I open a .kpf file on my Kindle or phone?
No. A .kpf file only opens in Kindle Previewer, the free desktop tool authors use to check formatting before publishing. It was never meant to reach a reading device — once a book is published, Amazon converts it into a different, DRM-wrapped format that your Kindle app or e-reader can actually render.
What's the difference between a .kpf and a .kcb file?
Kindle Create's Export step produces both. The .kcb file is the editable project you keep for future revisions; the .kpf file is the finished package you upload to KDP. Only the .kpf ever leaves the author's computer.
Why can't Calibre or a regular EPUB app open a KPF?
KPF is proprietary to Amazon's authoring pipeline, built for Kindle Previewer's rendering engine rather than as a portable reading format. Generic readers like Calibre have no code path for it — the same way they can't open a raw layout-software project file.
Is KPF the same format a Kindle book ships as?
No. KPF is a pre-publishing package. What a reader eventually downloads is a converted, DRM-protected Kindle format from the AZW/KF8/KFX lineage. The .kpf itself never reaches the Kindle Store catalog.
Conclusion
KPF is a publishing tool's export format, not something a reader ever opens. The confusion is understandable — it gets filed next to MOBI and EPUB in most format lists without that distinction ever being made. The more useful pattern to notice is the bigger one: proprietary packaging formats optimize for one company's pipeline, not for your ability to open a file anywhere you like. If that's the part that interests you, the DRM and Send to Kindle pieces on this site cover the reader-facing side of the same story.