Email to MD Link — Free Mailto Markdown Link Generator

Yes — for personal contact links, READMEs, docs and signatures it is still the simplest way to let someone reach you: one click opens their own mail client, no account or backend needed. Where it shines is pre-filled context: mailto:support@example.com?subject=Bug%20report&body=Hi%20team%2C%0D%0A opens a draft that already says what the email is about, which measurably increases the chance of a useful reply versus a blank compose window. What mailto cannot do is tracking, attachments or spam protection — for those you need a contact form.

Only partially — and any tool that promises otherwise is not being honest. Encoding an address as HTML entities (mailto:...) defeats naive harvesters that regex raw text for name@domain patterns, which still make up a large share of scraping traffic. But any bot that parses HTML can decode entities instantly, and modern scrapers do exactly that. The only strong protection is never publishing the address at all (use a contact form). This tool gives you the honest middle ground: one-click entity obfuscation plus a visible note about its limits.

Intent. Email to MD Link wraps an email address in a mailto: link — [Email us](mailto:hello@example.com) — with optional subject, body, CC and BCC fields. URL to MD Link wraps web addresses — [text](https://example.com) — and deliberately rejects the mailto: scheme, because validating http/https URLs and validating emails are different jobs with different rules. If you need a plain web link, use URL to MD Link; if you need a clickable email, stay here.

Per RFC 6068: recipients go right after mailto:, then fields are joined as ?subject=...&body=...&cc=...&bcc=..., and every value is percent-encoded. A space becomes %20, a comma becomes %2C, an ampersand becomes %26, and line breaks become %0D%0A (the CRLF pair the standard requires). So subject "Bug report" plus a two-line body "Hi team," / "The button is broken." becomes mailto:support@example.com?subject=Bug%20report&body=Hi%20team%2C%0D%0AThe%20button%20is%20broken. — write plain text and let the generator encode it; one unencoded & would silently cut your body in half.

A pragmatic subset of the rules: one @ sign, a dot-atom local part (letters, digits and !#$%&'*+-/=?^_`{|}~), and a dot-atom domain ending in a non-numeric label — support@example.com passes, while missing @, double dots, spaces and numeric-only TLDs fail with a plain-language error. Deliberately rejected are the exotic-but-legal forms: quoted local parts ("a b"@x.com) and IP-literal domains. Those are almost never what you mean when hand-writing a mailto link, and flagging them catches far more real typos than it rejects legitimate addresses.

Yes — switch to the Batch tab and paste one address per line, optionally followed by | and custom link text: a@example.com | Site A on one line, b@example.com | Site B on the next. The subject, body, CC, BCC and obfuscation settings apply to every line, each line is validated independently, and invalid lines are skipped with a report instead of silently producing broken links. The output is a ready-to-paste list of Markdown links.

Because HTML entities are an HTML feature — there is no such thing as an "entity" in Markdown syntax itself, so a Markdown-style [text](mailto:...) link cannot carry them reliably across renderers. Instead the obfuscation mode emits <a href="mailto:...">Email me</a>: browsers decode the entities and the visitor sees a perfectly normal "Email me" link. Inline HTML is valid inside Markdown documents — GitHub, GitLab and most static-site generators render it fine — so you can paste it straight into your .md file.