View Standard Fix
USE CASE Target

Email Not Displaying Correctly in Gmail: Fix Custom Font Fallback Overrides for MJML Framework for Editorial & Content Newsletters

Editorial newsletters rely on content layout readability and structural text spacing. If fonts default to Times New Roman or layout borders break, subscriber engagement metrics suffer. Below is the targeted integration guide to fix Custom Font Fallback Overrides inside Gmail App (iOS & Android) templates when using MJML Framework.

Technical Breakdown

Gmail App (iOS & Android) uses the WebKit / Blink which lacks support for standard rendering rules. This causes Custom Font Fallback Overrides elements to break or collapse when rendering templates.

MJML Framework Behaviors

The MJML transpilation compiler parses dynamic columns and wraps them in custom HTML conditional tags. If you paste direct tables or VML code blocks inside an MJML layout without proper escaping, the MJML compiler will try to clean the code, resulting in stripped Outlook namespaces and broken layouts. Keep your editorial body clean. Strip redundant CSS class definitions using Vaporize to ensure the newsletter stays under Gmail's 102KB clipping ceiling.

Remediation Code Block

To prevent Outlook's Times New Roman fallback override, wrap your custom font declarations inside an @media block that Outlook ignores, or use MSO conditional statements to override font-families specifically for Microsoft Word rendering engines. In your MJML Framework campaign manager, make sure you configure your links to run via {{unsubscribe_link}}.

<!--[if mso]>
<style type="text/css">
  body, table, td { font-family: Arial, sans-serif !important; }
</style>
<![endif]-->
<style>
  @import url('https://fonts.googleapis.com/css2?family=Montserrat&display=swap');
</style>

Live Code Sandbox Test

Interactive MJML Framework Custom Sandbox

Target Environment: Gmail App (iOS & Android)

How to Deploy inside MJML Framework

1

Copy the fixed VML or table wrapper code block from the remediation box above.

2

Wrap the entire RenderOps corrected table block inside an '<mj-raw>' tag block. This tells the MJML compiler to bypass parsing on this segment, exporting the exact conditional statements into the final HTML output.

Targeted Fixes by Use Case & Industry