You upload to Apple Books thinking, “this looks clean.”
Then something weird happens:
- File gets flagged
- Layout looks different on iPhone vs Mac
- Fonts change for no reason
- Images shift or resize
And the worst one… it passes validation, but the reading experience feels off.
Seen it too many times.
Apple Books is stricter than people expect—but also more forgiving in weird places. You just need to understand where it cares.
The #1 Reason Apple Books Files Break
You’re mixing print logic with eBook structure.
Apple Books is built around EPUB, not PDFs, not Word layouts.
That means:
- Structure matters more than appearance
- Clean HTML/CSS under the hood matters
- “Looks fine” is not enough
Most people export and hope.
That’s where it falls apart.
EPUB Structure Problems (The Hidden Layer Nobody Checks)
An EPUB is basically a zipped website.
Inside it:
- HTML files
- CSS styles
- Images
- Metadata
If that structure is messy, Apple Books will:
- Override your styles
- Ignore your fonts
- Rearrange content
This is the part everyone skips.
Quick reality check:
- Open your EPUB in a tool like Apple Books Preview or unzip it
- If the code looks chaotic → expect problems
Clean structure = predictable output.
Reflowable vs Fixed Layout (Pick Wrong, Everything Feels Broken)
Apple Books supports both.
But it behaves differently depending on what you choose.
Reflowable (Default)
- Text adjusts to screen
- Reader controls font size
- Works everywhere
Fixed Layout
- Design is locked
- Looks identical across devices
- Limited flexibility
Mistake I see constantly:
People force fixed layout when they don’t need it.
Then:
- Text becomes tiny on iPhones
- Readers complain
- Sales drop
Unless it’s a children’s book, cookbook, or highly visual content…
Stay reflowable.
Font Issues (Why Your Typography Keeps Changing)
You picked a nice font. Exported. Uploaded.
Now it’s different.
Here’s why:
- Font not embedded
- Font not licensed for embedding
- Apple Books overrides unsupported fonts
Critical rule:
- Always embed fonts properly in EPUB
Even then, Apple may still substitute in some cases.
Safe move:
Use web-safe or widely supported fonts if consistency matters.
Image Problems (Where Layout Starts Falling Apart)
Images are the biggest source of “why is this moving?”
Common issues:
- Images too large (Apple scales them unpredictably)
- Inline images breaking text flow
- Wrong alignment settings
What works reliably:
- Use block-level images (not inline)
- Set max-width: 100% in CSS
- Keep resolution reasonable (don’t dump 300 DPI print images blindly)
Important:
eBooks don’t need 300 DPI like print.
Overloading images just bloats the file and slows performance.
CSS Overrides (Apple Doesn’t Always Listen to You)
You can write clean CSS… and Apple Books still ignores parts of it.
That’s normal.
Apple prioritizes:
- Readability
- User settings
So things like:
- Line height
- Margins
- Font scaling
May be adjusted automatically.
If your layout depends on strict CSS control, it will break.
Table of Contents (The Navigation Trap)
There are two TOCs:
- Logical TOC (NCX / navigation file)
- Visual TOC (inside your book)
Most people only create one.
Apple Books expects both to be correct.
If not:
- Navigation breaks
- Chapters don’t jump correctly
- Reviewers may flag it
Quick check:
Tap the TOC inside Apple Books preview.
If it feels off → fix your navigation file.
Metadata Mistakes (Why Your Book Looks Unprofessional)
Metadata is what shows:
- Title
- Author name
- Cover
- Categories
Mess this up and your book looks amateur instantly.
Common issues:
- Missing author field
- Wrong language tag
- No cover embedded in EPUB
The one you can’t skip:
Embed your cover image inside the EPUB, not just upload separately.
Fixed Layout Specific Problems (If You’re Going That Route)
If you chose fixed layout, now the rules change.
Apple Books expects:
- Exact viewport settings
- Defined page dimensions
- Proper image scaling
Miss any of these:
- Pages crop incorrectly
- Content shifts on different devices
- File gets rejected
And remember:
Fixed layout does not adapt.
If it looks bad on a phone, that’s on the design—not the platform.
Quick Diagnostic Table (Find the Problem Fast)
| Symptom | What’s Actually Wrong | Fix |
|---|---|---|
| Font changed after upload | Not embedded / unsupported | Embed properly or use safe fonts |
| Images shifting | Inline or oversized | Use block images + max-width |
| Layout looks different on devices | Reflowable behavior | Simplify structure |
| TOC not working | Missing navigation file | Fix EPUB TOC structure |
| File passes but looks off | Messy HTML/CSS | Clean EPUB code |
| Fixed layout looks tiny on phone | Design limitation | Redesign or switch format |
Fix It Fast: What I Check Before Uploading
Run this every time:
- EPUB validates clean (no major errors)
- Fonts embedded and licensed
- Images optimized (not oversized)
- TOC works perfectly
- Metadata complete
- Tested on multiple screen sizes
Skip one, and it shows up later.
The “It Looked Fine Before Upload” Problem
This one drives people crazy.
You preview your EPUB somewhere else—it’s perfect.
Upload to Apple Books—and things shift.
That’s because Apple has its own rendering engine.
Always test inside Apple Books Preview.
Not optional.
The One Thing That Saves You From 80% of Problems
Keep your EPUB simple.
Not boring—simple.
- Clean HTML
- Minimal CSS
- No fancy positioning tricks
- Logical structure
Every time someone tries to “outsmart” EPUB formatting…
Apple Books humbles them fast.
Still Stuck? Here’s the Real Issue
Most people treat EPUB like a design file.
It’s not.
It’s structured content with styling—not layout control.
Once you accept that:
- Problems stop feeling random
- Fixes become obvious
- Your books pass faster and look better
Get the structure right first.
Everything else becomes predictable after that.