mailto: Link Builder
Network
The mailto: URI scheme (RFC 6068) is the standard way to make a clickable link that opens the user's default mail client with a pre-filled draft. This tool lets you compose multiple recipients, copy/blind-copy lists, a subject line, and a multi-line body, then assembles the URL with proper percent-encoding for spaces (%20), newlines (%0A), and special characters. You can copy the raw URL, copy a ready-made HTML <a href=…> anchor, or open it directly to see how your default mail client renders the draft. Useful for contact pages, support links, newsletter signup CTAs, structured bug-report templates, and any 'mailto first, web form second' pattern.
mailto:hello%40example.com?subject=Hello&body=Hi%20there%2C%0A%0AI%20wanted%20to%20reach%20out%20about%E2%80%A6%0A%0ABest%2C%0A<a href="mailto:hello%40example.com?subject=Hello&body=Hi%20there%2C%0A%0AI%20wanted%20to%20reach%20out%20about%E2%80%A6%0A%0ABest%2C%0A">hello@example.com</a>Notes
Follows RFC 6068. Multiple recipients are joined with commas. Spaces, line breaks, and special characters in subject/body are percent-encoded (space → %20, newline → %0A). Some mail clients impose URL length limits (Outlook on Windows ≈ 2,083 chars); keep the body short for compatibility.
How to use
- Enter one or more To addresses (use Add to add more rows).
- Optionally add Cc and Bcc recipients.
- Type a subject and a body — newlines and special characters are encoded automatically.
- Copy the mailto: URL, the HTML anchor snippet, or click Open in mail client to test.
- Try the presets (Support, Feedback, Newsletter, Bug Report, Cold Intro) for common templates.
Frequently asked questions
- What's the difference between mailto: and a webmail compose URL?
- mailto: is a standard URI scheme (RFC 6068) that opens whichever mail client the user has set as default — native (Apple Mail, Outlook desktop), Gmail through a browser handler, or anything else. Webmail compose URLs (https://mail.google.com/mail/?view=cm&to=…) are vendor-specific and only work in browsers logged into that service. mailto: is more portable; webmail URLs give you control over which inbox opens.
- Why are line breaks in the body so long in the URL?
- Newlines must be encoded as %0A (3 characters). Each blank line adds 3 chars, and non-ASCII letters/spaces also get percent-encoded (up to 9 chars each in UTF-8). That's why long pre-filled bodies bloat URL length quickly. Some clients (notably Outlook on Windows) cap URLs at ~2,083 characters.
- Can I include HTML in the body?
- No — mailto: bodies are plain text only. Some clients strip HTML tags, others show them literally. Use plain-text formatting (newlines, asterisks, dashes) and let the user enrich the message after their client opens. If you need real HTML, generate an email server-side and send it; mailto: is for kicking off a draft, not formatting it.
- Do all mail clients support cc/bcc/subject/body parameters?
- All four are in RFC 6068 and supported by every major client (Gmail, Apple Mail, Outlook, Thunderbird, mobile). Older corporate clients sometimes ignore bcc, and some mobile clients ignore body if you pass it through certain in-app browsers. Test on the platforms your users actually use.
Related tools
IP Address Inspector
Type an IPv4 or IPv6 address and see its class, scope (private / public / loopback / link-local), decimal value, binary, reverse-DNS notation, and /32 CIDR.
Port Number Reference
Searchable cheat sheet for ~60 standard TCP / UDP port numbers — from 22 (SSH) and 80 (HTTP) to 6379 (Redis) and 27017 (MongoDB).
DNS Record Reference
Searchable cheat sheet for DNS record types — A, AAAA, CNAME, MX, TXT, NS, SOA, PTR, SRV, CAA, DNSSEC, SVCB / HTTPS — with examples.
Subnet Calculator (IPv4 / CIDR)
Parse an IPv4 CIDR into network address, broadcast, netmask, wildcard, host range, and class. Shows binary breakdown and private/public status.
User Agent Parser
Parse a User-Agent string into browser, engine, OS, device, and CPU. Detects 20+ bots including GPTBot, ClaudeBot, PerplexityBot.
HTTP Status Code Reference
Searchable list of every HTTP status code (1xx-5xx) with summary, RFC, when to use, and common pitfalls.