Font licensing
Hebrew Font Licensing: Questions to Ask Before You Buy
Buying a font usually means buying permission to use software under stated terms, not ownership of the typeface. The practical task is to match the intended users, files, media, and distribution to the current license before production begins.
Treat the license as permission for a defined use
The font file is software and the letterform design remains protected. A license states what the license holder may do with the supplied files and resulting designs. Keep the terms and purchase record with the project files.
Do not infer rights from price, file format, or a download button. Read the current full terms linked from the product and license pages. This guide explains questions to ask; the approved license text remains the source of truth.
Identify the license holder and actual users
Decide whether the designer, studio, client, or another entity will hold the license. Then list who needs to install or access the files. A designer’s permission does not automatically transfer to every client employee or supplier.
Plan the handoff before purchase. A client may need its own license for continued editing, while final outlined artwork or exported images involve different file access. Follow the exact current terms rather than a general industry habit.
Name every medium and distribution path
List desktop design, print, social images, packaging, websites, applications, editable templates, video, and any product that embeds or distributes font data. The same visual campaign may involve several technically different uses.
For web use, confirm which files may be hosted, on which domains, and under what limits. For applications or templates, ask whether users receive or can extract font data. Do not upload desktop originals just because a browser accepts them.
Protect the files while collaborators work
Share font files only with people and systems covered by the license. Use controlled project storage rather than public folders or attachments that outlive the job. Remove access when a contractor no longer needs the files.
Printers and developers often need output or web assets, not unrestricted desktop files. Agree on deliverables and access early. If a vendor requires an installation, check whether the license covers that user before sending anything.
Check modifications, embedding, and redistribution
Outlining a word, modifying glyphs, subsetting, converting formats, and embedding are different actions. Technical capability does not grant permission. Locate the relevant clause or ask the foundry before altering files.
A logo made with a font and a modified font file are not the same deliverable. A PDF that securely displays text also differs from a template that lets recipients typeset new content. Describe the actual workflow when requesting guidance.
Keep a license record with the brand system
Record the license holder, purchase date, version of the terms, covered family and styles, approved users, domains, and source of the files. Link this record from the brand guide so future teams do not guess.
Review the record when the project expands to a website, app, company, vendor, or editable product. If the use is unclear, contact Font Penguin before production. A short question is cheaper than rebuilding a delivery workflow later.