CLOUD BACKUP & PHOTO LIBRARIES
An Obsidian vault is a folder, but keeping that folder usable across devices involves more than copying Markdown. Device support, attachment transfers and conflict handling determine whether notes stay dependable when you move between screens.
Quick answer
Choose Obsidian Sync when its supported app integration and recovery workflow match your devices. Consider Syncthing when you already manage compatible file-sync clients and want control over peer connections; verify mobile support before committing.
Steps to follow
-
Before you start
Keep the original data available while following this procedure. Record the application version, account, source path and destination you are actually using. If an error is involved, save its exact wording. Use a small, non-sensitive sample first so that an unexpected result is easy to inspect without disturbing your working library.
-
Set up the right scope
List every device, including its operating system and background limits. Compare the current Obsidian Sync plan’s limits with your vault and attachments. For Syncthing, check the actual client available on each platform rather than assuming identical Android and iOS support.
-
Apply the relevant settings
Copy a small vault with notes, links and attachments into a test location. Configure one sync system for that vault, let the first transfer finish and confirm the destination opens the expected folder in Obsidian.
-
Complete the first run
Edit notes sequentially on each device, then test a deliberate simultaneous edit on disposable content. Compare recovery of the earlier note, attachment completeness and behaviour after offline work.
Decisions and checks
The limitation that matters
Do not run two independent synchronisation systems over the same working vault without a carefully supported design. Syncthing is a general file synchroniser; it does not automatically supply Obsidian’s application-specific experience or universal mobile background support.
How to verify the result
Recover a previous note, follow an internal link and open a large attachment on each device. Base the decision on this workflow and the current plan terms, not just on whether the first text file appeared.
Keep the result reliable
After the first successful check, repeat the process with an ordinary working session or scheduled run. Record the date and the recovery location. Revisit the setup after changing devices, accounts, storage paths or software versions; yesterday’s successful job does not prove that a new configuration is covered.
Compare the options
| Situation / component | Purpose / action | What to check |
|---|---|---|
| Input | Preserve an unchanged sample | Know which account and location contain the original |
| Operation | Follow the procedure for your installed version | Review errors and skipped items, not only the completion message |
| Result | Open the resulting file or test the documented recovery route | Confirm that the content, version and access rights are correct |
Frequently asked questions
Can I remove the original immediately?
Keep it until you have verified the intended result and have an independent recovery copy where the data matters. A visible file name, a green icon or a completed task alone does not show that every needed item is recoverable.
What information helps if this fails?
Record the version, exact error, affected file type, available space and whether the same small sample works elsewhere. Share sanitized details through the official support route; passwords, recovery keys and private documents are not needed for an initial diagnosis.
Official documentation
This guide combines current official documentation with practical recovery checks. It does not claim hands-on testing of your installation. Menu labels and supported procedures can vary by release; follow the documentation for your installed version.