ReaderMagnet

How-To Guides

Formatting EPUB ARC Files Without Tears

October 5, 2026 · By ReaderMagnet Editorial Desk

How-To Guides indie authors reader magnets

Clean chapters, working TOC, and Kindle-friendly basics so ARC readers spend time on the story instead of support tickets.

Readers forgive a sentence they dislike. They do not forgive a file that will not open, a chapter that is one long block, or a table of contents that jumps to the copyright page every time. The ARC is already a favor. A broken file turns the favor into a support ticket, and the review you might have received becomes a note about the download.

You do not need to become a typesetter. You need a reflowable file a phone can open, with chapters a reader can find, and a cover that does not explode into a blank screen. EPUB is the format built for that. The spec the reading systems are aiming at is EPUB 3, maintained by the W3C and published as the EPUB 3.3 recommendation. You do not have to read the specification to export a clean book. You do have to open the file you exported and read ten pages of it on a device that is not your computer.

What should you hand a reader, and what should you keep back?

Hand them the book. A complete draft, in reading order, with a title page that matches the book you described on the landing page. If you are still moving scenes around, you are not ready to send the file. Say so and move the window. An ARC can contain a typo. It should not contain a note that says "TK chapter 12" or a comment bubble that says "make her meaner."

EPUB is the default for fiction because the reader can change the type size. That matters on a phone, which is where a lot of advance copies are actually read. A PDF can be the right extra when the book is heavily illustrated, is a workbook, or is the print layout you need a proofreader to see. PDF is a poor default for a novel. The type is frozen. The reader pinches and drags. They will not pinch and drag through 400 pages, and they should not have to.

If you offer both, say which one is the reading copy. "EPUB for reading, PDF if you specifically need the print layout" prevents a dozen emails. The page that should say this is covered in Landing pages for ARCs that reduce support. When the file fails anyway, the reader needs a person. On ReaderMagnet that door is ARC support.

Do not send a folder of chapter files. Do not send a link to a cloud document that requires the reader to make an account. Do not send the book as a stack of images. Those choices feel convenient on your side and hostile on theirs.

How do you structure the inside of the file?

Think of the EPUB as a sequence of chapters the device already knows how to navigate.

Start with a cover image that is an image of the cover, sized as a normal ebook cover rather than a poster. A cover that is tiny, or enormous, or a screenshot of your desktop, is a quality problem before the first sentence. Then a title page: title, author name, and the words "Advance reader copy" if you want the reader to remember the file is early. Then the story.

Use real chapter breaks. Each chapter should start in a way the reading system can list. If your tool has a style called Heading 1, use it for chapter titles and for nothing else. If you paint the chapter title by making the body text large and bold, many exporters will not build a table of contents, and the reader is stuck scrolling.

The table of contents should list chapters, not every scene break. A contents list of two hundred "scene" entries is not more professional. It is a maze. Front matter can be in the contents if it is long enough to need finding. The copyright page does not need to be the first place the file lands when the reader opens it. Set the start to the first page of the story, or to a title page, and then check that the device obeyed you.

Scene breaks inside a chapter should be a visible mark: a blank line with a simple ornament, or a centered asterisk. A string of empty paragraphs will collapse on some devices and the scenes will run together. That reads as a mistake even when the prose is fine.

Italics should be italics, not a different font you applied by hand. Tabs and manual spaces for indentation will not survive. Let the ebook style indent the first line, or do not indent and use space between paragraphs. Pick one. Mixed systems look like a paste from three different drafts, because they are.

Images, if you have any, need alt text when they carry meaning, and they need to be compressed enough that the file is not a brick. A novel does not need a full-bleed photograph between chapters. A cookbook might. Know which book you are formatting.

What should you remove before you export?

Remove the drafting furniture.

  • Comments and tracked changes. Accept them or reject them. An export that preserves your argument with yourself is not an ARC.
  • Highlighting you used as a reminder.
  • Running headers from the print layout, page numbers, and "Chapter 1" repeated in the header. Reflowable books do not have stable pages. A header that says the old chapter while the reader is in the new one is worse than no header.
  • Hyperlinks to your private notes, your source spreadsheet, or a localhost address.
  • Dummy sentences left over from a template, and the line "end of sample" in the middle of a chapter.
  • Another author's worksheet you copied as a template, still full of their characters' names.

Run a search for the drafting marks that have embarrassed authors before: a note-to-self abbreviation, a row of Xs, your editor's first name if it only appears in notes, and the title of the previous book if you reused the file. Search is cheaper than a reader's screenshot.

If the book quotes song lyrics, private emails, or a long passage from someone else, make sure you have the right to put that in a file you are distributing. An ARC still circulates. "It was only the review copy" is not a license.

How do you export without creating a new problem?

Use one tool for the export and learn its two buttons: the style that becomes a chapter, and the command that writes the EPUB. Switching tools the night before a send is how a clean draft becomes a file with no chapters.

After export, do not trust the exporter's green checkmark. Open the EPUB in a reading app on your phone, and open it in at least one other environment if you can. Read:

  • The first page the device shows. If it is the copyright page or a blank cover, fix the start.
  • A chapter jump from the table of contents, including the last chapter.
  • A page with italics, a scene break, and any special character you use, such as an em dash or an accented name.
  • The file size. If a novel is inexplicably huge, an image is probably uncompressed.

Change the type size while you read. If the chapter title overflows or the scene break disappears when the type is large, the styling is brittle. Readers with low vision will hit that setting on purpose. A file that only works at your preferred size is not finished.

If you have a PDF as well, build it separately. Do not print the EPUB to PDF and hope. And do not flatten the EPUB into a PDF and call it both.

The campaign mail should link the file you just tested, not the previous export still sitting in the downloads folder. That mistake is so common it deserves a line in the checklist. The mail around the file is in ARC email sequences that don't nag.

What do you do when a reader says the file is broken?

Ask for the device and what they see, in one question. "Blank after the cover on a Kindle" is a different fault from "the ZIP downloaded and I don't know what an EPUB is." The second person may need the store's own app, or a different format if you offered one. The first person may be hitting a broken stylesheet.

Do not send five attachments in one reply. Send one replacement, named with the title and the date, so everyone can tell which file is current. If you replace the file on a private page, say so. A silent swap is fine only if the old file was unreadable. If you changed the ending, tell the people who already downloaded it. They cannot review a book you quietly rewrote.

Keep a short reply you can paste:

"Sorry the file failed. Tell me the device and whether you chose EPUB or PDF. I'll send one replacement. You don't need to do anything else, and you don't owe a review."

That last clause matters. A broken file plus a review nag is how a one-star review gets written before the story starts. The promise you want in public is the honest review policy.

If several readers hit the same fault, stop new sends until you re-export. Hoping the next person has a more forgiving app is how the ticket pile grows. How to run an ARC campaign assumes the file is the book. When it is not, the campaign waits.

What is worth paying someone else to do?

Pay a formatter when the book has illustrations, footnotes, poems, or a structure your tool keeps flattening, or when you have already lost a day and the file still has no table of contents. Pay for a single clean EPUB, and ask them what they need from you: a styled manuscript, not a PDF of a paperback, unless they specifically want the PDF as a guide.

Do not pay for a file you cannot open yourself. The handoff includes you reading the first chapter on a phone. A formatter cannot see that you uploaded the wrong draft. You can.

Do not pay for "conversion" that is a free export you were avoiding because the menu was unfamiliar. If the book is a straightforward novel, an afternoon with one tool is enough. The afternoon is part of publishing. It is less painful than forty emails titled "it won't open."

A checklist you can run the day you upload

  1. Comments off, drafting marks searched, correct draft.
  2. Chapter titles in a real heading style.
  3. Table of contents lists chapters and opens.
  4. Cover looks like the cover. The story starts where you think it starts.
  5. Italics and scene breaks survive a larger type size.
  6. You read ten pages on a phone, including a jump to the last chapter.
  7. The filename includes the title and the date.
  8. The landing page names the format.
  9. You know where a broken-file reply goes.

Then upload that file and stop tinkering. A new export every night means nobody, including you, knows which version a review describes. Freeze the ARC. Fix true errors. Save the stylistic restlessness for the next edition, and tell readers if the file they hold has actually changed.

If you want the private page and the file in one place, list your book. Bring the EPUB you already opened on a phone. The page cannot repair a file you have not read.

How do series files and accessibility survive the export?

If the ARC is book two, the file should not assume the reading system will explain the series. Put "Book two of the North Ferry mysteries" on the title page in text, not only on the cover image. Cover text is invisible to a reader using a screen reader, and it is easy to miss inside a sample. A one-sentence note that the book spoils the previous volume belongs in the front, before chapter one, so a mistaken claim can back out before they are invested. That note should match the landing page. When the file and the page disagree, the reader trusts the file and then blames you.

Accessibility is not a separate deluxe edition. Real headings, a table of contents, and text rather than pictures of text are the accessible version. If a character name uses a special character, confirm it did not turn into a box on the phone. If you marked emphasis with a color, add italics or bold as well. Color alone disappears in a device set to a night theme, and it disappears for readers who do not see that color the way you do.

Series box sets should be separate exports, not three novels pasted into one file with no breaks. A reader who wants chapter one of book two cannot be asked to scrub through book one again. Give each novel its own contents entry. Then open that entry on the phone and see where it lands. If it lands on a blank page, the export added a section you did not notice. Delete the blank. The reader should never have to pass through your formatting debris to reach the story.