Studio
Preview and deployment answer two different questions. Preview: “does this work?” Deployment: “is this live for the world?” Here's how each one works — and how to recover when either misbehaves.
The key distinction
Preview is your private working copy — iterate freely, nothing is public. Deployment is the deliberate step that publishes the project. You can preview a hundred times; you deploy when you decide it's ready.The Preview tab runs your active project in a live runtime so you can click through it exactly as a visitor would. Studio mounts exactly one preview per active project — you'll never have two competing copies of the same project running.
The preview panel always tells you what's happening. Here's what each state means and what to do:
The retry button is in the preview panel itself, next to the status. Retrying is safe and idempotent — it won't duplicate your project or lose files. If retries keep failing, work through Troubleshooting.
When the preview looks right, the Deploy action in the Studio header prepares your project to go live. Deployment is separate from preview on purpose: it's the moment you decide the world should see the project.
From the terminal, litt deploy verify watches a deployment and verifies production health, and litt production finish runs the remaining production gates before a release. See Installation & Commands.
The shipping checklist
Before you deploy: preview on desktop and mobile widths, click every button and form, and read through the activity timeline once. Five minutes of checking beats an embarrassing rollback.