Skip to content

HTML rendering in test emails

If your test email looks off, we recommend first checking your HTML setup. Next, you can check for these issues:

Extension conflicts

Certain browser extensions may cause issues with Braze’s email editor. One example is Grammarly) when used with Google Chrome. If you’re using one of these extensions, you should either:

  • Edit Braze emails in a browser that does not have Grammarly as a browser extension
  • Contact your Braze account manager and ask to switch your email editors to HTML only or plain text.

The plain text view removes your WYSIWYG (what you see is what you get) editor, so you should first confirm that all team members are comfortable with HTML before making this request.

Email rendering

Emails render differently depending on browsers and email clients, so take note of which browsers and email clients you’re experiencing issues with.

  • Preview your emails using Inbox Vision to see what your emails look like in different browsers and email clients.
  • Once you’ve identified which browsers or email clients are causing issues, let your developer team know that they’ll need to modify their HTML and make edits to accommodate those browsers or email clients.

CSS inlining

There are times when the previews in Inbox Vision still do not match what is sent with Braze. This may be caused by the difference in CSS inlining performed by Braze and by other tools. If you suspect that this is the case, contact your Braze account manager to ask for CSS inlining to be turned off.

Still need help? Open a support ticket.

Last updated on December 21, 2021

WAS THIS PAGE HELPFUL?
New Stuff!