Obsidian as Your Default Markdown App: Opening Files Outside the Vault

For most of Obsidian's life, double-clicking a stray README.md was a small act of betrayal. Obsidian was the best Markdown app on your machine, and it flatly refused to open a Markdown file unless that file lived inside a vault. So the README in a cloned repo, the changelog in a downloaded zip, or the notes file a coworker sent you all went to a text editor, a browser preview, or VS Code. The feature request asking for this is one of the oldest threads on the forum and runs to nine pages.

Obsidian 1.14 fixes it. The October 5 public release lets you open individual Markdown files from anywhere on disk, register Obsidian as your system's default .md app, and (on macOS) preview Markdown in Finder with Quick Look even when Obsidian is closed. It is desktop only, and there is one catch that will trip up a lot of people, so let's start there.

Get the New Installer First ​

The in-app updater is not enough. File associations and the Quick Look extension live in the installer, and the changelog is explicit that opening Markdown files "requires the latest installer." If you have been accepting in-app updates for months, you are probably on an old installer even though the app itself reports 1.14.

Download a fresh copy from obsidian.md/download and reinstall over the top. Your vaults and settings are untouched. As of 1.14, Settings → General also shows a notice when a newer installer is available, so you will know next time without guessing.

Three Ways In ​

Once you're on the new installer, there are three entry points.

The command palette. Run Open file from outside the vault…, pick a Markdown file, and it opens as a tab in your current window, next to your regular notes. This is the one to bind to a hotkey (Settings → Hotkeys, search "outside") if you read a lot of repo docs.

Open with. Obsidian now registers itself with the operating system, so it shows up in Finder's or Explorer's Open with menu for .md files.

Make it the default. On macOS, select any .md file in Finder, press Cmd+I, choose Obsidian under Open with, and click Change All…. On Windows, right-click a Markdown file, choose Open with → Choose another app, pick Obsidian, and tick "Always". If you manage your Mac from dotfiles, the third-party duti tool does the same thing from a script:

# Make Obsidian the default handler for Markdown (macOS, requires: brew install duti)
duti -s md.obsidian net.daringfireball.markdown all

# Confirm it took
duti -x md

Quick Look needs no setup beyond the installer. Select a Markdown file in Finder and press Space to get a rendered preview instead of raw text. From a terminal, qlmanage -p README.md opens the same preview, which is handy for checking a doc before you commit it.

What Works on a File That Isn't in a Vault ​

A stray file is not a vault note, and the release notes are careful about what carries over. The ones you will actually notice:

• Relative paths resolve from the file's own folder. Image embeds and links to other local files are resolved relative to the Markdown file, which is exactly how GitHub and most static site generators treat them. A typical repo README renders correctly:

# my-project

![Architecture diagram](docs/architecture.png)

See the [contributing guide](CONTRIBUTING.md) and the
[API reference](docs/api.md) before opening a PR.

• Outline and Outgoing links work. The core Outline view gives you a heading tree for long docs, and Outgoing links lists the local files the document points to. For a sprawling docs/ folder, that pair is a decent way to navigate.
• It is not indexed into your vault. The file is opened, not imported. Don't expect it in vault search, in backlinks, in the graph, or in a Base. If you want any of that, move the file into the vault.
• Clicking an external .md link still uses the OS default. A file:/// link inside one of your notes is handed to whatever app the operating system picks, not the "open from outside" path. A forum request asks to change that; until then, setting Obsidian as the system default is the workaround.

The changelog describes all of this as viewing the file in the app. Treat it as a reader for Markdown that lives elsewhere, and keep anything you want to write, link, and query inside the vault where Obsidian can see it.

Where It Fits ​

This closes a gap rather than changing how a vault works, and that is the right size for it. For developers it means repo docs, design notes, and ADRs render in the same app, with the same theme and CSS snippets, as everything else you read all day. For everyone else it means the "where do I open this .md file" question finally has one answer.

Grab the new installer, set Obsidian as your default for .md, and press Space on the next README you download. If you already script your vault with the Obsidian CLI, this is the other half: Obsidian is now the Markdown app for files both inside the vault and out.