새로워진 스냅덱, 더 빠른 덱 제작 흐름을 만나보세요.

Font license guide

Font licenses should be checked before design is finalized. License issues discovered late force font swaps, export changes, and rework across websites, apps, decks, and brand assets. Checking source pages early—when you are still comparing Inter, Pretendard, and SUIT at 14px—is cheaper than replacing typography after handoff.

See it rendered for real

These samples load real font files and render the same copy, sizes, and weights you would ship. Compare rhythm on screen, not thumbnails.

Pre-ship checklist · Pretendard

OFL UI sans with four common checks

Licenses OFL-1.1 · open source page
Before you ship
Checks 4/4
Web embedding · app bundling · logo usage · PDF redistribution—confirm each in the publisher text.

대시보드 Pretendard · 12–24px

snapdeck font summarizes license context; production decisions need the official source page.

Logo vs UI roles

Display for wordmarks · sans for product UI

Recommended

UI button · Pretendard 600

Get started

Avoid

Logo face on a 14px button

Get started

Many free fonts allow UI body text but restrict logo and CI usage separately.

Questions to answer before shipping

  • Can the font be used on websites, apps, PDFs, videos, ads, social templates, and printed materials?
  • Are embedding, self-hosting WOFF2, modification, subsetting, and server-side rendering allowed?
  • Does logo, CI, BI, merchandise, or product name treatment require separate permission?
  • Are there attribution requirements, volume limits, or seat counts for desktop design tools?
  • If the font came from an aggregator, does the summary match the foundry or author’s original text?

License types you will see

Names vary by foundry; always read the attached license file or web page.

  • SIL Open Font License (OFL): common on Google Fonts; generally allows commercial use with bundling rules—read Section 2 for reserved names and renaming.
  • Apache 2.0: used by some open-source UI fonts; permissive but still check trademark guidance for logos.
  • Ubuntu Font License, Bitstream Vera, and custom corporate licenses: read redistribution clauses carefully.
  • Noonnu and independent Korean authors: conditions differ per font—never assume one rule for all.
  • Fontshare and commercial-free promotional licenses: confirm expiration, embedding, and app use explicitly.

Channel-specific checks

  • Web: self-hosted @font-face, CDN usage, pageview caps, and whether all weights must be shipped.
  • Mobile apps: bundling TTF/OTF in iOS and Android builds, hybrid WebView usage, and offline PDF export.
  • Slide decks: embedding in PowerPoint/Keynote, PDF handoff to clients, and video recording of webinars.
  • Brand: logo outlines vs. live text, social ad templates, and merchandise mockups shown to the public.
  • Developer docs: monospace fonts in code blocks bundled with CLI tools or open-source repositories.

Documentation habits that save teams

  • Record exact font name, version, publisher, download URL, and date checked in your design system README.
  • Store a screenshot or PDF export of the license section—not just a checkbox in a spreadsheet.
  • Note which weights ship in production (400, 500, 600) to avoid accidentally bundling restricted cuts.
  • Flag fonts with different desktop vs. web licenses before Figma libraries sync to code repos.
  • Re-check licenses when upgrading font files or switching from desktop install to web embedding.

A practical license review flow

  1. Confirm the exact font name, publisher, file version, and official source page—not a mirror download.
  2. Open the license text or EULA linked from the publisher; ignore aggregator paraphrases for final decisions.
  3. Map allowed uses to your delivery channels: marketing site, logged-in app, PDF reports, and logo lockups.
  4. Check embedding and redistribution sections before engineers add WOFF2 files to the repo or app bundle.
  5. Save the source URL and permitted use cases in your design system or legal tracker for future audits.

License features in snapdeck font

  • Licenses tab grouped by common questions: commercial use, web, app, and logo restrictions.
  • Source links on every catalog card so you reach the publisher page in one click from discovery.
  • Hints when a font’s terms differ between desktop design use and production embedding.
  • Cross-links to Similar and Pairs so legal-safe substitutions stay close when a font fails review.