Docs
What is Emu Email?
Emu Email is the latest addition to your email testing process. It emulates email clients in your browser, so you get feedback in real time and can fine-tune your emails faster.
It isn't a replacement for testing on real devices. It usually comes before, or alongside, real testing.
Your HTML never leaves your browser. It's saved in your browser so it's still there next time.
Code panel
The first step is to add your email's HTML. Paste it in, or load it from a URL.
- Paste or type into the code panel. Previews update as you type.
-
Load from a URL, such as your local dev server. Type the address and choose Load. It must
be https, or http for
localhost. The server has to allow the request (CORS), because your browser fetches the page directly. - Watch fetches the URL again every 2 seconds while the tab is open and updates the previews when the HTML changes. Editing the code stops watching.
- Hide code, above the code, hides the code panel to give the previews more room. Its column shrinks to a Show code button, which brings it back.
- Drag the line between the code and the previews to resize them. You can also focus it and use the arrow keys. Drag it to the left edge to hide the code, and out again to show it, or press Enter.
- Tab indenting is supported in the code panel, this affects default keyboard navigation. To move on from the code panel with the keyboard, press Esc, then Tab.
Multiple previews
When you fine-tune an email design, it helps to look at several versions at once. Something adjusted to work on desktop can make mobile look worse, or the other way round. Picking colours that work in every forced dark mode can be tricky.
You can open up to 5 previews side by side to compare them.
- Add preview, at the top right of the first preview, copies the settings of the last preview, ready to change.
- Each preview's title lists what's applied to it, such as "iPhone 17 Pro Max, Outlook iOS dark", even when there's only one. With nothing applied, it says "Preview", or "Default" next to other previews. When the list is too long to fit, hover over the title to see all of it.
- Each button above a preview (Device, Sizing, Colour scheme, Accessibility, Blocked content) opens its options. The reset button at the top right of the options puts them back to the defaults, for that preview only.
- Remove closes a preview. The first preview stays.
- Sync scrolling, next to Add preview, keeps every preview at the same scroll position. It's highlighted while it's on.
- Drag the line after a preview to change its width, or focus it and use the arrow keys. Double-click it, or press Enter, to reset the width.
Device
Device sets the size of the preview's viewport.
- Fit to size (the default) fills the space the preview has.
- Desktop is 800px wide and as tall as the space.
- Phones: iPhone Duo folded (466 × 678) and unfolded (626 × 890), iPhone 17 Pro Max (440 × 956), Samsung Galaxy S26 (360 × 780) and Google Pixel 10 (412 × 924).
- Custom size: drag the preview's right edge, bottom edge or corner, or type the exact width and height in pixels. Phones can be turned to Landscape.
A preview that fills the space shows the width the email is laid out at, because a narrow preview can trigger the email's mobile styles.
Sizing
Zoom
Zoom works like zooming a web page in a browser (Ctrl or Cmd and + or −). The email is laid out in a smaller viewport and scaled up, so its media queries react just as they would for a reader who zooms in. It goes from 25% to 500%.
WCAG asks that text can be resized to 200% without losing content or functionality (1.4.4 Resize Text), and that content reflows to fit a width of 320 CSS pixels without scrolling in two directions (1.4.10 Reflow). That is the same as 400% zoom on a 1280px wide screen. So check your email at 200% and 400%.
Font size
Font size emulates a reader's preferred default font size, set in their browser or device settings. Browsers default to 16px. It goes from 8px to 72px.
Text sized in rem, em or % follows the reader's setting. Text sized in
px doesn't. Setting a size on the root element, such as html { font-size: 16px },
overrides the reader's setting for the whole email.
Not covered: in a real browser, a root size in % or em still follows the reader's
setting, but in Emu Email any font size on the root element wins. Keywords such as medium and
<font size> aren't covered either.
The same WCAG guidance applies: text should still work at 200% (1.4.4 Resize Text), which is a font size of 32px.
Colour scheme
Light, Dark and System
- Light
- The default. What most readers see.
- Dark
-
Shows the dark mode styles in your email:
@media (prefers-color-scheme: dark)rules and the dark values oflight-dark(). - System
- Follows your system setting.
Safari has two issues here. Before Safari 27 it can't switch the preview between light and dark at all, so
Light and Dark both follow your system setting (the page shows a note when this happens). In Safari 27,
prefers-color-scheme rules switch, but light-dark() doesn't. To check dark mode in
Safari, change your system's appearance, or use another browser, such as Chrome or Firefox.
The forced dark modes rewrite your email's colours the way each client does. Each one says how closely it matches the real client, explained in How accuracy is measured.
Android forced dark
The forced dark mode built into Android's browser engine (Chromium).
Accuracy: exact matches on 600,000 colours.
Gmail Android dark
The same as Android forced dark, except that an email with
<meta name="color-scheme" content="light only"> is left in light mode. It hasn't been
measured separately.
Gmail iOS dark
It takes the same light only opt-out as Gmail Android.
| Style | Tests | Exact | Close | Worst |
|---|---|---|---|---|
color | 471 | 80.9% | 100% | N/A |
background | 561 | 80.6% | 99.8% | 4 |
border-color | Not tested yet | |||
Outlook web dark
Accuracy: exact matches on 601,024 pairs of text and background colours, and on 100,000 more with decimal channels.
Table cell borders (td and th) are recoloured too. Other borders aren't changed.
Outlook Android dark
| Style | Tests | Exact | Close | Worst |
|---|---|---|---|---|
color | 99 | 100% | N/A | N/A |
background | 100 | 79% | 94% or more | 6 |
border-color | 40 | 100% | N/A | N/A |
The furthest out are the most saturated magenta and red backgrounds. Borders aren't recoloured.
Outlook iOS dark
| Style | Tests | Exact | Close | Worst |
|---|---|---|---|---|
color | 100 | 99% | 100% | N/A |
background | 100 | 99% | 100% | N/A |
border-color | 40 | 100% | N/A | N/A |
Borders aren't recoloured.
Outlook Windows dark
Classic Outlook for Windows, which shows email with Word. It inverts every colour, dark and saturated ones included,
and text and backgrounds change the same way. It has no opt-out: color-scheme and the email's own dark
media queries make no difference.
Text with no colour set follows Word: it's black, or white on a dark background, before the colours are inverted. So in dark mode it's light on most backgrounds and dark on what were dark ones. Text set to black is inverted like any other colour, so it's always light.
Borders change like everything else. Links with no colour set start as blue (#0000ff). Images aren't
changed, and transparent images stay transparent.
| Style | Tests | Exact | Close | Worst |
|---|---|---|---|---|
color | 147 | 59.2% | 100% | N/A |
background | 1226 | 71.9% | 100% | N/A |
border-color | 3 | 66.7% | 100% | N/A |
Every tested colour comes out within 2 steps. The one sharp edge is among yellows: Outlook brightens some and darkens others, and a colour one step over that line changes by about 20 steps. The tests include many colours chosen right at it.
Yahoo! web dark
Yahoo! Mail on the web, on its #323232 reading pane with #fdfdfd text. The email's own
prefers-color-scheme: dark styles don't apply. It changes the colours the email writes, in its style attributes, its
<style> rules and its color and bgcolor attributes, rather than the
colours as they finally show. A colour it can't read is left alone: a keyword such as currentColor, a
gradient, or a shorthand with more than a colour in it, like border: 1px solid #ccc written in a
<style> block.
- Dark text (luminance below 0.5) becomes light: black becomes
#fdfdfd, other colours keep their hue. - Light backgrounds (luminance above 0.7) become dark: white becomes
#131313, other colours keep their hue. - Very dark and very light borders get lighter. Everything else is left as it is.
Colours that are almost white can come out unexpectedly: #fffffe as a background becomes dark olive
(rgb(153, 153, 0)), because the hue of a near-white is kept at full strength. In
<style> blocks, only style rules and @media rules are kept in dark mode, so
@supports, @font-face and similar rules stop applying.
Accuracy: exact matches on 2,326,335 colour values and on nine whole test emails.
How accuracy is measured
Where a forced dark mode doesn't match exactly, its table compares Emu Email's colours with the real client's:
- Tests
- How many colours were compared.
- Exact
- The percentage that matched exactly.
- Close
- The percentage within 3, which is barely visible. N/A when every colour is exact.
- Worst
- The furthest out any colour was. N/A when every colour is exact or close.
The difference is measured on RGB channels, from 0 to 255, and is the biggest difference in any one channel.
For example, if the client shows rgb(20, 30, 40) and Emu Email calculates
rgb(20, 30, 47), that colour is out by 7.
Accessibility
Semantic view
The semantic view shows the structure and hierarchy of your email by removing all its styles. Layout tables are flattened, and images are replaced by their alt text, or a "No alt text" box.
It shows how a computer reads your email, whether that's an AI agent or assistive technology such as a screen reader. Sizing, Colour scheme, Blur, Colour blindness and Blocked content are turned off while it's on.
Blur
Blur gives a rough idea of how your email looks to someone with blurred vision. It goes from 0, no blur, to 10px. The blur stays the same on screen at any zoom, so you can see whether zooming in makes your email readable again.
- Check that the important content stands out by size and contrast, not detail.
- Check that buttons and links can still be found.
It's a simple blur, not a medical simulation: real vision loss varies from person to person.
Colour blindness
Shows your email as someone with one of these types of colour blindness would see it:
- Achromatopsia: no colour vision, only light and dark.
- Deuteranomaly and deuteranopia: weak or no green cones; reds and greens are hard to tell apart. Deuteranomaly is the most common type.
- Protanomaly and protanopia: weak or no red cones; reds and greens are hard to tell apart, and reds look darker.
- Tritanomaly and tritanopia: weak or no blue cones; blues and greens, and yellows and pinks, are hard to tell apart. Both are rare.
- Check that nothing relies on colour alone, such as links only shown by colour, or red and green labels.
- Check that text and buttons still stand out from their backgrounds.
It works with any colour scheme, so you can check a dark mode too. The weaker forms (the "-omaly" types) vary a lot from person to person; these show a moderate case.
Headings menu
Lists every heading in your email, as a screen reader would. It flags skipped heading levels, empty headings, headings hidden from screen readers, and an email with no headings or no level 1 heading.
- Check the structure of the email.
- Check that the headings clearly describe the content.
The headings menu is one of the most common ways screen reader users move through content. This shows you what they hear. Choose a heading to find it in the preview.
Links menu
Lists every link in your email, as a screen reader would. It flags links with no text, link text that doesn't say where the link goes (such as "click here" or "read more"), and links hidden from screen readers.
- Check that each link's text clearly describes where it goes.
Screen reader users often use the links menu. They hear each link's text without the content around it. This shows you what they hear. Choose a link to find it in the preview.
Blocked content
See your email as it looks when an email client blocks some of it. Each preview has its own settings.
- External assets: blocks external assets such as web fonts and linked style sheets.
- Images: blocks images and background images as well as all other external assets.
- Styles: removes all
<style>elements and any<link rel="stylesheet"/>elements. - Custom: use CSS selectors to remove elements. Provide a comma-separated list of selectors and those elements will be removed from the preview. Only the targeted element is removed; its content remains. Use this to test fallbacks for progressive enhancements. For example, remove
inputto see the fallback for an interactive email.
Images embedded as data: URLs still show. Inline style attributes are kept when
styles are removed. Blocked content is turned off while the semantic view is on.