How to Use Auto-Save in the Sparkforge Blog Post Editor
Auto-Save in the Sparkforge Blog Post Editor saves your edits in near real time so a browser crash or accidental tab close won't cost you work. Toggle it on or off from the top action bar; the preference is stored per browser.
Auto-Save in the Sparkforge Blog Post Editor saves your draft as you write. It runs with a small delay so performance stays smooth, and the toggle lives right in the top action bar.
What Auto-Save does
Auto-Save writes your edits to the server in the background while you work. If your browser crashes or a tab closes, your latest changes survive. The status indicator in the top action bar shows the current state.
- Reduces the risk of losing content during editing.
- Cuts the need for manual saves.
- Shows live status with a visible indicator.
- Can be turned on or off per browser.
Turn Auto-Save on or off
- Open the Blog Post Editor from your dashboard.
- Find the Autosave Toggle in the top action bar.
- By default, Auto-Save is enabled; the tag reads Autosave on.
- Hover the Autosave on tag and click Disable Autosave to turn it off.
- When disabled, the tag becomes Last saved with a timestamp (for example, "Last saved May 22, 6:30 PM").
- Hover the Last saved tag and click Enable Autosave to turn it back on.
Where the preference is stored
Auto-Save preference is browser-specific. It is saved in your browser's local storage under the key blog-editor-autosave-enabled.
- The setting does not sync across devices or browsers.
- If Auto-Save is off and no last-saved data exists, the tag shows Autosave off.
- Clearing your browser storage resets the preference to default.
Frequently Asked Questions
What happens if my browser crashes with Auto-Save on?
Does Auto-Save sync across devices?
Can I still save manually?
Does Auto-Save slow down the editor?
Was this article helpful?
Thanks for the feedback.