# No Kerning after Export

**URL:** <https://forum.glyphsapp.com/t/no-kerning-after-export/25394>\
**Category:** Glyphs\
**Tags:** kerning\
**Created:** [March 16, 2023, 1:39pm UTC](https://forum.glyphsapp.com/t/no-kerning-after-export/25394 "2023-03-16T13:39:49Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![a2z](https://forum.glyphsapp.com/user_avatar/forum.glyphsapp.com/a2z/32/19124_2.png) [@a2z](https://forum.glyphsapp.com/u/a2z)\
**Post date:** [March 16, 2023, 1:39pm UTC](https://forum.glyphsapp.com/t/no-kerning-after-export/25394/1 "2023-03-16T13:39:49Z")

</div>

I’ve set up my kerning using KernOn (not sure if that changes anything) and once I export my typeface, the kerning doesn’t register in any design platforms. Any ideas how to fix this?

Note: I’ve also made 100% sure it’s the correct file installed.

 ![Screenshot 2023-03-16 at 09.38.00](https://forum.glyphsapp.com/uploads/default/original/3X/2/0/202121af98306b681cc5a7a2b982f1a3f13f7d16.png)

 ![Screenshot 2023-03-16 at 09.38.03](https://forum.glyphsapp.com/uploads/default/original/3X/e/6/e6e3144d66f79738f83459bf27ec4cc1baa3db3e.png)

---

<div class="post-metadata">

**Author:** ![FlorianPircher](https://forum.glyphsapp.com/user_avatar/forum.glyphsapp.com/florianpircher/32/30457_2.png) [@FlorianPircher](https://forum.glyphsapp.com/u/FlorianPircher)\
**Post date:** [March 16, 2023, 2:06pm UTC](https://forum.glyphsapp.com/t/no-kerning-after-export/25394/2 "2023-03-16T14:06:10Z")

</div>

Are you using the current cutting-edge Glyphs version? And have you a custom `kern` feature defined _Font Info_ → _Features_?

---

<div class="post-metadata">

**Author:** ![a2z](https://forum.glyphsapp.com/user_avatar/forum.glyphsapp.com/a2z/32/19124_2.png) [@a2z](https://forum.glyphsapp.com/u/a2z)\
**Post date:** [March 16, 2023, 2:23pm UTC](https://forum.glyphsapp.com/t/no-kerning-after-export/25394/3 "2023-03-16T14:23:49Z")

</div>

I do not have a kern feature. I’m also running 3.9.1, not the newest cutting edge version.

---

<div class="post-metadata">

**Author:** ![FlorianPircher](https://forum.glyphsapp.com/user_avatar/forum.glyphsapp.com/florianpircher/32/30457_2.png) [@FlorianPircher](https://forum.glyphsapp.com/u/FlorianPircher)\
**Post date:** [March 16, 2023, 2:29pm UTC](https://forum.glyphsapp.com/t/no-kerning-after-export/25394/4 "2023-03-16T14:29:04Z")

</div>

Can you have a look at the current version number in _Glyphs_ → _About Glyphs_. The latest non-cutting-edge should be 3.1.2.

---

<div class="post-metadata">

**Author:** ![a2z](https://forum.glyphsapp.com/user_avatar/forum.glyphsapp.com/a2z/32/19124_2.png) [@a2z](https://forum.glyphsapp.com/u/a2z)\
**Post date:** [March 16, 2023, 2:32pm UTC](https://forum.glyphsapp.com/t/no-kerning-after-export/25394/5 "2023-03-16T14:32:06Z")

</div>

Yup, sorry made a mistake - it says 3.2 (3179).

I think it might be an issue on my computer, as a friend of mine exported the typeface and it worked, working on clearing my font caches now to see if that helps.

---

<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 16, 2023, 2:33pm UTC](https://forum.glyphsapp.com/t/no-kerning-after-export/25394/6 "2023-03-16T14:33:20Z")

</div>

This is why I was going to ask how you made “100% sure” you were using the current exports.

Read this: [Testing your fonts in Adobe apps | Glyphs](https://glyphsapp.com/learn/testing-your-fonts-in-adobe-apps)

---

<div class="post-metadata">

**Author:** ![a2z](https://forum.glyphsapp.com/user_avatar/forum.glyphsapp.com/a2z/32/19124_2.png) [@a2z](https://forum.glyphsapp.com/u/a2z)\
**Post date:** [March 16, 2023, 2:44pm UTC](https://forum.glyphsapp.com/t/no-kerning-after-export/25394/7 "2023-03-16T14:44:34Z")

</div>

Didn’t realize font caches could cause an issue, I figured as long as I was deleting the previous version properly it would be fine - it wasn’t… All sorted now, just cleared my caches and we’re running smoothly.