PNG exports of gradients contain transparent/translucent pixels
When exporting frames with gradients to PNG, you'll get semi-transparent pixels—even when all gradient stops are 100% opacity. This happens whether the gradient is applied directly to the frame or on a separate layer, as long as there's no solid fill behind it.
The attached Figma file includes four test frames. Visually, they appear identical, but only the fourth frame—with a solid fill behind the gradient—exports as fully opaque. You can verify this with a tool like: PNG transparency checker; the first three exports contain semi-transparent pixels.
A workaround is to move the gradient to a separate layer, then apply a solid fill to the frame behind it, like the fourth frame in the attached file. This avoids the PNG transparency problem but adds unnecessary layer complexity.
Repro Steps
Create a new Figma Design file
Add a frame
With the frame selected, change its fill to Linear Gradient.
@ksn, @Junko3 , @Tom Reem – sorry for the bump, but I posted 👆this almost a month ago with no reply. I even opened an official ticket last week (1443620) and haven’t heard back on it either.
Even a quick “we’re investigating” would be helpful. Other Report a Problem threads seem to get official responses within a few days, so I just want to make sure this hasn’t slipped through the cracks. It’s a frustrating bug for anyone using Figma Design for App Store assets since Apple reject PNGs with transparent pixels.
App Store Connect error “Images can’t contain alpha channels or transparencies” for PNG with a gradient background exported from Figma.
Hey @Uhl - apologies for the delay. Let me check in with our support team on this one. I’ll get back to you once I get an update.
Update for you @Uhl:
First, let me apologize again for the break in communication. I totally get wanting some validation, and we fell short of that.
After checking in with the support team, it looks like there was a support follow up response to the ticket you had originally made on 7/3, that was sent to you on 7/4.
Support also responded to each message we got from you afterwards (looks like 7/10 and/or possibly 7/11). I’m not entirely sure if you received those, so we’re thinking there’s something that blocked the communication from getting to you.
I know this may be an off-putting ask, but could you try checking your spam folder? If you’re emailing while on a company network, it’s also possible that the firewall that’s been put up has been blocking our responses to you as well. Please let me know when you have a chance if the latter is a possibility.
The current action I’ve taken: I spoke with our technical quality team, and was able to get your newest ticket escalated with them.
Thank you again for being patient with me 🙏🏻
Ah, I just realized what happened—I missed that reply because it was part of an older support case. My mistake for tacking on a new issue to an existing ticket!
Could you make sure any more replies about the PNG issue are sent under this ticket so I don’t miss them again? Thanks!
And for those who running into this problem, Figma support confirmed it’s a new bug:
Our engineering team has conducted a comprehensive investigation and confirmed that the problem you're facing is indeed related to a new bug. I am very sorry to let you know that at this time, unfortunately, we do not have an estimated timeline for a resolution.
No worries! We should have still made sure your separate issues ended up in separate tickets to avoid this confusion. I can’t be certain on my end, but I’m thinking we overlapped somehow with the timing of tickets.
I saw TJ was able to get in touch with you via the ticket you preferred above and got this situated, but let me know if you’re still needing help with anything related to this. Happy to help further! 😁
