Mailto link generator
An email link that
opens filled in.
A mailto link generator turns an address, a subject and a message into one link that opens a new email, with those parts already filled in, in the visitor’s mail program. Fill in the form, copy the link or the HTML, and test it. Spaces, line breaks and symbols are encoded the way RFC 6068 describes, which is the part that is easy to get wrong by hand.
It runs in your browser and nothing you type is sent to us. A mailto link needs the visitor’s own mail program, so when a contact form is the better choice is further down.
By the Builderify team
One address or several, separated by commas. Leave it empty for a “share by email” link.
The draft it should open
- To
- hello@yourbrand.com
- Subject
- Quote request
Hi, I'd like a quote for the spring & summer package. Thanks,
- i Every address in the link can be harvested from your page by anyone or anything that reads its source. RFC 6068 section 7 says so about all mailto links on public pages.
Already have a mailto link? Take it apart
How a mailto link
is put together.
A mailto link is the word mailto:, then the address, then any extra fields written like a web address’s query. RFC 6068 requires programs to handle the subject and the body, and promises nothing for the other fields, so test Cc and Bcc in the programs your visitors use.
| Part | Written as | What it does |
|---|---|---|
| mailto: | mailto:chris@example.com | Starts every link. It tells the browser to open an email program rather than a page. |
| The address | chris@example.com | The To line. Several go in one list, separated by commas. It is optional: with nothing after mailto: the draft opens with nobody in the To line. |
| ? | ?cc=bob@example.com | Comes once, before the first field. Every field after it is joined with &. |
| & | &subject=Quote%20request | Goes between fields. Using ? twice is the mistake RFC 6068 marks as wrong. |
| cc= and bcc= | cc=bob@example.com | Copies. The RFC says the values do not necessarily end up as headers in the draft, so a program may ignore them. |
| subject= | subject=Quote%20request | The subject line. Programs must handle this one. |
| body= | body=Hi%2C%0D%0AThanks | The message text: plain text, meant for short messages. Programs must handle this one too. |
From RFC 6068, sections 2 to 4 and 6.1, and MDN’s page on email links.
Characters that
need escaping.
A link cannot hold a raw space or a raw line break, and some symbols already mean something inside it. Each one is written as a percent sign and two hexadecimal digits, which is what the generator does for you.
Type your subject and message as plain text. Pasting text that is already encoded would encode its percent signs a second time, the double-escaping that RFC 6068 section 7 warns about.
- A space
- %20
- Not +. A + standing for a space cannot be told from a real +, so RFC 6068 says to write %20.
- A line break in the body
- %0D%0A
- The RFC says line breaks in the body must be written this way, and should not be used in other fields.
- &
- %26
- It separates fields, so it has to be written out when it is part of your text, as in "spring & summer".
- ? and =
- %3F and %3D
- Also delimiters. They are encoded when they are part of the text.
- #
- %23
- The RFC says a # in a field value must be escaped as %23.
- %
- %25
- The escape character itself.
- +
- %2B
- The RFC says a + may be encoded, and addresses use it for sub-addresses (bill+ietf@example.org). This tool always does.
- é, ü, emoji
- UTF-8 bytes, such as %C3%A9 for é
- Non-ASCII text is turned into UTF-8 bytes and each byte is percent-encoded.
- & inside HTML
- &
- In an HTML page the & between fields is written &, which is why the HTML snippet differs from the plain link.
From RFC 6068, sections 2, 5 and 6. The generator percent-encodes every character other than letters, digits and - . _ ~, and in an address also leaves ! $ ' ( ) * as the RFC’s own examples do. That is more than the RFC strictly needs, and any program that reads the link decodes it.
How to use the
link you made.
Use the HTML where you can paste code, or the plain link where an editor asks for a link address. The two differ in one way: the HTML writes each & as &.
The snippet is a normal anchor element, <a href="mailto:…">. MDN uses the same form to show a link that opens the visitor’s email program. The ampersands are already written as &, as RFC 6068 says an HTML page needs.
Use the whole line that starts with mailto:. Then open the page and click it: editors differ in what they do with a link they did not make themselves, and only a test shows it.
MDN says the content of a link should show where it goes, even out of context. “Email sales” says it; “click here” does not. If you can, write the address in the text as well, so a visitor with no mail program set up can still copy it.
The draft is built by whichever program their system uses for email, so click the link on a phone and in a second browser as well, send one to yourself, and look at what arrives.
What a mailto link
cannot do.
None of these is a bug in a link; they come with the scheme. Knowing them tells you when a link is enough and when it is not.
It needs the visitor's own mail program
The link only hands a draft to whatever program the visitor's system uses for email. MDN calls it a link that opens in the user's email program, and RFC 6068 says opening it does not cause an immediate interaction with a server.
It cannot attach a file
RFC 6068 has no field for attachments. It says a link's creator can only count on the subject and the body being understood.
It cannot fill in a name or address
The RFC says there is no way to substitute variables, so a link cannot put the visitor's own address into the message.
Your address is public
The RFC says mailto links on public pages expose addresses for harvesting, Bcc addresses included.
You never learn whether it was sent
The RFC describes the program creating a message that the user can edit, send, or choose not to send. Opening the link sends nothing to your site.
Long messages make long links
The body is described as primarily for short messages, and every character of it sits in the link.
Why a mailto link
does nothing.
A mailto link opens the draft in whichever program the visitor’s browser and system have set for email links. If nothing opens, either the link is malformed or that setting is empty or pointing somewhere unexpected.
It must start with mailto:, use ? once before the first field and & between the rest. RFC 6068 shows a link with two question marks and marks it wrong. The generator never makes that mistake; a hand-edited link can.
In a page’s HTML source, the & between fields is written &. The HTML from this tool already does that.
A college IT guide gives the settings: on Windows 11, Default apps, then a search for MAILTO; on macOS, Mail, Settings, General, Default email reader. For webmail it shows Chrome’s chrome://settings/handlers page and Firefox’s Applications settings, where mailto is listed. It also says Safari does not natively support webmail handlers for mailto links.
If it works in one place and not another, the link is fine and the setting is the cause. That is a fact about the visitor's system, and a reason to show the address in plain text next to the link.
The settings steps are Pima Community College’s IT guide, read on 20 November 2026; menus change between versions of each system.
When a form is
the better answer.
A mailto link is right for a small site where the owner reads their own mail, and for a “share by email” link. It is the wrong tool when you need to know a message arrived, or when visitors do not have a mail program set up.
| Mailto link | Contact form on the page | |
|---|---|---|
| Needs a mail program | Yes: the draft opens in the visitor’s own program. | No: the visitor types into the page. |
| Where a message goes | From the visitor’s mail account to the address in the link, if they send it. | The Bubble’s Contact Form block takes name, email and message straight into your leads, and the Inbox receives messages from the widget’s contact form. |
| Do you know it was sent | No: the visitor may edit it, send it or close it. | A message that arrives is in your leads. |
The contact page guide covers what to put on the page, and why a WordPress contact form does not send email is for a form that has stopped delivering. Builderify is free to start, with 250 free credits a month and no monthly fee: see pricing.
Start freeMailto links, before you ask.
Write mailto: and the address, then ? and subject=, then & and body=, with each space written as %20 and each line break as %0D%0A. For example, mailto:hello@yourbrand.com?subject=Quote%20request&body=Hi%2C%0D%0AThanks. The generator does the encoding: fill in the To, Subject and Message boxes and copy the link. Cc and Bcc are added the same way, as cc= and bcc=.
Write it as %0D%0A. RFC 6068 says line breaks in the body must be encoded this way, and that they should not be used in other fields, such as the subject. In the generator, press Enter in the Message box and it writes the %0D%0A for you.
Not reliably. RFC 6068 has no field for attachments, and it says the creator of a link can only expect a program to understand the subject and the body. To give visitors a file, link to it as a download on your own site instead.
A mailto link only hands a draft to whichever program the visitor's browser and system use for email links, so it can open an unexpected program, or none, if that setting is missing or points elsewhere. First check that the link starts with mailto:, uses one ? and then & between fields, and that your HTML writes each & as &. Then check the default mail program on that computer or phone: the section above lists where a college IT guide says to find it on Windows 11, macOS, Chrome and Firefox.
It is not private. RFC 6068 says mailto links on public web pages expose addresses for harvesting, and that this includes addresses in a Bcc field. If you do not want your address collected from the page, use a contact form instead.
It makes one standard mailto link. RFC 6068 defines the scheme for every program, with no Gmail version and no Outlook version. What opens depends on the visitor's settings: someone who has told their browser to hand email links to Gmail gets a Gmail draft, and someone else may get a desktop program.
No. The link is built in your browser and nothing you enter leaves the page.
Sources
Every page above was opened on 20 November 2026. RFC 6068 is dated October 2010 and is the current definition of the scheme; the settings steps in section 05 are a third party’s and are not tested here. The comparison table’s Builderify column comes from the Bubble and Inbox module pages. ← All free tools
More on customer support
All support guides- Contact Us Page Examples: What to Put On It What to put on a contact us page: the channels you can answer, hours, reply time, a short accessible form, five annotated examples and a free page builder.
- WordPress Contact Form Not Sending Email? Find the Cause WordPress contact form not sending email? Check the To address, put your own domain in From, add SPF and DKIM, then send via SMTP. Free diagnoser inside.
- How to Set Up a Shared Inbox for a Small Business Set up a shared inbox for support@: Google Workspace, Microsoft 365 and Gmail steps, a setup picker, and the rules that stop two people answering one email.
- Customer Service Email Templates for 14 Situations Free customer service email templates for 14 situations, from refunds and delays to angry customers. Pick a tone, add your details, copy the reply.
Stop losing the visitors
you already paid for.
More leads from the traffic you already have, and follow-up that sends itself. Free to start. No card, no monthly fee.