eBook Creator

How do I create an ebook with chapters and a cover, and export it as EPUB or PDF?

Open AnyTool Ebook Creator, fill in the book details (title, subtitle, author, language and a description), pick a colour cover theme or upload your own image, then add chapters in the sidebar and write each one in Markdown. The Table of Contents is built automatically from your chapter titles, and a book-like live reader shows the cover, contents and chapter pages as you type. When you are done, export a valid EPUB 3 for e-readers and Kindle, a fixed-layout PDF, or the whole book as a single Markdown file. Everything runs in your browser — your manuscript is never uploaded.

Add, reorder and delete chapters; the table of contents follows your titles
Write chapters in Markdown — headings, bold, italic, lists, quotes and code
Design a colour cover or upload your own PNG/JPEG cover image
Export a spec-valid EPUB 3 (zipped on-device), a PDF, or one Markdown file
Book-like live reader preview · 100% in your browser, nothing uploaded

What is

EPUB

EPUB (electronic publication) is the open ebook standard maintained by the W3C. An EPUB file is a ZIP archive that contains a “mimetype” marker, a META-INF/container.xml pointing to a package (OPF) file, that package’s metadata, a manifest of every resource and a spine that sets the reading order, navigation documents (nav.xhtml for EPUB 3 and toc.ncx for EPUB 2), and one XHTML document per chapter plus styles and an optional cover. Because the text is reflowable, an EPUB adapts to any screen size, which is why e-readers and reading apps use it.

Generators

Related terms

EPUB 3OPF packageReflowable textTable of contents (nav.xhtml)

Frequently Asked Questions

AnyTool Ebook Creator runs completely client-side. Your title, chapters, metadata and even an uploaded cover image stay on your device — the EPUB is packaged locally with JSZip and the PDF is laid out locally with pdf-lib, so nothing is uploaded, logged or stored on a server. The optional “Save draft” keeps a copy only in this browser’s localStorage, which you can clear with Reset, and the page works offline once it has been cached.

No. The entire book is built in your browser. The EPUB is zipped on your device and nothing you write is sent to a server.

The tool exports a spec-valid EPUB 3 file, which is the format e-readers and most reading apps use. Amazon’s Kindle accepts EPUB through its own Send-to-Kindle service and Kindle Previewer, which convert the EPUB into Kindle’s internal format, so you may need that extra conversion step rather than copying the EPUB on directly. Because EPUB text is reflowable, always open the file in a reader such as Apple Books, Calibre, Thorium or Kindle Previewer and check it before publishing.

It produces a valid EPUB, which Kindle now accepts via Amazon’s tools. Use Send-to-Kindle or Kindle Previewer to load it onto a Kindle.

EPUB stores your book as reflowable XHTML, so the reader can change the font, size and margins and the text re-flows to fit any screen; that makes it the right choice for e-readers, phones and Kindle. The PDF export is a fixed-layout book — a cover page, a contents page and each chapter starting on its own page with footer page numbers — which looks identical everywhere and is ideal for printing or sharing a precise on-screen copy. The Ebook Creator builds both from the same manuscript so you can offer either.

EPUB is reflowable text that adapts to any screen — best for e-readers. The PDF is fixed-layout, best for printing and on-screen reading.

The Table of Contents is generated directly from your chapter list. In the EPUB it is written into both the EPUB 3 navigation document (nav.xhtml) and the EPUB 2 toc.ncx so older and newer readers can both navigate; in the PDF it appears as a Contents page; and in the live reader it appears as a clickable contents view. Because it is rebuilt from the live chapter list, any time you add, rename, reorder or remove a chapter the contents stay in sync everywhere.

Automatically from your chapter titles. Reordering, renaming or deleting a chapter updates the contents in the EPUB, PDF and live preview.

Write an ebook with a cover, chapters and an automatic table of contents, then export a valid EPUB 3, a PDF and a Markdown file — entirely in your browser, nothing uploaded.

Features

Book metadata + a colour cover theme or your own uploaded image
Markdown chapters you can add, reorder and delete
Automatic table of contents derived from chapter titles
Spec-valid EPUB 3 zipped on-device, plus PDF and Markdown export
Book-like live reader preview — 100% client-side, nothing uploaded

PriceFree

CategoryGenerator

PlatformAll (browser-based)

PrivacyThe manuscript and cover are processed locally and never uploaded; the EPUB and PDF are built on-device

Input: No upload — write chapters in Markdown, Optional cover image (PNG/JPEG)

Output: EPUB 3 (.epub), PDF (.pdf), Markdown (.md), Live book reader preview

Detailed Explanation

Methodology

How the Ebook Creator Models and Builds a Book

AnyTool Ebook Creator models a book as plain metadata (title, subtitle, author, language and a description), a cover (either a generated colour theme or an uploaded PNG/JPEG image), and an ordered list of chapters, each a title plus a Markdown body. A pure, reusable engine (ebookEngine) renders each chapter’s Markdown to HTML with the marked library and assembles the export artefacts on-device: the Table of Contents is derived automatically from the chapter titles, chapters can be added, renamed, reordered and deleted, and a book-like live reader pages through the cover, the contents and each chapter as the author writes. Nothing is sent to a server — the manuscript, the cover image and every export are produced entirely in the browser.

A book = metadata + cover + an ordered list of Markdown chapters
Markdown is rendered to HTML locally with the marked library
The table of contents is generated automatically from chapter titles
Chapters can be added, renamed, reordered and deleted
A book-like live reader previews cover, contents and chapter pages

Technical Details

Packaging a Spec-Valid EPUB 3 in the Browser

The EPUB export follows the W3C / IDPF EPUB specification and is zipped on-device with JSZip (lazy-imported). The archive begins with a “mimetype” entry that is added first and stored uncompressed, exactly as the Open Container Format requires, followed by META-INF/container.xml pointing to the OPF package. The OPF carries Dublin Core metadata (title, creator, language, description and a UUID identifier generated with crypto.randomUUID), a manifest listing every resource, and a spine setting the reading order. Navigation is provided both ways — an EPUB 3 nav.xhtml document and an EPUB 2 toc.ncx — for broad reader compatibility, alongside one XHTML document per chapter (well-formed, with void elements self-closed), a stylesheet, a generated title page, and an optional cover image with its own cover.xhtml. The PDF export is laid out separately with pdf-lib.

mimetype is written first and stored uncompressed, per the OCF spec
OPF holds Dublin Core metadata, a manifest and a spine, with a crypto.randomUUID identifier
Both nav.xhtml (EPUB 3) and toc.ncx (EPUB 2) navigation are emitted
One well-formed XHTML document per chapter, plus a stylesheet and optional cover
EPUB is zipped with JSZip and the PDF is built with pdf-lib — all on-device

Privacy & Security

Privacy, Exports and the Honest Caveats

Because the book is assembled in the browser, the manuscript, metadata and any uploaded cover are never uploaded, logged or stored, and the page works offline once cached; an optional draft can be saved only to the browser’s localStorage and cleared with Reset. The author can export a reflowable EPUB 3 for e-readers, a fixed-layout PDF (cover page, contents and chapters with footer page numbers), or the whole book as a single Markdown file. The tool is explicit that EPUB is reflowable text best suited to e-readers and that reading it on a Kindle may require converting the EPUB with Amazon’s Send-to-Kindle or Kindle Previewer tools; that the styling is intentionally clean and basic (headings, paragraphs, lists, quotes and code) rather than a designed layout; and that the file should always be tested in a reader such as Apple Books, Calibre, Thorium or Kindle Previewer before publishing — it is a writing-to-ebook builder, not a full publishing, typesetting or DRM suite.

No upload, logging or storage — works offline once cached
Optional draft saved only to localStorage, cleared with Reset
Three exports: reflowable EPUB 3, fixed-layout PDF, single Markdown file
EPUB is reflowable; reading on Kindle may need Amazon’s conversion tools
Basic styling — test in a reader (Apple Books / Calibre / Kindle Previewer)

Ebook creation: in-browser (AnyTool) vs typical online ebook makers
Capability	AnyTool	Typical online ebook makers
Processing	Runs entirely in your browser	Often server-side or AI-backed
Manuscript privacy	Never uploaded; built on-device	Usually uploaded to a server
Chapters	Add, reorder, delete · Markdown	Fixed or limited editor
Table of contents	Auto from chapter titles	Manual or absent
EPUB	Spec-valid EPUB 3 (nav.xhtml + toc.ncx)	Varies; sometimes EPUB 2 only
Exports	EPUB · PDF · Markdown	Often one format or paywalled
Cover	Colour theme or your own image	Templates, often gated
Cost / signup	Free, no signup, no watermark	Often gated or watermarked

AnyTool assembles the EPUB and PDF locally in the browser and uploads nothing; the cover image stays on your device.

Cite This Page

Title: Ebook Creator (chapters + cover, auto table of contents, EPUB 3 + PDF + Markdown export, 100% client-side)
Author: AnyTool
Published: January 1, 2026
Modified: February 8, 2026
Section: Generators
URL: https://www.anytool.tech/ebook-creator

Formatted Citation

AnyTool. "Ebook Creator (chapters + cover, auto table of contents, EPUB 3 + PDF + Markdown export, 100% client-side)." AnyTool, January 1, 2026. https://www.anytool.tech/ebook-creator

A privacy-first, 100% client-side ebook creator that turns a manuscript into a finished ebook entirely in the browser with no server call, no CDN and no upload, so the title, chapters, metadata and an optional cover image never leave the device and the tool works offline once cached. A pure, reusable engine (ebookEngine) models a book as plain metadata (title, subtitle, author, BCP-47 language and a description), a cover that is either a generated on-brand colour theme or an uploaded PNG/JPEG image, and an ordered list of chapters where each chapter is a title plus a Markdown body; chapters can be added, renamed, reordered and deleted, and the Table of Contents is derived automatically from the chapter titles. Each chapter’s Markdown is rendered to HTML locally with the marked library, and a book-like live reader pages through the cover, the contents and each chapter as the author writes. The EPUB export follows the W3C / IDPF EPUB 3 specification and is zipped on-device with a lazy-imported JSZip: the archive begins with a "mimetype" entry added first and stored uncompressed exactly as the Open Container Format requires, followed by META-INF/container.xml pointing to the OPF package, an OPF carrying Dublin Core metadata (title, creator, language, description and a UUID identifier generated with crypto.randomUUID) together with a manifest of every resource and a spine that sets the reading order, both an EPUB 3 navigation document (nav.xhtml) and an EPUB 2 toc.ncx for broad reader compatibility, a generated title page, one well-formed XHTML document per chapter (with void elements self-closed so the markup is valid XHTML), a reflowable stylesheet, and — when supplied — an embedded cover image with its own cover.xhtml referenced from the manifest and spine. The PDF export is laid out separately with pdf-lib as a fixed-layout book: a cover page (either the uploaded image scaled to fill or a themed typographic cover), a Contents page, and each chapter beginning on its own page with heading-aware Markdown rendered to wrapped, paginated text and footer page numbers. The author can also export the whole book as a single Markdown file, and an optional draft is saved only to the browser’s localStorage and cleared with Reset. The page is explicit and honest that it builds a valid EPUB 3 and a matching PDF from the user’s own writing rather than designing fancy page layouts or writing the book: EPUB is reflowable text best suited to e-readers, reading it on a Kindle may require converting the EPUB with Amazon’s Send-to-Kindle or Kindle Previewer tools, the styling is intentionally clean and basic (chapter headings, paragraphs, lists, quotes and code), and the file should always be tested in a reader such as Apple Books, Calibre, Thorium or Kindle Previewer before publishing — it is a writing-to-ebook builder, not a full publishing, typesetting or DRM suite.