Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteThe dependable setup is a scheduled, one-way copy of your complete Obsidian vault from the computer you use most to a separate destination such as an external drive, NAS, or protected off-site backup. Use Obsidian File recovery for quick local rollbacks, and keep Sync or Git for device access or version history—not as your only disaster-recovery copy.
What an automatic Obsidian backup must protect
Obsidian stores notes locally on your device by default. A vault is a folder, not just a database, so a usable backup must preserve the files that make the vault work:
As an Amazon Associate I earn from qualifying purchases.
- Markdown notes: your written content and frontmatter.
- Attachments: images, PDFs, audio, video and other files linked from notes.
- The
.obsidianfolder: workspace layouts, appearance settings, hotkeys and community-plugin configuration. Include it when you want the restored vault to behave like the original.
A backup is useful only if it is separate from the working copy and can be restored to a known point in time. If a deletion, sync mistake, disk failure or malware event changes the original, a copy that changes at the same moment may preserve the problem instead of the earlier version.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The arrangement that covers the most failure cases
Use separate layers for separate jobs. No single Obsidian feature is designed to provide instant rollback, device access, version history and disaster recovery at the same time.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Layer 1: File recovery for immediate rollback
Obsidian’s File recovery feature keeps local snapshots so you can recover from an accidental edit or deletion. Obsidian documents a default minimum interval of five minutes between snapshots and seven days of retention. Those limits are useful for recent mistakes, but the snapshots remain on the same device and are not a complete backup.
Layer 2: A scheduled, one-way copy for disaster recovery
Have the computer used most often with the vault copy the entire vault on a schedule to a different disk, NAS or off-site backup location. One-way means changes flow from the source vault to the backup job, not in both directions. Configure retention or dated versions so a deletion is not instantly the only state available.
Layer 3: Sync or Git only for the problem it solves
Use synchronization when you need the same vault on several devices. Use Git when you need an auditable change history and a remote repository. Both can be valuable, but neither removes the need for an independent backup copy.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchSet up an automatic backup step by step
- Choose the backup device. If the vault is synchronized across a desktop, laptop and phone, designate the desktop or laptop where you do most of your editing as the backup source. A single authoritative source reduces competing jobs and makes restore decisions clearer.
- Locate the vault folder. In Obsidian, identify the exact folder opened as the vault. Do not back up only a subfolder such as “Notes”; the attachments and
.obsidiandirectory may be elsewhere in the vault hierarchy. - Decide what is included. Copy Markdown files, attachments and
.obsidian. Exclude temporary files only when you know what they are and why they can be recreated. If a community plugin stores important data in a particular subfolder, verify that it is inside the vault before excluding anything. - Prepare a separate destination. Use an external hard drive or SSD, a NAS share, or a dedicated off-site backup location. The destination should remain available to the scheduled job but should not be treated as another live editing location. A second physical location protects against theft, fire and a failure that affects both the computer and a nearby drive.
- Configure a one-way scheduled copy. Use your operating system’s backup utility, a NAS task or a backup application. Set the vault folder as the source and the separate destination as the target. Choose a schedule based on how often the notes change: frequent writers may prefer several runs per day, while a daily run may be adequate for a vault that changes less often. Keep dated versions or a retention window rather than only one mirror.
- Prevent simultaneous editing during the first full copy. Let the initial job finish, then confirm that the destination contains the expected note count, attachments and
.obsidianfolder. If the tool offers verification, enable it. - Enable File recovery in Obsidian. Keep its local snapshots for quick undo of recent edits. Adjust the snapshot interval and retention when the vault’s value or editing frequency justifies it, while remembering that this remains a local rollback layer.
- Document the restore path. Write down the source folder, destination, schedule, retention policy and the person or account that can access the backup. A backup that nobody can locate or decrypt is not a recoverable backup.
- Test a restore. At regular intervals, copy a dated backup into a new test folder and open that folder in Obsidian as a separate vault. Check notes, attachments, internal links, search, templates, themes and any important plugin settings. Never test by overwriting the live vault.
How the main methods differ
| Method | Best use | What it protects | Main limitation |
|---|---|---|---|
| Scheduled one-way copy to an external drive, NAS or off-site backup | Primary automatic backup and disaster recovery | A separate copy of the complete vault, with point-in-time versions when retention is configured | Requires a separate destination and periodic restore checks |
| File recovery | Fast rollback of a recent local edit or deletion | Recent snapshots on the working device | Device-local, short retention; Obsidian states it is not a complete backup solution |
| Obsidian Sync | Keeping one vault available on multiple devices | Synchronized vault content and, depending on the plan, version history | Obsidian states that synchronization is not a backup; retention depends on the plan |
| Obsidian Git | Auditable history and a remote, versioned copy | Committed states and their differences | Privacy, credentials, conflicts and the commit/push workflow require active management |
| Local Backup plugin | Archived local copies in a chosen folder | Additional snapshots stored where you configure them | It is a community plugin, and its destination still needs protection from device loss |
Compare any option on seven practical axes: whether it is one-way or can propagate deletions, how far the copy is from the working device, how much point-in-time history it keeps, privacy and encryption, restore speed and granularity, platform support, and ongoing cost. A strong design usually combines File recovery, a scheduled separate copy, and Sync or Git only when their specific benefits are needed.
Rank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Why Obsidian Sync is not your backup
Sync keeps a vault available across devices; it does not create the independent, administrator-controlled recovery copy that a backup requires. Obsidian’s documentation explicitly says, “Syncing is not a backup.” If an unwanted change is synchronized, the same change can appear on every connected device.
Obsidian’s documented Sync version-history windows are one month on the Standard plan and 12 months on the Plus plan. Attachments are retained for two weeks. These are service retention periods, not a guarantee that every historical state or attachment will remain available indefinitely, and the documentation page does not state a publication date. Do not choose a backup policy that assumes Sync will retain more history than your plan provides.
If you use Sync, make the synchronized vault on your designated desktop or laptop the source for the independent scheduled copy. Avoid editing the same files from multiple devices while a restore is in progress; first recover into a separate vault, inspect it, and then decide which state should become authoritative.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Using File recovery correctly
File recovery is the quickest route when a note was edited or deleted recently and the original device is still available. Open Obsidian’s settings, enable the File recovery core plugin, and review its snapshot interval and retention values. The documented defaults are a minimum of five minutes between snapshots and seven days of retention.
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Use it for events such as overwriting a paragraph, removing a block, or deleting a note moments ago. It is not sufficient for a failed drive, a stolen laptop, ransomware, or a mistake discovered after its retention window. Because the snapshots are local, a hardware failure can remove both the vault and its recovery history.
Using Obsidian Git without turning it into a fragile backup
Obsidian Git can commit vault changes, show a history of revisions and push that history to a remote repository. That makes it useful when you need to answer “what changed?” or restore one earlier version of a note.
- Set privacy first. Treat note text, attachments and metadata as potentially sensitive. Choose a private repository when the content is not intended for public access.
- Protect credentials. Use the repository’s supported authentication method, keep tokens out of notes and scripts, and remove access promptly when a device or account is retired.
- Choose attachment rules deliberately. Large binary files can make repositories unwieldy, while excluding them means a Git restore may not reproduce the complete vault. Decide whether attachments belong in the repository and maintain the separate scheduled copy either way.
- Make commits and pushes predictable. A remote repository is only current through the last successful push. Check for failed commits, rejected pushes and merge conflicts rather than assuming the background process completed.
- Keep the independent copy. Repository deletion, credential compromise, an accidental force-push or an incorrect ignore rule can affect the versioned copy. Git history is an additional layer, not a reason to remove the ordinary backup.
What a Local Backup plugin can and cannot do
The Local Backup community plugin can create archived copies in a folder you choose. It is convenient when you want snapshots without configuring a separate operating-system job, and its storage location and retention can be tailored to your workflow.
Because it is a community plugin, treat it as one component rather than the whole recovery plan. A folder on the same internal disk is exposed to the same disk failure, theft and malware as the vault. Point it to a separately protected destination when possible, and still perform test restores.
Rank #4
- High capacity in a small enclosure – The small, lightweight design offers up to 6TB* capacity, making WD Elements portable hard drives the ideal companion for consumers on the go.
- Plug-and-play expandability
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- SuperSpeed USB 3.2 Gen 1 (5Gbps)
External drive, NAS or off-site destination?
External hard drive or SSD
An external drive is simple and fast for a local restore. Connect it for scheduled runs, keep it disconnected when practical, and maintain more than one dated version so a bad edit is not mirrored as the only copy. A second drive rotated to another location improves protection against events that affect the whole room or building.
NAS
A NAS keeps the destination available on your network and can run its own scheduled job. Restrict write access, use separate accounts where supported, and check whether the NAS keeps historical versions rather than only mirroring the latest state. A NAS in the same home is convenient but does not by itself provide off-site protection.
Off-site backup
An off-site destination addresses loss of the computer and local backup hardware together. Evaluate its encryption, retention, restore granularity, platform support and recurring cost before relying on it. The evidence available here does not establish provider pricing or regional availability, so those details must be verified for the service you select.
Restore an accidentally deleted or damaged note
If the mistake is recent
- Stop editing the affected note so you do not create more changes before recovery.
- Use File recovery on the original device to locate a snapshot from before the deletion or unwanted edit.
- Restore the content into a temporary note or test vault first. Compare links, frontmatter and attachments before replacing the live file.
If the local snapshots are gone
- Find the dated version in the scheduled backup destination or Git history.
- Restore the file, or the entire vault when the damage is broader, into a separate folder.
- Open the restored folder as a different Obsidian vault and verify links, attachments and settings.
- Copy only the confirmed files into the working vault, or switch to the restored vault after recording which state is authoritative.
Do not restore directly over the only remaining copy. Keeping the damaged state until the recovered version has been checked gives you a way back if the first restore is incomplete.
Best Value
- Plug-and-play expandability
- SuperSpeed USB 3.2 Gen 1 (5Gbps)
Common failure modes and fixes
The backup contains notes but no images or PDFs
The job probably targeted a notes subfolder instead of the vault root, or it excluded attachment directories. Change the source to the complete vault folder and verify several attachment types in a test restore.
Settings and plugins disappeared after restore
The .obsidian folder was omitted, or the restore was opened as a new vault without its configuration. Include .obsidian when preserving workspace and plugin settings matters. Review plugin credentials separately; configuration files may contain sensitive values.
A deletion appeared in the backup
The process is acting as a live mirror or has no version retention. Convert it to a one-way scheduled job with dated versions or a retention window, then test that an older state remains available after a deliberate test deletion.
The backup job reports success but cannot be restored
A successful copy is not proof of a usable restore. Check destination permissions, available space, file counts and the ability to open a restored vault. Schedule a recurring test restore rather than waiting for an emergency.
iCloud on Windows creates duplicates or corruption
Obsidian’s documentation warns that iCloud Drive on Windows may lead to file duplication or corruption. Do not make that synchronization folder your only protected copy; use it, if at all, as the source for a separate backup routine and verify restores.
Several devices are editing at once
Choose one primary backup device and let it run the scheduled copy. Sync the vault for access, but resolve conflicts before deciding which content enters the protected backup. A backup job cannot determine which competing edit is correct.
Quick Recap
Security and privacy checks
- Use destination permissions that prevent every account and application from modifying the backup.
- Encrypt the external drive, NAS volume or off-site repository when the vault contains confidential information.
- Keep recovery credentials and encryption keys somewhere separate from the computer being backed up.
- Review community-plugin configuration before copying it to a shared or cloud destination; it may include tokens, endpoints or other secrets.
- When using Git or a remote service, confirm repository visibility, account recovery and token revocation procedures.
- Retain at least one version that a current synchronization event cannot overwrite.
A practical maintenance schedule
| When | Check | Expected result |
|---|---|---|
| After initial setup | Run the first full copy and open it as a separate vault | Notes, attachments, links and required settings are present |
| After changing the vault location or sync arrangement | Confirm the scheduled job still points to the intended source and destination | The job is backing up the active vault root, not an obsolete folder |
| After changing plugins or attachment practices | Inspect the copied .obsidian folder and representative attachments |
The restore contains the files needed for the new workflow |
| At regular intervals | Restore a dated copy into a disposable test folder | The backup opens and can be searched and edited without touching production |
| When a job fails | Check destination availability, permissions, space and retention | The next run completes and an older version remains available |
Final checklist
- The most-used desktop or laptop is the designated backup source.
- The source is the complete vault folder, including attachments and, when needed,
.obsidian. - A scheduled job copies one way to a separate drive, NAS or off-site destination.
- Historical versions are retained instead of keeping only a live mirror.
- File recovery is enabled for recent local mistakes, with its five-minute and seven-day defaults adjusted when appropriate.
- Sync is used for multi-device access, not treated as the backup.
- Git, if used, has protected credentials, an appropriate repository privacy setting and a reliable commit/push routine.
- A dated restore has been opened as a separate Obsidian vault and checked.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
