Redeploy, roll back and unpublish

Publishing changes#

Edits to your screens are not live automatically. When you're ready, publish again — a new deployment is built and swapped in when it's ready. Visitors keep seeing the old build until the new one is complete, so there's no broken window mid-deploy.

Deployment history#

Every publish is kept as a deployment, with its own preview URL. This gives you two useful things: a record of what was live when, and a way to show a proposed build to someone without making it the live site.

Rolling back#

Pick an earlier deployment and roll back to it. The site returns to that exact build immediately — there's no rebuild, because the old build still exists.

Roll back first, debug second. It takes seconds and it stops the bleeding.

Unpublishing#

Unpublish takes the site offline but keeps the site record, its subdomain and its deployment history — so you can bring it back later on the same address.

Delete removes the site entirely and releases the subdomain for anyone to claim. That one is not reversible.

Site limits#

Unpublishing frees the slot the site was occupying against your plan's published-site limit. Deleting does too. See Plans and limits.