What is Slack's equivalent of a Markdown link?

Use ` `, such as ` `. Use ` ` when you want the full address displayed.

Can I use `[label](url)` directly in Slack?

Slack does not use that standard Markdown form as its documented link syntax. Convert it before posting if you need a labeled link.

Why did Slack show a link preview?

Slack may fetch preview information for some URLs. Workspace settings and the destination site's response can affect whether a preview appears.

Does link formatting bypass document permissions?

No. Formatting only changes appearance. The destination still enforces its own authentication and access rules.

How to Format Links in Slack

Slack uses angle brackets for links rather than standard Markdown link syntax. Convert `[Project brief](https://example.com/brief)` to `<https://example.com/brief|Project brief>`. The URL comes first, followed by a vertical bar and the visible label. For a bare link, use `<https://example.com/brief>`. Slack may also generate a link preview, depending on workspace settings and the destination. A Markdown-to-Slack converter can rewrite links while preserving labels, but you should verify escaped characters, tracking parameters, and access permissions before posting. Never treat a visible label as proof that the destination is safe or available to every reader.

Convert the link structure correctly

Standard Markdown places the label in square brackets and the URL in parentheses. Slack's documented message syntax places the URL inside angle brackets. Add a vertical bar before the optional label. The basic conversion is `[Release notes](https://docs.example.com/release)` to `<https://docs.example.com/release|Release notes>`. The label is what most readers see in the message. Keep it specific, such as `Release notes` or `Incident ticket`, instead of using vague text such as `click here`. If the URL contains characters that interact with Slack formatting, inspect the generated value. Preserve the complete destination, including its path and any required query string.

Handle plain URLs and previews

Use `<https://example.com>` when the full URL should be visible. This form can help readers identify the destination, but long URLs reduce readability. A labeled link is usually better for routine updates. Slack can show a preview for some shared URLs. The preview is separate from the link text and can depend on workspace configuration, the target site's response, and whether Slack can retrieve page information. Do not rely on a preview as the only explanation. Add context in the message, especially when the link opens a dashboard, approval request, or private ticket. Remove unnecessary tracking parameters when policy permits, but do not remove parameters required for authentication or routing.

Review permissions and special link cases

Formatting changes how a link appears, not who can open it. A private document can still return an access error to a channel member. Check the destination permission model before posting. For Slack mentions and special references, use the syntax documented for the relevant Slack surface rather than assuming ordinary Markdown rules apply. A Markdown converter should not turn every bracketed expression into a link. It should recognize valid protocols, preserve intentional text, and leave malformed destinations visible for review. After conversion, test the label, destination, punctuation, and preview in a low-risk channel. This review catches copied quotation marks, missing schemes, and links that point to the wrong environment.

How do you do it step by step?

1Find each Markdown link in the source and separate its label from its destination URL.
2Convert the pair to `<URL|Label>`, or use `<URL>` when the full address should remain visible.
3Check the protocol, path, query parameters, and punctuation around the converted link.
4Confirm that the destination grants access to the intended Slack audience.
5Post a test message, inspect any preview, and correct the text before publishing the final update.

Working example

This example changes two common Markdown link forms into Slack message syntax.

Input

[Runbook](https://docs.example.com/runbook)\nhttps://status.example.com

Result

<https://docs.example.com/runbook|Runbook>\n<https://status.example.com>

The link format does not change destination permissions. Readers still need access to private pages.

Frequently asked questions

What is Slack's equivalent of a Markdown link?: Use `<URL|Label>`, such as `<https://example.com|Example site>`. Use `<URL>` when you want the full address displayed.
Can I use `[label](url)` directly in Slack?: Slack does not use that standard Markdown form as its documented link syntax. Convert it before posting if you need a labeled link.
Why did Slack show a link preview?: Slack may fetch preview information for some URLs. Workspace settings and the destination site's response can affect whether a preview appears.
Does link formatting bypass document permissions?: No. Formatting only changes appearance. The destination still enforces its own authentication and access rules.