Can I email…

Can I email…

Lifecycle & Email
Look up any HTML or CSS feature and see which email clients render it before you build the template.
ACCESS
No login
PRICE
Free
HOST
Tilt Studio
CATEGORY
Email design & compatibility
Last updated
August 4, 2026

Preview

Can I email…

What it is.

Can I email… publishes support tables for HTML and CSS in emails. It's launched and maintained by @HTeuMeuLeu and the team at Tilt Studio, with support data contributed by the email community on GitHub.

You search a feature and get a client-by-client verdict, so a technique that breaks in one desktop client shows up before the template goes out. The support table covers desktop, webmail and mobile clients side by side.

What you get.

  • A client-by-client support verdict for any HTML or CSS feature used in email
  • Community-contributed data, kept on GitHub where you can see the history
  • The full support dataset as JSON for your own tooling
  • Feature pages that name which clients need a fallback
HOW TO USE IT

How to set it up.

1

Open caniemail.com and type the feature you're about to use into the search box.

2

Read the client column for the platforms your list opens on most.

3

Open the feature page for the notes on partial support.

4

Where support is thin, plan the fallback before you write the template.

5

For automated checks, pull the dataset from the JSON endpoint instead of the page.

Pricing Plans

Can I email…

$0

full support tables and the JSON data, no account

Use cases

Settle the Outlook argument

Look the feature up and show the client-by-client verdict.

Choose a layout technique

Check support before you build the template, not after QA finds it.

See how the data changed

Read the history on GitHub when a verdict looks out of date.

Best for

Before you build a template

Check the techniques you plan to use while changing them is still cheap.

Settling a rendering argument

A designer wants a layout the developer says will break. The table answers it with a client list.

Open the tool

Opens on Google in a new tab.

Open the Tool

Questions about Can I email…

Does it need a login?

Questions about Lifecycle & Email

Why does the same email look different in two clients?
Before you start
  • The feature you are about to use, named.
  • A view on which clients your list opens in most.
Strengths
  • Free with no account, and the support data is open on GitHub.
  • The same dataset comes down as JSON, so a build step can check a template automatically.
  • Community contributions mean new client behavior lands quickly.
Limitations
  • Support data is community-contributed, so a brand-new client version can lag until someone tests it.
  • It tells you what renders, and nothing about whether the email lands in the inbox.
  • Partial support is common, so read the feature page notes before trusting a green cell.
Skip this if
  • You already build email in a framework that handles client support for you.
Ideal for
  • Email developers
  • Lifecycle marketers
  • Design engineers

Got the free stack.
Need the engine?

Free tools give you the data. We turn it into pipeline for 300+ B2B tech companies, across organic search and paid media.