Skip to main content
Font support is available for email templates built with Elemental markup in Design Studio (Beta). Set a font_family on your email channel element and Courier handles the rest — including automatic font loading for Google Fonts.
This feature applies to Elemental content (version: "2022-01-01") on the email channel only. Classic Designer templates are unaffected.

Setting a Font

Add a font_family field to your type: "channel", channel: "email" element.
Pro Tip: Use the exact fontFamily string from the catalog for the most reliable results. Fuzzy matching is supported (e.g., 'Roboto', sans-serif resolves correctly), but the canonical value is safest.
How font loading works:
  • Web-safe fonts (e.g., Verdana, Geneva, sans-serif) — applied via CSS font-family only. No external loading required.
  • Google Fonts (e.g., Roboto, Arial, sans-serif) — the stylesheet is fetched automatically on Courier’s servers. You don’t need to include any <link> tags.
  • Default — if font_family is omitted, Helvetica, Arial, sans-serif is used.

Font Catalog

Courier supports 70 fonts across two source types. Query the full catalog via GraphQL to get the latest list and exact fontFamily values.

Querying the Catalog

Use the Courier client SDKs to query the font catalog from your application.
sourceType returns either system (web-safe) or google (Google Fonts). Use the fontFamily field value as-is for the font_family property in your Elemental content.

Web-Safe Fonts

Web-safe fonts are installed on most operating systems and render consistently across all email clients without any external loading. See Web Fonts vs Email-Safe Fonts for background on email client compatibility. The 10 web-safe fonts in the catalog and their fontFamily values are available by querying the catalog with sourceType: "system".

Google Fonts

Courier automatically loads these fonts for supported email clients. For unsupported clients, rendering falls back to the next font in the stack (see Email Client Support).

Email Client Support

Fonts are loaded server-side for supported clients. For unsupported clients, the email falls back gracefully to the next font in the CSS stack — no broken layout, no error. For example, with font_family: "Roboto, Arial, sans-serif", Gmail and Outlook render the email in Arial while Apple Mail renders it in Roboto.
Best Practice: Always include a web-safe fallback in your font stack (e.g., Arial, sans-serif) so the email looks great in all clients, not just those that support web fonts.

Elemental Overview

Learn how to build email content with Elemental markup

Channel Element

Full reference for the channel element and its fields

CSS Classnames

Apply custom CSS styles to Courier email template blocks

Email Safe Formatting

HTML and CSS best practices for cross-client email rendering