User Rating 0.0
Total Usage 0 times
Configuration
Define recipients and content
Separate multiple emails with commas
Advanced Settings
Generated Code
Ready-to-use HTML
Live Preview
HTML Source Copied!
QR Code for Mobile
Generate a link to see QR code
Enter email details to generate
Is this tool helpful?

Your feedback helps us improve.

About

The mailto: URI scheme is the standard method for creating email hyperlinks on the web, defined primarily by RFC 6068. While seemingly simple, improper implementation often leads to broken links, particularly when dealing with special characters, line breaks, or multiple recipients. A robust implementation requires strict percent-encoding of the subject and body parameters to ensure compatibility across diverse clients like Outlook, Gmail, and Apple Mail.

This tool addresses the two most critical failures in email link generation: Character Encoding and Spam Vulnerability. By automatically converting reserved characters (e.g., &, ?, =) into their hexadecimal equivalents and offering HTML entity obfuscation, this generator produces production-grade code that resists scraping bots while maintaining full user accessibility.

email tool html generator mailto spam protection productivity

Formulas

The syntax for a mailto URI is structured as a scheme followed by the recipient path and an optional query string for headers.

URI
mailto:to_addr?headers

Where the headers component is a query string of key-value pairs:

ni=1
keyi=encode(valuei)&

Crucially, the body parameter must treat newlines as the sequence %0D%0A (CRLF) rather than typically ignored encoded whitespace.

Reference Data

CharacterNamePercent-EncodedHTML Entity (Dec)HTML Entity (Hex)
SPACESpace%20
@At Sign%40@@
:Colon%3A::
/Slash%2F//
?Question Mark%3F??
=Equals%3D==
&Ampersand%26&&
LFLine Feed%0A
CRCarriage Return%0D
,Comma%2C,,
%Percent%25%%
<Less Than%3C<<
>Greater Than%3E>>
#Hash%23##
$Dollar%24$$

Frequently Asked Questions

No. The `mailto` URI scheme (RFC 6068) does not officially support the `attachment` parameter due to significant security risks. While some older, non-standard email clients might support it locally, it will fail for 99% of web users (Gmail, Outlook Web, Apple Mail). File transfers should be handled via server-side upload links included in the body text.
This is an encoding issue. Outlook and strictly compliant mail clients require a Carriage Return + Line Feed sequence (`\r\n`) encoded as `%0D%0A`. If you only use `%0A` (Line Feed), some clients render it as a space. This tool automatically forces the correct `%0D%0A` sequence.
It stops simple scrapers. Entity encoding (e.g., converting `@` to `@`) works because the browser renders the symbol visually, but basic HTML parsers see the code, not the address. However, sophisticated bots using headless browsers (like Puppeteer) can still read the decoded text. It is a "speed bump", not a firewall.
It varies by browser and OS, but a safe limit is approximately 2,000 characters. If your generated link exceeds this (e.g., a very long body), it may be truncated or fail to open. For long content, consider using a web form instead.