Submit Article Requests

Do you have a suggestion for an article you would like to see created?
Feel free to submit this form and add your suggestions to our document board.

Please fill out the contact form below and we will reply as soon as possible.

  • Integration Hub
  • Contact Us
  • Docs home
  • Workflows
  • Setup & Configuration

Email rendering best practices

Write HTML emails that display consistently across Gmail, Outlook, Apple Mail, and mobile clients

Updated at March 27th, 2026

Submit Article Requests

Do you have a suggestion for an article you would like to see created?
Feel free to submit this form and add your suggestions to our document board.

Please fill out the contact form with the details about the help content you'd like to see.

  • Home

  • Getting Started

    • Installation & Developers

      • Web Experiences

        • Mobile Experiences

          • Workflows

            • Analytics & Data

              • Account Management

                • Integrations

                  Table of Contents

                  Use inline CSS Use tables for layout Avoid background images Design for mobile first Test across clients before sending

                  Email clients render HTML differently. An email that looks correct in Gmail may break in Outlook or display poorly on a phone. These practices help you avoid the most common rendering issues.

                  Use inline CSS

                  Many email clients strip <style> tags from the email head. Apply CSS directly on each HTML element with the style attribute so your styling survives regardless of the client.

                  Use tables for layout

                  Modern web design uses <div> elements, but HTML emails are more reliable with <table> elements for layout. Outlook in particular ignores many CSS layout properties but handles table-based layouts consistently.

                  Avoid background images

                  Background images don't display in all email clients. Use solid background colors instead. If you need a graphic, add it as an inline <img> element rather than a CSS background.

                  Design for mobile first

                  Build your emails to be responsive — use fluid widths and stack columns on narrow screens. A mobile-first approach ensures readability on smaller devices, then scales up for desktop. Most email opens happen on mobile.

                  Test across clients before sending

                  Send test emails and check rendering in multiple clients before publishing your Workflow. For quick checks, use the built-in test email feature and send to accounts on different providers.

                  For more thorough testing, tools like Litmus and Email on Acid let you preview how your email renders across dozens of clients simultaneously.

                  html emails

                  Was this article helpful?

                  Yes
                  No
                  Give feedback about this article

                  Related Articles

                  • Configure email settings
                  • Build Email Messages
                  • Manage email suppression lists
                  • Create a Firebase Cloud Messaging service
                  Appcues logo

                  Product

                  Why Appcues How it works Integrations Security Pricing What's new

                  Use cases

                  Appcues Integration Hub User Onboarding Software Feature Adoption Software NPS & Surveys Announcements Insights Mobile Adoption

                  Company

                  About
                  Careers

                  Support

                  Developer Docs Contact

                  Resources

                  The Appcues Blog Product Adoption Academy GoodUX Case studies Webinar Series Made with Appcues

                  Follow us

                  Facebook icon Twitter icon grey Linkedin icon Instagram icon
                  © 2022 Appcues. All rights reserved.
                  Security Terms of Service Privacy Policy

                  Knowledge Base Software powered by Helpjuice

                  Expand