Markdown Links

Markdown links allow you to create clickable text that points to another location.

A link usually contains two parts:

1. The text users click
2. The destination URL

Basic syntax

[Link Text](https://example.com)

Example

[MDConvertHub](https://mdconverthub.com)

Output

If you're new to Markdown, start with Markdown Basics — this page focuses only on link syntax.

Inline links are the most common type of Markdown link.

Syntax

[GitHub](https://github.com)

Example

Visit the [GitHub website](https://github.com).

Output

Use inline links whenever you want to place the destination directly beside the text.

Reference links keep documents cleaner, especially when the same URL is used multiple times.

Example

Visit the [documentation][docs].

[docs]: https://mdconverthub.com/docs

This style is commonly used in large README files and long technical guides.

Markdown can automatically convert URLs into clickable links.

Example

<https://mdconverthub.com>

Output

This is useful when you want to display the full URL.

You can also create clickable email addresses.

Example

<support@example.com>

Or

[Email Us](mailto:support@example.com)

When clicked, the user's email application opens automatically.

Relative links point to files inside the same project.

Example

[Installation Guide](docs/installation.md)

GitHub repositories commonly use relative links because they continue working when the project is moved.

You can also link to other guides in this documentation cluster:

[Markdown Lists](/markdown-lists)

Many Markdown platforms automatically generate anchor links for headings.

Example

[Jump to Installation](#installation)

## Installation

This creates quick navigation within long documents. See the Markdown Headings guide for how heading structure affects anchor links.

Images can also be wrapped inside links.

Example

[![Logo](logo.png)](https://example.com)

This technique is often used for badges and clickable logos.

For image syntax on its own, read the dedicated Markdown Images guide.

Follow these recommendations when creating Markdown links.

• Use descriptive link text.
• Avoid generic phrases like "Click here."
• Check that every URL works.
• Prefer HTTPS links whenever possible.
• Use relative links inside repositories.
• Keep link text short and meaningful.

Good

Read the [Installation Guide](/markdown-basics)

Avoid

[Click here](https://example.com)

Try the Markdown Link Checker before publishing long documents.

Missing closing parenthesis

Incorrect

[GitHub](https://github.com

Correct

[GitHub](https://github.com)

Empty link text

Avoid

[](https://example.com)

Instead

[Project Website](https://example.com)

Broken relative paths

Incorrect

[Guide](guide.md)

Correct

[Guide](docs/guide.md)

Always verify the file path before publishing.

Platform	Inline	Reference	Auto Links	Relative Links
GitHub	✅	✅	✅	✅
GitLab	✅	✅	✅	✅
VS Code	✅	✅	✅	✅
Obsidian	✅	✅	✅	✅
Notion	✅	Partial	✅	Limited
Discord	✅	❌	✅	❌

Well-written links improve both readability and navigation.

Try to:

• Link only relevant content.
• Avoid placing several links in one sentence.
• Use clear, descriptive text.
• Regularly check for broken links.
• Organize internal documentation using relative links.

For a compact syntax lookup while you write, keep the Markdown Cheat Sheet open.

Continue learning Markdown with these guides:

Available now

• Markdown Basics — core concepts for beginners
• Markdown Cheat Sheet — quick syntax lookup
• Markdown Syntax — complete reference with examples
• Markdown Headings — document structure with H1–H6
• Markdown Paragraphs — blank lines and spacing
• Markdown Lists — ordered, unordered, nested, and task lists
• Markdown Images — syntax, URLs, alt text, and GitHub paths
• Markdown Tables — syntax, alignment, and GitHub GFM

Coming soon to MDConvertHub Docs

• Markdown Code Blocks

Open the Markdown Editor and experiment with inline links, reference links, relative links, and heading anchors.