overflow
CSS property · 3 supported, 10 partial, 2 unsupported across 15 clients
Client Support
| Client | Category | Engine | Support |
|---|---|---|---|
| Gmail | webmail | Gmail Web | Partial |
| Gmail Android | mobile | Gmail Mobile | Partial |
| Gmail iOS | mobile | Gmail Mobile | Partial |
| Outlook 365 | webmail | Outlook Web | Partial |
| Outlook (New) | desktop | Outlook Web | Unsupported |
| Outlook Classic | desktop | Microsoft Word | Unsupported |
| Outlook iOS | mobile | Outlook Mobile | Partial |
| Outlook Android | mobile | Outlook Mobile | Partial |
| Apple Mail | desktop | WebKit | Partial |
| Apple Mail iOS | mobile | WebKit | Partial |
| Yahoo Mail | webmail | Yahoo | Partial |
| Samsung Mail | mobile | Samsung | Partial |
| Thunderbird | desktop | Gecko | Supported |
| HEY Mail | webmail | WebKit | Supported |
| Superhuman | desktop | Blink | Supported |
Client-by-client behaviour for overflow
Fully supports overflow (3): Thunderbird, HEY Mail, Superhuman.
Partial support (10): Gmail, Gmail Android, Gmail iOS, Outlook 365, Outlook iOS, Outlook Android, Apple Mail, Apple Mail iOS, Yahoo Mail, Samsung Mail. Expect rendering quirks unique to each engine — partial support typically means a subset of values, an ignored shorthand, or sanitizer-specific rewrites.
No support (2): Outlook (New), Outlook Classic. Plan fallbacks for these clients before relying on overflow in production sends.
Fixes & Workarounds
Outlook (New)
UnsupportedContent will always be visible. Design accordingly.
Before
<div style="max-height: 200px; overflow: hidden;">
Long content that gets clipped...
</div>After
<!-- Show full content, or truncate server-side -->
<div style="max-height: 200px;">
Shortened content that fits...
<a href="https://example.com/full">Read more</a>
</div>Content will always be visible — design for full content display
Outlook Classic
UnsupportedContent will always be visible. Design accordingly.
Before
<div style="max-height: 200px; overflow: hidden;">
Long content that gets clipped...
</div>After
<!-- Show full content, or truncate server-side -->
<div style="max-height: 200px;">
Shortened content that fits...
<a href="https://example.com/full">Read more</a>
</div>Content will always be visible — design for full content display
Gmail
PartialContent will always be visible. Design accordingly.
Before
<div style="max-height: 200px; overflow: hidden;">
Long content that gets clipped...
</div>After
<!-- Show full content, or truncate server-side -->
<div style="max-height: 200px;">
Shortened content that fits...
<a href="https://example.com/full">Read more</a>
</div>Content will always be visible — design for full content display
Gmail Android
PartialContent will always be visible. Design accordingly.
Before
<div style="max-height: 200px; overflow: hidden;">
Long content that gets clipped...
</div>After
<!-- Show full content, or truncate server-side -->
<div style="max-height: 200px;">
Shortened content that fits...
<a href="https://example.com/full">Read more</a>
</div>Content will always be visible — design for full content display
Gmail iOS
PartialContent will always be visible. Design accordingly.
Before
<div style="max-height: 200px; overflow: hidden;">
Long content that gets clipped...
</div>After
<!-- Show full content, or truncate server-side -->
<div style="max-height: 200px;">
Shortened content that fits...
<a href="https://example.com/full">Read more</a>
</div>Content will always be visible — design for full content display
Outlook 365
PartialContent will always be visible. Design accordingly.
Before
<div style="max-height: 200px; overflow: hidden;">
Long content that gets clipped...
</div>After
<!-- Show full content, or truncate server-side -->
<div style="max-height: 200px;">
Shortened content that fits...
<a href="https://example.com/full">Read more</a>
</div>Content will always be visible — design for full content display
Outlook iOS
PartialContent will always be visible. Design accordingly.
Before
<div style="max-height: 200px; overflow: hidden;">
Long content that gets clipped...
</div>After
<!-- Show full content, or truncate server-side -->
<div style="max-height: 200px;">
Shortened content that fits...
<a href="https://example.com/full">Read more</a>
</div>Content will always be visible — design for full content display
Outlook Android
PartialContent will always be visible. Design accordingly.
Before
<div style="max-height: 200px; overflow: hidden;">
Long content that gets clipped...
</div>After
<!-- Show full content, or truncate server-side -->
<div style="max-height: 200px;">
Shortened content that fits...
<a href="https://example.com/full">Read more</a>
</div>Content will always be visible — design for full content display
Apple Mail
PartialContent will always be visible. Design accordingly.
Before
<div style="max-height: 200px; overflow: hidden;">
Long content that gets clipped...
</div>After
<!-- Show full content, or truncate server-side -->
<div style="max-height: 200px;">
Shortened content that fits...
<a href="https://example.com/full">Read more</a>
</div>Content will always be visible — design for full content display
Apple Mail iOS
PartialContent will always be visible. Design accordingly.
Before
<div style="max-height: 200px; overflow: hidden;">
Long content that gets clipped...
</div>After
<!-- Show full content, or truncate server-side -->
<div style="max-height: 200px;">
Shortened content that fits...
<a href="https://example.com/full">Read more</a>
</div>Content will always be visible — design for full content display
Yahoo Mail
PartialContent will always be visible. Design accordingly.
Before
<div style="max-height: 200px; overflow: hidden;">
Long content that gets clipped...
</div>After
<!-- Show full content, or truncate server-side -->
<div style="max-height: 200px;">
Shortened content that fits...
<a href="https://example.com/full">Read more</a>
</div>Content will always be visible — design for full content display
Samsung Mail
PartialContent will always be visible. Design accordingly.
Before
<div style="max-height: 200px; overflow: hidden;">
Long content that gets clipped...
</div>After
<!-- Show full content, or truncate server-side -->
<div style="max-height: 200px;">
Shortened content that fits...
<a href="https://example.com/full">Read more</a>
</div>Content will always be visible — design for full content display
Production guidance for overflow
overflow is a CSS property. Across the email client matrix, 3 of 15 tracked clients support it fully, 10 only partially, and 2 not at all. The clients most likely to require a workaround for this feature are Outlook (New), Outlook Classic, Gmail. Each of them needs a tailored fallback — see the per-client examples above for the specific code fix Emailens recommends.
When in doubt, ship a baseline that renders without overflow and treat it as progressive enhancement on clients where support is verified. Emailens automatically detects cross-client divergence on this feature when you preview an email, so you can see exactly which template paths break before a campaign goes out.
Related Features
Test your email across all 15 clients
Preview rendering, catch CSS issues, and get actionable fixes — free.
Try Emailens FreeSupport data last updated Apr 27, 2026 · synced from caniemail.com via @emailens/engine.