Export

Every project workspace has an Export menu in the toolbar. The options you’ll see depend on the project’s kind — design-only formats hide on code-shaped projects, and PowerPoint variants only appear on slide decks.

The seven formats

Format	What you get	Available on
Project ZIP	The full workspace in a single archive	Every kind
Standalone HTML	One self-contained `.html` with everything inlined	Designs, slide decks
PDF	The preview printed to a PDF	Designs, slide decks
PowerPoint (screenshots)	One image per slide, full-bleed	Slide decks only
PowerPoint (editable)	Native shapes + text + images	Slide decks only
Claude Code handoff	Workspace ZIP + a CLAUDE.md describing what’s inside	Designs, slide decks
Figma	A new Figma file with your design captured into it	Designs, slide decks (coming soon)

Code-shaped projects

Apps and Component libraries only export to ZIP. The other formats don’t fit code — there’s no slide to capture, no design to hand off as design, no Figma-shaped output.

For Apps and Libraries, ZIP is the source archive. Clone it, build it, ship it. Internal Atelier bookkeeping (the .atelier/ folder, your AGENTS.md) is filtered out.

Project ZIP

The full workspace as a single archive. A manifest file lands at the root with the project name, type, included paths, and an exported-at timestamp.

The default filename is the project’s slug plus the format extension — recipe-app-design.zip.

Standalone HTML

A single .html file with everything inlined: CSS, JavaScript, images as base64, fonts as @font-face declarations. Works offline.

Use this for a portfolio share or a quick deliverable. Above a few megabytes the file gets unwieldy; below that, this is the most frictionless way to share.

Builds from the file currently open in the preview if it’s HTML; otherwise from the project’s index.html.

PDF

The preview printed to PDF. Searchable text where possible, rasterized where CSS demands it. Hyperlinks survive.

Page setup follows the preview’s viewport — designs in landscape A4 (or letter depending on locale), slide decks at 16:9 per page.

Slides-specific formats

Slide decks get two PowerPoint variants. See Slide deck → Export.

Screenshots

Each slide captured as an image and embedded full-bleed. Pixel-perfect — your audience sees what the preview renders. Text isn’t selectable inside PowerPoint; fonts don’t matter because they’re rendered before export.

Editable

Studio walks the rendered slides and produces native PowerPoint shapes — text, fills, images. Your reviewer can fix a typo in PowerPoint without re-rendering. Some advanced CSS effects (complex gradients, masking, web fonts) degrade.

Speaker notes attach as native PowerPoint notes in both modes.

Claude Code handoff

The Claude Code handoff is a ZIP with a CLAUDE.md at the root. The CLAUDE.md tells the receiving Claude Code session:

The project name and kind.
The original prompt (what you asked for).
An optional build prompt (notes for the receiving agent).
A listing of the files in the bundle.
How to pick the work up.

A typical CLAUDE.md the export produces:

# Recipe app design
 
This bundle was produced by Atelier as a handoff to Claude Code. The user
finished a design exploration as a `hi_fi_design` project and is now passing
the artifacts here for production implementation.
 
## What the user asked for
 
A recipe app for indie cooks. Search by ingredient, save favorites,
collaborative grocery lists.
 
## Build instructions
 
Use Next.js 16 + Postgres. Auth via OIDC backend-for-frontend.
 
## Files in this bundle
 
- index.html
- styles.css
- scraps/sketch-1.napkin
- …
 
## How to pick this up
 
- Read the artifacts in this bundle to learn the visual + interaction direction…

The handoff is the inverse of the From Claude Code bridge — Studio → Claude Code instead of Claude Code → Studio.

Figma

Capture the design into a new Figma file. The result is a Figma URL, not a downloadable file — the browser opens to the generated frame.

This option is coming soon. The menu item shows “coming soon” until it’s available.

What’s hidden from exports

A handful of paths never make it into any export — host bookkeeping that isn’t part of your artifact:

The .atelier/ folder.
Your AGENTS.md (private to the project’s chat).

If you need any of these, copy them out of the workspace first and they’ll travel like any other file.

Status while exporting

The Export button shows what’s happening:

Preparing — reading files, building the manifest.
Capturing — (PowerPoint only) walking slides.
Saving — writing bytes to disk.
Done — saved successfully.
Error — surface the message; reverts after a couple of seconds.