How to Move a Vault File in Obsidian: What You Need to Know

Obsidian stores everything locally, which gives you real control over your files — but it also means moving things around requires a bit more thought than dragging files in a typical app. Whether you're reorganizing folders, switching devices, or migrating to a new storage location, understanding how Obsidian handles vault files makes the difference between a smooth move and a broken setup.

What Is an Obsidian Vault, Actually?

A vault in Obsidian is simply a folder on your device. Inside it, your notes are plain Markdown (.md) files, and Obsidian stores its configuration in a hidden .obsidian subfolder. There's no proprietary database, no locked file format — just files and folders your operating system already understands.

This matters because it changes how you approach moving things. You're not exporting from a database; you're relocating files your OS already manages.

Moving a Single File Within a Vault

The simplest case: you want to reorganize a note from one folder to another inside the same vault.

You have two reliable methods:

• Within Obsidian's file explorer: Right-click the file in the left panel and select Move file to…. Obsidian will let you choose a destination folder and — critically — will automatically update any internal links pointing to that file.
• Drag and drop in the file explorer panel: Works the same way, with the same automatic link-updating behavior.

The automatic link update feature is important. Obsidian tracks wikilinks ([[Note Name]]) and can update them when a file moves. This only applies to links within the same vault, and it depends on your Files & Links settings — specifically whether "Automatically update internal links" is enabled. Check that setting before moving files if your vault is heavily linked.

Moving Your Entire Vault to a New Location 📁

This is a common need: moving the vault to a different drive, a cloud-synced folder, or a new computer.

Because a vault is just a folder, the core process is straightforward:

1. Close Obsidian before moving anything.
2. Copy or move the entire vault folder using your file manager (Finder, Windows Explorer, etc.) to its new location.
3. Reopen Obsidian and use Open another vault → Open folder as vault, then navigate to the new location.

The .obsidian folder travels with the vault, so your plugins, themes, hotkeys, and settings all come along automatically.

What can break: If you use community plugins that reference absolute file paths, or if you have external application integrations that point to the old location, those references will need updating manually. Most setups don't have this problem, but heavily customized vaults sometimes do.

Moving a Vault to a Cloud Storage Folder

Many users move their vault into a Dropbox, OneDrive, iCloud, or Google Drive folder for cross-device access. Technically this works the same as any folder move — but the variables multiply.

Key considerations:

Obsidian also offers its own Obsidian Sync service, which is designed specifically for this use case and handles conflict resolution differently than third-party cloud storage. Whether that tradeoff matters depends on how many devices you use and how often you edit across them simultaneously.

Moving Files Between Two Separate Vaults

This is where things get more nuanced. If you drag a note from one vault folder into another using your file manager, the file itself moves cleanly — but internal links won't transfer automatically. Wikilinks that referenced other notes in the original vault will become broken links in the new vault unless those notes also exist there.

Steps that reduce friction:

• Move the file using the OS file manager (not inside Obsidian)
• In the destination vault, check the Unlinked mentions or use the broken links checker to identify what needs repair
• If the note uses embedded files (images, PDFs, attachments), those will need to move separately and be relinked

The more interconnected your notes are, the more cleanup work a cross-vault move involves.

The Variables That Determine Your Outcome 🔧

How straightforward any vault file move turns out to be depends on several factors specific to your setup:

• How linked your notes are — A standalone note moves cleanly; a heavily linked hub note creates more post-move work
• Which plugins you use — Some plugins (Dataview, Templater, folder-based plugins) have path dependencies
• Your sync method — Local-only, cloud folder, or Obsidian Sync each behave differently
• Operating system — macOS, Windows, and Linux handle hidden folders and file permissions differently
• Mobile vs. desktop — Mobile vaults have their own folder restrictions depending on the platform

A user with a simple, lightly-linked vault moving to a new local folder has almost nothing to worry about. A user with a large, interconnected vault using multiple community plugins, synced across three devices, faces a meaningfully different set of considerations before moving anything.

Understanding which of those descriptions fits your situation is the part no general guide can settle for you.