Docs › Apps & Sync › Write offline + auto-sync on reconnect
Write offline + auto-sync on reconnect
Last updated May 14, 2026 · 3 min read
Offline writing isn't a degraded fallback — Slima was designed from the start to write smoothly with no network.
What works offline
- ✅ Typing, editing
- ✅ Creating, deleting, renaming files
- ✅ Creating versions (the version system works locally)
- ✅ Viewing version history, restoring
- ✅ Reading all content of the current book
What doesn't work offline
- ❌ AI Coach chat (needs cloud AI)
- ❌ AI chapter analysis, AI Beta Readers
- ❌ Seeing the latest content written on other devices (not synced down yet)
- ❌ Share links (can be created, but recipients can't reach the content)
How auto-sync works
- You write something → saved instantly to local IndexedDB
- With no network → the change enters a pending queue
- Slima detects the network is back → auto-pushes
- Push order follows timestamp + file dependency
Once back online, syncing usually completes quickly.
Seeing what's pending
You don't manage the pending queue by hand. While you're offline, every change is buffered locally and waits in a pending queue; the moment Slima detects the network is back it pushes them automatically. When you're signed in and online, the sync indicator in the file panel header reflects the state — it turns to a pending color while changes are still waiting to upload, then back to synced once they're through.
Does a sudden disconnect lose anything?
No. The first of Slima's four protection layers is instant local IndexedDB saving — the moment the network drops, what you wrote is already on your device.
See: Why versioning: 4-layer protection
Syncing after a long offline session
Say you wrote for several hours on a plane:
- Land, connect to wifi → auto-sync starts
- Depending on the volume of changes, it may take a while
- The sync doesn't block you from continuing to write — you can upload and edit at the same time