Edit a live site

1. 1Open the site and choose Visual Edit. Your live page opens in the editor.
2. 2Hover to highlight an element and click to select it; the style panel shows everything you can change. Double-click text to edit it where it is.
3. 3Undo and redo with the buttons in the header, or Ctrl+Z and Ctrl+Y.
4. 4Click Save. The change is written into the site's own HTML and is live at once.

You can change text, font size and weight, colours, bold, italic and underline, alignment, padding and margin, borders and corner radius, width and height, and opacity. On a multi-page site, switch pages with the page menu in the header.

What it doesn't do

• Edits made in the desktop view apply to every screen size. Switch to the tablet or phone preview first and the edit applies to that size only, so a phone fix never moves your desktop layout.
• It edits what is on the page but can't add or delete elements — use Code Edit for that.
• Content created by your scripts is shown but can't be edited here; the panel tells you where it comes from, such as a Data collection.
• Your edits are saved as CSS rules that win over the original ones. Untouched properties, including your own breakpoints, keep working, but a hover effect on an edited property may stop showing.

On Pro, choose Code Edit to open the site's files: the file tree on the left, the editor on the right. HTML, CSS, JavaScript, JSON, Markdown and text files open with syntax highlighting. Add, rename or delete files, and upload or replace images and other assets from the same tree.

Saving writes straight to the live site at the same address — no build and no redeploy. The first save of a session asks whether to keep a backup; yes keeps one version in Versions.

1. 1Open the site and choose Replace files under Deploy (Replace file on a single-page site).
2. 2Drop the new version. A single-page site takes one HTML file. A multi-file site takes a ZIP or a folder with index.html at the top, and every current file is replaced.
3. 3The new files go through the same checks as a new deploy — plan limits and the security scan — then the site updates at the same address.

The address, password, custom domain, forms, bookings, data, chatbot, Google Analytics and analytics history all stay as they are. A site keeps its kind: a single-page site can't take a ZIP, and a multi-file site can't take a single HTML file. Owners and editors can replace files.

Every update — Replace files, a GitHub push, a Site Builder publish, an API deploy or a save in either editor — keeps the version it replaces. Plus keeps 1 per site and Pro keeps 3 per site; Free keeps none.

1. 1Open the site and choose Versions under Deploy. Each version says where it came from and which files it edited, added or removed. Add a note when the reason matters.
2. 2Click Restore, read what will change on the live site, and confirm. The version you replace is kept too, and the message that confirms it has Undo.
3. 3Click Keep on a version and it is never rotated out, whatever you deploy next — one per site, and the pin can be moved.

• A restore replaces files only: the site goes back to exactly the files in that version, and files added since are removed. Password, custom domain, forms, bookings, chatbot and analytics stay as they are.
• Every restore is scanned again before it goes live.
• Saves in the editors, and edits through the API, made by the same person within 10 minutes count as one version, so a busy editing session doesn't push out older versions.
• Versions don't count toward your storage.
• After a downgrade to Free, existing versions stay listed but can't be restored.