Saving and publishing.

In Glopzi, save and publish are the same action for paid plans. Click Save and your changes go live on the CDN within seconds. There’s no separate “publish” step.

On a trial license, save stores your configuration on our servers but does not push to the CDN. Animations on your site stay at whatever was last published (or nothing, if this is your first save). When you upgrade, we recompile and push automatically. See How trial saves are different below.

The Save button visually reflects whether you have unsaved changes:

• Greyed out: nothing to save. The configuration on disk matches what’s in the editor.
• Lime, active: unsaved changes exist. Click to push them.
• Loading state: showing “Saving” with a small spinner while the bundle compiles and uploads.
• Confirmation: showing “Saved” briefly after success, then returning to greyed out.

Closing the browser tab with unsaved changes triggers the browser’s own “Are you sure you want to leave?” warning. Same for clicking Exit in the toolbar.

The full save flow, in order:

• Validation. The editor sends your current configuration to our server. We verify the structure and check your license status.
• Storage. The configuration is written to our database, tied to your site. Past versions are kept in case you need to roll back through support.
• Compile. A small JavaScript bundle is built from your configuration. Only animations and effects you actually use end up in it. We also generate a small CSS file that prevents flicker on first paint.
• Sign and upload. The bundle is signed and pushed to our CDN under your unique key. Existing CDN cache for your site is invalidated.
• Done. The next request to your site picks up the new bundle. Most visitors see the change within a few seconds.

On WordPress, an additional step copies the bundle to your server’s local storage so visitors get it from your own domain even if our CDN is briefly unreachable. This happens transparently and adds no extra wait.

Glopzi treats published work and the ability to ship new work as two separate things. This is the save-gate model, and it has a few concrete consequences:

• If your subscription expires, animations you already published keep running for visitors. We never silently revoke work you paid for.
• You won’t be able to save new changes while your subscription is inactive. The Save button shows a notice and links to the dashboard to reactivate.
• A small “Animated by Glopzi” badge may appear on the page to indicate the site is running on a lapsed subscription. Reactivating removes it on the next save.
• Cancelling a subscriptiondoesn’t immediately disable saves. You retain edit access through the end of your billing period.

A trial license gives you the full editor at zero cost. Saves are kept on our server but don’t reach the CDN and don’t affect your visitors. The Save button shows “Saved (trial)” instead of just “Saved” to make this obvious.

When you activate a paid plan, all of your trial saves are recompiled and pushed automatically. The work you did during the trial doesn’t need to be redone.

For more on trial behavior, see Plans, billing, and trial.

• Save button stays in “Saving” for more than 30 seconds. Something is wrong with the connection. Check your network, then try again. If the problem persists, the error is on our end and our status page (linked in the dashboard) will reflect it.
• Save succeeds but the live site doesn’t update. Hard refresh the live page (Ctrl+Shift+R / Cmd+Shift+R). Your browser may be holding the previous bundle.
• Save fails with a license error. Open the License keys page for activation troubleshooting.
• Save fails with a domain error.The site you’re editing isn’t in your bound domains. See Adding and managing domains.

• Plans, billing, and trial: how the trial converts and what the paid plans include.
• License keys: activation, multiple sites, and what happens when keys change.
• Canvas and live preview: the difference between Preview and Save.