Exporting and publishing
Dizire Engine supports several export paths because the finished use case is not always the same. EPUB is for a packaged ebook, PDF is for fixed-layout review or delivery, DOCX is for editable manuscript handoff, and Markdown is for plain-text workflow portability.

Export should happen after the manuscript is stable, not as a substitute for preview or metadata cleanup. The workspace and release editor both support the final handoff stage.
On this page
Where to export
The main release editor includes an Export Manuscript block with buttons for Export to DOCX, Export to PDF, and Export to EPUB. The writing workspace adds top-bar shortcuts for Export EPUB and Export Markup (.md).
That split is intentional. The release editor is the best place when you are thinking about the whole publication package. The workspace shortcuts are better for direct manuscript handoff when you are already inside the book.
Shared behavior
No matter which format you choose, the export is built from the saved release record: release title, premise, optional prologue, chapter text, chapter order, and the merged publishing profile created from project defaults plus release overrides.
EPUB
EPUB is the richest package in the current export set. It uses the publishing profile to include optional title, copyright, acknowledgments, about-the-author, also-by, next-book, and character-bio sections. It can also embed the release cover art when the release has a saved cover image.
EPUB is also the format the system uses for server backups when deleting releases or whole projects. That makes it the closest thing to the app's archival publication package.

EPUB reflects the metadata and page-toggle decisions more strongly than the plainer export paths, so clean publishing settings matter most here.
PDF and DOCX
PDF is useful when you want a stable reading copy, a print-style review artifact, or a file someone can open without editing the manuscript structure. The preview page even includes a Print / Save PDF action for a quick visual proofing pass.
DOCX is better when the file still needs outside editing, annotation, or compatibility with standard manuscript tools. It carries the manuscript structure into a format that remains easy to revise elsewhere.
Markdown
Markdown export is different from the book-facing formats. It creates a plain-text package with release metadata, premise, opening state, carryover threads, ending state, prologue, and chapter content in a readable .md file.
This is useful when the next step is another writing tool, LLM workflow, plain-text archive, or a manual transformation pipeline rather than direct reader delivery.
Decision rule
Do not choose the format by habit. Choose it based on what happens immediately after the export.
Next step
Once the export paths are clear, the next publishing questions are channel fit and pre-flight checks. Continue through the wiki home publishing track for the upcoming articles on choosing the right export format and final quality checks.