A small text-only book workflow
This tool is for a manuscript you can represent as plain-text chapters: a short guide, a collection of essays, a workshop reading or a personal writing sample. It creates two files from the same text. The EPUB contains a title page, a navigation document and one XHTML file per chapter. The HTML reading copy puts the chapters in one self-contained document with a linked contents list.
The preview above lets you check chapter order, headings and paragraph boundaries before downloading. It shows the same text and order used in the files, but it is not an emulation of an e-reader. Reading systems choose their own fonts, margins, pagination and other presentation details. Open the EPUB in your intended reading system and review the result before distributing it.
Prepare your chapters
Enter a book title and the author name or pen name you want to include. Choose the manuscript's primary language. The selection sets language metadata; it does not translate or convert your text. Unicode text, including Tamil and Hindi, remains text in the generated XHTML. Display depends on the fonts available in the reading system; this tool does not embed fonts or repair legacy font encodings.
Start the manuscript with a line such as # First chapter. Every later line beginning with a hash and a space starts another chapter. A blank line ends a paragraph. A single line break within a paragraph becomes a space, which helps when prose was wrapped to a fixed line width. Use separate paragraphs when the separation matters. Poetry, code indentation, tables and other layouts that depend on preserved line breaks need a more suitable editor.
Only chapter headings and paragraph breaks have structural meaning here. Asterisks, Markdown links, numbered lists and HTML-looking text remain ordinary text. The builder does not fetch URLs, import documents or execute supplied markup. Do not paste a web page's source and expect the page layout to be reproduced. A chapter heading must have text, and every chapter must contain at least one paragraph; an empty chapter stops the build rather than disappearing silently.
Try the fictional example
The example contains two chapters, “A small beginning” and “Another page”, each with two paragraphs. Build it and follow the contents links in the preview. Downloading the EPUB produces a package with eight files: the required media-type marker, the container description, a stylesheet, a navigation document, a title page, two chapter documents and the package metadata. Downloading the HTML reading copy gives you those chapters in one document instead.
Edit a heading or a paragraph after building. The previous preview and download controls disappear until you build again, so an old file is not offered as if it reflected the edit. Clear all removes the title, author, text and results. Reloading starts a new empty page session. Save any manuscript you want to retain in a separate file before closing the page.
What the EPUB includes
The EPUB uses the EPUB 3 package structure. Its metadata includes the supplied title, author and primary language, a newly generated book identifier and the build time in UTC. Each build creates a new identifier, so a regenerated file is not a stable update of the same book in every reader library. The package lists its resources and reading order explicitly, and the navigation document links to the chapter files.
File contents are UTF-8, and manuscript characters are escaped as text rather than interpreted as HTML. The archive contains no scripts, forms, remote images, external stylesheets, tracking pixels or network resources. The generated layout is reflowable rather than a fixed page design. It supplies no ISBN, cover artwork, footnotes, embedded media, digital rights management or bookstore submission metadata.
Use the downloads and understand the limits
The HTML reading copy can be opened in a browser or printed through its Print command. Its styles are included in the file, so it does not need this website to remain available. Both downloads contain your title, author and manuscript text; treat them as copies of your work and choose where to keep or share them. Clearing this web form does not delete a downloaded file.
This builder is deliberately smaller than a general ebook editor. It does not validate an existing EPUB, preserve a Word document's formatting, convert PDFs, check copyright or prove that a store will accept a file. It does not run EPUBCheck. Check the generated book with an appropriate validator and your target reading system when preparing a publication. Accessibility information beyond the basic text structure and language metadata is not supplied automatically.
The bounds of 200,000 characters, 50 chapters and 2,000 paragraphs keep creation and preview work manageable in the browser. Titles are limited to 160 characters, author names to 120 and chapter headings to 160. Unsupported XML control characters and invalid text are rejected. Use a modern browser with secure-context UUID support. Technical reference: W3C EPUB 3.3 specification.