Skip to converter

EPUB to HTML — packaged chapters become a single reflowed page

A public-domain ebook is being placed on a class site as one continuous reading page. The conversion walks the ebook's spine, joins the listed chapter documents in that order, and emits sanitized markup. The packaging that made it an ebook — per-chapter CSS, navigation, page numbers, images — is removed along the way, so what you get is a plain document, not a book.

Page layout, fonts, margins, headers, footers and page breaks are not reproduced: the text stream is reflowed, not re-laid-out.

Drop files here or EPUB, up to 8 MB
    Add a file to start.

    Processed on your device. Files aren’t sent anywhere.

    No sign-up. Nothing to install.

    From packaged chapters to one page

    Follow one ebook through the stages.

    1. The archive is opened and the spine is read, so the reading sequence is established before any text is taken.
    2. Each spine-listed chapter document is parsed; unreferenced files are never touched.
    3. Chapter markup is reflowed into elements: headings, paragraphs, lists, tables.
    4. The chapters are joined in spine order into one document.
    5. The result is sanitized: scripts, styles and unsafe links are removed.
    6. A single .html file is produced, capped at 400000 characters.

    Where the chapter boundaries go

    Chapter headings usually survive as heading elements, so the outline of the book is still visible. What disappears is the visual break: the ebook's own CSS that started each chapter on a new page, its page numbers and its navigation list.

    On your site the chapters therefore run together as one column. If you want visible breaks, add them yourself with the site's stylesheet — the converter does not invent styling, and original styling is not carried.

    What the sanitizer removes from the packaging

    Ebook packaging contains more than text, and none of the executable or presentational parts belong in the output.

    Packaging elementIn the HTML outputEffect on reading
    Spine-listed chapter textkept in spine orderthe book reads in the intended sequence
    Chapter headingskept as heading elementsoutline visible, page breaks absent
    Per-chapter CSSremovedyour site supplies the appearance
    Images and cover artdroppedcaptions arrive without figures
    Navigation listnot carried as navigationno chapter jump menu
    Scripts and unsafe linksremovednothing executes, unsafe destinations are dropped

    Reading the result as a page

    The output behaves like a long article rather than a book.

    • One document, one scroll: there is no page turning and no chapter switching.
    • Only spine-listed content appears, so a chapter missing from the spine is missing from the page.
    • Tables reflow to your site's width instead of the ebook's page size.
    • Footnote behaviour depends on the output format, so check the notes you expect in the converted page.
    • One file up to 8 MiB is accepted; ZIP entries are limited to 4 MiB each and 16 MiB total, so an oversized archive is rejected rather than partially converted.

    Questions about the joined reading page

    Does each chapter stay a separate file?
    No. Spine-listed chapters are joined into one sanitized HTML document in spine order.
    Will the ebook's own styling appear?
    No. Scripts, styles and unsafe links are removed, so your site's stylesheet provides the appearance.
    Why is one chapter missing?
    Only documents listed in the spine are read. A file present in the archive but not referenced by the spine is skipped.
    Is the ebook uploaded to a server?
    No. The archive is unpacked inside the browser tab using vendored libraries, no remote request is made, and scripts inside the ebook are never executed.

    Share this converter

    More sharing options