Font Modification Rights: Can You Edit, Subset, or Fork a Font?

What Counts as Font Modification

The word "modification" in a font license covers a broader range of actions than most people expect. At the most obvious end sits glyph editing: opening a font in FontForge or Glyphs and redrawn a letterform is clearly modification. But the legal definition extends into territory that feels technical or even automatic.

Font modification includes any of the following actions, though different licenses draw the line in different places:

The key principle is that font software is protected by copyright law in most jurisdictions. The font file itself, and the code that defines its outlines and metrics, receives the same copyright protection as any other software. The designer or foundry that created it retains those rights unless they explicitly grant them away through a permissive license.

This means that even technically simple operations, like running a font through a compression tool or stripping OpenType features you do not use, may require explicit permission from the license. Always check your specific license before making any change to a font file, regardless of how minor it seems.

OFL Modification Rules

The SIL Open Font License (OFL) is the most widely used open-source font license and one of the most permissive when it comes to modification. Google Fonts, most fonts on Font Squirrel, and thousands of fonts on GitHub use the OFL. Understanding its rules is essential for any designer or developer working with open-source typefaces. For a broader overview of the OFL alongside Apache 2.0 and Creative Commons, see the guide to open source font licenses.

The Reserved Font Name Mechanism

The most important restriction in the OFL is the Reserved Font Name (RFN) clause. When a font author designates certain names as "reserved," you are prohibited from using those names for any modified version of the font. The reservation typically covers the font family name and sometimes the foundry name.

For example, if you modify the Lato font (which uses the OFL), you cannot distribute your modified version under the name "Lato." You must rename it. This requirement exists to protect the original author's reputation: end users should not confuse a modified derivative with the original, carefully crafted typeface.

The Copyleft Requirement

The OFL has a copyleft requirement for derivatives: any modified version you distribute must also be released under the OFL. You cannot take an OFL font, modify it, and release it under a more restrictive commercial license. This makes the OFL a "share-alike" license for font files, similar to how the GPL works for software.

Importantly, this copyleft requirement applies only when you distribute the modified font files themselves. Using an OFL font in a commercial product, embedding it in a website, or including it in an app does not require you to release your product under the OFL.

Subsetting Legality

Subsetting is the process of creating a smaller version of a font by removing characters that your project does not use. A full Latin font might contain 600 glyphs covering dozens of languages, but an English-only website may only need around 200. Subsetting eliminates the unused glyphs, reducing file size by 50 to 80 percent in some cases.

From a technical standpoint, subsetting is a form of modification: you are producing a new font file that contains fewer characters than the original. Whether this is legally permitted depends entirely on your license.

The Tacit Acceptance Problem

A common misconception is that because subsetting is so widely practiced for web performance, it must be universally accepted. This is not the case. Many foundries tacitly accept subsetting because it is nearly impossible to enforce otherwise, and because denying it would make their fonts practically unusable for modern web delivery. But tacit acceptance is not the same as legal permission.

If your EULA says "you may not modify the font software" and contains no web exception, subsetting is technically a license violation even if the foundry has never enforced it. This becomes legally relevant during audits, mergers and acquisitions, or if your relationship with the foundry deteriorates.

Our Font Subsetter tool can perform the technical operation of subsetting, but the legal right to subset depends entirely on your license. Always verify permission before subsetting a commercial font.

Commercial Font Modification Restrictions

Most commercial font licenses contain language along the lines of "you may not modify, adapt, translate, reverse engineer, decompile, disassemble, or create derivative works based on the font software." This is broad enough to cover virtually every form of modification, including the gray-zone actions listed earlier.

In practice, what this means differs by foundry, by font, and by the specific action you want to take. Understanding the landscape of commercial EULA types helps you know what questions to ask.

How to Read Your EULA for Modification Rights

When reviewing a commercial EULA for modification rights, look for these specific terms:

• 1.Modification clause - Does it say "no modification" or does it carve out exceptions for specific use cases?
• 2.Derivative works - Are derivative works prohibited? Is there a definition of what constitutes a derivative?
• 3.Web embedding clause - Does the web embedding section mention format conversion or subsetting specifically?
• 4.Technical modifications - Some EULAs distinguish between artistic modification (glyph changes) and technical modification (format conversion), allowing the latter.

When in doubt, contact the foundry directly. Most foundries have a licensing team or support email that can clarify what is and is not permitted for your specific use case. Getting written confirmation protects you legally even if the EULA is ambiguous.

Variable Font Axes and Modification

Variable fonts are a single font file that contains a continuous design space, defined by one or more axes such as weight, width, or slant. A variable font can interpolate smoothly between a hairline weight and an ultra-bold, or between condensed and extended, using the same file. This raises new questions about modification rights that traditional font licensing never had to address. Beyond licensing, variable fonts also offer significant performance advantages over static font stacks; see our guide on variable font performance for implementation details.

Using Axes as Intended: Not Modification

When you use a variable font's axes through CSS or application controls, you are not modifying the font. Rendering a font at weight 350 or setting a custom optical size value uses the font exactly as the designer intended. These are legitimate design operations that the font file was built to support. No license distinguishes a user from a modifier based on where they position an axis slider.

/* Using variable font axes - always legal */
body {
  font-family: 'Inter Variable', sans-serif;
  font-weight: 350;         /* Interpolated weight */
  font-variation-settings: 'wdth' 85, 'opsz' 18;
}

Extracting Static Instances: A Gray Area

The modification question becomes more complex when you want to extract a static instance from a variable font. Using a tool to generate a standalone weight-500 OTF from a variable font file is a form of modification: you are producing a new font file that did not previously exist.

Under the OFL, this is permitted. Under most commercial licenses, it is not, unless the license specifically addresses variable font instance extraction. Some commercial variable font licenses explicitly prohibit creating static instances because the foundry sells those instances separately.

Programmatically Locking Axes

Locking an axis (setting it to a fixed value at the font file level rather than through CSS) is also technically modification. This includes actions like using a font tool to permanently set the weight axis to 700 and baking that into the binary. Again, the OFL permits this; most commercial licenses do not.

Rasterization and Embedding

Rasterizing Text to Images or PDFs

Rasterizing text means converting font-rendered text into a static image, a PDF, or another format where the individual characters are no longer separate, editable text objects. The font is used to render the text, but the output is an image file that no longer contains the font data itself.

This is generally not considered font modification. You are not changing the font file; you are using it to produce output. Most commercial licenses explicitly permit using a font to create printed or digital materials, and rasterized output falls squarely within that permission. Creating a logo as a PNG, exporting a presentation as a PDF, or generating a social media image all involve rasterization and are almost universally permitted by font licenses.

Embedding in PDFs and E-books

Embedding is different from rasterizing. When you embed a font in a PDF or e-book, the actual font data, or a subset of it, is included in the output file. Readers use that embedded font data to render editable text. This is a different legal question from rasterization and requires its own license permission.

Most commercial font EULAs cover desktop use, which includes creating PDFs with embedded fonts from your licensed desktop application. However, server-side PDF generation, embedding in redistributable documents, or embedding in e-books (ePub, MOBI) may require separate license tiers. Check for clauses covering:

• •Document distribution - Can you send PDFs with embedded fonts to third parties?
• •E-book rights - Do you have explicit permission to embed in ePub or MOBI files?
• •Server-side generation - If a server generates PDFs with the font, do you need a server license?

Font Embedding Permission Bits (fsType)

Font files contain a technical field called fsType in the OS/2 table that signals the font creator's embedding intentions. These bits communicate whether a font is installable, preview-and-print only, editable, or restricted. However, these bits are informational, not enforced by law. A font marked as "restricted" is not necessarily restricted by its actual license, and vice versa.

Some applications (notably Microsoft Office) read and respect fsType flags. Others ignore them. From a legal standpoint, the EULA governs your rights, not the fsType value. If a font's fsType says editable but the EULA says no modification, you cannot modify it. Conversely, if fsType says restricted but the OFL grants modification rights, you can legally modify despite the bit value.

For a deeper technical treatment of fsType values and how applications interpret embedding permission bits, see our guide on Font Embedding Bits.

Related Licensing Guides