Autosave and Save
Atomicat saves Page Builder work through manual save and autosave.
Manual save is the action you trigger from the builder header. Autosave runs in the background for eligible edited pages when the page content has changed.
Manual save​
Use Save in the builder header when you want to commit the current page changes.
Manual save is recommended:
- Before leaving the builder.
- Before publishing.
- After major layout changes.
- After adding or removing forms.
- After editing custom code, pixels, or SEO settings.
- Before testing the page externally.
Autosave​
Autosave checks for modified content while you work and saves eligible page changes in the background.
Autosave is designed as a safety layer, not a replacement for manual save. If you are making important changes, click Save before leaving the page or publishing.
Last edited status​
The builder header can show a saved time based on the page creation or last edited timestamp.
Use this timestamp as a quick confirmation that Atomicat registered a recent save. If you do not see the expected update after a major change, click Save manually.
What Atomicat validates on save​
When a page is saved, Atomicat prepares and validates the page data before storing it.
| Save area | What Atomicat checks |
|---|---|
| Sections | Cleans and serializes the page section structure. |
| Forms | Validates form elements and saves form field configuration. |
| Quizzes | Processes quiz structure when the page is a quiz. |
| Accordions | Ensures accordion items have the required container structure. |
| Custom code | Checks custom code fields for suspicious or malformed script behavior. |
| Elements and media | Stores information about elements and media used on the page. |
| Builder sync | Updates builder sync metadata and revision information. |
Form save behavior​
If a page contains forms, Atomicat validates and saves form configuration during save.
This includes field items and related form settings such as reCAPTCHA, autoresponder, and webhooks when configured.
If form validation fails, the builder may prevent the save and show an error so the form can be fixed before publishing.
Custom code safety​
Atomicat checks custom code fields before saving. If suspicious redirect-injection behavior or malformed tags are detected, the save can be blocked.
Review custom code carefully before saving:
- Header code
- Body code
- Footer code
- Tracking snippets
- Third-party scripts
Save troubleshooting​
If saving fails:
- Check whether a form field or form integration is incomplete.
- Review custom code for malformed
<script>,<style>, or<noscript>tags. - Remove suspicious redirects or unsupported scripts.
- Save again after fixing the issue.
- Contact support if the page still cannot save.
Best practices​
- Save manually after completing each major page section.
- Save before opening preview links in another tab.
- Save before publishing changes to a live page.
- Avoid editing the same page in multiple browser tabs at the same time.
- Validate forms before launching traffic to the page.
Related docs​
FAQ​
When should I use this Autosave and Save page?
Use this page when you need to understand the workflow, settings, or decisions related to Autosave and Save. It is most helpful before editing a live asset, publishing changes, or troubleshooting behavior in an Atomicat workspace.
What should I check before changing Autosave and Save?
Confirm that you are in the correct workspace, project, page, funnel, site, or account area. Review access permissions, saved changes, publishing status, and any connected integrations before making updates.
How do I verify that Autosave and Save is working correctly?
Preview the affected page or feature, test the main user path in a fresh browser session, and confirm that forms, redirects, tracking, products, quizzes, or publishing states behave as expected.
What should I do if Autosave and Save does not work as expected?
Recheck the configuration described on this page, save the changes again, clear browser cache if needed, and test with a simple version of the setup. If the issue continues, collect the page URL, workspace details, and screenshots before contacting support.