Obsidian Sync vs Syncthing After a Week Offline: Which Copy of the Daily Note Wins

A week offline is the stress test sync marketing never demos. Laptop in a cabin without reliable internet. Phone on airplane mode for focus. E-ink tablet full of daily notes. When radios return, Obsidian Sync and Syncthing both try to reconcile reality—and someone has to decide which copy of 2026-09-21.md wins.

This is not a feature checklist. It is what happens after seven days of divergent edits, how each tool shows the fight, and which habits keep you from losing the paragraph you wrote when the storm knocked out the starlink dish.

What “a week offline” does to a vault

Every device accumulates a private timeline. Daily notes accrue. Plugin state drifts on the machines that run Obsidian. Attachments may exist on one disk only. When connectivity returns, sync is not “catching up”—it is merging parallel universes that shared a folder name.

Hot files lose. Daily notes, scratchpads, and project status docs edited on two devices without a rendezvous are conflict magnets. Cold files (finished essays, reference PDFs) usually just appear.

Obsidian Sync after the blackout

Obsidian Sync understands Obsidian’s objects. Conflicts surface in ways aimed at note files. For vaults that only ever change inside Obsidian clients, that focus is a strength: less noise from random filesystem thrash, clearer note-level conflict UX.

After a week offline, expect:

• Conflict copies or conflict resolution UI for notes edited on multiple devices
• Faster emotional recovery if every writer was Obsidian
• Confusion if a plain text editor or another app also wrote into the vault folder on Android
• Dependency on Sync’s account and sync history behavior for recovery narratives

Sync wins when your offline week was “several Obsidian clients, no freelancers editing the folder.” It is less magical when the e-ink device used a different editor against the same markdown path.

Syncthing after the blackout

Syncthing reconciles files, not notes. After a week, it will transfer everything that differs and create sync-conflict copies when both sides wrote the same path. That honesty is refreshing and messy. You may get conflict files for JSON you never meant to sync, plus the one daily note you care about.

Syncthing wins when:

• You already treat the vault as a folder of files
• Non-Obsidian tools edit markdown
• You want peer sync without an Obsidian subscription
• You can keep ignore rules tight so the conflict blast radius is mostly real notes

It loses when you expected a CRDT and got a pile of sync-conflict siblings after vacation.

Which copy of the daily note wins?

Neither tool can know which paragraph is “right.” They can only refuse to clobber. Winning is a human merge:

1. Reconnect one hub device first (usually the desktop) and let it stabilize.
2. Bring devices online one at a time, not all at once.
3. Search for conflict markers / conflict filenames before you keep writing.
4. Merge daily notes on the fastest screen; prefer append of unique sections over line-by-line archaeology.
5. Delete conflict siblings the same day.

If both copies have unique content, the winner is a new third file that contains both—then replace the canonical daily path. Ego attachments to “my phone version” are how people delete the cabin paragraph.

Habits that survive offline weeks

Device-scoped capture. Offline tablet writes Inbox/device-date.md, not the canonical daily note. Merge when online. This single habit eliminates most daily-note conflicts.

One writer for structure. Renames and folder moves wait until all devices are online and synced. Offline restructuring is how Syncthing earns its horror stories.

Pre-trip sync ritual. Before you leave coverage, open each device, confirm sync idle, then go offline. Starting the week already divergent is optional pain.

Ignore rules for Syncthing. Do not sync plugin thrash into the offline tablet. Fewer files mean faster catch-up and fewer irrelevant conflicts.

Know your authority. Decide beforehand: desktop is merge authority unless it was powered off the whole week. Write that down in a note you will actually read at the airport.

Mixed fleets

Obsidian Sync on laptop/phone plus Syncthing to an e-ink folder is a common hybrid—and a common footgun if both systems touch the same paths. Prefer one sync fabric per path. If the tablet is Syncthing-only, keep its share to inbox folders that Obsidian Sync does not also fight over, or keep the tablet outside Sync entirely.

Two fabrics can work as layers (Sync for Obsidian clients, Syncthing for a read-only export tree). They fail as two writers on one daily note.

Attachment and media surprises

Offline weeks are when you screenshot, draw, or drop PDFs on one device only. After reconnect, Syncthing will eventually move the binaries if they live in the share. Obsidian Sync will too, within its size and type rules. The surprise is not that files arrive—it is that a daily note on device A links to an attachment that only existed on device B until catch-up finished. Open the note too early and you think the media is gone.

Wait for sync idle before you panic-edit links. If you must work mid-catch-up, paste a temporary local path note instead of rewriting the canonical daily file on a third device.

Large vaults also teach patience: a week of photos in an attachments folder can saturate a phone hotspot. Prefer syncing text first—another argument for inbox markdown without huge binaries on travel devices.

Security and trust boundaries

Obsidian Sync’s trust is the vendor and your account security. Syncthing’s trust is your devices and how you introduce them. After offline travel, verify you are not approving a stranger’s device in a tired airport state. For Syncthing, prefer reconnecting known devices over new shares. For Sync, prefer official clients over copying vaults through random USB sticks that later re-enter the sync web with older trees.

Encrypted disks help when laptops leave your sight. Sync does not replace full-disk encryption. Neither does Syncthing.

Recovery drills worth doing once

Simulate: edit a daily note on two machines offline (airplane mode), then reconnect. Practice the merge. Time how long catch-up takes on your real vault size. If catch-up is hours, your offline travel kit should include a smaller subset vault.

Also practice “desktop dead.” If the authority machine dies while you are away, which device becomes authority? If the answer is unclear, your sync plan is incomplete.

Decision guide

Prefer Obsidian Sync when every offline writer is an Obsidian client and you want note-centric conflict handling.

Prefer Syncthing when offline writers include other editors, you want peer control, and you will maintain ignores plus human merges.

Prefer inbox-per-device regardless of tool when offline weeks are normal. The tool that “wins” the daily note is the one that never had to choose—because you never dual-wrote the same path.

After a week offline, the winning copy is the merge you do carefully on a good screen. Everything else is just how loudly the tools announce that physics happened while you were away.

A reconnect order that reduces tears

When you regain connectivity, resist the urge to unlock every device at once. Power the hub laptop first, authenticate, wait until sync reports idle. Then the phone. Then the e-ink tablet. Each step should end idle before the next begins. Parallel reconnects maximize conflict fan-out because each device uploads its offline truth into a moving target.

If you already parallel-reconnected, stop writing. Let the storm finish. Only then search for conflicts. Writing during catch-up is how a third version appears and makes the merge triple-wise.

Finally, glance at the clock: if catch-up will take hours on hotel Wi-Fi, switch the travel devices to a small inbox vault for the rest of the trip next time. A week offline is easier when the traveling corpus is intentionally small.

When to split the vault before you travel

If your main vault is huge, copy a travel subset: active projects, current daily folder template, and a thin attachments directory. Sync that subset with whichever tool you trust. Leave the archive at home. Offline weeks become merges of dozens of files instead of thousands, and conflict review stays human-sized.

Coming home, merge travel inbox into the main vault deliberately—like importing a branch—not by pointing Syncthing at both roots and hoping. Branch metaphors help even if you are not using git: travel is a branch; home is main; you merge with eyes open.

People who refuse to split vaults pay in airport hours. People who split but forget to bring templates invent new daily note formats on the road and create naming conflicts of a different kind. Pack the template once.

Pack the template once, reconnect in order, merge on a fast screen, and delete conflict siblings before you reward yourself with being ‘fully synced.’ The week offline was the easy part; the reconnect is the exam.

Pass that exam once on purpose at home, and the real trip stop feeling like a data-loss lottery every time the cabin Wi-Fi finally returns.