Professional eBook formatting turns a final manuscript into a structured digital publication that remains readable when a reader changes the font, text size, screen orientation, color theme, or device. It is not the same as shrinking the print PDF to fit a phone.
For most novels, memoirs, and text-led nonfiction, the best delivery target is a reflowable EPUB. Image-led children’s books, comics, textbooks, and designs whose meaning depends on exact page geometry may need fixed layout. Amazon KDP can also accept KPF, DOCX, and other supported manuscript formats, but every upload still needs structural and visual testing.
The workflow below begins with the editable manuscript and ends with a validated, platform-tested file.
The layout model determines nearly every later decision. Choose it before styling chapters, placing images, or building navigation.
In a reflowable eBook, text adapts to the reader’s screen and preferences. The reader can enlarge type, change font, alter line spacing, rotate the device, or use assistive technology. Use reflowable layout for novels and most nonfiction, where reading order matters more than fixed page coordinates.
Fixed layout preserves the position of text and images on a page. Use it only when layout is essential to meaning, such as a picture book, comic, highly visual cookbook, or illustrated textbook. Fixed layout requires more device-specific testing and can present additional accessibility challenges.
PDF preserves print pages rather than reflowing text. It can be appropriate when a distributor explicitly sells PDF as a separate product, but it is usually a poor master for a reflowable retail eBook. If the only source is PDF, extraction and cleanup are often more reliable than one-click conversion.
Treat platform requirements as release criteria, not permanent facts. Recheck the official help page immediately before upload.
|
Platform or use |
Recommended input/output | Current limit or caveat |
Quality check |
| Wide retail and library distribution | Valid EPUB 3 | Meet each distributor’s profile in addition to W3C conformance | EPUBCheck, Ace, and independent EPUB readers |
| Amazon KDP reflowable eBook | EPUB, KPF, or clean DOC/DOCX | Complex Word formatting may convert poorly | Kindle Previewer and KDP online preview |
| KDP additional inputs | HTML ZIP, RTF, TXT; limited-language PDF cases | Accepted input does not guarantee the best conversion | Inspect the converted result carefully |
| Fixed-layout picture book or comic | Fixed-layout EPUB or KPF as the platform requires | Exact layout increases device and accessibility risk | Test every target device class and orientation |
| Legacy MOBI workflow | Do not use as the default master | KDP ended fixed-layout MOBI uploads in March 2025 | Verify any remaining legacy case in current KDP help |
| Apple Books | Standards-compliant EPUB | Follow the current Apple Books Asset Guide | EPUBCheck plus Apple’s preview/testing workflow |
| Draft2Digital conversion | Clean supported source or preformatted EPUB | Accepted inputs and limits can change | Review the generated EPUB before distribution |
| PDF sold as an eBook | A deliberate fixed-page PDF product | Usually poor as a one-click source for reflowable EPUB | Test zoom, navigation, accessibility, and platform acceptance |
Complete developmental editing, copyediting, fact checking, permissions, and proofreading before conversion. Formatting is not an editorial pass. Late text changes can break links, notes, navigation, image references, and carefully tested reading order.
A visually polished Word file can hide unstable structure. Search for manual tabs, repeated spaces, text boxes, floating images, multiple hard returns, local font overrides, typed page numbers, headers and footers, and headings created only with bold text.
Use paragraph styles rather than manual appearance. A Heading 1 style communicates structure; bold 18-point text merely looks like a heading. Conversion tools, navigation generators, and assistive technologies need the structure.
Define a small, predictable set of source styles and use each consistently. The exact style names can vary by workflow, but the roles should be clear.
Avoid creating dozens of nearly identical styles. A lean style map produces cleaner HTML and CSS, makes global corrections easier, and reduces platform-specific surprises.
Put sections in a logical reading order. A common sequence is title page, copyright page, dedication, table of contents, optional introduction or foreword, body chapters, acknowledgments, about the author, other books, and a current contact or signup link.
Do not copy every print convention automatically. Reflowable eBooks do not need running headers, footers, blank verso pages, folios, or “turn the page” instructions. Remove any element that depends on a fixed left or right page.
Begin each major section with a real heading and a structural break. Do not press Enter repeatedly to push a title down the screen. Empty paragraphs expand unpredictably when readers change type size or spacing.
Use chapter breaks for chapters and parts. Use a semantic scene-break marker for internal transitions. If a decorative glyph is used, include a text or accessibility-safe treatment so the break remains meaningful when styling or images are unavailable.
A professional EPUB needs a navigation document. The visible table of contents may be included in the reading order, and the machine-readable navigation must connect each entry to the correct section.
For long nonfiction, add a page list only when the publication has a meaningful print-page source and the workflow can map it accurately. Do not invent fixed page numbers for a purely reflowable edition.
Readers should control the body font and size. Use relative CSS units, a restrained hierarchy, and enough contrast rather than forcing a print font at a fixed point size.
Start from the best available source image. Resize and compress for the target platform without enlarging a small or blurred file. Place images in the intended reading order and avoid floating Word layouts that cannot translate reliably to narrow screens.
Write alternative text for informative images. Decorative images should be marked so assistive technology can skip them. Complex charts may need a nearby explanation or long description rather than a one-line alt attribute.
A wide print table rarely survives on a phone. Remove nonessential columns, split complex tables, repeat context in prose, or use a fixed-layout product only when the table’s geometry is essential. Check horizontal scrolling behavior on every target reader.
Use real ordered and unordered lists. Do not type a bullet character at the start of ordinary paragraphs. Semantic lists resize and announce correctly in assistive technology.
Create linked notes with a return path to the reference. Test both directions. Avoid tiny note text or print-only instructions such as “see note at the bottom of page 47.”
Link descriptive text rather than “click here.” Remove tracking URLs that are unnecessary, use secure destinations, and decide how the book should behave when a reader is offline. Test the table of contents, cross-references, retailer links, and author links separately.
These examples show the structural change that matters more than visual polish.
|
Source problem |
Before | After |
Why it works |
| Chapter headings | Bold, centered body text | Semantic chapter heading plus structural break | Navigation and assistive technology recognize the chapter |
| Scene breaks | Three or more blank paragraphs | Consistent scene-break element styled with CSS | Spacing survives font and device changes |
| Paragraph indents | Tab or repeated spaces | Paragraph style with CSS first-line indent | Indentation scales predictably |
| Table of contents | Typed page numbers and plain text | Linked navigation with section targets | Reflowable pages do not have stable print numbers |
| Print furniture | Running header, footer, folio, blank verso | Remove from the reflowable edition | Avoids repeated clutter and empty screens |
| Images | Floating image with text wrap | Inline or responsive image with caption and alt text | Preserves reading order and accessibility |
| Wide table | Eight rigid columns | Simplified, split, or explained in prose | Reduces horizontal overflow on phones |
| Footnotes | Plain superscript and note text | Unique linked reference and return target | Readers can move to the note and back |
For broad distribution, export a valid EPUB that follows the current W3C EPUB specification and the receiving platform’s profile. W3C’s EPUB 3.3 Recommendation defines the package, content documents, navigation, resources, layout controls, and accessibility-related foundations of the format.
For KDP, use a current supported route such as EPUB, KPF created with Kindle Create, or a clean DOC/DOCX when the book is simple. KDP’s current support page also lists HTML ZIP, RTF, TXT, and limited-language PDF cases. These are accepted inputs, not guarantees of identical output quality.
MOBI should be treated as a legacy format rather than the default master. KDP says fixed-layout MOBI uploads stopped being accepted in March 2025 and directs authors toward its current supported workflows. Preserve an old MOBI only when a documented legacy need remains.
Run EPUBCheck on the final EPUB. It tests conformance and reports packaging, markup, metadata, navigation, resource, and other structural problems. Resolve errors before distribution; review warnings rather than dismissing them automatically.
Run Ace to identify accessibility issues such as missing image descriptions, language metadata, structural problems, and navigation concerns. Automated testing cannot judge every editorial or accessibility decision, so combine it with manual review.
Save the tool version, date, report, corrections, and final file hash or release filename. A documented validation record makes later retailer issues and updates easier to reproduce.
A file can pass validation and still look poor. Open the final package in Kindle Previewer and at least one EPUB reading system outside Kindle. Test on a small phone viewport, a larger tablet or desktop view, and an actual device when the audience or layout risk justifies it.
Upload the same release candidate that passed validation and preview. Do not make a silent last-minute edit after testing. Complete the title metadata, contributors, description, categories, territorial rights, price, and identifier fields, then use the platform’s online preview.
Download or inspect the converted result when the platform makes it available. If the platform changes the file, repeat the relevant navigation and visual checks. Publish only after the live-store preview, sample, and product metadata match the approved edition.
Likely cause: chapter titles are manually styled rather than structurally marked, or the navigation file is incomplete. Apply a consistent heading role, regenerate navigation, and test every target.
Likely cause: tabs, multiple spaces, blank paragraphs, or conflicting local styles. Clean the source, replace manual spacing with CSS, and retest at several font sizes.
Likely cause: weak source images, broken file references, unsupported types, oversized dimensions, or floating layouts. Rebuild from original images, embed them correctly, constrain them responsively, and validate the manifest.
Likely cause: rigid CSS, unsupported features, fixed widths, or reader-specific assumptions. Simplify the styling, use interoperable EPUB features, and test the exact receiving platform again.
Likely cause: missing return links or duplicate anchors. Give each note/reference a unique target and test the round trip in more than one reading system.
Likely cause: an image, font, stylesheet, or content file is absent from the package or manifest. Add or remove the reference, rebuild the package, and rerun EPUBCheck until the release file is clean.
Likely cause: hardcoded foreground/background colors or transparent artwork designed only for white pages. Use theme-resilient colors and test transparent images on dark and light backgrounds.
Likely cause: the converter is reconstructing reading order from fixed page coordinates. Return to the editable source when possible; otherwise extract, clean, restyle, and rebuild instead of accepting the first automatic conversion.
DIY formatting can work for a clean, text-led manuscript with a simple style system. Professional conversion is useful when the source is PDF, the layout is image-heavy, the book contains complex tables or notes, accessibility requirements are demanding, or the release must work across several retailers without trial-and-error.
A good service should request the final editable source, identify reflowable versus fixed layout, explain supported features, provide a proof, run validation, allow corrections, and deliver the final EPUB rather than only uploading it to one platform.
ISBN Services’ eBook Conversion product currently advertises a $69 service with a 48-hour turnaround for standard projects and notes that complex fixed-layout books can also be discussed. Confirm the live scope, price, file requirements, and revision terms before ordering.
For most novels and text-led nonfiction, use a reflowable EPUB as the wide-distribution master. KDP also supports KPF and DOC/DOCX workflows. Choose fixed layout only when exact page geometry is essential.
Some platforms accept PDF in limited workflows, but PDF is fixed-page and often converts poorly to reflowable text. Use the editable manuscript or rebuild the content when a professional EPUB is the goal.
Yes. KDP’s current supported-formats page accepts EPUB files that meet the Kindle Publishing Guidelines and recommends checking them with Kindle Previewer before upload.
Not as the default master. EPUB and KPF are the current primary workflows. KDP says it stopped accepting fixed-layout MOBI uploads in March 2025; verify any remaining legacy requirement before producing MOBI.
Reflowable text adapts to the device and reader settings. Fixed layout preserves page coordinates. Reflowable is best for most prose; fixed layout is reserved for books whose meaning depends on exact visual placement.
Run the current EPUBCheck release, resolve errors, review warnings, then use Ace and manual testing for accessibility. Validation is followed—not replaced—by visual and device QA.
Use previewers for breadth and at least one actual device when possible. Complex, image-heavy, fixed-layout, or accessibility-sensitive books deserve broader real-device testing.
No. If the eBook uses an ISBN, it needs an identifier for the digital product. KDP does not require an ISBN for eBooks, but other distribution plans may.
A simple, final DOCX can be converted quickly; complex images, tables, notes, accessibility work, fixed layout, or a damaged PDF source take longer. Time estimates should include proof review and corrections, not only export.
Good eBook formatting is a repeatable production process: choose the layout model, clean the source, apply semantic structure, create navigation, format for reflow, prepare accessible images and links, export, validate, preview, troubleshoot, and approve the exact release file.
EPUB is not a miniature print book. The reader controls the screen, type, spacing, theme, and orientation. A professional file respects that control while preserving the author’s hierarchy, meaning, and brand.
