The BEST Way To Add Media To Your Obsidian Vault // EP 4
Based on FromSergio's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Drag-and-drop media into an Obsidian vault creates embedded previews while storing the underlying files in the vault’s local folder structure, not on Obsidian servers.
Briefing
Obsidian can store media without bloating a vault by combining smart attachment handling, rich embeds for YouTube and tweets, and optional offloading of images to a third-party service. The core workflow is simple: drag media into the vault, let Obsidian create a note for it, and then control where those files land so your file explorer stays clean.
When a screenshot or other image is dragged into an Obsidian vault, it appears inside the note as an embedded preview. Under the hood, Obsidian places the media as its own file alongside the vault’s markdown notes—meaning the actual storage location is wherever the vault lives, not on Obsidian’s servers. To prevent clutter, the transcript recommends creating an “attachments” folder and setting it as the default location for new attachments via Obsidian’s Settings → Files and Links → “default location for new attachments.” After that change, re-dragging the same image results in the attachment being stored in the attachments folder rather than appearing in the root of the vault. A further refinement is nesting attachments inside an existing folder like “journal,” so the attachments directory stays out of sight during everyday note-taking.
For video and social content, the workflow shifts from file storage to embedding. YouTube videos can be added by using the Share → Embed option, copying the embed code, and pasting it into Obsidian in preview mode so the video renders directly in the note. For timestamped note-taking while watching, a Chrome extension called “world brains” (spelled “world brains max” in the transcript) adds a sidebar and lets users insert clickable timestamps during playback. Those timestamped notes are then copied back into Obsidian, where selecting a timestamp jumps to the corresponding moment in the browser video.
Tweets can also be embedded, but the transcript distinguishes between single tweets and long threads. One approach uses an “embed tweet” option that generates code for a single post, though the result is described as visually unappealing. Another uses “twit frame,” where the embed source code is pasted into Obsidian and the tweet URL is swapped to display a specific tweet more cleanly. For threads, embedding may only capture one tweet, so the recommended workaround is to take a long scrolling screenshot of the entire thread using CleanShot X’s scrolling capture feature, then paste that image into Obsidian.
Finally, the transcript addresses the storage problem head-on: uploading lots of media can overwhelm free cloud plans. A community plugin called “imager” offers a free way to upload images (and small videos) without consuming vault storage. After installing and activating the plugin, users authenticate with an Imager account and choose to upload content to Imager. The media then appears in Obsidian preview while being hidden from public view in the Imager account, and the files are not deleted—just offloaded—helping preserve storage space in the vault.
Cornell Notes
Obsidian media management can be kept tidy and storage-friendly by combining three tactics: (1) drag-and-drop attachments with a dedicated default folder, (2) embed rich content like YouTube videos and tweets using copy/paste embed code, and (3) offload images to Imager via a community plugin to avoid vault storage growth. For attachments, setting Settings → Files and Links → “default location for new attachments” to an “attachments” folder prevents clutter in the vault root. YouTube embeds use Share → Embed code, while timestamped note-taking can be done with a Chrome extension that inserts clickable timestamps. Tweets can be embedded cleanly for single posts (e.g., via twit frame), but long threads may require a scrolling screenshot workflow (CleanShot X) or other workarounds. Imager reduces storage pressure by uploading media externally while keeping it viewable in Obsidian.
How does Obsidian store media when an image is dragged into a vault, and why does that matter?
What’s the practical way to stop attachments from cluttering the vault root?
How are YouTube videos embedded in Obsidian, and how can notes be tied to timestamps?
What are the two main approaches for embedding tweets, and how do they differ for threads?
How does Imager help avoid vault storage limits, and what does the plugin do?
Review Questions
- What Obsidian setting controls where new attachments are stored, and how would you configure it to keep your vault root clean?
- Why might embedding a long Twitter thread fail in Obsidian, and what alternative workflow is recommended?
- How does the Imager plugin change the storage behavior of images added to an Obsidian vault?
Key Points
- 1
Drag-and-drop media into an Obsidian vault creates embedded previews while storing the underlying files in the vault’s local folder structure, not on Obsidian servers.
- 2
Create an “attachments” folder and set it as the default location for new attachments to prevent clutter in the vault root.
- 3
For YouTube, use Share → Embed code and paste into Obsidian preview mode to render the video inside notes.
- 4
Use a timestamp-capable Chrome extension (world brains max) to capture notes tied to specific moments and then paste them back under the embedded video.
- 5
Embed single tweets using embed code (e.g., via twit frame), but handle long threads by taking scrolling screenshots with CleanShot X when embedding only captures one post.
- 6
If storage limits are a concern, install the Imager community plugin and authenticate to upload images externally while keeping them viewable in Obsidian previews.