Markdown · <code>[text](https://example.com)</code>
Links
Inline, reference and automatic links connect text to a URL.
Key facts
| Inline | <code>[text](https://example.com)</code> |
|---|---|
| Title | <code>[text](url "title")</code> |
| Reference | <code>[text][id]</code> plus a definition |
| Autolink | <code><https://example.com></code> |
| Angle brackets | Required when the URL contains spaces |
| Standard | CommonMark §6.3, §6.5 |
Inline and reference forms
An inline link puts the destination in parentheses immediately after the text. An optional title follows in quotes and becomes the tooltip. Reference links keep the destination in a separate definition, which is useful when the same URL appears many times or when the prose should stay readable.
Reference identifiers are case-insensitive and collapse whitespace. A missing definition means the text renders literally, brackets and all — a common cause of broken documentation after a refactor.
Autolinks and escaping
Angle brackets around a URL create a link without separate link text. GFM also auto-links bare URLs in text, but that is an extension; plain CommonMark does not. Spaces or parentheses inside a destination need angle brackets or percent-encoding.
Rendered links are a security boundary. A previewer that accepts untrusted input must allow only safe schemes and add rel="noopener" when opening new tabs.
Frequently asked questions
Why is my reference link showing brackets?
The definition is missing or its id does not match. Definitions can appear anywhere in the document.
Are bare URLs linked automatically?
In GFM, often yes. In strict CommonMark, only angle-bracket autolinks are guaranteed.