# UnnestComponents in VF

**URL:** <https://forum.glyphsapp.com/t/unnestcomponents-in-vf/28725>\
**Category:** Glyphs\
**Created:** [February 1, 2024, 2:28am UTC](https://forum.glyphsapp.com/t/unnestcomponents-in-vf/28725 "2024-02-01T02:28:16Z")\
**Posts on this page:** 7\
**Page:** 2

<div class="post-metadata">

**Author:** ![eliason](https://forum.glyphsapp.com/user_avatar/forum.glyphsapp.com/eliason/32/269_2.png) [@eliason](https://forum.glyphsapp.com/u/eliason)\
**Post date:** [August 27, 2025, 1:45pm UTC](https://forum.glyphsapp.com/t/unnestcomponents-in-vf/28725/21 "2025-08-27T13:45:55Z")

</div>

As I understand it, that decomposes all the way down to the paths. Won’t that give me incompatible masters in a font (like this) in which the pixels overlap in some masters and not in others?

---

<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:** [August 28, 2025, 7:28am UTC](https://forum.glyphsapp.com/t/unnestcomponents-in-vf/28725/22 "2025-08-28T07:28:03Z")

</div>

No, it works fine. Overlaps are not removed in a VF.

---

<div class="post-metadata">

**Author:** ![eliason](https://forum.glyphsapp.com/user_avatar/forum.glyphsapp.com/eliason/32/269_2.png) [@eliason](https://forum.glyphsapp.com/u/eliason)\
**Post date:** [August 28, 2025, 3:50pm UTC](https://forum.glyphsapp.com/t/unnestcomponents-in-vf/28725/23 "2025-08-28T15:50:20Z")

</div>

Seems to have worked, thanks for your help!

---

<div class="post-metadata">

**Author:** ![Martino](https://forum.glyphsapp.com/letter_avatar_proxy/v4/letter/m/49beb7/32.png) [@Martino](https://forum.glyphsapp.com/u/Martino)\
**Post date:** [September 27, 2025, 6:02pm UTC](https://forum.glyphsapp.com/t/unnestcomponents-in-vf/28725/24 "2025-09-27T18:02:15Z")

</div>

I’m revisiting the topic a bit, because I’m setting up a parametric slant, and I have to say it works perfectly if I need to generate a static italic (or slanted) font.  
The problems arise with a VF. Despite everything, the components, some of which are nested, don’t behave as they should.  
I tried using UnnestedComponents, but it seems to be incompatible with the slant filter: it prevents the upright from being slanted.  
Any suggestions? Is it possible to decompose and flatten the outlines before slanting? I’ve tried everything, but to no avail. Glyphs slants first and then decomposes.  
Thanks for any suggestions.

---

<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:** [September 27, 2025, 6:43pm UTC](https://forum.glyphsapp.com/t/unnestcomponents-in-vf/28725/25 "2025-09-27T18:43:29Z")

</div>

Did you try PreFilter parameters?

---

<div class="post-metadata">

**Author:** ![Martino](https://forum.glyphsapp.com/letter_avatar_proxy/v4/letter/m/49beb7/32.png) [@Martino](https://forum.glyphsapp.com/u/Martino)\
**Post date:** [September 27, 2025, 8:41pm UTC](https://forum.glyphsapp.com/t/unnestcomponents-in-vf/28725/26 "2025-09-27T20:41:28Z")

</div>

I thought about it, but then I read this: “same as Filter, but applied before decomposition. Only applies to static fonts.”  
But my instance is variable. And in any case, it’s not very clear how and when the prefilter is invoked: it states that the prefilter acts before decomposition. Interpreted correctly, this means that the decomposition occurs before the transformation, which is found in the filter.  
So, in theory, the decomposition has already occurred when the font is slanted.  
But that’s not the case for me. In my opinion, it doesn’t happen. And to confirm my idea, I tried manually decomposing some critical glyphs. Well, the variable slant works well, at least for the decomposed glyphs.  
Anyway, out of curiosity, given your suggestion, I tried and inserted UnnestComponents into the prefilter, but unfortunately, it had no effect. The problematic glyphs remained as they were, with their display glitches.

---

<div class="post-metadata">

**Author:** ![Aida](https://forum.glyphsapp.com/user_avatar/forum.glyphsapp.com/aida/32/29971_2.png) [@Aida](https://forum.glyphsapp.com/u/Aida)\
**Post date:** [October 14, 2026, 6:20pm UTC](https://forum.glyphsapp.com/t/unnestcomponents-in-vf/28725/27 "2026-10-14T18:20:39Z")

</div>

It looks like there was recently an update to the Unnest Components filter to apply to variable fonts (thank you for that!). But it doesn’t seem to apply to virtual masters, only the primary masters so I’m still getting export errors with VFs that need unnesting+have virtual masters.

[Previous page](https://forum.glyphsapp.com/t/unnestcomponents-in-vf/28725.md?page=1)
