Check the project before checking the files
Export QA starts inside the document project. Confirm the title, Binder order, included sections, excluded sections, Trash, front matter, back matter, and any notes that should stay private before generating files.
If the source project is messy, every exported format inherits that mess. A short readiness pass before export prevents many of the mistakes authors usually catch after uploading a file.
Review each format for its real job
DOCX is useful for editing and platform upload, EPUB is useful for ebook reading tests, PDF is useful for fixed proofing, TXT and Markdown are useful for portable source text, and ZIP is useful for records and handoff.
Awtter supports unlimited exports, so authors can generate each format, inspect the result, revise the source, and export again without treating each proof file like a scarce resource.
Open the files before publishing
Do not rely on a download alone. Open the DOCX, page through the PDF, load the EPUB in a reader, scan the text exports, and inspect the ZIP contents before sending files to KDP, Draft2Digital, an editor, or a client.
Look for missing chapters, duplicated sections, visible notes, inconsistent headings, bad scene breaks, empty sections, and any front matter or back matter that landed in the wrong position.
Keep a backup with the final export
A final export is easier to trust when it sits beside a project backup from the same moment. If a platform, editor, or client asks for changes later, you can return to the exact source state that produced the reviewed files.
That pairing gives authors a cleaner revision loop: restore the project if needed, make the update in the Binder, run the readiness checklist, and export the corrected package.