# Save, synchronize and recover your work

Understand local saves, cloud copies, offline work and device changes.

## Local save versus cloud synchronization [#local-save-versus-cloud-synchronization]

Your presentation is saved locally in the browser. Cloud synchronization makes a registered copy available to your account on another device. A cloud copy does not prove that every recent local change has uploaded.

Check the footer status for local-only content, changes pending upload, synchronization in progress or synchronized content. Wait for synchronization before expecting another device to have the latest changes.

## Work offline [#work-offline]

Work already available locally can remain usable offline. New work waits for reconnection. Another device cannot recover a presentation that was never synchronized.

Do not clear browser site data as a troubleshooting shortcut. Download an editable backup first, particularly for local-only presentations or pending changes.

## Adopt or stop synchronizing [#adopt-or-stop-synchronizing]

New presentations queue cloud registration automatically. Existing local-only, imported and recovery documents require explicit adoption for cloud synchronization. If storage is full, the presentation remains local with storage feedback.

**Stop syncing** removes the cloud copy only after confirming that the local presentation and images are available. It preserves local editing but permanently revokes existing share links. Enabling synchronization again does not restore those links.

**Delete** removes the local presentation and queues permanent cloud deletion. It is not the same as stopping synchronization.

## Sign out and multiple devices [#sign-out-and-multiple-devices]

Signing out preserves account-local data; other accounts cannot access it through the app. Let synchronization reconcile work instead of repeatedly importing copies to force an update. Keep a backup before resolving uncertain outcomes.

See [storage and plans](/en/docs/account/plans) and [troubleshooting](/en/docs/troubleshooting).