# How saving works and how to recover unsaved edits > Understand how Nodespell saves Projects automatically, what the save status means, and how to review, save, export or discard edits that could not save. Source: https://docs.nodespell.com/projects/saving-and-recovery/ · Last updated: 2026-11-10 Nodespell saves every Project automatically as you edit; there is no Save button for the live Project. A status in the project bar tells you whether your latest changes are saved, still saving, or need your attention. If a change cannot be saved, Nodespell keeps it on your device so you can review it, save it again, export it, or discard it. ## What does the save status mean? The save status sits in the project bar at the top of the workspace. Quiet states are plain text; states that need attention are coloured pills. Hover or open a pill for details. | Status | Meaning | | ------------------- | ------------------------------------------------------------------------------------- | | **Saved** | Your latest changes are saved. | | **Saving…** | Your latest changes are being saved. | | **Changes pending** | You are still adjusting a value, such as dragging a slider. It saves when you finish. | | **Retrying** | Nodespell could not reach the server and is retrying automatically. | | **Not saved** | Some changes are not saved yet. Keep the tab open. | | **Needs action** | The server refused some changes. Open the pill to retry or export them. | While the connection is healthy, Nodespell also keeps a backup of unsaved changes on your device, and the details say **A backup is kept on this device.** The backup gets its own pill only when something is wrong: | Backup pill | Meaning | | ----------------------- | ---------------------------------------------------------------------------- | | **Saved locally** | Changes are kept on this device and waiting for the server. | | **Not backed up** | Changes are not protected locally. Keep the tab open until they save. | | **Uploads pending** | Media uploads are incomplete. The local backup does not include those files. | | **_n_ unsaved** | Unsaved actions are building up. Editing pauses at 99. | | **Editing paused** | 99 actions are waiting to save. Editing resumes when saves finish. | | **Needs attention** | Some kept edits need your review. Their save outcome may be unknown. | | **Save status unknown** | Nodespell could not check the kept edits. Keep the tab open. | ## What happens when you go offline? When your connection drops, Nodespell shows **You're offline** and changes cannot be saved until you are back online. Keep the tab open: edits stay in the tab and in the local backup, and saving resumes when the connection returns. Temporary interruptions recover without you making another edit. ## Review recovered edits When some edits could not be saved, they stay on this device until you decide what to do. Open **Needs attention**, or the **Needs action** pill, and choose **Review changes** to see the **Unsaved changes** list. Each change shows what it was (for example **Moved**, **Renamed**, **Connected** or **Picked a take**), which nodes it affects, and its status, such as **The server refused this**, **May already be saved** or **Not sent yet**. | Action | What it does | | ------------------------------------ | ----------------------------------------------------------------------- | | **Show** | Selects the affected node in the graph. | | **Use mine** / **Use all mine** | Puts your recorded version back into the Project. | | **Save mine** / **Save _n_ changes** | Saves the changes that can be saved automatically, together. | | **Discard** / **Discard all** | Removes the change from this device. The saved Project is not affected. | | **Export for support** | Downloads a recovery file you can send to Nodespell. | Some changes cannot be put back automatically and say **Redo by hand**. For these, the list shows **Your values, as recorded** with a copy button for each field, so you can redo the change yourself. ## How do you know a recovered edit is saved? After you save a recovered edit, Nodespell checks it against the Project. Confirmed changes move to **Saved**, and when everything is confirmed the list shows **All changes are saved**. If only part of a recovery succeeds, the saved parts move to **Saved** and the rest stay listed for review, for example **Save not confirmed** or **Project refused it**. **Check status** checks again. A refused change does not block other edits that can save safely. You can keep working while it waits for review. ## Export a copy of unsaved work Use **Export copy** in the save or recovery panel to download a recovery file of the edits that are not saved. Export before you discard anything you might need. If an export fails, keep the tab open and try again. ## Discard unsaved changes 1. Open the recovery panel and choose **Discard changes**. 2. Read **Discard retained edits?**. It explains that all retained local edits for this Project are removed and the saved Project reopens. 3. Select **Discard and reload**, or **Keep changes** to cancel. Changes that were already saved on the server stay. Discarding also removes edits that were waiting behind a refused one. > **Caution:** Discarded edits cannot be brought back. Use **Export copy** first if you may need them. ## What happens with two tabs or two devices? Only one browser tab edits a Project at a time. The project bar shows the editing state: | Status | Meaning | | --------------------- | ----------------------------------------------------------------------------------------------------------------- | | **Editing** | This tab is editing the Project. | | **Viewing** | Another tab of yours is editing. Click anywhere to edit here; the other tab saves its changes first, then pauses. | | **_name_ is editing** | A teammate is editing. Choose **Request editing** to ask them to hand over. | | **Paused** | This tab paused after a while without activity. Move the pointer or press a key to continue. | | **Reconnecting…** | Nodespell is reconnecting. Your changes are safe on this device. | While viewing, you can still browse Assets and inspect media. If your other tab or device stops responding, Nodespell offers **Take over now**. Anything that tab had not saved stays in it and does not appear in the new tab, so you can still export it there. ## Closing a project with unsaved changes When you close a Project, Nodespell first finishes saving. If some changes have not finished saving, the Project stays open with **Project not closed**, and nothing is lost. Check the recovery notice, then try again. ## Frequently asked questions ### Do I need to save my project? No. Nodespell saves the live Project automatically. Use **File** > **Save Version ...** only when you want a named [snapshot](https://docs.nodespell.com/projects/projects-and-snapshots/). ### Is it safe to close the tab while it says Not saved? No. **Not saved** means some changes have not reached the server. Keep the tab open until the status returns to **Saved**, or export a copy first. ### Why is editing paused? Editing pauses when 99 actions are waiting to save, so unsaved work cannot grow without limit. It resumes when saves finish. ### Does discarding changes affect saved work? No. Discarding removes only the unsaved edits kept on this device. Changes already saved on the server remain. ### Can two people edit the same project at once? Only one tab edits a Project at a time. Another person can request editing, and the current editor chooses whether to hand over. See [Team projects](https://docs.nodespell.com/teams/team-projects/). ## Related - [Projects and snapshots](https://docs.nodespell.com/projects/projects-and-snapshots/): save named versions. - [Projects dashboard](https://docs.nodespell.com/projects/dashboard/): open and manage Projects. - [Team projects](https://docs.nodespell.com/teams/team-projects/): editing a shared Project. - [Support](https://docs.nodespell.com/account/support/): what to send when something goes wrong. - [Troubleshooting](https://docs.nodespell.com/reference/troubleshooting/): fixes for common problems.