Cloud Sync
Cloud Sync keeps selected Octoclip data aligned across devices when they are not on the same local network. It is designed for ongoing multi-device use through your configured WebDAV / S3 storage path.
Cloud Sync is a paid feature. Use Free + Nearby Sync first to confirm the core cross-device flow, then enable Cloud Sync when you need cross-network or long-term sync.
When to use Cloud Sync
Use Cloud Sync when:
- your devices are often on different networks;
- you want clips, collections, aliases, and settings to follow you over time;
- local discovery is blocked by a router, VPN, guest Wi-Fi, or enterprise network;
- you prefer a user-controlled WebDAV / S3 storage path.
Use Nearby Sync instead when two devices are on the same local path and you want the shortest transfer route.
What can be synced
Depending on your settings and version, Cloud Sync may include:
- clip history within the selected sync scope;
- collections and favorites;
- aliases and reusable input data;
- selected sync metadata and preferences.
Start with a conservative scope, such as collections and aliases, before syncing full clip history.
First-time setup
Cloud Sync only works on devices with paid features enabled. Use the official pricing page and the in-app license page for current plans and activation limits.
Go to Octoclip settings and open Cloud Sync.
Prepare your provider endpoint, account, credentials, bucket/path, and region information as needed.
Start narrow. Expand only after the first sync succeeds.
Use the same storage path and the same encryption key on every device. Cloud Sync content is end-to-end encrypted with a key you hold, so a device with a different key cannot decrypt it—content will silently fail to appear even when the connection is fine.
Copy a unique string on device A, then confirm it appears on device B.
Sync behavior
- Cloud Sync targets eventual consistency, not strict real-time mirroring.
- When new data is ready, an anonymous notification service signals your other devices to fetch it. This signal only says "new data is ready"—it carries no clip content or key.
- Offline changes are queued locally and synced after reconnect.
- Concurrent edits may resolve according to the latest version or product-specific conflict handling.
- Large images/files may take longer than short text.
Security and storage boundaries
Cloud Sync content is end-to-end encrypted on your device with a key you set, then uploaded as ciphertext. Your encryption key and storage credentials stay in the device keychain / secure store—not on any Octoclip server. A second device needs the same storage configuration and the same key to decrypt. Octoclip and your storage provider only ever see ciphertext.
If you lose the encryption key, the encrypted clips already in your bucket cannot be recovered—no one, including Octoclip, can decrypt them. Save the key in a password manager before enabling Cloud Sync.
Your cloud data path still depends on the WebDAV / S3 provider you configure. Octoclip does not control that provider's availability, retention, region, or backup—those remain your storage provider's responsibility. Review its access control and settings.
For sensitive clips, consider:
- not syncing full clip content;
- shortening history retention;
- excluding sensitive apps or sources;
- using local-only workflows when possible.
Troubleshooting
If Cloud Sync fails, check in this order:
- Both devices have paid features activated.
- Cloud Sync is enabled on both devices.
- Provider endpoint, credentials, bucket/path, and region are correct.
- Both devices use the same encryption key (a mismatched key prevents decryption, so content arrives but never shows).
- Sync scope includes the item you are testing.
- Network access to the provider is not blocked.
- Test with a short plain-text clip before testing files.
Continue with Sync failed or Logging and diagnostics.