{"id":29610,"date":"2021-06-02T10:00:00","date_gmt":"2021-06-02T14:00:00","guid":{"rendered":"https:\/\/www.litmus.com\/?p=29610"},"modified":"2025-12-09T15:14:22","modified_gmt":"2025-12-09T20:14:22","slug":"css-resets","status":"publish","type":"post","link":"https:\/\/www.litmus.com\/blog\/css-resets","title":{"rendered":"Email marketing assumptions: My email needs all those CSS resets"},"content":{"rendered":"\n\n\t
\n
\n \t
\n \t\t
\n \t\t\t
\n \t\t\t\t

Mailbox and internet service providers (ISPs) do strange things to our emails. One way to combat this? Using CSS resets for a fresh start. But email clients have come a long way. So, let\u2019s take a closer look at this common email marketing assumption:<\/p>\n

Does my email need CSS resets?<\/i><\/p>\n

What is a CSS reset?<\/h2>\n

A CSS reset is a set of styling rules in the head of an email that account for known bugs or issues in various email clients like Gmail and Outlook. The resets prevent your email from looking funky and provide a clean, consistent foundation on which to code and style your emails. Like starting with a truly blank canvas.<\/p>\n

What are common CSS resets?<\/h2>\n

There are general resets, and then there are client-specific resets. Most of them are to override Outlook issues<\/a> or blue links<\/a> in Apple, Gmail, and Android clients. Back in 2014, email marketing advocate and author Jason Rodriguez shared his reset code<\/a> which sparked a discussion<\/a> in the Litmus Community where fellow email geeks shared their resets. This was clearly a problem back then.<\/p>\n

So are they still needed today?<\/h3>\n

While websites may not need CSS resets anymore, emails still do.<\/p>\n

Unfortunately, there\u2019s still no<\/i> universal email development standards (we wish!). That means email clients, apps, and devices each have their own unique way of rendering your email, including adding to or altering your code. The result? An inconsistent subscriber experience and an email that can look broken. Ugh.<\/p>\n

However, the resets you need have changed over the years as email clients have evolved. I spoke with our email developer, Carin Slater, to learn more about this.<\/p>\n

On the one hand, Outlook has since resolved ExternalClass and ReadMsgBody padding issues that required CSS resets to fix. But on the other hand, we\u2019re now dealing with relatively new things like Dark Mode. And every update that email clients make to their product introduces new ways for your emails to break. Like when Outlook.com started replacing body with div<\/a> in emails. That was fun.<\/p>\n

For emails in today\u2019s world, Carin likes to reference Jay Oram\u2019s email CSS resets<\/a> and R\u00e9mi Parmentier\u2019s email bugs documentation<\/a>.<\/p>\n

See if your CSS resets work<\/h2>\n

The CSS resets your emails need depend on where your audience opens emails. Do you have little to no subscribers using Outlook? Count your blessings and cross that one off your list.<\/p>\n

While you don\u2019t want to bloat your code with unnecessary CSS resets that could slow down load time or clip your email, if you want to throw all of them into your email just in case, the impact should be minimal.<\/p>\n

Then, find out if your resets are doing the trick. See how your emails look across 100+ different email clients and devices with Litmus Email Previews. Ready to see Litmus in action?<\/p>\n

BOOK A DEMO \u2192<\/a><\/p>\n

Curious about other email marketing assumptions?<\/b><\/p>\n