Zurich Public Transport (ZVV) is replacing its expensive proprietary corporate typography with a more cost-effective alternative to slash millions in licensing fees. This strategic pivot targets the recurring costs of digital display licenses and software integrations across their massive transit network, prioritizing fiscal efficiency and open-standard compatibility over legacy brand aesthetics.
To the uninitiated, changing a font seems like a superficial branding exercise—a “paint job” for the city’s trams and trains. But for those of us who live in the architecture of the digital stack, This represents a calculated move to eliminate a specific type of technical debt: the proprietary licensing tax. In the world of enterprise software, fonts are not just shapes. they are licensed software assets. When you scale a typeface across thousands of digital signage screens, mobile apps, and internal terminals, the Conclude User License Agreements (EULAs) become predatory.
The financial hemorrhage occurs because proprietary foundries often charge based on “page views” or “app installations.” For a public utility with millions of daily interactions, these micropayments aggregate into a multimillion-franc liability. By switching to a more accessible or open-source alternative, Zurich isn’t just saving money; they are decoupling their infrastructure from the whims of third-party licensing audits.
The Licensing Tax: Why a Font Costs Millions
Most people assume that once a company buys a font, they own it. That is a dangerous misconception. Most professional typefaces are licensed, not sold. For a massive entity like ZVV, the licensing complexity is a nightmare. You have desktop licenses for the designers, server licenses for the web developers, and specialized licenses for embedded systems in those high-resolution LED displays at the platforms.
When a transit authority updates its app or refreshes its digital kiosks, they often trigger new licensing tiers. If the contract is based on “impressions,” every single time a commuter looks at a digital timetable, the foundry technically earns a fraction of a cent. Multiply that by the millions of commuters in Zurich, and you have a recurring operational expense that provides zero functional utility to the passenger.
This is a classic example of platform lock-in. Once a brand is built around a specific typeface—like the ubiquitous Helvetica or Frutiger—the cost of switching is high because it requires updating every single physical and digital touchpoint. However, as the cost of these licenses scales linearly (or worse, exponentially) with digital growth, the “switching cost” eventually becomes lower than the “maintenance cost.”
The 30-Second Verdict: Fiscal Sanity vs. Brand Ego
- The Problem: Proprietary EULAs creating massive, recurring “per-impression” costs.
- The Solution: Migration to open-standard or lower-cost typography.
- The Technical Win: Reduced legal friction and streamlined asset deployment across the CI/CD pipeline.
- The Bottom Line: Millions of francs saved by treating typography as infrastructure rather than art.
Variable Fonts and the Death of the Static Asset
Beyond the balance sheet, there is a massive technical upgrade happening here. The move away from legacy proprietary fonts often coincides with the adoption of Variable Fonts (VF). In the old world, if you wanted a “Bold,” “Italic,” and “Light” version of a font, you had to load three separate files. This increased HTTP requests and slowed down the rendering of digital signage.
Variable fonts change the game by packing multiple styles into a single .woff2 or .ttf file. Instead of discrete weights, the font exists on a continuum. A developer can specify a weight of 452 instead of just 400 or 500. This is critical for public transport displays where “readability” isn’t a suggestion—it’s a safety requirement.
By utilizing variable axes, ZVV can optimize the “x-height” (the height of lower-case letters) and “aperture” (the openness of letters like ‘c’ or ‘e’) in real-time based on the screen’s resolution and ambient lighting. This ensures that a commuter can read a departure time from 20 meters away, regardless of whether they are looking at a 4K OLED screen or a legacy LED matrix.
“The transition to open-source or variable typography in public infrastructure is less about aesthetics and more about sovereign control over the user interface. When you rely on proprietary licenses for your primary communication layer, you’ve essentially outsourced your brand’s visibility to a third-party vendor’s billing department.”
Legibility vs. Aesthetics in Public Infrastructure
There is a tension between “graphic design” and “information architecture.” A font might look beautiful in a print brochure, but if it fails the WCAG (Web Content Accessibility Guidelines) for contrast and legibility, it is a failure of engineering.
Public transport fonts must solve for “glanceability.” This means minimizing “character ambiguity”—the risk of a user confusing an ‘I’ (uppercase i) with an ‘l’ (lowercase L) or a ‘1’ (one). Proprietary fonts often prioritize the “look” of the brand over these micro-optimizations. By moving to a modern, technically-driven typeface, Zurich can implement better “hinting”—the process of aligning the font’s outlines with the pixel grid of a screen to prevent blurring.
| Feature | Proprietary Legacy Fonts | Modern Open-Standard/VF |
|---|---|---|
| Licensing Model | Per-seat / Per-impression (Expensive) | Open Source / Flat Fee (Low/Zero) |
| Payload Size | Multiple files per weight (Heavy) | Single file for all weights (Light) |
| Rendering | Static Hinting | Dynamic Axis Adjustment |
| Integration | Manual License Tracking | Automated via Package Managers |
The Broader Shift Toward Open-Source Sovereignty
This move by Zurich is a microcosm of a larger trend hitting the public sector. We are seeing a mass exodus from “Big Tech” licensing models toward open-source sovereignty. Whether it’s moving from Microsoft SharePoint to an open-source alternative or switching from proprietary fonts to Google Fonts or Inter, the goal is the same: reducing dependency.
When a city’s infrastructure depends on a proprietary license, they are vulnerable to “price gouging” during contract renewals. If a foundry decides to triple the price of a license, the city has two choices: pay the ransom or undergo a multi-million franc rebranding project. By adopting open-standard typography now, Zurich is effectively “future-proofing” its visual identity.
From a developer’s perspective, this likewise streamlines the deployment pipeline. Instead of managing license keys in a .env file or worrying about legal audits during a codebase migration, the team can simply pull the font from a GitHub repository and deploy it across the entire network. It transforms a legal headache into a standard software dependency.
the “millions” being saved aren’t just coming from the lack of license fees. They are coming from the reduction in administrative overhead, the improvement in digital performance, and the elimination of vendor lock-in. Zurich is proving that in 2026, the most “innovative” design choice a city can make is to stop paying for things that should be open.
