ePUB.
The standard format for digital books, generated from the same source documents you already maintain. IDPF-standard e-books that open on Adobe Digital Editions, Apple Books, and the e-readers, tablets, and publishing platforms your readers already use.
What ePUB delivers.
ePUB is ePublisher's e-book output format. It produces a single packaged book file that conforms to the IDPF ePUB standard — a compressed container of structured HTML, styling, navigation, and metadata that any compliant ePUB reader can render. Where browser-based formats target a help portal and PDF targets a print-equivalent paged document, ePUB targets the e-book experience: long-form reading, offline access, and reflowed layout that adapts to the reader's device and chosen text size.
Output validated against the EpubCheck reference validator during the development cycle, so your book starts on the right side of the standard.
Selectable through Target Settings; ePublisher embeds the cover image so iTunes, Apple Books, Adobe Digital Editions, and other readers display the correct e-book icon.
Title, author name, file-as author, and a unique book identifier — set through Target Settings or Merge Settings to match your publishing workflow.
Paragraph- and table-level page-break priorities, so long chapters render efficiently on memory-constrained mobile devices instead of arriving as one enormous page.
Selectable independently from body content, so the front matter and the back matter can each carry their own page treatment.
Alternate book titles configurable per locale through Merge Settings, for multi-language editions of the same source.
Where ePUB fits.
ePUB is the right output when your readers want a book, not a help system or a PDF. Three deployment patterns drive most adoption:
Reference manuals, user guides, training material, and reading-heavy documentation are well suited to the ePUB reading experience: bookmarks, reading-progress tracking, adjustable font size, and full offline access on the reader's device. Right when content is meant to be read end-to-end rather than searched topic-by-topic.
ePUB readers exist on every major mobile platform — Apple Books, Adobe Digital Editions, and a long list of third-party reader apps. For audiences who already consume long-form content through an e-reader app, an ePUB is the natural delivery format: the reader app handles pagination, typography, and storage.
Once an ePUB is on the device, the content is fully available without a network connection. This makes ePUB a fit for field use, classroom use, and any deployment where readers cannot be assumed to have continuous access to a documentation portal.
ePUB vs. ePublisher's other outputs.
ePUB and the rest of ePublisher's output formats are produced from the same source project. The choice between them is a question of how the reader will consume the content.
Long-form reading on e-readers and tablets.
Right when the content is a book — read sequentially, possibly offline, with the reader app handling pagination and typography. Reflowable layout is a feature, not a limitation.
A documentation portal.
If readers will arrive through a browser, search across topics, and expect a polished documentation site — responsive HTML5, advanced search, GA4 analytics, AI-assisted features.
Fixed-layout, print-equivalent delivery.
PDF and ePUB are both offline formats but make opposite layout choices. PDF preserves a fixed page layout; ePUB reflows. For regulatory artifacts or anything that needs to look like a printed page, PDF is right.
What makes ePublisher's ePUB stand out.
Single source, every output format
ePUB is generated from the same ePublisher source project as Reverb 2.0, Dynamic HTML, PDF, and the legacy help formats. Authors work in their preferred document tool — Adobe FrameMaker, Microsoft Word, DITA XML, or Markdown — and ePublisher applies the project's Stationery to produce each target format. Conditional content, variables, and styling carry across consistently. There is no separate ePUB source set to maintain.
Reader-aware rendering decisions
ePublisher's ePUB output reflects what real e-book readers do with content, not just what the standard permits. Tables render with paragraph markup by default — because every reader tested has limitations rendering tables larger than the available screen — with full table markup available as an opt-in for content where it is appropriate. Image-in-cell warnings surface during generation rather than turning into rendering bugs in the reader.
Cover and metadata controlled at the project level
Cover image, cover page template, author, file-as author, book ID, and localized titles are all configurable through Target Settings and Merge Settings — not buried in the source documents. Marketing and editorial decisions about how the book presents itself in the reader's library stay with the project, not with each writer.
Long-content handling out of the box
The ePUB standard recommends breaking long content into smaller chunks to keep page rendering responsive on constrained devices. ePublisher's standard page-break controls — paragraph- and table-level page-break priorities, configurable in the Style Designer Options panel — apply directly to ePUB output, so authors don't need a separate ePUB-specific authoring discipline.
Cover-page customization through page templates
For teams that want full control over the front matter, the cover page template (Pages/Cover.asp) is customizable through ePublisher's standard override mechanism — the same mechanism used to customize cover and index pages across other formats.
Authoring once, publishing to any format.
ePUB is one of several outputs ePublisher generates from the same source project. The same documents that produce ePUB for an e-book release can also produce Reverb 2.0 for a customer-facing portal, Dynamic HTML for embedded in-product help, PDF for printable user guides, and legacy formats like HTML Help, Oracle Help, and Sun JavaHelp — all in a single publishing run.
Reaching multiple audiences with consistent content means writing once, branding once, and shipping everywhere your readers are.
Ready to ship your documentation as an e-book?
See how ePUB output fits your distribution and reader experience. Walk through your use case with us, or start a free 14-day ePublisher trial.