Skip to content

Fonts

Name a font family in your CSS and it is used:

body { font-family: "Lato", sans-serif; }
h1 { font-family: "Playfair Display", serif; }

Any family from Google Fonts works. You do not link a stylesheet or write @font-face: the service reads the family names in your template and makes them available. The first document that uses a family waits a moment while it is fetched; after that it is cached for everyone.

  • The font files come from a fixed version of the Google Fonts collection, so a document looks the same today and next year.
  • Families are matched by name, ignoring case, spaces and punctuation.
  • Each account can bring in 30 new families an hour. Families already cached cost nothing. Past that allowance the document still renders, with a built-in font in place of the new one.
  • The font used in a document is embedded in the PDF.

Every document also has a base set: Liberation (metric-compatible with Arial, Times New Roman and Courier New), DejaVu, and Noto for Arabic, Hebrew, Devanagari, Thai and other scripts. They are the fallback when a family is not found, and cover text that your chosen font has no glyphs for.

Families published with separate files per style, such as Lato, Poppins, Fira Sans, Ubuntu and Barlow, support every weight and italic they offer.

About a third of Google families are published only as variable fonts, a single file covering a range of weights. Inter, Roboto, Open Sans and Montserrat are among them. The service does not apply a variable font’s axes yet, so these families render in their regular style whatever font-weight or font-style you ask for. Validation tells you when this applies, with a VariableFontStyles note. If you need bold in one of these families today, pick a similar family that has static files.

Fonts that are not on Google Fonts are not supported yet.