---
title: "Saving, local copies, and app updates"
description: "Know which changes save automatically, how local browser copies help, and when to reload ImagineMate after a new release."
sidebar:
  order: 16
lastModified: 2026-11-01
---

## Automatic saving or a save button?

- **Chapter manuscript:** saves automatically; wait for **All changes saved** when possible.
- **Boards:** synchronize their document changes while connected.
- **Book synopsis, outline, title, and settings:** use their explicit save buttons.
- **Bible edits and other forms:** follow the save or add control shown by that form. Do not assume every input is saved on each keystroke.
- **Uploads:** wait for the upload to complete.

## Local copies

ImagineMate retains recently used chapter data and a copy of structured world data in your browser. These make repeated navigation faster and help during a temporary connection loss.

Local copies are specific to your browser profile and account. Clearing site data, using another device, or using a private browsing window can remove or bypass them. They are not a substitute for server-confirmed saving.

## Offline limits

An already available chapter can retain edits and reconcile them when the connection returns, as long as it still belongs to the same revision. A chapter that has never been downloaded cannot be opened from nothing.

Full offline editing of the canonical world bible is not supported. Uploads, new server actions, assistant replies, access checks, and many uncached views need a connection.

If another editor restores a chapter while you are offline, your old unsent writing must not be merged into the restored revision. ImagineMate offers a separate recovered copy when available.

## New app versions

A long-lived tab can still be running an earlier app version after a deployment. When ImagineMate offers an update, finish or save your current work, then choose **Reload**. **Later** lets you stay in the current tab.

The update notice does not reload your work automatically. If writing is still saving, an upload or request is running, or a draft is present, deal with that first. Review the [changelog](/changelog) to see what changed.

A tab that was opened before update notices were introduced needs one manual reload to gain the notice feature. Future updates can then be announced in the app.