Can I Email: The Essential Guide to Email Client HTML and CSS Support

Email marketing remains one of the most effective digital channels, but creating emails that render consistently across the fragmented email client landscape presents unique challenges. Unlike web browsers, where standards support has converged significantly, email clients vary dramatically in their HTML and CSS capabilities.

Can I Email is the definitive resource for email developers--a database tracking 302 HTML and CSS features across 44+ email clients. Similar to Can I Use but specifically designed for email development, this tool helps you make informed decisions about which features to use based on your audience's email client distribution.

Understanding Email Client Fragmentation

The email client ecosystem differs fundamentally from web browsing. While modern browsers like Chrome, Firefox, Safari, and Edge all support consistent web standards, email clients operate on entirely different rendering engines with varying levels of standards compliance.

Why Email Clients Differ from Web Browsers

Email clients use a variety of rendering engines, creating a fragmented landscape:

• Apple Mail uses WebKit, the same engine as Safari, providing near-modern browser support
• Gmail uses a combination of HTML sanitization and partial CSS support
• Outlook (Windows) uses the Microsoft Word rendering engine, significantly limiting modern CSS
• Yahoo Mail, AOL, and other webmail clients have their own proprietary implementations

This fragmentation means that an HTML email that renders perfectly in Apple Mail might appear broken in Outlook, even though both are mainstream email clients.

According to the Can I Email database, which tracks 302 HTML and CSS features across 44+ email clients and their variants, support varies dramatically from 93% (Apple Mail) to just 19% (Outlook Windows). This range means email developers must carefully balance advanced features against broad compatibility.

Outlook maintains significant market share in enterprise environments, making its limited support a critical consideration for B2B email marketing. Users in corporate environments often have no choice but to use Outlook, requiring email developers to accommodate its limitations.

What HTML Features Work in Email

Well-Supported HTML Elements

Most email clients support these fundamental HTML elements:

• Structural elements: <table>, <tr>, <td>, <tbody>, <thead>, <tfoot>
• Text formatting: <p>, <span>, <div>, <h1> through <h6>
• Text-level semantics: <strong>, <b>, <em>, <i>, <u>
• Links: <a> with href attribute
• Images: <img> with src, alt, and basic attributes
• Lists: <ul>, <ol>, <li>

Limited or Unsupported HTML

Many modern HTML elements have limited or no support:

• Forms and inputs: Generally not supported or severely restricted
• Semantic elements: <header>, <nav>, <main>, <article>, <section>, <footer> are ignored or stripped
• Script tags: Never execute in email
• Interactive elements: <button>, <input>, <select> typically non-functional
• Embedded content: <iframe>, <object>, <embed>, <video> generally blocked

The Table-Based Layout Reality

Despite being considered outdated in modern web development, HTML tables remain the foundation of email layouts. This is because:

1. Tables provide consistent layout across clients with varying CSS support
2. Email clients historically stripped <div> and <span> styles
3. Table nesting allows for complex layouts without CSS positioning
4. Outlook for Windows requires table-based layouts for reliable rendering

CSS Support in Email Clients

Fully Supported CSS Properties

The following CSS properties have broad support across email clients:

• Font properties: font-family, font-size, font-weight, font-style, line-height
• Text properties: color, text-align, text-decoration, text-indent
• Background: background-color (solid colors only)
• Border: border, border-color, border-width, border-style
• Margin: margin (limited on some clients)
• Padding: padding (limited support)

Partially Supported CSS

Several properties have partial or conditional support:

• Width/Height: width and height work on images and tables but not on all elements
• Display: display: block and inline generally supported; flex and grid have limited support
• Position: position: relative limited; position: absolute not supported
• Overflow: overflow: hidden has partial support
• Border-radius: Supported in most modern clients but not legacy ones

Unsupported CSS

Many modern CSS features are unsupported in email clients:

• CSS Grid: Not supported in most email clients
• CSS Flexbox: Limited support in Apple Mail and some modern clients
• CSS Variables: Not supported
• Animations/Transitions: Very limited support
• Custom Fonts via @font-face: Partial support, varies by client

Email Client Rankings and Support Levels

Tier 1: Excellent Support

Apple Mail (macOS and iOS) -- Support: 93% (macOS) and 92% (iOS). Uses WebKit rendering engine, supports most modern CSS including media queries, responsive design, and advanced styling. Best platform for testing cutting-edge email features.

Samsung Email (Android) -- Support: 82%. Better CSS support than many competitors. Good choice for reaching Android users.

Tier 2: Moderate Support

Gmail (All Platforms) -- Support varies: 50% (Desktop), 36% (Android), 38% (iOS). Strips certain CSS properties and classes, requires inline styles for reliable rendering. Gmail clips emails longer than 102KB.

Yahoo Mail -- Support: ~43%. Limited CSS support with some quirks in image handling.

Tier 3: Limited Support

Outlook (Windows) -- Support: 19%. Uses Microsoft Word rendering engine, does not support CSS Flexbox, Grid, or many modern properties. Requires table-based layouts and does not support background images. Despite these limitations, Outlook maintains significant market share in enterprise environments, making it a critical consideration for B2B email marketing.

Integration Patterns and Best Practices

Inline Styles Are Still Essential

Despite advances in internal CSS support, inline styles remain the most reliable method for email styling:

• Gmail strips <style> tags in some contexts
• Internal CSS has ~85% support but varies by client
• Inline styles guarantee rendering across all clients

Progressive Enhancement Strategy

Use a layered approach to email styling:

1. Base layer: Inline styles for all critical styling
2. Enhancement layer: Internal CSS for responsive features
3. Feature detection: Media queries for responsive layouts

Conditional Styles for Outlook

Use Microsoft conditional comments to target Outlook specifically with table-based fallbacks and layout adjustments. This approach ensures that emails render correctly even in the most challenging email client.

Cost Optimization for Email Testing

Professional email testing services like Litmus and Email on Acid offer comprehensive previews across 90+ email clients, but these subscriptions can be expensive for small teams. Fortunately, there are cost-effective strategies for managing testing expenses.

Free Options

• Can I Email: Check feature support before coding
• Mailtrap: Email testing for development
• Gmail/Outlook web: Free account testing

Tiered Testing Approach

1. Initial tests: Free webmail clients
2. Targeted tests: Most common clients in your audience
3. Full testing: Annual or quarterly comprehensive tests

Building a Testing Matrix

Rather than testing every email across every client, build a testing matrix based on your audience's actual email client distribution, template complexity, and new features being tested. Most organizations need to test on 5-8 key clients rather than all available options.

Accessibility in Email

According to the Email Markup Consortium's 2025 Accessibility Report, 99.89% of emails contain accessibility issues, with only 21 out of 443,585 tested emails passing all automated checks. Only one email client (SFR Mail) supports all 20 tested accessibility features.

Common Accessibility Issues

• Missing language attributes: 96.67% of emails lack proper lang attributes
• Tables without presentation role: 86.24% use tables without role="presentation"
• Missing H1 headings: 76.78% lack proper heading structure
• Links without discernible text: 72.04% have inaccessible links
• Images missing alt text: 51.42% lack proper image descriptions

Making Emails Accessible

• Use proper heading hierarchy (H1, H2, H3)
• Add lang attributes to the <html> and <body> elements
• Mark layout tables with role="presentation"
• Ensure all images have descriptive alt text
• Make links descriptive (avoid "click here")
• Maintain sufficient color contrast (4.5:1 ratio)

Accessible email design shares many principles with SEO-friendly web development, where proper semantic HTML, alt text, and structural elements improve both accessibility and search engine visibility.

Tools and Resources

Primary Reference Tools

• Can I Email -- Feature support database, email client scoreboard, searchable CSS/HTML support tables, free to use
• Litmus -- Email previews across 90+ clients, email analytics, template testing, paid subscription
• Email on Acid -- Cross-client testing, spam testing, accessibility checks, paid subscription

Development Tools

• MJML -- Open-source markup language that compiles to email-compatible HTML with automatic responsive design
• Foundation for Emails -- Email framework with responsive components, Inky templating language, free
• Postcards Email Builder -- Visual email template builder with code export capability

Validation Tools

• W3C HTML Validator: Check for HTML errors
• Accessibility checkers: Parcel, accessibility-checkers
• Spam score testers: Mail-Tester, SpamAssassin

Conclusion

Creating effective emails requires navigating a fragmented client landscape where support ranges from 93% (Apple Mail) to 19% (Outlook Windows). The Can I Email resource provides the foundation for understanding what HTML and CSS features work where, enabling informed decisions about email development.

Key Strategies for Success

1. Start with a baseline: Use inline styles for universal compatibility
2. Check before implementing: Verify feature support on Can I Email
3. Know your audience: Target testing based on actual client distribution
4. Plan for Outlook: Build table-based layouts with Outlook-specific fallbacks
5. Prioritize accessibility: Only one email client fully supports accessibility features

By combining these approaches with modern email development tools like MJML or Foundation for Emails, teams can create emails that reach audiences effectively while managing development and testing costs efficiently. For organizations looking to implement sophisticated email automation workflows, our AI & Automation services can help streamline your email marketing operations.

Sources

1. Can I Email -- The definitive resource for checking HTML/CSS feature support in email clients
2. Can I Email Scoreboard -- Rankings showing email client support percentages
3. Designmodo: HTML and CSS in Emails -- Comprehensive guide on email HTML/CSS limitations
4. Email Markup Consortium Accessibility Report 2025 -- Critical findings on email accessibility issues
5. MJML - The Email Framework -- Open-source markup language for responsive email HTML
6. Foundation for Emails -- Email framework with responsive components