How different are Superhuman and Gmail?

They disagree on 38 of the 97 features verified in both clients, or 39%. 54 features render in both and are the safe intersection to build on.

What works in Superhuman but not Gmail?

25 features, including , , @font-face, @supports, accent-color and 20 more. Each needs a fallback if the send reaches both clients.

Which engines are these two clients using?

Superhuman renders with Blink; Gmail renders with Gmail Web. Where two clients share an engine the divergence is usually configuration, and where they do not it is the engine itself.

Is this measured in the real clients?

No. These are documented support levels derived from caniemail.com (MIT-licensed), carried in @emailens/engine data version 0.18.22 and last synced Nov 10, 2026. That sync date is not a test date: caniemail's own per-feature tests run from Feb 28, 2019 to Sep 16, 2026. Anything described as a transform is applied per those documented rules rather than captured from a real client.

Superhuman vs Gmail: CSS Support Differences

Superhuman renders with Blink; Gmail renders with Gmail Web. The gap runs almost entirely one way: 25 features work in Superhuman and break in the other, against 1 in the reverse direction. Build for the stricter one and the permissive one follows.

Support data derived from caniemail.com (MIT) - last synced Nov 10, 2026 - engine data v0.18.22

work in both

the safe intersection

only in Superhuman

breaks in Gmail

only in Gmail

breaks in Superhuman

partial on one side

renders, with caveats

Works in Superhuman, breaks in Gmail

Each of these needs a fallback if the send reaches both.

Works in Gmail, breaks in Superhuman

<form>

Partial on one side

These render in both, but one client applies caveats the other does not. They fail quietly, which makes them the expensive ones.

A further 5 features render in neither client. Not a difference between them, but the other half of the answer to what you can actually use, so the four counts above deliberately do not sum to 97.

203 of 300 features have no confident data point for at least one of these clients, so they are excluded from every count above rather than assumed either way.

Where the divergence sits

Two pairs with the same headline number can be different problems. For these two it concentrates in CSS Properties.

CSS Properties 30
HTML Elements 4
CSS At-Rules 4

14 of these already have a fix

Each links to a copy-paste snippet that keeps the feature working in Gmail without dropping it in Superhuman.

Check your own HTML against both

Paste your email

Check your email, free

Questions

How different are Superhuman and Gmail?: They disagree on 38 of the 97 features verified in both clients, or 39%. 54 features render in both and are the safe intersection to build on.
What works in Superhuman but not Gmail?: 25 features, including <picture>, <svg>, @font-face, @supports, accent-color and 20 more. Each needs a fallback if the send reaches both clients.
Which engines are these two clients using?: Superhuman renders with Blink; Gmail renders with Gmail Web. Where two clients share an engine the divergence is usually configuration, and where they do not it is the engine itself.
Is this measured in the real clients?: No. These are documented support levels derived from caniemail.com (MIT-licensed), carried in @emailens/engine data version 0.18.22 and last synced Nov 10, 2026. That sync date is not a test date: caniemail's own per-feature tests run from Feb 28, 2019 to Sep 16, 2026. Anything described as a transform is applied per those documented rules rather than captured from a real client.

Zero-Friction Engine Preview

Test your email in Gmail, Outlook and Apple Mail

Preview rendering, catch CSS issues, and see what Outlook does to your VML. Free, no account. All 21 clients with one.

Check your email, free

No signup · Five clients free, Outlook Classic included · All 21 with an account