Docs › Apps & Sync › Same-file multi-device edit: choosing a version
Same-file multi-device edit: choosing a version
Last updated June 2, 2026 · 3 min read
Two devices edited the same passage — desktop wrote version A, mobile wrote version B. Which one counts? Slima doesn't decide for you — it pops a conflict-resolution dialog so you choose.
What triggers it
A typical scenario:
- You edit a passage in Chapter 3 on the desktop
- Mobile (which you forgot to let sync) also edits the same passage
- The desktop reconnects and tries to push → the cloud notices "mobile's edit hasn't come down yet"
- The desktop pulls mobile's version → finds both edited the same passage → conflict
The conflict-resolution dialog appears.
What the dialog looks like
The dialog shows both versions side by side (read-only): "My Version" on the left, "Other Device Version" on the right, so you can see the differences before deciding which one to keep.
Underneath are two resolution actions, plus a "Resolve Later":
| Choice | Result |
|---|---|
| Keep mine | The current device's version wins; the other syncs in but is overwritten |
| Use theirs | The other device's version wins; the current one is overwritten |
| Resolve Later | Closes the dialog without deciding; the conflict stays unresolved and pops up again next time |
Look before you choose
When you pick "Use theirs," any edits you made on the current device after the conflict will be overwritten — and the version you didn't pick is not saved off automatically, so review the side-by-side compare carefully before you commit.
If you're unsure and worried about picking wrong, the safest move is to manually save a version of the chapter before resolving the conflict, so the current content is preserved. See Restore a version.
How to avoid conflicts
The simplest habit: before switching devices, confirm the previous one finished syncing (status bar 🟢 green).
See Sync status and pending items.