# Build and download

> Free proofs, counted finals, how long a build takes, and where your files are.

Steps 5 and 6 on your Factory page. One build makes both files: the
**EPUB** and the **print PDF** of the interior at your trim size.

## Proof or final

| | Proof | Final |
|---|---|---|
| Button | **Build proof — free** | **Export final — uses 1 of 3** |
| Cost | Free | Uses one of the finals on your pass |
| Print PDF | A small "PROOF" line at the foot of every page | Clean: the one you send your printer |
| EPUB | Identical either way | Identical either way |
| Limit | 30 per project in any 24 hours | 3 on a pass; more can be added |

Build proofs as often as you like while you revise. Read the **EPUB first**,
since it shows the text and structure fastest. Then read the PDF for pages and
breaks. Export a **final** when you're done; the page asks you to confirm
first.

A final that **fails isn't counted**. The final is refunded automatically. A
final that builds with a warning is counted, because the files are ready.

## How long

Usually a minute or two, longer if other books are building at the same
time. You can leave the page open. One build runs at a time per book.

## Downloads

Step 6 keeps your builds:

- **Final files:** the print PDF and EPUB. Save copies somewhere of your
  own.
- **Latest proof:** the most recent proof PDF and EPUB.
- **Earlier builds:** older builds, with their date and size. Every final is
  kept. Of the proofs, the factory keeps your latest five, your first one,
  and the last one of each day you built.

Downloads keep working for 30 days after your pass ends. See
[Your Factory Pass](factory-pass.md).

## If a build fails

The page says what went wrong in plain words. Most messages say whose
problem it is:

- **The problem is on our side.** The message says so: the build was
  interrupted, or the problem is in our typesetting setup and there's
  nothing to change in your manuscript. Run it again, or email us the
  message and we'll fix it and build it again for you.
- **The problem is in one paragraph of your text.** The message quotes the
  text **near** it (*Near: "…"*). Search your manuscript for those words and
  look in that paragraph for anything unusual, such as a stray `[[marker]]`,
  an @ sign or a pasted symbol.
- **The typesetter couldn't say where.** Email us the message. If you
  changed a paragraph just before the build, check that one first.

Other messages you might see:

- **A style that isn't in your template.** Remove it or change it to a
  factory style, or ask us to add it. [Inspect](inspect.md) lists these as
  custom styles not in your transmittal.
- **A chapter or section start inside a styled block** (a quotation,
  epigraph or signature that runs right up to the next heading). This is our
  bug; email us. Meanwhile, an empty paragraph before the heading works
  around it.
- **An image that couldn't be read.** Insert it again in your editor from
  the image file (not a linked or pasted preview), export the `.docx` and
  build again.
- **An unreadable file.** Export it again from your editor as a `.docx`.

**Technical detail** under the message is for the studio; include it if you
write to us.

Stuck? Write to [j@djinna.com](mailto:j@djinna.com) with the message the
page showed.

---
Source: https://studio.jdbb.net/help/build-and-download