Need help with transactional-email-templates?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

6.6K Stars 1.2K Forks MIT License 38 Commits 11 Opened issues


Responsive transactional HTML email templates

Services available


Need anything else?

Contributors list

Responsive transactional HTML email templates

Transactional HTML emails often get neglected. Styling HTML email is painful. Tables, inline CSS, unsupported CSS, desktop clients, web clients, mobile clients, various devices, various providers.

We’ve tried to remove some of the pain for you and open-sourced a collection of common templates for transactional email.

Each template is responsive and each has been tested in all the popular email clients.

How to use

  • Use these email templates for your transactional emails
  • Use them as is or think of them as boilerplates for more detailed emails
  • Ensure you inline the CSS before sending the email out

What are transactional emails?

Typically any email that is triggered by or sent automatically from your application.

  • Welcome emails
  • Actionable emails
  • Password resets
  • Receipts
  • Monthly invoices
  • Support requests
  • App error alerts
  • Reminders
  • etc.

Inline the CSS

Before sending HTML emails you should inline your CSS.

We recommend using Premailer to accomplish this.

Our repo contains both the original templates with a separate CSS stylesheet, as well as templates with CSS already inlined for you to preview. See the


Tested and verified

We’ve tested these email templates across all the major desktop, web and mobile clients, using Litmus. See the test results.

Email design workflow with Grunt

You also might be interested in this Grunt task for compiling and testing html emails. We used this to help design and test our transactional emails.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.