Deliver every format, named and ready for the printer
The Deliver tab renders every format at full size in the file types you tick, names each file by client, job, format and version, adds print PDFs with bleed and crop marks, and zips it all with a delivery note.
Intermediate4 min readUpdated 25 September 2026Studio · Deliver
On this page
Delivery is where small mistakes cost the most: a file called final_final2.png, a poster without bleed, a missing size. The Deliver tab builds the whole handover in one go, from the same design you reviewed, so every file is there, full size and properly named.
Before you deliver
Delivery works from the key visual design and its format boards. A format with no board is greyed out with Not built yet; build it on the Key visual tab first (see Start a job from the client's brief). The top of the panel shows how many formats are ready, for example 3 of 4 formats ready.
Choose file types for each format
Each ready format has four boxes: PNG, JPG, WebP and Print PDF. Studio ticks sensible ones for you:
| Format group | Ticked by default | Why |
|---|---|---|
| Social, Screen, Custom | PNG and JPG | PNG for sharp text and flat colour; JPG as the small file most platforms and chat apps prefer |
| Print and Outdoor | Print PDF and JPG | The PDF for the printer; the JPG for proofing on a phone or posting online |
WebP is smaller than PNG or JPG at the same look and suits websites. Tick it for a website hero or email header when the client's developer asks for it.
Build the package
- Check the file list under What goes in the zip.
- If the job has a brand, decide on Include … brand sheet.
- Press Build the package. Studio renders each format in turn and shows its progress.
- Save the zip. The job is marked Delivered, every format in the package is ticked done, and the delivery is listed under Delivered before with its date and file count.
Send as a link builds the same files and gives you a link instead of a zip. The client downloads each file, or everything as a zip, from their browser. See Review and delivery links.
How files are named
Every file follows client_job_format_version, lower case, with spaces turned into hyphens. For a client called Lekki Nights, a job called Launch, and the second version:
lekki-nights_launch_instagram-post_v2.pnglekki-nights_launch_a3-poster_v2.pdflekki-nights_launch_v2_delivery.zipfor the zip itself
The version number is the number of versions saved on the Review tab (v1 if there are none). So if you saved v3 for review and the client approved it, the delivered files say v3 too, and everyone is talking about the same thing. Rename a format on the Brief tab if you want a different name in the file.
What the print PDF contains
- The artwork at its trim size in mm, as set by the format (A4, A5, A3, the 18 × 24 in poster, the business card, the roll-up banner).
- 3 mm bleed on every side, made by extending the edge pixels outwards, so background colour runs past the cut.
- Crop marks outside the bleed.
- TrimBox and BleedBox set, so the printer's software finds the cut line on its own.
- A slug line under the artwork with the client, job, format, version, trim size, bleed, and a reminder that the colour is RGB.
Outdoor formats (billboards, the lamp-post banner) have no set size in mm. Their PDF takes its size from the pixels at 300 dpi, so check the real size and the file they want with the printer or sign maker before you send it.
The delivery note and brand sheet
Every package includes a delivery note, a small web page the client can open in any browser. It lists every file with its size, every format with its pixel size (and mm for print), which versions were approved, the fonts used in the design (so whoever edits it next installs them first), and print notes.
When the job has a brand and Include … brand sheet is ticked, the zip also carries a brand sheet page: each colour with its role, hex, RGB and an approximate CMYK starting point, the headline and text fonts, the logo's minimum size and clear space, and the voice, do and don't lists. See Save client brands and reuse them.
Common problems
- Nothing to deliver yet. The job has no key visual design on this device. Design it on the Key visual tab first.
- Could not build the package. Try fewer formats at once. Very large formats use a lot of memory. Untick file types or formats, build, then build again for the rest.
- Fonts look wrong in the files. Studio waits for the design's fonts before rendering. If a font never loaded (you were offline, or it was a local font that is not on this device), open the design in the Editor and fix the missing font first.