HTML → EPUB
Package a web page or a saved article into an ebook, with the navigation and clutter stripped and chapters built from the headings.
Drop your HTML
or click to choose — the only ceiling is your own memory, none on our side
Most of an HTML file is not the thing you want to read. A saved article carries a masthead, a navigation bar, a sidebar of related links, a newsletter form, a cookie banner, a footer of legal text and a few scripts. The article itself is often less than a fifth of the file.
So this conversion starts by throwing the website away. Navigation, headers, footers, asides, forms, iframes and scripts are removed; if the page uses a main or article element, that is treated as the content and everything outside it is discarded. What is left is split into chapters on whichever heading level you pick, and packaged as a valid EPUB 3 with a table of contents built from those headings.
It is the right tool for a long piece you want to read away from a screen full of distractions, for documentation you would rather have on an e-reader, or for turning your own site's output into something you can hand to someone. It takes a saved file rather than a URL, because this page has no server to go and fetch one with — which is the same reason nothing you convert here is ever uploaded.
Format by format
| What it does | HTML | EPUB |
|---|---|---|
| Designed for | A browser window, with navigation around it | A book, read start to finish |
| Chapters | None — headings are just headings | Real, with a table of contents |
| Page furniture | Menus, sidebars, forms, banners | None, by definition |
| Offline reading | Needs the assets saved alongside | Self-contained in one file |
| On an e-reader | Awkward | Native |
| Metadata | A title tag, if you are lucky | Title, author and language in the OPF |
What actually changes
Most of an HTML file is furniture: menus, sidebars, footers, share buttons. This strips those and keeps the article, then splits it into chapters on whichever heading level you choose. It is a judgement call made by code, so check the chapter list before you rely on it.
What survives
What does not
How it works
Save a page from your browser first with Ctrl+S or Cmd+S, then drop the file here.
Nav, header, footer, aside, forms and scripts are removed; the article stays.
Chapters split on the heading level you picked, with a table of contents to match.
FAQ
Not here — this page has no server, so it cannot fetch a URL on your behalf. That is the same reason nothing you convert is uploaded. Save the page in your browser with Ctrl+S or Cmd+S and drop the file in.
Either the page has no headings at the level you chose, or its headings are styled divs rather than real h1 or h2 tags, which is depressingly common on sites built with page builders. Try a different level; if none works, the page has no machine-readable structure to split on.
No — image tags still point at the original website, so they need a connection to display and will break if the site moves them. Fully self-contained packaging is on the list.
One file at a time for now. For a set of pages, concatenate them into a single HTML file first and split on h1; that also gives you control over the chapter order, which a folder does not.
Often very well, because documentation tends to use real heading elements and a main or article wrapper. Split on h2 for a single long page, or h1 if you concatenated several pages together.
Whichever level marks the divisions you want as chapters. h1 for a page where each section is a top-level heading; h2 for a long article with a single h1 title and h2 sections.
DualBook translates the EPUB you just built and returns both languages together.
