Cloud sync

Before you start

• A Swebsy account, signed in, with a verified email

Cloud sync stores a copy of a project on Swebsy’s servers and keeps it in step as you work. It gives you an off-device backup, the same site on more than one machine, and it is the prerequisite for version history and Swebsy Hosting.

New sites you make while signed in back up on their own once your email is verified. A site made while signed out stays entirely local until you save it to the cloud. Local editing never depends on the network.

Cloud sync is on every plan, including Free, which includes 100 MB of cloud storage. Version history — the snapshots and restore points — is paid. See Plans & billing.

Save a site to the cloud

1. Open the site in the Studio.
2. Click Save to Cloud in the topbar.

Save to Cloud sits in the topbar until the site is linked.

Expected result

A confirmation reads “Saved to cloud — this site now syncs automatically”, and the button is replaced by a small cloud status icon.

That first save uploads the project and every image and file it uses. Later syncs only send what changed.

How automatic syncing behaves

Once a site is cloud-linked, Swebsy pushes changes in the background about 30 seconds after you stop editing. There is no Save button to remember.

Hover the status icon for the current state and the time of the last sync:

Status	Meaning
Saved to cloud	The cloud copy matches this device
Syncing…	An upload is in progress
Sync failed — will retry	A push did not go through; the next idle save tries again
Newer in cloud	Another browser or device saved — see below

Click the icon for a menu with Sync now (push immediately) and Version history….

Once linked, the button becomes a status icon with the sync menu behind it.

A failed sync never costs you work

Your project is saved locally first, every time. Sync failures affect only the cloud copy, and clear themselves on the next successful push.

Working on a second device

Sign in on the other machine and open the Swebsy home page. Cloud projects that aren’t on that device appear under In your cloud with a Load onto this device button.

Swebsy syncs between devices, it does not merge

Editing the same site on two devices at once does not combine the two sets of changes. Finish on one device and let it sync before you start on the other.

When the cloud has a newer version

The site always opens with this browser’s version, and nothing covers the editor. If the cloud holds a newer version saved from another browser or device, the status button turns into an amber label — Newer in cloud, or Both changed when this browser has edits too — and its menu opens once to say what changed on each side.

Your edits keep saving in this browser. They don’t back up to the cloud until you choose:

• Open the cloud version — this browser switches to the cloud version. If this browser had changes, its version is saved as a copy first.
• Keep this browser’s version — the cloud version is saved as a copy, then this browser’s version backs up as the latest.

A copy is a site of its own in My Sites, named like “Portfolio (cloud version, Oct 25)”, and backed up to your cloud straight away, so the version you didn’t pick is never only in one browser. It isn’t published. Delete it from My Sites when you no longer need it. If your cloud storage is full or your plan no longer includes backup, the copy is kept in this browser only, and Swebsy says so.

If the newer cloud version is one this browser saved itself (an answer that never came back), Swebsy recognises it and carries on without asking.

Images and files

Assets upload alongside the project and are stored by content, so the same image used on ten pages — or re-uploaded after a re-import — is stored once and counted once against your storage.

A single file may be up to 95 MB (SVG files up to 2 MB). A bigger file stays in your site in this browser and is named as not backed up; the rest of the site still backs up. The project itself (the pages, styles, and settings, without assets) may be up to 5 MB, which is a very large site in practice.

Deleting a site

Deleting a site from My Sites removes the copy in this browser. The cloud copy is kept.

A deleted site reappears under “In your cloud”

Because the cloud copy survives, the site shows up again in the In your cloud list with a Load onto this device button, and it keeps counting toward your storage. There is currently no in-app way to delete a cloud project — contact support if you need one removed.

That is worth knowing before you delete a site to free up storage: it will not free any. To reduce storage, remove unused images from projects you keep. Unpublishing a hosted site takes it offline but retains its deployments, so it does not immediately reduce storage either.

Common issues

“Save to Cloud” asks you to sign in — you are signed out. Sign in or create a free account; the save carries on once your account can back up.

“Verify your email to continue” — cloud sync needs a verified email address, on every plan. Check your inbox for the verification link.

Storage limit reached on the Free plan — Free includes 100 MB of cloud storage. Remove unused images, or upgrade for more. See Plans & billing.

Sync stopped after a storage warning — automatic retries stop once storage is full, to avoid a loop. Free up space or upgrade, then click Sync now.

The status icon shows an error but the site is fine — that is expected and harmless; your local save succeeded. It clears on the next successful sync.

A site is on this device but not under “In your cloud” — it was never saved to the cloud. Open it and click Save to Cloud.