Email clients all render HTML differently. Here’s what tinysend does to help and what to keep in mind.
What tinysend does automatically
- sends both HTML and plain text versions — if a client can’t display HTML, subscribers get the text version
- plain text is generated automatically from your HTML
- attachments are stored and linked in the post
- images are hosted on tinysend’s CDN
You write your email in whatever client you already use. tinysend delivers it as-is — no template wrapping, no reformatting.
How major clients render your emails
- Gmail — good HTML/CSS support, strips some styles for security, clips messages over 102 KB
- Outlook (desktop) — uses Word’s rendering engine, limited CSS support, inconsistent spacing, blocks images by default
- Apple Mail — best rendering of all clients, shows images by default, consistent across iOS and macOS
- Yahoo/AOL — decent support, some quirks with padding and margins
- Mobile clients — smaller screens, touch targets should be 44px+, single-column layouts work best
Tips for best results
- keep layouts simple — single column works everywhere
- use web-safe fonts (Arial, Georgia, Verdana) — custom fonts won’t load in most clients
- keep total email size under 100 KB to avoid Gmail clipping
- use alt text for images — some clients block them by default
- avoid background images, JavaScript, forms, and video embeds
- short paragraphs read better on mobile
Testing
The preview step in tinysend’s sending flow lets you check how your email looks before it goes to subscribers. Send test emails to yourself on different clients to catch rendering issues early.
Questions?
Contact us at hi@tinysend.com.