Skip to main content
Question

Exporting at 2x/3x/Custom Scale Adds 1px Extra on Width & Height (Inconsistent Bug)


lalit_figwiz

When I export a frame or component at any scale factor (@2x, @3x, or custom), Figma sometimes adds an extra 1 pixel to both the width and height.

For example:

  • A 100×100 frame exported at 3x should result in 300×300, but instead, I get 301×301  or 300x301 or even 301x300.

  • This does not always happen, but when it does, it's consistent across devices and files.

  • Affects both PNG and JPG exports, regardless of pixel grid alignment or stroke presence.



    🛠️ Workarounds I’ve Tried (with partial success):

  • Creating a new frame, copying content into it, and exporting again — occasionally works.

  • Manually scaling the frame by the desired factor (e.g., scale by 3x), then exporting at 1x — this consistently avoids the 1px error.

  • However, these are not ideal for batch exporting or asset automation.

4 replies

Nellya
  • Power Member
  • 662 replies
  • July 11, 2025

Hi. Make sure your frame position doesn’t have sub-pixels after dot like 1224.1 or 245.45. This is often the reason why extra pixels are added after export.


Gayani_S
Figmate
  • Community Support
  • 2202 replies
  • July 11, 2025

Hi ​@lalit_figwiz, thanks so much for the detailed explanation and for doing a lot of troubleshooting already, and that’s super helpful.

I saw that you submitted a support ticket (#1426733) and our team has already responded. When you get a moment, could you please add support-share@figma.com to your file with can edit’ permissions? That’ll help the team dig into the specifics and get a better look at what’s going on.

 

Thank you, 

Gayani 


lalit_figwiz
  • Author
  • New Member
  • 1 reply
  • July 11, 2025
Nellya wrote:

Hi. Make sure your frame position doesn’t have sub-pixels after dot like 1224.1 or 245.45. This is often the reason why extra pixels are added after export.

Thanks for sharing 
But there are no sub pixels I was exporting in 300x400. It’s been happening with different assets. 
 


Gayani_S
Figmate
  • Community Support
  • 2202 replies
  • July 17, 2025

Hey everyone! I’m going to share the outcome of the ticket here, so anyone else running into the same issue can stay informed and benefit from the update.

 

Our engineering are aware of this issue. However, to be transparent, this will not have an immediate resolution as the team needs more time to investigate this. This is happening because the X or Y position of the some of the nested layers inside the frame are on a decimal place rather than an integer.

When a layer is set to a sub-pixel value this can cause the export to either be cropped by a pixel or an extra pixel wider. For now the recommendation is to ensure that the X,Y values are whole integer numbers for the frame and all nested layers.

 

You can either manually change its coordinates from the Properties Panel, or by using the Round-to Pixel function from the menu. Here is how to use the Round-to-pixel function: 

 

  1. Select that object and go to main menu - from there choose quick actions
  2. Search for Round to pixel and click this:

 

We’d also suggest also activating Snap to Pixel Grid to see if that helps. You can also enable it from the main menu - Quick actions:

Hope this helps! 


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