A Decade of Google Sans: From Product Lock‑Screens to Open‑Source – A Must‑Read Design Journey

Making Google Sans Flexible

Seven concrete design problems drove the evolution of Google’s brand typeface.

Challenge 1 – Product lock‑screens mismatched the 2015 logo

After the 2015 logo redesign, hundreds of product lock‑screens (fixed logo‑plus‑product‑name combos) required updating. Treating each lock‑screen as a unique logo proved unscalable. Google created Product Sans, a geometric, tightly‑spaced font optimized for large‑size product names. The same lock‑screen implementations remain in many Google apps.

Challenge 2 – Product Sans performed poorly in marketing and UI

Product Sans looked attractive but failed in short‑duration ads and small‑size UI text. Google commissioned Colophon Foundry to refine character shapes, stems, x‑height, and contrast, producing Google Sans, a font that works well on billboards and UI headings.

“Google Sans is driven by designer needs, not a top‑down decision,” noted Tobias Kunisch, Google font design lead.

Challenge 3 – Small‑size readability

When Google Sans launched in 2018 it was paired with Roboto for body text, creating a dual‑font system. To obtain a version suitable for small sizes, the team collaborated with the Search design group and Colophon Foundry, releasing Google Sans Text in 2020. Google Sans Text features taller, tighter characters, reduced geometric roundness, increased spacing, and matches Roboto’s proportions, improving legibility on devices such as the Pixel 3.

Challenge 4 – Limited script support

Google Sans initially covered only Latin scripts. Extending the family to support more than 20 writing systems required designing tens of thousands of new glyphs, each respecting the visual conventions of scripts such as Arabic, Chinese, Japanese, Korean, Russian, Thai, and Turkish. Partnerships with specialist foundries enabled the creation of the world’s largest multilingual font family.

Challenge 5 – Google Sans Mono unsuitable for code

Google Sans Mono (2020) was intended for medium and large sizes but proved hard to read at small sizes, especially distinguishing “a” and “o”. Google launched a dedicated project to create Google Sans Code, a monospaced typeface optimized for programming. Research on 20 common programming languages informed the design of distinct glyphs, numbers, and operators. Universal Thirst executed the final design, and Google Sans Code was open‑sourced in 2025 for the Gemini product.

Challenge 6 – Lack of expressive flexibility

To give designers fine‑grained emotional control, Google partnered with Font Bureau to develop Google Sans Flex, a variable font with six axes: weight, width, optical size, slant, slope, and roundness. The optical‑size axis automatically adjusts glyph shapes for different display sizes, from smartwatches to billboards, while preserving readability. A user study involving over 3,000 participants showed that participants valued the ability to adjust height, elegance, and roundness, confirming the importance of flexibility. Google Sans Flex received the 2024 Red Dot Design Award.

Challenge 7 – Proprietary font fragmentation

Google Sans was initially proprietary, leading to fragmented typography across first‑party and third‑party apps (e.g., Gmail vs. WhatsApp). In 2025 Google open‑sourced Google Sans and Google Sans Flex to enable a unified visual language across the ecosystem.