Skip to main content

Font conflict and resolution

Learn about font conflict issue, why it happens, how to fix it, and best practices to prevent this issue.

Supriya Bisht avatar
Written by Supriya Bisht
Updated this week

Font conflicts occur when two fonts share the same hidden identifier (font metadata) called the PostScript Name (PSName).

Fonts rely on PSName for identification. If two fonts share the same PSName, the operating system assumes that they are identical, even if they’re different versions or formats.

Every font has multiple names (font metadata). For example, family name (Helvetica Neue), full name (Helvetica Neue Regular), and the hidden but crucial PostScript Name (PSName) (HelveticaNeue-Regular).

Operating systems (OS) rely on PSName for font registration. When you sync a font, the operating system doesn’t ask “What’s your family/font name?” but check the PSName. If it finds another font already registered under that PSName, it considers it as duplicate font, even when the fonts are different versions or come from different sources.

This strict reliance on PSName is both the strength and weakness of the system. It ensures consistency when identifiers are correct. But when PSNames are same, you see font conflict symptoms that feel random and frustrating.

Examples:

  • Duplicate versions

  • Different font formats (TTF vs, CFF)

  • Mixing sources (purchased from foundry vs. synced from Monotype)

  • Historic cross-licensing

  • Duplicates within a family

  • Legacy vs. modern releases

Why font conflicts occur

Font conflicts can happen when multiple font management tools—or multiple copies of the same font—are active at the same time. This most commonly occurs when two fonts share the same PostScript (PS) Name, which is how design applications identify fonts.

When more than one active font uses the same PSName, design applications such as Adobe Illustrator, InDesign, and Photoshop may experience:

  • Fonts not rendering correctly

  • Unexpected font substitutions

  • Inconsistent type behavior

  • Occasional glitches or crashes

Resolving font conflict

Font conflicts can’t be eliminated entirely, but they can be avoided and minimized. Monotype Desktop app handles font conflicts issues in a user-friendly way, by activating only a single font for unique PSName.

This is done to shift conflicts from mysterious failures to manageable, predictable decisions for you.

The Monotype Desktop App v7.7.x detects, displays, and helps resolve font conflicts on your machine. The app partners with your operating system and other font managers to ensure a smooth and consistent font experience.

Where can I view font conflicts in the Monotype Desktop App

The app provides a dedicated Font Conflicts tab where you can see all fonts on your machine that share the same PSName and conflicts with each other.

This tab helps you to:

  • View all conflicting fonts: whether they come from Monotype, the system, local folders, or Adobe.

  • See the fonts that conflict grouped by their PostScript Name.

  • Click any font row to open a detailed pop-up showing:

    • PSName

    • Font format

    • Version

    • Source (Monotype, System, Local, Adobe, etc.)

How can Monotype Desktop App resolve font conflicts

Monotype Desktop App v7.7.x handles font conflicts depending on where the conflicting fonts originate. The scenarios and recommended steps to fix them are:

Scenario

Description

Resolution

Monotype Fonts are in conflict with each other

If the app detects that a newly requested Monotype font shares a PSName with an already activated Monotype font (from your synced inventory or imported fonts):

  • The older Monotype font will be automatically deactivated.

  • The newly requested Monotype font will be activated.

  • This ensures only one active font per PSName, preventing conflicts.

Unsync the Monotype font you no longer need for that PSName. This removes it from the Font Conflicts tab entirely.

Monotype Font conflicts with a system/local/Adobe font

If a Monotype font conflicts with any system, Local, or Adobe font:

  • The Monotype font will be deactivated by default to prevent system-level conflicts.

If you want to use the Monotype font:

  1. Deactivate the conflicting system/local/Adobe font using your OS font manager
    (e.g., Font Book on macOS).

  2. After the system font is deactivated, activate the Monotype font from the Monotype Desktop app.

If you want to use the System font:

Unsync the Monotype font for that PSName in the Monotype Desktop app.

System/local/Adobe fonts conflict with each other

If multiple system/local/Adobe fonts share the same PSName:

  • All of them will appear under the Font Conflicts tab.

  • All conflicting fonts remain active, since the Monotype Desktop app does not manage system fonts.

Deactivate the unnecessary font(s) using an external font manager (e.g., Font Book on macOS).


Once deactivated, the conflict is removed from the list.

Monotype fonts (including imported fonts) will not be activated if a System, Local, or Adobe font with the same PSName is already active on your machine.

Best Practices

While we are improving Monotype Fonts, you can also adopt simple best practices in font management and use new conflict-resolution tools as they arrive to reduce font conflict issues.

  • Keep your font libraries tidy and remove duplicates.

  • Stick to one source per family instead of mixing purchased and synced versions.

  • Align across teams so that everyone uses the same version of a font.

  • Contact our support team if fonts disappear or swap unexpectedly. Chances are it’s a PSName conflict in disguise.

Font conflicts aren’t random events. They’re a predictable outcome of how operating systems rely on PSNames. When two fonts claim the same hidden identity, the OS can’t tell them apart, and something breaks.

By surfacing conflicts clearly, offering user-friendly choices, and cleaning up duplications, you can make font management far smoother.

Frequently Asked Questions

Q1: Why do fonts disappear after installation?

The OS may overwrite one font if two share the same PSName. For example, if you install Font v1.2.1, not realizing that v1.2.2 is already present. Both fonts share the same PSName. The OS keeps only one, and it’s not always the one that you want.

Q2: Can I install both TTF and CFF versions of the same font?

No. Both formats share the same PSName, so only one can be active.

Many font styles are made available in two technical formats: OpenType TTF (TrueType outlines) and OpenType CFF (Compact Font Format - PostScript outlines). Both format versions of the same style always have the same PSName thus users can only install and use one format at a time.

Q3: How do I prevent font conflicts?

You can adopt best practices in font management and use conflict-resolution tools as they arrive to reduce font conflict issues.

Q4: Give an example to illustrate font conflict and its resolution?

Font conflict scenario:

A design team installs Helvetica from a subscription service. Later, they add a purchased version from a foundry. Both share the same PSName. The OS silently picks one, causing design layouts to break.

Resolution:

The team removes duplicate fonts, aligns to one source, and uses conflict-resolution tools.

Result:

Consistent font rendering and fewer support tickets.

Troubleshooting checklist

  • Adopt font management best practices

  • Check for duplicate fonts from different sources

  • Verify PSName using font management tools

  • Remove duplicates and restart the application

  • Sync fonts from a single source.

  • Contact our support team.

Need More Help?

Click on the chat icon to ask your question or contact our support team on [email protected].

Did this answer your question?