Saving is now more reliable on canvases with lots of nodes, even when your connection isn't great.

What's different

When your save collides with a change made elsewhere, only your edits are sent. If the same canvas was edited in another tab, or a generation result was just written back to it, your save can bump into that change. Now it goes through by uploading only the nodes you changed — no need to download the whole canvas first. The bigger the canvas and the slower the connection, the bigger the difference.
New things added elsewhere show up for you. When that happens, nodes and connections added on the other side are brought into the canvas you have open. Things you deleted yourself are not brought back.
The last save before you leave is smaller. Before you head to top-up or close the tab, the final save only sends what changed, so it is far more likely to arrive before the page goes away.

Tip

The save status is shown under the canvas name — "Saved to cloud" means everything is stored.

This applies to personal canvases; team canvases already sync in real time.