Guides
YouTube to Obsidian: Building a Video Vault
Obsidian notes are Markdown files in a folder on your disk. That single fact decides most of what is good about keeping video notes there.
A Markdown summary and an Obsidian note are the same object. There is no import, no conversion and no format negotiation — you save the file into the vault folder and it is a note.
That makes Obsidian the lowest-friction destination for exported summaries, and it changes the calculation about whether an archive is worth building. When keeping something costs one file save, keeping everything becomes reasonable.
What owning the files actually buys
"You own your notes" is marketing language until you consider what the alternative fails at.
| Markdown files | Hosted notes app | |
|---|---|---|
| Works offline | Always | Usually partly |
| Searchable by other tools | Yes — grep, Spotlight, anything | No |
| Survives the app shutting down | Yes | Export and hope |
| Version control | Ordinary git | Whatever they built |
| Sync | Your problem | Solved for you |
| Collaboration | Poor | Good |
The last two rows are the honest cost. Obsidian is excellent for one person keeping a long-lived personal archive and mediocre for a team working together, which is the opposite trade-off from a hosted workspace.
The routine
- Summarize the video and export as Markdown.
- Save it into the vault as
Videos/<channel> - <title>.md. - Add frontmatter: the source URL, the channel, the date, and a couple of tags.
- Write two sentences at the top — why you watched it, what you took from it.
- Link it to at least one existing note before you close the file.
Step five is the whole system. A note nothing links to is a note you will never find again, because you will not remember it exists to search for it. The link is what makes the vault a network rather than a directory.
Linking is what makes it compound
The reason to use Obsidian rather than a folder of text files is the links, and the reason links matter for video notes specifically is that videos are where you encounter ideas without context.
A talk mentions an approach you have seen before in a different field. In a folder of files, that connection exists only in your head and evaporates. Linked to the note where you first met the idea, it becomes permanent — and the second time you come across it, the note already has two sources.
After a hundred videos the graph is doing work you did not do deliberately. Opening any concept note shows every video that touched it, which is a literature review you assembled by accident.
The discipline that makes this work is linking to concepts rather than to videos. A note per idea, with videos linking into it, produces a useful graph. Videos linking to videos produces a tangle.
Frontmatter worth having
Obsidian reads YAML frontmatter at the top of a file and makes those fields queryable. Four fields cover almost every question you will later ask.
source — the video URL. Without it the note is orphaned from its evidence.
channel — who made it, which is the proxy for how much you trust it.
watched — the date, which is how you find things by "around when I was working on X".
tags — two or three, not eight. Tags you apply inconsistently are worse than none.
Everything else can live in the body. Frontmatter is for the fields you will filter on, and a field you will not filter on is a field you will stop filling in.
Why plain text is the durable choice
There is a longer-horizon argument for this that goes beyond Obsidian specifically, and it is the reason the format matters more than the app.
Markdown is text with a handful of punctuation conventions. It opens in any editor written in the last forty years and will open in any editor written in the next forty. Nothing needs to still exist for the file to be readable — not Obsidian, not us, not any company.
That is an unusual property. Notes in a hosted workspace depend on that workspace continuing to operate and continuing to offer an export that works. Notes in a proprietary binary format depend on someone maintaining a reader.
Institutions that think about this professionally reach the same conclusion. The UK National Archives' guidance on selecting file formats for long-term preservation favours open, well-documented and widely-supported formats for exactly the reason above: the dependency chain is almost empty.
For a personal archive you intend to still have in ten years, that matters more than any feature.
Where this breaks down
Sync is genuinely your problem. Obsidian sells a sync service and plenty of people use a cloud drive instead. Either works; neither is automatic, and a vault that exists on one laptop is one laptop failure from gone.
Mobile capture is awkward. Watching on a phone and getting a summary into the vault involves more steps than doing it at a desk. In practice most people batch it — summarize on mobile, file it later.
The summary is still a paraphrase. Owning the file does not make its contents verified. Anything you build on needs checking at the timestamp.
Nothing here integrates with Obsidian. There is no plugin from us. The Markdown export is the integration, and it works because both ends speak the same format.
Graph views flatter you. A dense-looking graph is not evidence of understanding. Links made carelessly produce an impressive picture and answer no questions, which is worth remembering when the visualisation starts feeling like the point.
A vault is a long game
Worth setting expectations honestly: this is not useful in month one. Twenty notes with a few links is less helpful than remembering the videos.
It becomes useful somewhere around note one hundred and fifty, when you start finding things you had forgotten you knew, and the graph surfaces connections you would not have made. That is a year of ordinary use for most people.
The implication is that the structure has to be cheap enough to sustain for a year without enthusiasm. Five minutes per video is not sustainable. Ninety seconds — export, save, frontmatter, one link — is. Build the system you will still be doing in month eleven, and the note-taking itself stays the part that deserves your attention.
Frequently asked questions
Is there an Obsidian plugin for this?
Not from us. None is needed — an exported Markdown summary saved into the vault folder is already an Obsidian note, because Obsidian notes are Markdown files.
Do timestamp links work inside Obsidian?
Yes. They are standard Markdown links to a moment in the video and open in your browser, so every section of the note stays one click from its source.
How should I name the files?
Channel first, then title, in a Videos folder. Channel-first sorts related material together and makes the source visible in the file list, which matters when you are scanning rather than searching.
When does a vault start being worth the effort?
Around a hundred and fifty notes, which is roughly a year of ordinary use. Keep the per-video routine under two minutes, because a heavier system will not survive that long.
One file save per video
Export the Markdown, drop it in the vault, link it to something you already know.
Summarize a video — free
