Ebooks For Kindle

What actually happens when you turn a manuscript into something Amazon will accept

Most people who want to publish on Kindle download Microsoft Word, write a book, click File > Export, and expect it to work. It does not work. The reason is simple: Word documents are terrible for e-readers. They carry invisible formatting baggage that reflows incorrectly on Kindle devices, which is why the whole process of creating Ebooks For Kindle involves cleaning, converting, and testing in a specific order before you ever hit publish. Amazon accepts three file types: MOBI, KPF, and EPUB. KPF is the current standard. It is the format Kindle Create produces and the one Amazon recommends. EPUB works but sometimes looks wrong on Kindle devices. MOBI is the old Amazon format and has been deprecated for years. If you are starting from scratch, use Kindle Create. It is free from Amazon and handles most of the tedious conversion work. Here is what I actually do. I take the clean DOCX file, strip all manual formatting, rebuild the structure with proper Heading styles, embed fonts only where absolutely necessary, and run it through Kindle Create. Then I open the exported KPF in Kindle Previewer 3 to check the interior. The previewer catches broken TOCs, misplaced images, and font issues that you will never see in the final upload. This pipeline takes about 20 minutes for a standard 60,000-word book.

I hit a specific problem once with a nonfiction book that had twelve comparison tables. The tables were built in Word using nested columns. When I ran it through Kindle Create, every table after the fifth one collapsed into single-column layout with no borders. I spent two hours fighting with the auto-converter before I figured out the workaround. I had to rebuild each table as a styled paragraph using em-dashes and spaced characters instead of actual table markup. It looked acceptable on the Kindle screen because e-ink readers do not render complex grids well anyway. Amazon's own guidelines mention this but do not give you a step-by-step fix, which is why I remember it.

The formatting rules you need to know before you start

Kindle e-books are reflowable text. That means the content flows around the reader's display settings. Font size, font family, margins, and line height are all controlled by the reader, not the author. Your job is to structure the content semantically so the reflow works correctly. This is the part most beginners get wrong. You use paragraph styles, not manual indentation. You use the Heading 1 through Heading 4 hierarchy consistently, and you insert page breaks manually where you want them — between chapters, before new sections. Kindle does not respect physical pages, but it does respect page break tags. If you skip this, your chapter starts will appear mid-screen and look sloppy. Images need to be embedded, not linked. A linked image will not display on any Kindle device. The maximum recommended image resolution is 1000 pixels on the longest side. Larger images get compressed badly by Amazon's server and end up blurry. JPEG is fine for photographs. PNG works better for diagrams because it does not introduce compression artifacts. Keep individual image files under 600KB if you can.

Hyperlinks are supported but behave differently than on the web. Clicking a link opens it in a browser or within the Kindle app depending on the device. If you include a URL that points to a download, make sure it works on mobile data, because many Kindles do not have full browser capabilities. I learned this the hard way when a reader emailed me complaining that a link in my book opened a blank page on their basic Kindle Paperwhite. The link pointed to a JavaScript-heavy webpage that the Kindle browser cannot render. I updated the link to a plain PDF hosted on a static server and pushed a corrected version through KDP.

What the conversion process actually looks like in practice

There are two main paths. Path one is Kindle Create. You import your DOCX, the software analyzes the structure, you adjust the cover and TOC settings, and it spits out a KPF file. This is the easiest route and works for most fiction and straightforward nonfiction. Path two is Calibre. Calibre can convert almost anything to EPUB and then you upload the EPUB to KDP. Calibre gives you more control but requires you to understand EPUB internals. I use Calibre only when Kindle Create fails me, which is rare but happens with books that have complex front matter or unusual typography. Here is a detail most guides miss: Kindle's conversion engine strips out certain CSS properties silently. If you set a specific font size in your source document, it may ignore it completely. If you use text-transform or letter-spacing aggressively, it will break on some devices. The safest approach is to set sizes in EM units and let the Kindle reader's font scaling handle the rest. This way, when a user increases their font size to 1.5x or 2x, your layout adapts instead of breaking. Another thing that trips people up is the handling of special characters. Em-dashes, en-dashes, smart quotes, and ellipses all need to be properly encoded. If you paste text from a sources that uses Windows-1252 encoding without converting to UTF-8, you will get replacement characters in your final ebook. I once uploaded a book where every em-dash appeared as a box character because I had saved the DOCX from an old version of Word that used the wrong encoding. The fix was to open the file in Notepad, copy the text, paste it into a fresh DOCX, and reconvert. It added twenty minutes to the process but saved me from pulling a listing down after publication.

Common mistakes that will cost you time and money

The most expensive mistake is publishing without testing on real devices. Kindle Previewer 3 has a good simulation mode but it does not perfectly match a real Paperwhite or Oasis. I always test on at least two physical Kindles before submitting. Colors, image positioning, and font rendering all behave slightly differently on the hardware versus the simulator. The second most common mistake is ignoring the previewer's warnings. Kindle Previewer will flag issues like broken internal links, missing alt text on images, or inconsistent heading styles. Some of these warnings are minor. Others will cause your book to look bad on certain devices. Do not ignore them. I once had a reader complain that my book's table of contents was missing half the chapters. The TOC was generated fromHeading 2 tags, but the section headers in the middle of chapters were also tagged as Heading 2. The previewer had flagged this as a potential issue. I did not fix it because the warning seemed cosmetic. It was not. The Kindle app merged the section headers into the TOC and pushed the actual chapter entries out of view. A third issue is the cover image. Amazon requires a minimum of 1000 pixels on the shortest side and a maximum of 2560 pixels. The aspect ratio should be 1.6:1 for most paperback and ebook combinations. If your cover has important text near the edges, trim it inward by at least 50 pixels because some Kindle models add a subtle bezel that crops the edges. I learned this after a reader sent a photo of their screen showing the book title partially cut off on the bottom corner of a Kindle Scribe.

Alternatives when Kindle Create and Calibre are not enough

Some books simply do not convert cleanly. Academic texts with footnotes, books with heavy mathematical notation, and graphic novels are the usual suspects. For these cases, you may need a professional formatter. Services like Vellum (Mac only) or Atticus handle these edge cases much better than the free tools. They cost money but they save hours of manual fixing. If your book is shorter than 50,000 words and mostly prose, the free tools are fine. If you are dealing with complex layouts, budget for a formatter. There is also the question of DRM. Amazon adds DRM to all Kindle ebooks automatically unless you opt out during upload. This does not protect your book from piracy — it just makes it harder for average users to share copies. The debate over whether DRM helps or hurts sales is ongoing. I stopped caring about it after I realized that the people who pirate my books were not going to buy them anyway, and the people who buy them are fine with it. If you publish through KDP Select, you must accept DRM as part of the exclusivity agreement. If you publish wide, you can skip it.

The final step before you go live

Before you click publish on KDP, verify three things. First, confirm that the TOC generates correctly by navigating to it on a Kindle device or the Previewer. Second, check the sample chapter that Amazon auto-generates. Sometimes the sample pulls from the wrong section of your book and shows broken formatting. Third, look at the book's metadata on the Amazon product page. Title, author name, description, and keywords should all match what you submitted. I once published a book where the metadata page showed the wrong subtitle because I had left a placeholder in the KDP form and forgot to replace it. The correction took three business days to process and the book was briefly unavailable during that time. The whole process is not complicated but it is detailed enough that skipping steps will show up in the final product. Spend the time on formatting and testing, and the rest of the publishing process goes smoothly.