What Common Errors Do Creators Make In Sigil Epub?

Honestly, tinkering with Sigil always turns up the same little traps that trip people up — and I’ve fallen into a bunch of them myself. The most painful, frequent mistake is skipping validation. You can edit everything in Sigil and feel like the book is done, but without running epubcheck you’ll miss broken links, duplicate IDs, bad MIME types, and structural issues that kill the book on real readers. Another common rookie move is mangling the EPUB container: forgetting the uncompressed, first-line MIME type rule, or renaming files with spaces/capital letters that break on case-sensitive readers. Images with absolute paths, filenames with weird characters, or placing images outside the EPUB folder structure also lead to missing artwork on devices.

Manifest and spine problems show up next — creators rename chapter files, move them around, and forget to update the manifest or spine, which results in chapters loading out of order or not at all. Duplicate IDs crop up when pasting content from multiple HTML files, and those duplicate IDs wreck internal links and the TOC. Speaking of TOC, relying solely on auto-generated NCX without verifying the nav.xhtml in EPUB3 is a trap: some readers prefer nav.xhtml, some need both, and forgetting to regenerate the table of contents after edits is a fast path to chaos. Covers are another sticky point — people add a pretty image but don’t set it properly in content.opf metadata, so the metadata doesn’t point to the cover and stores/catalogs don’t show it. Fonts are fun but dangerous: embedding fonts without correct @font-face declarations or using incorrect MIME types will either bloat the file or have fonts ignored entirely.

Formatting sins are everywhere because many creators paste from Word or other editors into Sigil without cleaning the HTML. That results in inline styles, excessive tags, missing semantic headings (authors using

+bold instead of h1/h2), and broken accessibility. Inline CSS is tempting but hard to maintain; external stylesheets are cleaner and portable. Accessibility often gets ignored — missing alt text on images, no landmarks, poor heading structure, and ignoring language tags means a lot of readers (and stores) will flag the book. People also forget to test on multiple devices: what looks fine in Sigil’s preview can behave very differently on Kindle, Kobo, or Apple Books because of vendor quirks with CSS or fonts.

For fixes, I’ve found a few rituals that save a lot of headaches: always run epubcheck (there’s a plugin in Sigil), keep filenames simple and lowercase, clean Word HTML with a tool like HTML Tidy before importing, use semantic tags for chapters and headings, embed fonts properly and test fallbacks, and compress images for size without sacrificing quality. Back up before big edits, regenerate the TOC after renames, and try the book on at least one real device. It’s a bit of housekeeping, but getting these basics right makes publishing so much more relaxing — and you get to spend more time on story instead of frantic metadata rescue.