Skip to main content

Email Safe Formatting

When formatting emails in HTML, it's important to consider the compatibility across different email clients, as some may not support certain CSS styles or HTML tags. Here are some HTML-safe formatting techniques commonly used in emails:

Inline CSS​

Use inline CSS styles rather than external or internal stylesheets. This ensures that your styling is more likely to be rendered consistently across various email clients. Additionally, you can leverage the brands designer to apply CSS styles to your email templates.

Styles in head

Some email clients like Gmail will only support <styles> in the <head> element.

Basic HTML tags​

Stick to basic HTML tags like <p>, <div>, <span>, <a>, <strong>, <em>, <ul>, <ol>, <li>, <h1> to <h6>, etc. These are widely supported across email clients.

Tables​

Tables are often used for layout in HTML emails because they are well-supported across different email clients. However, keep your table structures simple and avoid complex nesting.

Email clients like gmail will impose certain limitations on HTML tables like:

  • Handling of nested tables can be inconsistent, leading to layout distortions or unexpected behavior in the email layout.
  • Lack of support conditional formatting for table cells, which limits dynamic content presentation within tables.

Inline Images​

Embed images using the <img> tag and provide appropriate alt attributes for accessibility. Make sure to host your images on a reliable server.

Image hosting

Courier does not host images at this time for src paths. The exception is using Image Blocks for your templates which will host the image on our server.

Use the <a> tag for hyperlinks. Ensure that all links are clickable and provide descriptive anchor text.

Font Styles​

Use CSS for basic font styles like color, size, family, and weight. Avoid using web fonts that may not be supported by all email clients.

Web Fonts​

While desktop fonts are loaded onto an individual computer so they can be used in word processors and other applications, web fonts are stored online and downloaded by browsers. When someone accesses a page on a website, web fonts are specified through CSS ⸺ often using the @font-face declaration.

Email clients that do support web fonts include:

  • Apple Mail
  • iOS Mail
  • Android Mail (not Gmail)
  • Thunderbird
  • Outlook for macOS

Web Safe Fonts​

Fonts that are deemed web safe are more likely to be supported across email clients. However, it's important to note that even though a font is classified as web safe, it doesn't guarantee complete safety for use in email marketing.

  • Arial (sans-serif)
  • Verdana (sans-serif)
  • Helvetica (sans-serif)
  • Tahoma (sans-serif)
  • Trebuchet MS (sans-serif)
  • Times New Roman (serif)
  • Georgia (serif)
  • Garamond (serif)
  • Courier New (monospace)
  • Brush Script MT (cursive)

Email Safe Fonts​

While the font choices may not be particularly thrilling, opting for these options guarantees a uniform experience across various email platforms. Additionally, you might discover an email-safe font that mirrors your brand's preferred typeface.

  • Arial
  • Courier New
  • Georgia
  • Times New Roman
  • Trebuchet
  • Verdana

Background Colors​

You can set background colors for elements using CSS. Keep in mind that some email clients may not fully support background colors.

Responsive Design​

Consider using responsive design techniques to ensure that your email renders well on different devices and screen sizes. Media queries can be used to adjust the layout based on the viewport size.

Testing​

Always test your HTML emails across different email clients and devices to ensure consistent rendering. There are tools available that can help with email testing, such as Litmus or Email on Acid.

By following these guidelines, you can create HTML emails that are compatible with a wide range of email clients while still allowing for attractive and engaging formatting. If you have any questions regarding email styles and formatting, you can always reach out to our support team.

Was this helpful?