Free · No tracking · Open source

Obsidian links that actually work in chat.

A tiny redirector that turns vault and file query parameters into obsidian:// deep links — so notes you paste into Slack, WhatsApp, Telegram or email open in one tap.

Convert a link → Get the agent skill
Bytes shipped~3 KB
Servers0
TrackingNone
CostFree, forever
link converter · live
ready
obsidian://
https://
try:
How it works

One redirect.
Zero magic.

obsid.net is a static page with a single job: read your vault and file query params and bounce the browser to an obsidian:// URI. No server, no database, no cookies.

01You paste in chat
https://obsid.net/?vault=Obsidian&file=Sites%2FJoost.blog%2FPosts
tap→
02obsid.net redirects
// 302 Location:
obsidian://open?vault=Obsidian&file=Sites/Joost.blog/Posts
open→
03Obsidian opens the note
// vault: Obsidian
// file: Sites / Joost.blog / Posts
Use cases

Made for notes that travel.

Every messenger, mail client and project tool sanitises unfamiliar URI schemes. obsid.net wraps your obsidian:// link in plain HTTPS so it survives the trip and still opens in the app on the other end.

Share clickable notes

Paste an obsid.net link into any chat. Recipients tap it, the redirect fires, and Obsidian jumps to the exact note — no copy-pasting paths.

SlackWhatsAppTelegramiMessage

Agent-safe note links

Let Codex, OpenClaw or Claude Code emit canonical, paste-ready links in their reports and task updates — never a malformed deep link.

CodexOpenClawClaude Code

Convert what you already have

Got a backlog of obsidian://open?… URIs in old notes or emails? Run them through the converter and replace them in place.

EmailNotionJiraLinear
Agent skill

Teach your agent to link properly.

Drop the obsid-link-builder skill into Codex, OpenClaw or Claude Code so they emit canonical obsid.net URLs whenever they reference a note.

SKILL.mdobsid-link-builder · 2.1 KB
Download ↓
build_obsid_link.shhelper script · 0.8 KB
Download ↓ 
mkdir -p "$CODEX_HOME/skills/obsid-link-builder/scripts"
curl -fsSL https://obsid.net/skills/obsid-link-builder/SKILL.md -o "$CODEX_HOME/skills/obsid-link-builder/SKILL.md"
curl -fsSL https://obsid.net/skills/obsid-link-builder/scripts/build_obsid_link.sh -o "$CODEX_HOME/skills/obsid-link-builder/scripts/build_obsid_link.sh"
chmod +x "$CODEX_HOME/skills/obsid-link-builder/scripts/build_obsid_link.sh"
Bash · ~/.codex/skills/obsid-link-builder
FAQ

Quick answers.

Anything else? Open an issue on the GitHub repo — it's just a static page, contributions welcome.

Do you log my links or vault names?
No. obsid.net is a static page served from a CDN — there's no server-side logic to log against. Conversion happens in your browser; the redirect is a plain client-side location.replace().
What happens if Obsidian isn't installed?
The browser tries the obsidian:// URI and falls back to a "couldn't open" prompt. obsid.net itself doesn't block — it just hands the URI to the OS, same as if you'd clicked it directly.
Can I self-host this on my own domain?
Yes. The whole project is open source on GitHub. Fork it, deploy the static files anywhere (Netlify, Pages, S3 + CloudFront), and point your domain at it.
Why not just paste obsidian:// directly?
Most chat apps either strip non-http schemes, render them as plain text, or refuse to make them tappable. Wrapping in HTTPS keeps the link clickable on mobile and desktop alike.
Does this work with Obsidian Sync vaults?
Yes — the redirect doesn't care how the vault is stored, only that Obsidian can resolve the vault name on the recipient's machine. If the same vault is open there, the link opens.