Back to Toolkit
Google Search Verified Fix

How to Fix Custom Font Fallback Overrides in Outlook 2016
for MJML Framework Campaigns

A programmatic integration guide for resolving email rendering crashes inside Outlook 2016 using MJML Framework's layout editor environment.

Root Bug Analysis

Outlook 2016 does not support Google Fonts. If fallback fonts are defined, MSO overrides the entire family chain to Times New Roman, ignoring Arial or sans-serif fallbacks.

Active rendering engine: Microsoft Word (MSO)

MJML Framework Specific Guide

MJML compiles typography to global styles, which Outlook intercepts. To prevent Outlook's Times New Roman fallback override, wrap your custom font declarations inside an @media block that Outlook ignores.

Integration Step:

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.

ESP Unsubscribe Alignment

When compiling custom HTML templates for MJML Framework, you must ensure your layout retains deliverability compliance loops. MJML Framework requires you to insert their specific unsubscribe merge tag, otherwise your campaign delivery will be flagged by automated spam audits.

MJML Framework Unsubscribe Tag:{{unsubscribe_link}}

Documented Client Behavior

Expected layout behavior based on target rendering engine specifications:

Documented behavior: Font family falls back to Times New Roman if custom web font fails inline parsing. Wrapping font style links in Outlook-safe styling tags overrides this.

Interactive MJML Framework Custom Sandbox

Target Environment: Outlook 2016

Auto-compile fixes inside RenderOps Workspace

Load layout code directly into our Font Stack Builder to compile responsive table frameworks that display cleanly in Outlook 2016.

Launch Font Stack Builder

Fix Custom Font Fallback Overrides on Other clients for MJML Framework