Guides

Sending your own HTML

HTML you paste, upload or write is sent as you wrote it, with one exception: before it leaves, we take out anything that could run code, and anything email apps can’t show. The HTML editor lists what it will take out under your code, and the deliverability check counts the parts your readers would miss.

What we keep

  • Tables, text, links (web, email and phone addresses) and pictures on web addresses.
  • Inline styles, including !important.
  • <style> blocks, with their @media rules, and the class names and ids they select. We send them in the email’s <head>, where Gmail reads them.
  • Blocks only classic Outlook reads (<!--[if mso]>…<![endif]-->), as written: the tables that keep columns in place, rounded buttons and background pictures drawn in VML, and Outlook’s settings.
  • Blocks for every app but classic Outlook (<!--[if !mso]><!-->…<!--<![endif]-->).
  • A page colour set on <body>.

What we remove

  • Scripts and event handlers. Email apps never run them.
  • Forms and their fields. Most email apps can’t send a form. Link to a page with the form instead.
  • Pictures written into the HTML (data: and cid: addresses). Most email apps don’t show them. Upload the picture to your library and use its web address.
  • SVG drawings. Gmail and Outlook don’t show them. Use a PNG or JPEG picture.
  • Video, audio and embedded frames. Email apps don’t play them. Use a picture that links to the video.
  • Image maps. Use separate pictures, each with its own link.
  • Links to stylesheets and fonts, and @import. Most email apps ignore them, and a font request tells the font’s host who opened the email. Your text falls back to the next font in its list.

Your document’s own <html>, <head> and <meta> tags are replaced by ours; what they carry that matters (your styles, your page colour, Outlook’s settings) is kept.

Styles that must show

Put the styles your email can’t do without inline, on the elements themselves, and use a <style> block for responsive rules and finishing touches. Some email apps ignore parts of a <style> block, and some ignore it altogether, but inline styles are the ones every app reads.

HTML from another tool

HTML exported from an email builder (MJML, Stripo, Beefree, Mailchimp, or a Figma plugin such as Emailify or Email Love) can be pasted into the HTML editor as it is: its Outlook blocks and responsive class names are kept. Check the preview and the list under your code before you send, and send yourself a test.

You can also upload it. On New campaign or New template, the HTML door takes an .html file, or the .zip your tool exported. A ZIP’s pictures are added to your picture library, and the email points at them there, so they show in every inbox. A picture the HTML names by a path in a folder, such as images/hero.png, cannot show anywhere else: the deliverability check holds the send until that picture has a web address.

Questions? Ask us.