Skip to main content

Vector rendering inconsistencies when expanding strokes - causing issue with shape builder


Lauren_Medved

I’m looking into Figma Draw vs Adobe Illustrator and noticing some inconsistencies when using vector tools such as expanding / outlining strokes. Below I’ve attached two screenshots of the letter “e”. The black is from Adobe and the white is from Figma. This “e” was created using Georgia font as the default style, expanded to vector, sized to be 62.9px tall (specific for my use case), given a 2px outer stroke, and then expanded to vector again.
 

Adobe
Figma


As you can see, the Figma version has much more vector points. Though Adobe does have an extra line between the expansions (not sure if this is intentional or a bug, its always happened).

The rendering issue becomes more apparent when using the shape builder tool. As you can see, the Figma version has extra lines and loses the hole in the “e” whereas Adobe’s tool seamlessly combines the different sections. I use the tools in the exact same way, highlighting only the solid sections of the “e”, yet I cannot seem to get the Figma tool to combine properly without manually selecting the extra points/lines with the lasso which is more of hassle than what I do in Adobe. 
 

Adobe
Figma

I know Figma Draw is still in beta and these tools are still new, but I figured it’d be useful to share this. I would love to make the switch to Draw for my team, but I am worried how these issues will impact my vectors as I scale things. I work on a library of over 1,000 icons and they get used in a variety of sizes and exported in a variety of ways. I am worried that these inconsistencies may show and render incorrectly when exported as compared to the Adobe Illustrator counterparts. 

2 replies

Tom Reem
Figmate
  • Figmate
  • 67 replies
  • May 21, 2025

Hi ​@Lauren_Medved, thank you very much for raising this and for taking the time to explain why it matters to your team.

I can definitely see how this would be important when scaling a large icon library, especially across different sizes and export methods. I’ve raised your post internally with our Engineering team for review and will follow up with more clarity as soon as any updates are available.

 

Really appreciate you laying this out so thoroughly — and thanks again for your patience while we take a deeper dive.


Tom Reem
Figmate
  • Figmate
  • 67 replies
  • June 2, 2025

Hi ​@Lauren_Medved — circling back with some good news!

 

I’ve been in with the product team, and they’ve recently rolled out a few improvements that should resolve the issues you called out here. You can count on the results you're looking for in this case. ✅

 

We’re continuing to make updates to ensure long-term reliability, and really appreciate your patience as we work toward a smoother experience. When you have a chance, feel free to give it another go and let us know how it works out. 🙏🏻


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings