Why Ebooks Look Broken and How to Fix Them

Why Ebooks Look Broken, and How to Fix EPUB Formatting Issues

A symptom-first guide to broken ebook formatting: match what you see to its cause, then apply the smallest fix that works.

You open the book you saved for the weekend. A sentence breaks mid-line and resumes on the next one. The text is too small to read comfortably and too stubborn to enlarge. An apostrophe has turned into an empty box. Somewhere in chapter three, an image frame sits blank.

None of this means your device is failing, or that your eyes are. Nearly all EPUB formatting issues trace back to four cause families: the file's layout type, styling hard-coded during authoring, your reader app's settings, or a flawed conversion somewhere in the file's history. That is a mechanics problem, and mechanics problems have fixes.

This guide works symptom-first. Match what you see to why it happens, then apply the smallest fix that works, cheapest first: settings before fonts, fonts before file surgery, file surgery before conversion. Most broken ebook formatting can be repaired without repurchasing the book or mangling it in a converter.

The symptom-to-cause map

Start with what you see. Each symptom points to a specific, addressable cause; the sections that follow explain the fixes.

Fixed-layout or reflowable: the fork behind most EPUB formatting issues

A reflowable EPUB is text plus instructions. The file holds paragraphs and chapters; your reader decides how they fit the screen, using your font size, margins, and line height. Change the size and the text reflows to fill the space.

A fixed-layout EPUB, usually marked FXL, freezes the page instead. It is a print facsimile: geometry locked, text pinned in place, magnification the only lever. Publishers choose it when layout is the point, as in comics, children's picture books, and design titles, because reflow would destroy the design.

On a phone, that decision lands badly: microscopic text, pinch-zoom gymnastics, margins eating the display. The book is behaving exactly as designed. The design just assumed a different page.

To tell which one you hold, check the book's properties or details page in your reader app, where the layout type is usually listed. The behavioral tell is simpler. If raising the font size changes nothing, you are almost certainly holding a fixed-layout file, and no setting will unlock resizing. Confirm that before blaming the app.

Reader settings can soften fixed geometry. They cannot override it. If a fixed-layout edition is genuinely unreadable on your phone, a tablet or a reflowable edition of the same title is the honest fix.

Hard line breaks: typewriter habits that shatter paragraphs

The most common authoring sin is pressing Enter at the end of every line, as if typing on a typewriter. The second is pasting text from a PDF, where every line ends in a break, or exporting from a careless Word document. On the original page, the breaks look fine. When the text reflows onto a larger screen, they shatter the paragraphs: sentences stop mid-line and short lines stack into staircases.

The reader-side truth is blunt. No setting can fully repair hard breaks baked into the source, because the paragraph structure is wrong inside the file. The fix is file-side: strip the breaks with a paragraph-level find-and-replace, or re-export from a clean source. If your material starts life as PDFs, this is the central problem in any conversion, and converting PDFs to EPUB without wrecking the layout deserves its own careful walkthrough.

The same discipline governs styling. Formatting belongs in the stylesheet, where every reader can interpret it, not scattered as inline style hacks that render differently in each app. The rule under both problems is identical: the file should describe the text, not one particular page. Clean the source formatting before any conversion, and most of this never happens.

Reader-side settings that fix EPUB display problems without touching the file

Before any file surgery, exhaust the reader app. A surprising share of display complaints dissolve here.

• Override publisher defaults. This toggle, present in most serious reader apps, is the first switch to try when a book fights you. It sets aside the publisher's stylesheet and lets yours take over.
• Swap the font. Forcing a standard font family is a reliable workaround for broken embedded fonts.
• Adjust line height, margins, justification, and hyphenation. Stretched lines with wide gaps between words usually mean full justification without hyphenation; ragged ones usually mean the opposite. Both are settings, not defects, and tuning a reading display for visual comfort is a skill worth an afternoon.

Different apps also render the same EPUB differently. Trying a second reader is a legitimate diagnostic step, not defeat: if the book looks fine elsewhere, the problem lives in your default app, not the file, and comparing EPUB reader apps becomes the next task.

If you want a quieter tool for the job, SReader is one option. It imports EPUB, TXT, Markdown, pasted text, and article links, then shows the text in Line, Word, or Book mode at a pace you control, with adjustable text settings for comfort. Everything stays on your device: no account, no ads, no feed. One honest limit applies to PDFs. SReader extracts and reflows the text rather than preserving the page layout, and it performs no OCR. Expect readable text, not a facsimile.

Font embedding and glyph substitution

An EPUB can carry its own fonts. When embedding works, you see the typeface the publisher chose. When it fails, it fails silently: the reader substitutes a fallback font and keeps going.

Two failure modes, two symptoms. If the substituted font lacks the glyphs the text needs, characters become boxes or vanish: tofu where apostrophes and quotation marks should be. If the substituted font has different metrics, its spacing disagrees with the layout, and lines overlap or clip at the edges.

The fix is two-tier. Reader-side, force a standard font family in settings; that sidesteps the broken embedding entirely. File-side, re-embed the fonts, or strip the broken font references and re-export.

Conversions sometimes strip fonts deliberately. Embedded typefaces can carry licensing restrictions a converter will not carry across, so it drops them and lets your reader substitute. That is why a converted file often renders differently from the original, and why font problems cluster after conversion.

Under the hood: image paths, duplicate IDs, and spine order

An EPUB is a zipped mini-website: XHTML chapters, stylesheets, images, plus two lists. The manifest records every file in the package; the spine defines reading order. Structural mistakes in that machinery produce the ghostlier symptoms.

• Broken image paths: the manifest points at an image that is not where the path says it is, so the frame stays empty. This is the direct cause of most missing images.
• Duplicate IDs: validation errors that break cross-references and internal anchors.
• Spine mistakes: chapters appear out of sequence, or content disappears entirely because it never entered the spine.
• Broken internal links: table-of-contents entries that dead-end or land on the wrong page.

A validator reads the package and reports these errors before a reader ever sees them; free tools such as EPUBCheck do exactly this. Run one before hand-editing anything. A structural error is cheaper to fix at the source than to patch by eye.

Legacy MOBI and AZW files, and the conversion that fixes them

Old Kindle-era MOBI and AZW files often render poorly on modern apps, and converting them to EPUB can genuinely refresh the layout. Conversion is also a double-edged tool. Word-to-EPUB exports and misconfigured Calibre or Scrivener presets introduce formatting sins of their own: hard breaks, inline styles, mangled structure.

Convert when an old library looks rough in every app, not just one; that points at the file, not the reader. Convert safely by preferring reflowable output over strict layout preservation, letting text flow instead of freezing the old page. Convert from the best available source, because conversions of conversions compound their parents' errors. And keep the original untouched while you experiment. Never practice on your only copy.

The workflow: diagnose, validate, and re-export without destroying the book

Order matters. Cheap, reversible steps first; file surgery last.

1. Work on a copy. Never edit your only original.
2. Identify the layout type, fixed or reflowable, and run a validator to surface structural errors before you guess.
3. Exhaust reader-side settings: override publisher defaults, swap the font, adjust line height, margins, and justification. Test in a second app.
4. Apply the smallest targeted fix: re-embed fonts, repair image paths, or strip hard breaks, one change at a time so you know what worked.
5. Validate again.

There is also an exit condition. When validation shows the edition itself is broken, the right move is a corrected edition: request one from the publisher, or buy the version that was fixed. Some books are broken at the source, and no reader or converter repairs a publisher's file.

Readable at last

The four cause families again: layout type, authoring habits, reader settings, conversion flaws. The fix ladder never changes: reader settings, then font overrides, then validation and structural repair, then conversion. Cheapest first, smallest first.

This matters beyond aesthetics. Text that flows cleanly is the entry point to focused reading: no negotiating with the file, no rereading sentences a hard break chopped in two. If you want to test that with a calmer tool, Try SReader, a local-first reader with no account, no ads, and no feed for EPUB, TXT, Markdown, pasted text, and PDF text on iPhone, iPad, Mac, and Android.

Almost no ebook problem requires destroying the book. Or your reading momentum.