Will the export frame change size problem be solved?

Ask the community
1

Hello,

Will the export adding 1px to widths and heights be solved?

I saw other topics related to this issue (like this one: Export adds 1 pixel to widths and heights - #2 by Gleb) and I’m sure Figma’s team is aware of it, but is there any way this problem will be solved soon?

When on my workflow, I don’t usually worry where and if I’m putting the frames on a non decimal number on the coordinates. Is there any way this will be solved, or for now I just need to check the coordinates everytime I export something? For me it’s an unnecessary added worry, not ideal when wanting to export things fastly and in bulk.

Also, is there another way to check this faster that I’m not aware of?

Thanks in advance! :slight_smile:

1 Like
3

image
image1728×1188 155 KB

This icon is set at 16x16px. However, once exported, a pixel is added to the SVG. Please help as this is happening to most of our icons.

SVG code:

<svg xmlns="http://www.w3.org/2000/svg" width="16" height="17" fill="none" viewBox="0 0 16 17">
  <path fill="#FB9C23" d="M15.593 8.02 8.973 1.4a1.38 1.38 0 0 0-1.946 0L.407 8.027a1.373 1.373 0 0 0 0 1.946l6.62 6.614A1.334 1.334 0 0 0 8 17a1.38 1.38 0 0 0 .98-.407l6.613-6.613a1.386 1.386 0 0 0 0-1.96Zm-8.26-2.74a.667.667 0 0 1 1.334 0v4a.667.667 0 1 1-1.334 0v-4Zm.7 7.673a1.026 1.026 0 0 1-1.013-.98.98.98 0 0 1 .98-1.02 1.02 1.02 0 0 1 1 .98.987.987 0 0 1-.967 1.02Z"/>
</svg>
4

I have also had this problem, exporting a frame to an image. The parent frame being exported was at whole value dimensions and x/y coordinates. I am certain there were child frames at decimal dimensions and x/y coordinates due to a scale, but the parent frame should not change upon export if after a scale it’s 1440x900 at 0/0 for example.

5

This bug still seems to be live and kicking.

6

Hey @Petri_Tolppanen1 ,
Thanks for flagging this. We’ve released an update when exporting objects with a multiplier applied no longer adds an extra pixel to width and/or height, via the Little Big Updates. More information here:

If you are still running into this issue, please reach out directly to the support team so we can investigate it here.
Be sure to use your Figma account email, include links to the file, and share it with support-share@figma.com so they can take a closer look. Thank you!

7

I saw an answer on another thread where the issue is caused by the frame starting from a sub pixel value which happened to me as well. It can be very hard to notice if the X value is like 130.02. I wasn’t expecting that to ever happen because I have the snap to pixels setting on so I didn’t check the frame position initially.

1 Like
8

Your tip just saved me. @Petri_Tolppanen1! Thank you!

1 Like