There is a quiet trap that catches designers, developers and hobbyists alike: the assumption that because a font landed in your downloads folder for free, you are free to use it. You are not, necessarily. A font file is a piece of software, and like any software, what you may do with it is governed by its license — not by how you obtained it.

This matters more than it sounds. Use the wrong font in a client logo, a commercial app, or a product you sell, and you can be looking at a cease-and-desist or a retroactive licensing bill. The good news is that the whole landscape comes down to a handful of license families, and once you can recognize them, the rules become simple. Here is the practical map — and, because this is a Linux-first site, how to read a font's license straight from your own machine.

A quick, honest caveat first: this is a plain-English explainer, not legal advice. License terms vary in their details and we are font people, not lawyers. When real money or real risk is involved, read the actual license text or talk to someone qualified.

The four rights you are actually licensing

Before the license types, fix one idea in your head: "using a font" is not one permission but several, and they are sold and granted separately. A license can grant some and withhold others.

The four that matter in practice are desktop use (installing the font and setting type in documents, images, logos), web embedding (serving the font with @font-face so it loads in a browser), app/product embedding (bundling the font inside software, a game, or a device), and modification (editing the glyphs and redistributing the result). A typical commercial "desktop license" grants only the first. The other three often cost extra or are forbidden outright. Most confusion in font licensing comes from assuming that one right implies the others. It does not. The misunderstanding becomes especially expensive once a font moves from personal experimentation into public-facing commercial environments — whether that means a SaaS dashboard, a monetized media platform, or a branded interface connected to projects like Casino Betwest, where typography becomes part of a product's visible identity rather than just a local design choice.

Proprietary and commercial EULA fonts

These are the fonts you buy from a foundry or that ship bundled with an operating system or an application. Their terms live in an End User License Agreement, and the EULA is the law of the font.

Commercial EULAs are usually tiered exactly along the four rights above: a desktop license for a fixed number of seats, a web license often metered by monthly pageviews, a separate app/embedding license, and sometimes a distinct ebook or broadcast license. The file itself is almost never redistributable — you cannot pass it to a collaborator or check it into a public repository. Fonts that came bundled with software (say, with a design app or an OS) are typically licensed for use within that environment, which is not the same as a free-standing license to use them anywhere. When in doubt with a paid or bundled font, the EULA is the only source of truth.

"Free for personal use" — the most misread label on the internet

This is where most people get burned. A huge share of the fonts on free-download sites are released as "free for personal use," and that phrase means exactly what it says and no more: free for things that make you no money. The moment a font touches commercial work — a client project, a product you sell, a monetized YouTube channel, a company's marketing — it needs a paid commercial license that the "free" download did not include.

If a font's license says "personal use only," treat it as off-limits for anything professional until you have bought the commercial tier. The price of ignoring this is not theoretical; foundries do enforce it.

SIL Open Font License (OFL) — the open standard

If there is a gold standard for genuinely free, do-what-you-need fonts, it is the SIL Open Font License. The overwhelming majority of high-quality open fonts — including most of Google Fonts and superfamilies like IBM Plex — use OFL, and it is the one to look for.

Under OFL you may use the font for anything, personal or commercial, with no fee. You may embed it in documents, on the web, and inside apps and products. You may modify it and redistribute your modified version. Two conditions are worth committing to memory. First, you cannot sell the font by itself — it can only be sold bundled inside a larger package (software, a product, a collection), never as a standalone product. Second, the license uses Reserved Font Names: if you modify the font and redistribute it, you must rename it so your version does not carry the original's reserved name. Derivatives also stay under OFL. For the vast majority of real-world uses, OFL means "yes, you're fine" — which is exactly why it has become the default of the open type world.

GPL with the Font Exception

You will see GPL attached to some open fonts, and there is a subtlety here that trips people up. The plain GNU GPL is designed for programs, and applied naively to a font it could create a nasty side effect: because embedding a font in a document arguably combines the two, a strict reading could try to impose the GPL on every document that uses the font. That is obviously not what anyone wants.

The fix is the GPL Font Exception, a clause most GPL-licensed fonts carry that explicitly says documents embedding or using the font are not themselves bound by the GPL. So: a GPL-with-exception font is free to use, modify and redistribute, and your documents stay yours. Just confirm the exception is actually present before you rely on it. (Worth noting, since you're here: Fontmatrix the application is GPL v2 — that governs the software, not the fonts you manage with it.)

Apache 2.0, public domain and CC0

A few more you will meet. Some open fonts — historically Roboto, among others — ship under the Apache License 2.0, a permissive license that allows commercial use and embedding as long as you preserve the license notice. Public domain and CC0 fonts carry no conditions at all: do anything, attribute nothing. These are the most permissive of all, though genuinely public-domain fonts are rarer than the internet implies, so verify rather than assume.

What about Google Fonts?

Short version: Google Fonts is safe. Every font in the library is open source and free for both personal and commercial use, released under either the OFL or Apache 2.0. You can self-host them, embed them in apps, and bundle them in products. They are the path of least resistance precisely because the licensing is settled — which is why so much of the web runs on them.

How to check a font's license on Linux

The advantage of working on Linux is that the answer is usually sitting on your disk. A few reliable moves:

When you install an open font from a package or a download, the license almost always travels with it as an OFL.txt, LICENSE, or COPYING file in the same archive or in /usr/share/doc/<fontname>/. Read it; it is the definitive answer. Fonts also carry license metadata inside the file itself, in the name table (license description and license URL fields). You can read those without opening a GUI: otfinfo --info yourfont.ttf (from the lcdf-typetools package) prints the embedded license string and URL when present. And of course, Fontmatrix surfaces font metadata directly in its inspector, so you can check a face's classification and embedded information alongside a live preview before you commit to using it anywhere.

The habit worth building is simple: before a font goes into anything that ships or sells, find its license, confirm it covers the specific right you need — desktop, web, app, or modification — and only then use it.

The five myths to unlearn

Most licensing accidents trace back to the same handful of false beliefs. That a free download equals free use — it does not; the license decides. That buying a font lets you do anything with it — no, the EULA sets boundaries, often by use type. That OFL lets you sell the font — only bundled inside something larger, never on its own. That a desktop license automatically covers web @font-face — frequently it does not, and web use is a separate grant. And that embedding a font in a PDF is always permitted — it depends on the font's embedding permissions and license. Internalize those five and you have avoided the great majority of trouble.

Frequently asked questions

Can I use a free font for commercial work?

Only if its license permits commercial use. Fonts under the SIL OFL, Apache 2.0, or public domain/CC0 are free for commercial use. Fonts labeled "free for personal use" are not — they require a separate paid commercial license. Always confirm the license before using a font in paid or for-profit work.

What is the difference between OFL and GPL for fonts?

OFL is purpose-built for fonts: free use including commercial, embedding and modification, with the conditions that you can't sell the font standalone and must rename modified versions (reserved names). GPL is a software license; for fonts it should carry a Font Exception so that documents using the font aren't themselves forced under the GPL. Both allow free use, but OFL is the more common and more font-specific choice.

Are Google Fonts free for commercial use?

Yes. Every font on Google Fonts is open source and free for both personal and commercial use, released under the SIL OFL or the Apache License 2.0. You can embed them on the web, self-host them, and bundle them in applications and products.

Does a desktop font license let me use the font on a website?

Not automatically. Desktop use and web embedding (@font-face) are separate rights. Many commercial licenses sell them independently, often metering web use by pageviews. With open fonts under OFL or Apache 2.0, both desktop and web use are included.

How do I find out what license a font uses on Linux?

Look for an OFL.txt, LICENSE, or COPYING file shipped with the font, often under /usr/share/doc/. You can also read the license fields embedded in the font's name table with otfinfo --info file.ttf from the lcdf-typetools package, or inspect a font's metadata directly in Fontmatrix.