Configure System-Wide Kerning Pairs in Regedit

This article explores the relationship between the Windows Registry (regedit) and TrueType typography, specifically addressing how system-wide kerning pairs are handled across the operating system. You will learn about the structural limitations of the Windows Registry regarding font metric adjustments, where kerning data is natively stored, and the proper methods for deploying custom typographic kerning to Windows environments.

Does a Registry Parameter Exist for Kerning Pairs?

There is no registry parameter in Windows that allows an administrator to configure, add, or override system-wide kerning pairs for TrueType fonts.

Windows does not expose kerning tables or pair-adjustment metrics through the Registry because font metrics are designed to be immutable at the operating system configuration level. Instead, kerning logic is handled directly by typography APIs—such as Microsoft DirectWrite, Uniscribe, or legacy GDI—which read metrics natively embedded inside font binaries.

Where TrueType Kerning Data Resides

Kerning instructions are built directly into the compiled font file (.ttf or .otf) rather than the operating system settings:

• The kern Table: Legacy TrueType fonts contain a dedicated kern table that lists specific character pairs and their designated spacing offsets.
• The GPOS (Glyph Positioning) Table: Modern OpenType and TrueType fonts use the GPOS table to handle advanced kerning, optical adjustments, and contextual pair positioning.

When an application requests text rendering, the layout engine queries these internal font tables. If a font lacks specific kerning pairs, the Windows text subsystem cannot inject new pairs via the Registry.

Common Font-Related Registry Keys

While you cannot modify kerning pairs, the Windows Registry does offer keys for managing font availability, substitution, and fallback behavior under the following path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\

• \Fonts: Registers installed system fonts and maps font family names to specific font files.
• \FontSubstitutes: Defines string-based font substitutions (e.g., mapping Helvetica to Arial).
• \FontLink\SystemLink: Configures fallback fonts for character sets not supported by the primary font.

How to Apply Custom Kerning System-Wide

To achieve custom kerning pairs across an entire system or organization, administrators must modify and deploy the font file itself:

1. Edit the Font Binary: Open the custom TrueType font in a font editor (such as FontForge, Glyphs, or FontLab) and adjust the kern or GPOS tables with the desired pair metrics.
2. Recompile the Font: Export the updated typeface as a valid .ttf or .otf file.
3. Deploy via Group Policy or Intune: Distribute the updated font file to target machines and register it in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts.
4. Leverage Application-Level Settings: Ensure target applications (such as Microsoft Office, Adobe Creative Cloud, or web browsers) have kerning enabled, as some software disables pair kerning below specific point sizes by default.