Get AI summaries of any video or article — Sign up free
How To Use Obsidian: The Power Of Linking OUTSIDE Of Your Obsidian Vault thumbnail

How To Use Obsidian: The Power Of Linking OUTSIDE Of Your Obsidian Vault

5 min read

Based on Obsidian Explained (No Code Required)'s video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Hookmark is a Mac-only tool that enables clickable links to files without duplicating them into an Obsidian attachments folder.

Briefing

Linking documents and other computer items outside an Obsidian vault without duplicating files is the core payoff: Hookmark creates links that stay functional even after files move across folders or even outside the vault. That directly answers the common complaint that Obsidian links break when attachments are relocated, and it offers a workflow where Obsidian becomes a metadata-rich index for anything on a Mac—without forcing users to keep everything inside an “attachments” folder.

The setup starts with Hookmark, a Mac-only tool. After installing it and granting permissions, users can open an Obsidian note and create a link to a PDF (or other file) directly from Finder into the note. The usual Obsidian approach—dragging the file into the vault and then deleting the original—either duplicates content or risks breaking references if the file is moved later. Hookmark changes that by letting users keep the file where it already lives while still creating a clickable link inside Obsidian.

A key limitation appears immediately: embedding may not work as expected, even after installing an Obsidian community plugin via Community plugins → Advanced URI. Still, clicking the link to open the file works, which is enough to make the system useful. The bigger challenge is file mobility: out-of-the-box Hookmark links are described as static, meaning moving files can break them. The fix is to use Hookmark’s “advanced” tracking commands through Terminal. Users copy a command from Hookmark’s advanced instructions and paste it into Terminal. Then they switch to the “hook file version” command so Hookmark can track the file’s location dynamically.

Once that advanced configuration is in place, links behave more like Obsidian’s internal linking: when a linked file is moved in Finder to a different directory, the link remains up to date because Hookmark tracks where the file went. The result is a practical hybrid workflow—Obsidian stores the context (notes, metadata, and memory cues), while the actual files can remain in their original or preferred locations across the operating system.

Hookmark’s usefulness extends beyond PDFs and images. It can link to email items, capturing details like subject and sender/recipient information and jumping directly to the specific email (including within a thread). The transcript contrasts this with the clunkiness of manually copying email text or screenshots to create “links” that don’t truly point to the underlying item.

Finally, Hookmark can create new Obsidian notes from linked items. Users can set Obsidian as the default target in Hookmark settings so “hook to new” opens in Obsidian rather than Apple Notes, reducing friction. The overall message is that this tool makes Obsidian a cross-system linking layer for files, folders, and emails—without duplication—at the cost of a one-time Terminal configuration and some workflow quirks around embedding and note creation naming.

Cornell Notes

Hookmark turns Obsidian into a flexible index for items stored anywhere on a Mac, not just inside the Obsidian vault. Instead of duplicating PDFs or breaking links when files move, Hookmark can track a file’s location so links remain clickable even after the file is moved across folders or outside the vault. Achieving reliable tracking requires an advanced setup step using Terminal commands, because the default configuration can be static. Once configured, users can link not only documents but also emails down to specific messages within a thread. The payoff is less duplication, fewer broken references, and richer “memory cues” stored in Obsidian while the real files stay where they belong.

Why do Obsidian links often break when attachments are moved, and how does Hookmark address that?

The typical workflow pushes files into an Obsidian vault (often an attachments folder) so links reference a stable location. If the file is later moved, a static file-path link can break. Hookmark addresses this by tracking the file’s location behind the scenes. After applying the advanced “hook file version” Terminal command, the link stays functional even when the file is moved to a different directory or even outside the vault.

What’s the practical difference between “embedding” and “linking” in this workflow?

Embedding may not work as expected: even after installing the required Obsidian community plugin (via Community plugins → Advanced URI), the PDF didn’t embed in the note. The workflow still works because the link remains clickable—opening the PDF when selected—so users get navigation without relying on embedded previews.

What advanced step is required to make Hookmark links update after file moves?

Hookmark’s default behavior can be static and won’t automatically update when files move. The fix is to use the advanced tracking commands provided in Hookmark’s instructions: copy the appropriate command and paste it into Terminal. The transcript specifically calls out using the “hook file version” command so Hookmark can track files across vault-to-vault moves and vault-to-non-vault moves.

How does the workflow extend beyond files to emails?

Hookmark can create links to email items directly, pulling in key metadata such as subject and sender/recipient details. Clicking the link jumps to the specific email, including the correct thread context. This avoids the usual workaround of screenshotting or copying/pasting email text into Obsidian.

How can users make “hook to new” create notes in Obsidian instead of Apple Notes?

In Hookmark settings, users can change the default target under the Notes header to “Obsidian.” After that, using Hookmark’s “hook to new” creates a new Obsidian page/note from the linked item. The transcript notes that the generated filename can be awkward, so some users prefer creating direct links from Finder instead.

Review Questions

  1. What problem does the advanced Terminal configuration solve, and what symptom indicates it’s needed?
  2. Describe the workflow difference between duplicating files into an Obsidian attachments folder versus linking to files stored elsewhere.
  3. Which types of items can Hookmark link to besides PDFs, and what benefit does that provide compared with manual copy/paste?

Key Points

  1. 1

    Hookmark is a Mac-only tool that enables clickable links to files without duplicating them into an Obsidian attachments folder.

  2. 2

    Out-of-the-box linking may be static; advanced tracking requires Terminal commands to keep links working after files move.

  3. 3

    After the “hook file version” setup, links remain valid when files move between folders, between vaults, or outside the vault entirely.

  4. 4

    Embedding may not work reliably, but opening linked files still works even when previews fail.

  5. 5

    Hookmark can link to emails, capturing details like subject and sender/recipient info and jumping to the correct message/thread.

  6. 6

    Hookmark settings can route “hook to new” into Obsidian (instead of Apple Notes) to streamline note creation from linked items.

  7. 7

    Hookmark’s value is using Obsidian as a metadata-rich index while keeping the actual files in their preferred OS locations.

Highlights

Hookmark keeps Obsidian links alive even after files move—solving the “don’t move it or the link breaks” problem.
A one-time Terminal setup (“hook file version”) is the turning point from static links to location-tracking links.
Beyond PDFs, Hookmark can link directly to emails, including thread-specific navigation.
Setting Obsidian as the default target makes “hook to new” create notes in Obsidian instead of Apple Notes.

Topics

Mentioned