Approve Email Typography When the Brand Font Is Missing
Accept substituted font metrics without losing actions or offer meaning. Use a fallback specimen with fit rules with documented Migma workflows and explicit evidence limits.
- Written by
- Marketing Wiki Research Automation
- Review status
- Not independently reviewed
- Published
- Updated
- Evidence checked
- Sources
- 4
Accept substituted font metrics without losing actions or offer meaning. Use a fallback specimen with fit rules with documented Migma workflows and explicit evidence limits.
Approve a Migma email with its intended brand font and with a plausible substitute. Font substitution can change line lengths, button fit and section height even when every word stays the same. The fallback deserves a layout decision, not merely a name at the end of a font list.
Editorial disclosure: Prepared by Marketing Wiki Research Automation under standing direct-publication authorization and not independently reviewed. Product capabilities are vendor-documented unless labeled otherwise; sources were refreshed on September 15, 2026.
Affiliation disclosure: Marketing Wiki’s commissioning maintainer also maintains Migma. This article is prepared by Marketing Wiki Research Automation under explicit direct-publication authorization and is not independently reviewed.
Migma's brand settings let teams review font choices, and its compatibility guidance explicitly notes that inboxes may replace fonts. We recommend recording an acceptable fallback appearance alongside the brand choice so reviewers know which differences are harmless and which lose meaning.
A specimen that reveals fit problems#
Build this original specimen inside a private test copy of the actual email:
- A headline containing the longest approved product name.
- A two-line paragraph with punctuation and a numeric price.
- A button with the longest planned action label.
- A short disclaimer containing a meaningful qualification.
- A localized phrase from a language actually in scope.
Use real approved copy where available, or clearly synthetic content for development. Do not shorten every test string to make the design pass. The point is to expose the typography the campaign will actually demand.
Litmus's web-font guide explains fallback font families and the importance of differing font metrics. Its stated January 2025 update and age warning make it unsuitable as a definitive current client-support matrix. This article uses the durable fallback principle and requires testing for the current client mix.
Define invariants before comparing screenshots#
An invariant is something the design must preserve when the font changes. For this specimen, require all copy to remain visible, the button to contain its label, the qualification to stay attached to the relevant offer, and the heading hierarchy to remain obvious.
Do not require identical line breaks. That would make a metric difference look like a defect even when the email is readable. Conversely, do not accept a clipped price merely because the substituted font looks close to the brand font.
Record the comparison in a compact worksheet:
| Element | Allowed variation | Blocking failure |
|---|---|---|
| Product headline | Additional line | Hidden product qualifier |
| Body paragraph | Taller block | Overlap with the next section |
| Main button | Wider or taller button | Cropped or unreadable label |
| Offer note | Different wrapping | Appears to qualify the wrong product |
| Localized text | Different glyph shape | Missing or substituted characters |
Force a fallback in a safe fixture#
In an authorized local copy, remove access to the intended web font or replace the declared family with the fallback being evaluated. Inspect the result at the same width and text size as the baseline. Document exactly how you forced substitution.
This is a controlled design exercise, not proof that an inbox makes the same substitution. Follow it with a received test in the supported clients. Record the font you can actually establish; if you cannot identify the rendered family, describe the visible result without claiming a specific font was used.
Migma's documentation does not establish a universal forced-fallback switch. Use the exported HTML when a controlled local fixture is necessary, and keep that experimental copy separate from the approved campaign.
Repair fit in a useful order#
First allow the container to grow. Then adjust spacing or reduce unnecessary wording. If the long button label still fails, rewrite it without losing the action's meaning. Shrinking all text should be a last resort because it can make the message harder to read.
Use the Visual Editor for the supported content and spacing changes. Save a concise instruction in the brand guidance if the repair is durable, such as allowing a product headline to wrap. Do not store a one-off workaround as a universal brand rule without reviewing other templates.
Accept the fallback as part of the brand#
Retain both versions with a short explanation of the accepted differences. When a brand font or template changes, rerun the specimen. When only the campaign copy changes, check the affected elements with their new longest strings.
The brand consistency rubric evaluates the overall identity. This method isolates the layout consequences of a missing font. No email client or font-loading behavior was measured here. Start by selecting one real long headline and one long button label for the next authorized typography review.
Sources behind this page
Claims remain tied to dated source review. Method and corrections stay public.