<\/p>\n
<\/p>\n
So you’ve written your book. Congratulations<\/strong> that’s genuinely the hard part. Now comes the bit that trips up almost everyone: formatting it correctly for Kindle.<\/span><\/p>\n Amazon’s Kindle Direct Publishing platform is remarkably accessible, but it does have rules. Understanding those rules before<\/em> you upload can save you hours of frustration, rejections, and the sinking feeling of seeing your book look broken on a reader’s screen.<\/span><\/p>\n This guide walks through the official Kindle Publishing Guidelines in plain language so you can publish with confidence the first time around.<\/span><\/p>\n Amazon serves Kindle content across an enormous range of devices from the original Kindle e-ink readers and Paperwhite to Fire tablets, iOS and Android apps, and even desktop browser readers. Each of these environments renders content a little differently.<\/span><\/p>\n The guidelines aren’t bureaucratic red tape. They’re a checklist for ensuring your reader gets the experience you intended regardless of which device they’re reading on.<\/span><\/p>\n<\/div>\n When authors skip these guidelines, the result is often broken formatting, missing images, navigation that doesn’t work, or covers that look pixelated on high-res screens. None of that is a good first impression on a reader who just paid for your book.<\/span><\/p>\n Before you worry about formatting details, you need to choose how you’ll deliver your content to KDP. There are three main paths, and the right one depends on your skill level and how much control you want.<\/span><\/p>\n Amazon’s free desktop tool. Import a Word doc or PDF, apply a theme, export a publish-ready KPF. Perfect for fiction, memoirs, and self-help.<\/span><\/p>\n<\/div>\n Upload a formatted .docx and KDP converts it automatically. Works well for simple text-heavy books, but gives you less control over the final output.<\/span><\/p>\n<\/div>\n Full control over HTML and CSS. Essential for complex layouts, images, or interactive elements. If you’re comfortable with web tech, this is the way.<\/span><\/p>\n<\/div>\n<\/div>\n Not all Kindle formats are created equal. The primary distinction is between reflowable content<\/strong> and fixed layout content<\/strong>.<\/span><\/p>\n Reflowable<\/span><\/p>\n Novels, essays, non-fiction<\/span><\/p>\n Text adapts to the reader’s font size and screen. Most common type. Best experience for most books.<\/span><\/p>\n<\/div>\n Fixed Layout<\/span><\/p>\n Picture books, comics, art books<\/span><\/p>\n Page design is locked pixel-for-pixel. Used when spatial relationship between text and image is part of the experience.<\/span><\/p>\n<\/div>\n Print Replica<\/span><\/p>\n Technical books, textbooks<\/span><\/p>\n Essentially a PDF in a Kindle wrapper. Preserves exact print layout but sacrifices accessibility and resizability.<\/span><\/p>\n<\/div>\n<\/div>\n<\/div>\n \ud83d\udca1 Amazon recommends Print Replica only for titles where the print layout is truly irreplaceable.<\/span><\/p>\n Regardless of which format you choose, a few habits will keep your file healthy from the start.<\/span><\/p>\n Keep your source file clean<\/span><\/p>\n If writing in Word, avoid hitting Enter five times to create a page break that’s a classic mistake that causes chaos in conversion. Use paragraph styles, not inline formatting, wherever possible.<\/span><\/p>\n<\/div>\n<\/div>\n Get your image resolution right<\/span><\/p>\n Minimum 72 PPI for eBooks, though higher is always safer given today’s high-DPI Kindle displays. Always use RGB color mode<\/strong> for digital not CMYK.<\/span><\/p>\n<\/div>\n<\/div>\n Avoid special characters and decorative fonts<\/span><\/p>\n Em dashes created with hyphens, or fonts that haven’t been properly embedded, frequently render as little squares on some devices. Not a great look.<\/span><\/p>\n<\/div>\n<\/div>\n Your cover is the single most important marketing asset for your Kindle book. Amazon has specific technical requirements, and meeting them isn’t optional a substandard cover image will either be rejected or display poorly in search results.<\/span><\/p>\n Technical specs<\/span><\/p>\n Minimum size<\/span><\/p>\n 1000 \u00d7 625 px<\/span><\/p>\n<\/div>\n Recommended size<\/span><\/p>\n 2560 \u00d7 1600 px<\/span><\/p>\n<\/div>\n Aspect ratio<\/span><\/p>\n 1.6:1 (height:width)<\/span><\/p>\n<\/div>\n Format \/ Max size<\/span><\/p>\n TIFF or JPEG \u00b7 50 MB<\/span><\/p>\n<\/div>\n<\/div>\n<\/div>\n A high-resolution cover at the correct aspect ratio doesn’t just look better it signals professionalism to Amazon’s review process and to browsing readers alike.<\/span><\/p>\n Kindle readers expect to be able to jump around your book easily. This is especially important for non-fiction, where a reader might skip to a specific chapter.<\/span><\/p>\n KDP requires two things: a functional NCX table of contents<\/strong> (machine-readable navigation data embedded in your EPUB) and an HTML table of contents<\/strong> (the human-facing page inside your book). These aren’t the same thing, and you need both.<\/span><\/p>\n Pro tip for long non-fiction<\/span><\/p>\n Add sub-entries to your NCX so readers can navigate to individual sections within chapters. It’s a small effort that significantly improves the reading experience.<\/span><\/p>\n<\/div>\n<\/div>\n If you’re building your EPUB from scratch or editing the HTML directly, Kindle’s rendering engine is based on WebKit but it doesn’t support every CSS property, and some things behave differently than you’d expect in a browser. Here’s what to live by:<\/span><\/p>\n DO<\/span><\/p>\n Use semantic HTML DO<\/span><\/p>\n Use DO<\/span><\/p>\n Place all your styles in a linked stylesheet inside the EPUB’s CSS file. Avoid inline styles as much as possible.<\/span><\/p>\n<\/div>\n AVOID<\/span><\/p>\n AVOID<\/span><\/p>\n Using tables for layout. Tables work but only for actual tabular data.<\/span><\/p>\n<\/div>\n AVOID<\/span><\/p>\n Complex float-based layouts they break on smaller screens. Use Making your book accessible isn’t just good ethics it’s increasingly a requirement for distribution on Amazon’s platform. KDP’s accessibility guidelines align with the EPUB Accessibility 1.0 standard and WCAG 2.0.<\/span><\/p>\n Alt text for every image<\/span><\/p>\n Every image needs meaningful alt text. Purely decorative images can use an empty Reading order must match HTML order<\/span><\/p>\n Don’t use CSS to visually reorder content in a way that doesn’t match the underlying HTML. Screen readers follow the HTML order, not the visual layout.<\/span><\/p>\n<\/div>\n<\/div>\n Proper heading hierarchy<\/span><\/p>\n Don’t skip from Before you submit, Amazon expects you to have done basic quality assurance. This is where many self-publishers cut corners and it shows in the quality notifications they receive after publishing.<\/span><\/p>\n Your pre-publish checklist<\/span><\/p>\n When your book qualifies for Enhanced Typesetting, Kindle applies advanced layout algorithms borrowed from print typography: improved kerning and letter spacing, better hyphenation, justified text with optical margin alignment, and drop caps.<\/span><\/p>\n Page Flip<\/strong> lets readers visually browse your book like a thumbnail view without losing their reading position. For it to work correctly, your content needs to be cleanly structured with proper page break markers.<\/span><\/p>\nWhy these guidelines actually matter<\/span><\/h2>\n
Paths to getting your content on Kindle<\/span><\/h2>\n
Kindle Create<\/span><\/h3>\n
Word (.docx)<\/span><\/h3>\n
Hand-crafted EPUB<\/span><\/h3>\n
Comparing formats<\/span><\/h2>\n
General best practices<\/span><\/h2>\n
Cover image guidelines<\/span><\/h2>\n
Navigation guidelines<\/span><\/h2>\n
HTML and CSS guidelines<\/span><\/h2>\n
<h1><\/code> through <h6><\/code> for headings, <p><\/code> for paragraphs, <em><\/code> and <strong><\/code> for emphasis.<\/span><\/p>\n<\/div>\nem<\/code> or %<\/code> for font sizes (not px<\/code>). This ensures your text respects the reader’s chosen font size preference.<\/span><\/p>\n<\/div>\nposition: fixed<\/code> and position: absolute<\/code> these don’t behave predictably across Kindle devices.<\/span><\/p>\n<\/div>\nfloat<\/code> sparingly.<\/span><\/p>\n<\/div>\nAccessibility guidelines<\/span><\/h2>\n
alt=\"\"<\/code> this tells screen readers to skip them entirely.<\/span><\/p>\n<\/div>\n<\/div>\n<h1><\/code> to <h4><\/code>. This confuses assistive technologies and breaks the document outline that screen readers rely on.<\/span><\/p>\n<\/div>\n<\/div>\n<\/div>\nQA standards<\/span><\/h2>\n
\n
Enhanced Typesetting and Page Flip<\/span><\/h2>\n