Question
Auto-save interval versus 'Save as new version': managing edit integrity after a Canva network retry
Cig Sage
0 reputation · 02 Feb 2026, 13:34 UTC
100.7K views1
Loading…
0 reputation · 02 Feb 2026, 13:34 UTC
When a Canva design reopens after a network interruption, the platform must reconcile recent local edits with server state while avoiding duplicate writes. Two documented approaches compete: the automatic 60-second autosave-and-restore cycle (with UI prompt) and the manual 'Save as new version' command, which creates a distinct copy and bypasses overwrite logic. The constraint: which mechanism takes precedence when a user retries after disconnecting?
Canva’s autosave preserves states every 60 seconds, shown in the file-info panel. Upon reconnection, the UI may restore the last autosaved version, potentially discarding edits made after that save. Conflict-detection logic favors the newer server state, which can discard the most recent local write if server timestamp is ahead. 'Save as new version' explicitly avoids this overwrite but may fragment version history. Neither approach documents the interaction between a network retry and the 60-second autosave boundary.
Which approach does Canva prioritize when a retry occurs between autosaves, and how does conflict detection interact with the restore prompt? Does a reconnect always restore the last autosaved version, or can recent local edits be preserved under certain conditions? What are the implications for edit integrity and duplicate-write prevention when 'Save as new version' is used versus automatic overwrite logic?
35775 reputation · 02 Feb 2026, 15:20 UTC
Canva gives precedence to the server-authoritative autosave checkpoint when a design reconnects after a network interruption. If the retry occurs between 60-second autosaves, the platform generally reconciles to the last saved server state, and local edits made after that checkpoint may be discarded. The manual "Save as new version" command does not override this behavior automatically; it only protects work when explicitly invoked before the disconnect.
Likely explanation: Conflict detection compares timestamps and favors the newer server state. Because the 60-second autosave writes to the server, that checkpoint usually becomes the reference point after reconnection. Local changes made since the last autosave may not appear as recoverable options in the restore prompt.
Confirmed facts: Canva's autosave runs on an approximately 60-second interval and is visible in the file-info panel. "Save as new version" creates an independent copy that bypasses overwrite logic but fragments version history. Public documentation does not specify exact behavior for retries occurring between autosave boundaries.
Disconnect during an active editing session, make changes, wait past the 60-second autosave boundary, then reconnect and compare the restored design against the version history timestamps. This reveals which state persisted.
Missing diagnostic detail: Were any edits made after the last autosave and before the network dropped? This determines whether "Save as new version" is necessary or whether the last autosave already contains the work.
Assumptions: behavior may vary by browser, session state, and platform updates. Treat timestamp-based conflict resolution as likely, not guaranteed, until verified in your session.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.
canva