Convert a URL to a Markdown link in three steps
Markdown uses [link text](URL) for an inline link. The generator follows the CommonMark link specification and handles the extra formatting needed when a destination contains spaces, parentheses, brackets, or quotes.
Write the clickable text
Use a clear label such as “API reference” or “Download the release” instead of pasting a bare URL when readers need context.
Paste the destination
Enter a web URL, a domain such as example.com/docs, a relative file path, a section anchor, a mailto: address, or a tel: link.
Preview, then copy
Check the rendered link and copy the generated Markdown into the editor, README, issue, post, or notes app where you need it.
Build a batch of Markdown links without formatting each one
The bulk Markdown link generator accepts one entry per line in the format link text | URL | optional title. It skips blank lines, reports incomplete or invalid rows by line number, and combines every valid result into one block you can copy.
Resource lists
Format documentation links, research sources, release notes, or a “Further reading” section in one pass.
README navigation
Mix external project URLs with relative links such as ./CONTRIBUTING.md and anchors such as #installation.
What to paste
Paste plain lines separated with vertical bars. CSV upload and spreadsheet column mapping are not supported. This static browser tool also does not fetch page titles from URLs; automatic title lookup would send each public URL to a separate network service.
Use the same link builder for GitHub, docs, blogs, and notes
The output is standard inline Markdown, so it fits common writing workflows without platform-specific markup. The destination you choose still depends on where the Markdown will live.
GitHub and README files
This link builder works with GitHub and README links to external sites, repository files, and heading anchors. For a heading link, enter the final anchor such as #installation. The tool does not calculate GitHub heading IDs, so use GitHub’s official section-link guidance to copy or verify the generated anchor.
Technical documentation and wikis
Use relative paths when files move together inside the same docs project, and full URLs when the destination belongs to another site.
Reddit, blogs, and Obsidian
Paste the generated inline link where standard Markdown links are accepted. Obsidian wikilinks such as [[Project note]] are a separate format and are not generated here.
Avoid the characters that commonly break Markdown links
Handwritten links often fail because brackets are mismatched, the destination contains spaces or parentheses, or the URL uses an unsupported scheme. The generator escapes link text, encodes spaces, wraps destinations in angle brackets, and rejects executable schemes before producing output. It validates the format, not whether the page exists.
| Situation | Destination entered | Generated destination |
|---|---|---|
| Domain without a scheme | example.com/docs | <https://example.com/docs> |
| URL containing a space | https://example.com/setup guide | <https://example.com/setup%20guide> |
| GitHub or document section | #installation | <#installation> |
| Relative project file | ../docs/start.md | <../docs/start.md> |
| Email link | mailto:[email protected] | <mailto:[email protected]> |
Markdown link generator or URL-to-Markdown converter?
This page creates inline links, reference links, autolinks, and image embeds. It does not fetch a webpage or convert the page’s article content into Markdown, and it does not generate HTML anchor tags or hosted share links.
| Task | Typical syntax | Available here |
|---|---|---|
| Inline link | [Docs](https://example.com) | Yes |
| Reference link | [Docs][ref] | Yes |
| Autolink | <https://example.com> | Yes |
| Image embed |  | Yes |
| Convert webpage content | URL → page as Markdown | No |
Your link text stays in this browser
Link generation, validation, preview, and copying run locally in your browser. The tool does not fetch the destination page, send your entries to a conversion server, or require an account. That makes it practical for formatting public URLs as well as internal relative paths—while also meaning it cannot check whether a destination is live. See the Privacy Policy for the site’s network and data-handling details.
Reviewed against the generator’s actual output
Reviewed and tested by the MarkdownToWord.art team. Last updated: July 16, 2026. The examples on this page are checked against automated tests for URL normalization, optional titles, escaped link text, relative and root-relative paths, heading anchors, email and telephone links, unsafe URL schemes, and line-level bulk errors. To report a correction or an output that behaves differently in your Markdown platform, email [email protected].