Remote Sync
Keep your JSON document in sync across browser tabs and devices.
What remote sync does
- Shares updates between tabs
- Syncs changes across devices
- Keeps version history consistent
How syncing works
- You make changes
- Changes are saved automatically
- Other tabs and devices receive updates
Important behavior
- Updates arrive after a short delay
- You may see Update available
- Updates are not applied automatically
Update flow
- A newer version is detected
- The editor shows Update available
- You choose:
- Apply update
- Keep editing
Why updates are not automatic
Automatic updates could:
- Overwrite your work
- Cause confusion
Instead, you stay in control.
Sync across tabs
- Tabs share updates automatically
- Changes appear shortly after saving
Sync across devices
- Devices receive updates after saving
- Version history stays consistent
Things to remember
- Sync is not instant
- Updates require your confirmation
- Your edits are never overwritten automatically
Learn more:
Advanced: Sync & Conflict Resolution
For a deeper explanation of how this works, see Advanced: Sync & Conflict Resolution.
Sync works through version updates.
Sync model
- Changes are saved as versions
- Other sessions receive newer versions
- The editor compares versions to detect updates
Conflict prevention
- Older changes cannot overwrite newer versions
- Each save checks against the latest version
- Conflicts are avoided by rejecting outdated updates
Update handling
- New versions are detected
- They are not applied automatically
- Users explicitly choose when to update
Why this model works
- Prevents data loss
- Avoids merge conflicts
- Keeps behavior predictable
For more system details:
Last updated on