How-to

Save, publish and restore versions

Every edit you make stays in a draft until you save it. Publishing a save takes it live to your storefront. You can restore older versions at any time.

বাংলায়: ডিজাইনার এ যা করছেন তা সবসময় খসড়া থাকে। Save বাটনে ক্লিক করে সংরক্ষণ করুন। সংরক্ষিত কাজ এখনও দোকানে দেখা যায় না। Publish বাটনে ক্লিক করে লাইভ করুন — গ্রাহকরা সেই মুহূর্তে নতুন ডিজাইন দেখবেন। পুরোনো সংস্করণে ফিরতে থিম মেনু থেকে Version history খুলুন।

Where to find it: Designer › top bar Save and Publish buttons Who can do it: Anyone who can open the designer

The difference between Save and Publish

Save stores your changes but keeps them invisible to customers. You are editing a draft.

Publish makes your saved changes live. Everyone visiting your store sees the published version immediately.

You must save before you can publish.

Saving your work

Click the Save button in the top right. The button shows "Saving…" with a spinner while it works.

The save state badge (next to the theme name) shows:

Saved — no unsaved changes
Unsaved changes — you have edits that are not yet saved
Saving… — a save is in progress
Not saved — the save failed; the badge is red

Saving is fully manual — there is no autosave. If you close the designer tab without saving, your changes are lost.

Keyboard shortcut

Press Ctrl/Cmd+S to save.

Conflict resolution

If another person edits the same theme while you are working, you see an Edited elsewhere badge (amber, with a merge icon).

A full-width amber bar appears: "This store was edited somewhere else while you were working. Your changes no longer fit: <reason>."

Two buttons appear: Take theirs (use the server's version, discard your queue) and Keep mine (rebase your changes onto theirs). Save and Publish are blocked until you choose.

Offline

If your internet drops, the Offline badge (amber, cloud-off icon) appears. The Save button is disabled until you reconnect. Edits queued before the drop will send when you come back online.

Publishing your work

Click the Publish button in the top right (green, primary).
A dialog appears asking to confirm the publish with the message "becomes your live theme, and shoppers see it immediately."
A Page check runs automatically, showing "Checking the page…" inside the dialog.
If the check finds problems, they appear in the dialog under "The page check found <n> problems:" — up to 3 are listed, with a "+ N more" count. A line at the bottom says "You can still publish." Publishing is not blocked.
Click Publish or Cancel.

After publishing, the page reloads. If there were warnings, they appear in an amber line: "Published. <first warning>."

If the publish fails, a red error message appears left of the button. Try again.

What happens on publish

The theme you publish becomes the live theme. Your storefront immediately serves the new design to all visitors. The previous live theme (if any) moves into version history as a saved point.

You can restore an older version at any time — see "Restore a past version" below.

The Publish button is disabled when

You have unsaved changes (save first)
A publish is in progress ("Publishing…")
There is an unresolved conflict ("Resolve the conflict before publishing.")
Compile errors block publishing ("<n> errors must be fixed before publishing.")

Compile errors show red dots on nodes in the outline and as red messages under the fields in the right panel. Fix the error, and the block goes away.

Page check

Click the Check page button (top bar, checkmark icon) to run an audit at any time.

A popover opens showing findings grouped Fix before publishing / Worth fixing / Minor. Findings that name a section show as clickable buttons — click one to select that section and jump to the offending field.

The check runs automatically in the publish dialog (soft gate only — you can still publish even with findings).

Run the check again by clicking the Re-run button in the popover.

Common findings

Contrast — text colour is too close to the background
Missing alt text — images need descriptions for accessibility
Placeholder copy — sections still have "Lorem ipsum" or example text
Missing product — a section that should link to a product does not
Dead link — a link points to a product, page or collection that no longer exists
Too many sections — the page has more than recommended
CTA below the fold on mobile — a button is not visible on first scroll

Version history

Every time you publish, a snapshot is saved in version history. You can restore any past version.

Click the theme name in the top left to open the menu.
Click Version history.
A dialog opens showing every saved version in reverse order (newest first).

Each row shows:

Version number ("Version 1", "Version 2", etc.)
Status (draft, published, or archived)
Label (if you named it)
"Created <date> · published <date>" (if published)
A "never compiled" badge (rare — means the version has technical issues)

Save a version without publishing

Click the Name this save point input and type a name (up to 80 characters, e.g. "Before summer sale"). Click Save version…

A save point captures your current draft. Your draft stays unchanged — the save point is a copy. Success message: "Saved as version <n>. Your draft is unchanged."

Restore a past version

Click the Restore button next to a version. A confirmation appears:

"Your current draft will be replaced by version <n>. The live store is untouched until you publish."

(If the version never compiled, it adds: "This version never compiled, so you may not be able to publish it as-is.")

Click Restore into draft. Your draft is replaced immediately.

The live storefront does not change until you publish. You can try out the old version and undo (Ctrl/Cmd+Z) to go back to what you were working on.

Safety note from the dialog

"Restoring rewrites this theme's draft only — the live store keeps serving what you last published until you publish again. That makes restoring safe to try."

You cannot restore the row marked draft — that is the version you are currently editing.

Handling conflicts during save

If another person makes changes while you are editing, a conflict bar appears under the top bar:

"This store was edited somewhere else while you were working. Your changes no longer fit: <server message>."

Two options:

Take theirs — accept their version; your unsaved changes are lost
Keep mine — try to merge your changes onto theirs

Choose one to unblock Save and Publish. If you choose Keep mine and the merge fails, the conflict persists and you must choose again.

Questions people ask

Why does Save and Publish both exist?

Save stores your work safely without affecting the live store. Publish makes your changes visible to customers. Separating them lets you take your time editing without rushing customers to see an incomplete design.

Can I undo a publish?

No. Publishing is permanent — your changes go live immediately. However, you can restore an older version from Version history, which will replace the live theme and become the new draft.

What if I published by mistake?

Open Version history and restore the previous published version. This makes the old version live again. Undo (Ctrl/Cmd+Z) only works for unsaved edits in the current session.

Will customers see my draft?

No. Drafts are invisible until you publish. Customers always see the last published version.

What happens to old versions?

All versions stay in Version history forever. They are listed by publish date; the oldest ones are at the bottom. You can restore any of them at any time.

Other ways people ask this

save korbo designer
publish live korbo
version history dekh
restore older design
draft save
publish blocked error
page check problems
conflict bar resolve
offline designer save
design version restore
undo publish
save design changes
প্রকাশ করব কীভাবে
সংস্করণ ইতিহাস

The store designer — overview of the workspace
Add, arrange and edit sections and blocks — how to edit while you work

Related guides

Checked against the product on 2026-10-02.