Use your own HTML

Templates & contentUpdated

Paste or write a full HTML email in the source view, and know what EmailFig silently strips out of it on every save.

The HTML editor’s source view accepts a complete HTML document (doctype, <head>, <style> block, <body>) so you can paste in an email exported elsewhere or write one by hand. Stored HTML is capped at 1MB per template.

Use it

  1. Open a template with the HTML editor and click the </> button (“Edit HTML source”) next to the toolbar.
  2. Paste or type your document.
  3. Toggle back to the visual view to check it renders, then save.

The HTML editor with the source view open, showing a complete document: a doctype, a head block with a style block inside it, and the body below.

Every save quietly runs your HTML through EmailFig’s sanitiser. There’s no warning or diff; the cleaned-up version is just what gets saved. On every save it strips:

  • <script> tags and inline event handlers (onclick, onload, and the like), entirely.
  • Dangerous CSS inside <style> blocks and style attributes: expression(), javascript:/vbscript: URLs, -moz-binding, @import, and IE’s behavior:.
  • Any src, background or poster URL that isn’t http:// or https://, including anything pointing at localhost or an internal/private address.

If a tracking snippet or a javascript: link you pasted in has vanished after saving, this is why.

What’s kept

The sanitiser is generous about everything email actually needs and nothing else: presentational attributes (align, bgcolor, cellpadding, and similar), <style> blocks (cleaned, not removed), and HTML comments, including Outlook’s conditional comments, which is how imported templates keep their Word-rendering fallbacks.

If your content is over the limit

Templates over 1MB of stored HTML are rejected with an error on save. If you’re close, simplify inline styles or markup rather than embedding a giant asset. Images belong on a URL, not inlined as data.

Next steps