# Custom typeface exported from Glyphs not recognized by MS Word

**URL:** <https://forum.glyphsapp.com/t/custom-typeface-exported-from-glyphs-not-recognized-by-ms-word/35960>\
**Category:** Using Fonts\
**Tags:** export\
**Created:** [March 6, 2026, 11:13am UTC](https://forum.glyphsapp.com/t/custom-typeface-exported-from-glyphs-not-recognized-by-ms-word/35960 "2026-03-06T11:13:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![faber\_glyphs](https://forum.glyphsapp.com/user_avatar/forum.glyphsapp.com/faber_glyphs/32/32519_2.png) [@faber\_glyphs](https://forum.glyphsapp.com/u/faber_glyphs)\
**Post date:** [March 6, 2026, 11:13am UTC](https://forum.glyphsapp.com/t/custom-typeface-exported-from-glyphs-not-recognized-by-ms-word/35960/1 "2026-03-06T11:13:17Z")

</div>

Hi everyone, I’m having trouble getting MS Word to recognize a new typeface I designed in Glyphs. Previous fonts I exported worked immediately without tweaking any settings. Could this be a font caching issue, or are there specific custom parameters I need to set up upon export?

---

<div class="post-metadata">

**Author:** ![GeorgSeifert](https://forum.glyphsapp.com/user_avatar/forum.glyphsapp.com/georgseifert/32/259_2.png) [@GeorgSeifert](https://forum.glyphsapp.com/u/GeorgSeifert)\
**Post date:** [March 6, 2026, 11:45am UTC](https://forum.glyphsapp.com/t/custom-typeface-exported-from-glyphs-not-recognized-by-ms-word/35960/2 "2026-03-06T11:45:26Z")

</div>

Please have a look at this page: [Eliminating font cache problems | Glyphs](https://glyphsapp.com/learn/eliminating-font-cache-problems)

---

<div class="post-metadata">

**Author:** ![faber\_glyphs](https://forum.glyphsapp.com/user_avatar/forum.glyphsapp.com/faber_glyphs/32/32519_2.png) [@faber\_glyphs](https://forum.glyphsapp.com/u/faber_glyphs)\
**Post date:** [March 6, 2026, 11:56am UTC](https://forum.glyphsapp.com/t/custom-typeface-exported-from-glyphs-not-recognized-by-ms-word/35960/3 "2026-03-06T11:56:15Z")

</div>

Thank you for the suggestions. I have already tried clearing the font cache, but unfortunately, it did not resolve the issue.

The only workaround that succeeded was forcing the font into Word’s prioritized fonts section via the Terminal (using this row “defaults write com.microsoft.office PrioritizedFonts -array “[name-of-the-font]””).

However, this is not a sustainable solution. Since I need to deliver the final typeface to a client, requiring terminal commands is way too technical and creates unacceptable friction, which would likely lead them to abandon the font entirely. I need the font to work natively out of the box.

---

<div class="post-metadata">

**Author:** ![SCarewe](https://forum.glyphsapp.com/user_avatar/forum.glyphsapp.com/scarewe/32/18952_2.png) [@SCarewe](https://forum.glyphsapp.com/u/SCarewe)\
**Post date:** [March 6, 2026, 3:25pm UTC](https://forum.glyphsapp.com/t/custom-typeface-exported-from-glyphs-not-recognized-by-ms-word/35960/4 "2026-03-06T15:25:05Z")

</div>

How many fonts do you have installed? There were recently some reports that too many installed fonts (how many exactly was not determined) led to fonts not being shown.

---

<div class="post-metadata">

**Author:** ![mekkablue](https://forum.glyphsapp.com/user_avatar/forum.glyphsapp.com/mekkablue/32/23_2.png) [@mekkablue](https://forum.glyphsapp.com/u/mekkablue)\
**Post date:** [March 10, 2026, 4:57pm UTC](https://forum.glyphsapp.com/t/custom-typeface-exported-from-glyphs-not-recognized-by-ms-word/35960/5 "2026-03-10T16:57:29Z")

</div>

And a font installation conflict is also a possible cause. Consider trying a different machine Which Word are you talking about, Office 365 on Windows?