Reviewing & publishing changes

Studio saves your edits as you work, but nothing leaves the editor until you publish. Publishing from Studio is the first of three steps. The full path is Studio Publish → dashboard Create Preview → dashboard Publish. See Publishing your site.

Before you publish: where your edits live

Edits you haven't published yet are saved in your current browser, so:

You can close the tab and come back later, in the same browser, and your edits are still there.
Teammates don't see your unpublished edits, and you won't see them on another computer or in another browser.
Clearing your browser data, or using a private window, discards unpublished edits.

Publish from Studio at the end of each working session, even if you're not ready to go live. Your changes are then saved to your site, your teammates can see them, and they still won't reach visitors until you publish from the dashboard.

Review your changes

Click Review at the top of Studio. Review changes lists every file you've touched, grouped as:

Created: new pages, forms, or embeds.
Updated: edited files.
Renamed: renamed files.
Deleted: removed files.

Click See what's changed on a file to compare it with the published version. Click Back to edition to return to editing.

Publish

Describe your changes

Enter a short description, such as "Update pricing and add FAQ". It's required. It also helps your team understand the history of the site later.

Click Publish

Studio shows Changes Published, with a count of the changes. It also mentions a branch and a repository. That's how your site's history is stored, and you don't need to do anything with it.

Wait for the update

Studio shows Waiting for deployment... while the editing version of your site rebuilds. This usually takes a minute or two.

Reload

When it shows Deployment complete, click Reload (or refresh the page) to keep editing on the updated site.

Then go to the dashboard to create a preview and publish.

If a teammate publishes while you have Studio open, you'll see New website version detected. Click Reload to load their changes before you continue.

Undo changes

To undo…	Do this
Your last few edits while typing	`Ctrl+Z` (`Cmd+Z` on Mac).
Every unpublished change to one file	Open the file's actions menu and choose Revert changes. The file goes back to its last published version.
Something you've already published from Studio	Edit it back and publish again. If you haven't clicked Publish in the dashboard yet, your live site still shows the previous version, so nothing visitors see has changed.

If publishing fails

If you see Publish Failed, your edits are still in your browser and nothing is lost. Click Retry Publish. If it fails again, contact support and include the error message Studio shows.

Conflict Detected

Conflict Detected means the published version of a file is different from the one your editor loaded, usually because the site was updated since you opened Studio.

Wait a minute or two in case an update is still finishing, then refresh the page.
If the conflict is still there, open the file's actions menu, choose Duplicate, and make your changes in the copy. Then delete the original and rename the copy to the original name, so the page keeps its address.
If you're unsure, or it's your home page (index), contact support before deleting anything.

Styling & advanced options

Change backgrounds, text sizes, spacing, and colors for one page, one block, or one piece of text.

Recipes

Step-by-step instructions for common tasks in Studio, plus a checklist before you launch.