What does Obsidian Sync synchronize?
Obsidian Sync is the product's subscription service for synchronizing a vault between devices through a remote vault. Your local vault remains the working copy on the device. The setup documentation describes connecting an existing local vault, creating a remote vault, and joining that vault from another device.
Start by listing the devices, notes, attachments, and settings you want in the routine. A laptop used for research and a phone used for quick capture may not need every large attachment or every desktop setting. Writing that intention down makes later selective-sync behavior easier to diagnose.
Connect the first vault and verify the second device
Follow the current setup instructions to sign in, enable the Sync core plugin, and create or connect the intended remote vault. Confirm that the local vault and the remote vault are the ones you mean to join. The documentation recommends an independent backup and directs people already using another folder-sync service to its migration guidance first.
After the initial synchronization finishes, connect the second device using the documented join process. Use a harmless note named Sync trial with two short lines and a small sample attachment. Change a line on the first device, allow it to sync, and check the result on the second. This is a proposed acceptance exercise, not an instruction to experiment on the only copy of important notes.
| Check | Test material | Expected observation |
|---|---|---|
| First upload | One fictional note and a small sample attachment | Both appear in the intended remote-vault setup |
| Second device | The same note after synchronization | The expected content is available locally |
| One-device edit | Change one harmless sentence | The second device receives the change |
| Selective sync | A deliberately excluded sample item | Behavior matches the configured choice |
| Recovery review | An earlier version of the trial note | You can inspect the appropriate history without guessing |
Selective syncing and settings are device-specific decisions
Obsidian's Sync settings let you choose what to synchronize, including file and vault-configuration choices. Its documentation emphasizes device-specific settings for selective syncing and conflict resolution. Review the configuration on each device instead of assuming the first device's choices control all the others.
Create a small device matrix: laptop includes the required research attachments; phone includes the files needed for capture and reading; each has an intentional conflict preference. When an item seems missing, compare that matrix with the actual local settings before treating the situation as data loss or changing several settings at once.
Why do conflicting edits happen?
A conflict can occur when more than one device changes the same file before the changes synchronize. Obsidian documents automatic merging for Markdown, different handling for other file types, and an option to create a conflict file for review. Its conflict preference must be configured separately on each device.
If a conflict affects a real note, first preserve the versions you can inspect and avoid continuing unrelated edits to that note while diagnosing it. Identify the file type, devices, edit order, and selected conflict behavior. A file that was merged and a file that was replaced require different explanations; do not assume every attachment follows the same merge behavior as Markdown text.
Use logs and version history for the question they answer
The Sync activity log helps explain what happened during synchronization, including errors, skipped files, and merge conflicts. Obsidian notes that this log does not persist after the app is closed, so preserve the relevant diagnostic information before restarting when you need it for investigation.
Version history helps inspect earlier synchronized file versions. Local File recovery is a separate feature, and an independent backup serves another recovery need. Before restoring anything important, identify the version and content you intend to recover and retain the current copy where appropriate. A successful sync status does not establish that an unintended edit is the version you wanted.
Does Obsidian Sync replace a backup?
No. The setup documentation explicitly distinguishes synchronization from backup. Sync distributes changes, including changes you may later regret. Plan an independent recovery method, and verify it using non-sensitive sample material before relying on it. This guide does not establish a backup-retention or recovery guarantee for your subscription or device.
Why is a note or attachment missing on my other device?
Check the intended remote vault, current synchronization state, device-specific exclusions, and the activity log. Determine whether the file was skipped, changed, deleted, or simply not finished syncing. Consult the current limits and troubleshooting guidance for the actual message. Avoid creating a second overlapping sync setup as a guess at the solution.
Sources and editorial method
Official sources linked in this article were checked on October 28, 2026. Product facts come from those sources; recommendations and fictional evaluation exercises are editorial analysis. We have not run a comparative product benchmark. Recheck current plans, supported platforms, and documentation before purchasing or changing a workflow.