FontLens

Web Font Embedding & App Bundling: License Terms Compared

Updated Nov 11, 2026

Legal Boundaries: Visual Rendering vs Binary Distribution

Exporting static PNG graphics or vector SVG paths from a design tool simply renders letterform artwork into bitmap pixels or geometric shapes.

In contrast, Web Font Hosting (@font-face) and Native App Bundling (iOS / Android / Desktop) physically distribute digital font software binaries (.woff2, .ttf, .otf) to client devices. Because software binaries are transmitted over public networks or packaged inside compiled client distributions, these practices trigger distinct redistribution clauses under intellectual property law.


1. Web Font Embedding Considerations

When implementing web fonts, client browsers download font resources dynamically from your origin or CDN:

  • SIL OFL 1.1 (Pretendard, Inter, etc.): Self-hosting WOFF and WOFF2 files on your own cloud storage or CDN is fully authorized. FontLens indexes 49 OFL typefaces that fully support modern web hosting architectures.
  • Apache License 2.0 (Roboto): Highly compatible with web delivery. Retaining the Apache 2.0 license notice in your public assets directory or CSS headers satisfies compliance obligations.
  • Corporate Proprietary Licenses: Some corporate fonts allow web font display but explicitly forbid third parties from generating their own custom WOFF2 subset files, requiring users to link to official hosted CDNs.

2. Mobile & Desktop Application Bundling

Packaging fonts inside native app bundles (assets/fonts/) in React Native, Flutter, Swift, or Android APK distributions permanently packages the font binary into the distributed software:

  • Software Bundling Authorizations: SIL OFL 1.1 Clause 2 expressly permits font software to be "bundled, redistributed and/or sold with any software". This explicitly authorizes mobile app packaging and software suite distribution.
  • Open-Source Attribution Screens: When bundling OFL or Apache 2.0 fonts into commercial apps distributed through the Apple App Store or Google Play Store, include the font copyright statement and license text within your application’s "Legal Notices" or "Settings > About > Third-Party Licenses" view.

Direct Comparison: Web vs App Integration

Evaluation Criterion Web Embedding (@font-face) Mobile App Bundling
Target Asset Format WOFF2 / WOFF (Compressed web container) TTF / OTF (Native font software)
Delivery Mechanism Dynamic on-demand HTTP download Static compilation inside APK / IPA
SIL OFL 1.1 Stance Permitted across public networks Permitted under Clause 2 (Software Bundling)
Corporate Terms Usually permitted (Check CDN-only rules) Varies; verify embedded software restrictions
Operational Requirement Maintain asset headers / CSS credits Mandatory in-app Open Source License screen

Get notified when a font license changes

We'll email you when the license of a font we track changes.

Sign in with Google to turn on alerts.

By continuing with Google, you agree to receive FontLens license change emails. You can unsubscribe anytime.

Read the privacy policy·No marketing emails.