Paste any URL and see exactly which platforms render it as a clickable link, which strip it, and why. Built for the moment a slack:// or obsidian:// link silently fails inside someone else’s tool.
Custom URL schemes like slack://, obsidian://, and zoommtg:// only become clickable when an OS-level handler is registered for them. The browser is fine handing these off to the OS — the problem is upstream: most content platforms (Notion, Confluence, Gmail, GitHub, Linear) sanitize URLs before rendering, and their allowlists rarely extend past https, http, mailto, and tel.
The result: a slack://channel link pasted into a Notion page silently becomes plain text. The link target is intact, but the platform refuses to render it as an anchor. The fix is to wrap the custom scheme inside an https:// URL that handles the redirect client-side — which is exactly what Shortlink does.
Reference table covering common schemes across major content platforms. ✓ = renders as clickable link. ✕ = stripped or rendered as plain text. ~ = partial / depends on client.
| Scheme | Notion | Obsidian | Slack | Gmail | MS Teams | Linear | Confluence | GitHub | Markdown (generic) |
|---|---|---|---|---|---|---|---|---|---|
| slack:// | ✕ | ✕ | ✓ | ✕ | ✕ | ✕ | ✕ | ✕ | ? |
| obsidian:// | ✕ | ✓ | ✕ | ✕ | ✕ | ✕ | ✕ | ✕ | ? |
| zoommtg:// | ✕ | ✕ | ✕ | ✕ | ✕ | ✕ | ✕ | ✕ | ? |
| notion:// | ✕ | ✕ | ✕ | ✕ | ✕ | ✕ | ✕ | ✕ | ? |
| figma:// | ✕ | ✕ | ✕ | ✕ | ✕ | ✕ | ✕ | ✕ | ? |
| vscode:// | ✕ | ? | ? | ✕ | ? | ✕ | ✕ | ✕ | ? |
| linear:// | ✕ | ? | ? | ✕ | ? | ✓ | ✕ | ✕ | ? |
| msteams:// | ✕ | ? | ? | ✕ | ✓ | ✕ | ✕ | ✕ | ? |
| mailto: | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Notion strips non-HTTPS schemes when pasted into pages. Custom scheme URLs render as plain text.
Obsidian renders https:// and obsidian:// links natively but blocks most third-party schemes for security.
Slack auto-links https:// and its own slack:// scheme, but other custom schemes render as plain text.
Gmail web only renders standard HTTP(S), mailto, and tel links. All custom schemes render as plain text.
Teams supports msteams:// deep links but blocks competing custom schemes.
Linear allows HTTPS and its own linear:// scheme. Other custom schemes render as plain text in issue descriptions.
Confluence sanitizes URLs and rejects custom schemes entirely. Wrap them in HTTPS first.
GitHub Markdown only auto-links HTTPS, HTTP, and mailto. Custom schemes are stripped from issue/PR/README rendering.
CommonMark spec only auto-links HTTPS/HTTP/mailto/ftp. Custom schemes work in [label](url) syntax IF the renderer permits them.
Teams across the US East Coast lean heavily on Notion as a central wiki, with Slack as the comms layer. Custom scheme URLs are most often shared inside Notion docs, where they fail silently.
Use case: Wrap your slack:// channel deep links into HTTPS so they survive being pasted into Notion runbooks and onboarding pages.
West Coast product and design teams rely on Figma and Linear daily. Both platforms understand their own deep-link schemes but block competing ones.
Use case: Convert figma:// prototype links into universal URLs you can drop into Linear specs without breaking the click target.
UK teams frequently coordinate across Microsoft Teams, Confluence, and Jira — all of which sanitize non-HTTPS URLs aggressively.
Use case: Embed Zoom and Slack deep links inside Confluence pages and Jira tickets by wrapping the original scheme in a Shortlink.
In German-speaking markets, Confluence and Jira dominate enterprise documentation. Both block custom schemes natively.
Use case: Paste Shortlinks into Confluence pages to give teammates one-click access to Zoom calls or Figma prototypes from your specs.
French product teams often combine Notion with Slack and Figma. Cross-tool linking breaks the moment a custom scheme leaves its native app.
Use case: Generate Shortlinks once and reuse them in Slack, Notion, and email — the same HTTPS link works in every context.
Engineering teams across India frequently ship across time zones, leaning on async tools like Slack, Notion, and GitHub for handoffs.
Use case: Wrap GitHub Desktop and VS Code deep links into Shortlinks so engineers on the next shift can open them directly from a Notion handoff doc.
Tokyo-based teams often pair Slack with Figma and Notion. Sharing prototype links across these tools is common, and equally commonly broken.
Use case: Build figma:// and slack:// deep links once with the Shortlink builder, then reuse them across every internal document.
APAC teams running Atlassian stacks (Jira + Confluence) hit the custom-scheme block almost daily.
Use case: Convert custom scheme URLs into universal HTTPS links once, paste them anywhere, and stop manually re-explaining how to open the app.
Distributed and remote teams across every region run into the same problem: deep links that work in one app break the moment they leave it.
Use case: Use Shortlink to wrap any custom scheme URL into an HTTPS link that works in every tool your team uses.
Notion sanitizes pasted URLs and only renders standard HTTP(S), mailto, and tel links. The slack:// scheme is stripped before the link is rendered, so it shows up as plain text. Wrap the slack:// URL in a Shortlink (https://shortlink.studio/...) and Notion will render it as a clickable link that still opens Slack.
Obsidian renders https://, http://, mailto:, and its own obsidian:// scheme natively. Most other custom schemes (slack://, zoom://, figma://) render as plain text or are blocked. To embed a non-Obsidian deep link, wrap it in a Shortlink first.
A standard https://zoom.us/j/... link works in Notion and opens the meeting in the browser or app. The native zoommtg:// scheme does NOT work — Notion strips it. Use either the HTTPS Zoom URL or a Shortlink-wrapped zoommtg:// URL.
Slack auto-links HTTPS, HTTP, mailto, tel, and its own slack:// scheme. Other custom schemes (obsidian://, notion://, figma://) render as plain text. Wrap them in a Shortlink and they become clickable in any Slack message.
Most email clients (Gmail, Outlook web, Apple Mail) only render HTTPS, HTTP, mailto, and tel links. Custom schemes are stripped or rendered as plain text. The reliable fix is to wrap the custom scheme URL in an HTTPS link via Shortlink — recipients click the HTTPS link and get redirected to the app.
Use the main Shortlink converter to turn any slack://, obsidian://, zoom:// or notion:// URL into a universal HTTPS link.