Embedded vs. Static Font Rights explained.
Note: This feature requires a Connect + Insight Agency Platform subscription and the Desktop Client updated to 27.0.3 or later
Connect offers two types of font rights: Full Static Graphic Rights and Embedded Font Rights. Not sure what these terms mean? This article will help.
Full Static Graphic Font Rights are fairly straightforward. They allow you to use a font to create images for a wide range of uses. However, static rights are exactly that: Static, which is to say they do not have the font software embedded into the file.
Think of font software like instructions: they tell the entity reading the file, whether it’s a computer or a printer, what the text is supposed to look like. The moment you send a document to someone else—or move it into another system—you risk font substitution unless the font travels with the file in some form. Embedded Font Rights solve that problem by allowing you to embed the software into the file, ensurinh the file will behave predictably when it leaves the environment where it was created.
Static rights are adequate in many cases, but there are several key benefits to embedding a font:
Embedding keeps the typography consistent.
If the recipient doesn’t have the font installed, most applications will substitute a different font that may or may not be a close match. That can change:
line breaks and page count
spacing/kerning
brand “look”
legibility in regulated layouts (tables, forms)
Embedding reduces rework and production risk.
Printers, prepress teams, and downstream production systems need reliable inputs. A “missing font” error can stop a job cold or force last‑minute substitutions.
“Read-only” distribution (especially PDFs) For PDFs, embedding supports the idea that a document should be viewable/printable as intended without requiring the recipient to install anything.
That matters for things like annual reports, packaging approvals, contracts, and customer communications.
Embedding makes the file more self-contained for long-term retention.
Organizations often need files to render the same way years later (legal retention, regulated industries, brand archives). Depending on external font availability over time is fragile.
Cross-platform and workflow handoffs Files move through many tools—Office, Adobe, web-to-print portals, translation/localization workflows, DAMs, and automated rendering services. Those systems don’t share the same installed fonts.
Embedding reduces “it worked on my machine” failures during handoffs.
Common scenarios where embedding is the normal expectation
PDF documents distributed externally (reports, statements, marketing collateral)
Packaging/artwork files going to print vendors
PowerPoint/Keynote decks shared to clients or executives (so slides don’t reflow)
Templates shipped to regions/agencies (brand toolkits)
Editable files sent to localization partners
The licensing lens (without getting legalistic)
Embedding is effectively packaging a font (or part of it) inside something that will travel. That’s a different deployment than “a designer has it installed,” and it’s why font licenses often distinguish:
internal creation vs. external distribution
editable vs. read-only distribution
embedding in documents vs. embedding in software/apps