Skip to main content
ikhnm
New Member
Oct 14, 2026 7:17 AM UTC
Solved

Critical iOS Bug: Completely Wrong Images Displayed Instead of Original Photos After Recent Figma Update

Hello Figma Team,

I am reporting a serious image rendering bug that started on October 14, 2026, shortly after a recent Figma update.

This issue is severely affecting my daily work as a professional graphic designer.

What is happening?

When I open my Figma projects on my iPhone, some images are replaced with completely unrelated pictures.

For example, instead of a photograph of a woman wearing a winter jacket, Figma displays an illustration of a subway train.

This is not a situation where images are missing, blurry, or failing to load. Figma is displaying entirely different images that have nothing to do with my original files.

All images display correctly on my Windows computer.

Sometimes refreshing or reopening the file temporarily restores the correct images, but the problem keeps coming back.

When did the problem start?

  • October 13, 2026: Everything worked perfectly. All photographs displayed correctly on my iPhone.

  • October 14, 2026: The problem appeared suddenly, around the time of a recent Figma update.

  • Current Figma iOS app version: 26.39.1.

I suspect that the issue may be related to a recent update or a change in Figma's image rendering or caching system.

What I have already tried

I have spent considerable time troubleshooting this issue:

  1. Updated the Figma iOS app to the latest version — no improvement.

  2. Completely deleted and reinstalled the Figma app — no improvement.

  3. Opened Figma through Safari on my iPhone — exactly the same problem.

  4. Disabled my VPN — no improvement.

  5. Tested images downloaded from ChatGPT and Wildberries — both are affected.

  6. Logged into a completely different Figma account with available storage — the same issue occurred.

  7. Checked the original design files on my Windows computer — all photographs display correctly.

  8. Refreshed and reopened affected files — this sometimes temporarily fixes the images, but the issue returns.

My iPhone is relatively new and has plenty of available storage space.

Nothing has resolved the issue.

Important observations

  • The issue appeared suddenly after everything had been working normally the previous day.

  • The same problem occurs in both the Figma iOS application and Safari on iPhone.

  • Different Figma accounts are affected.

  • Images from completely different sources are affected.

  • Original images are displayed correctly on Windows.

  • Unrelated pictures appear in place of the original photographs.

  • Reinstalling Figma and disabling VPN do not help.

This suggests a possible problem with Figma's mobile image rendering, image caching, or image asset delivery.

Expected behavior

Images should display exactly as they do in the desktop version of Figma.

Actual behavior

Figma displays completely unrelated images instead of the original photographs on my iPhone.

Impact on my work

I am a professional graphic designer creating product listing images and infographics for online marketplaces.

I use Figma on my iPhone regularly to review designs and check product photography.

This bug makes it impossible to reliably review my projects on mobile. I constantly have to refresh files, and even then the correct images do not always appear.

This is significantly disrupting my work.

Request to the Figma Team

Could you please:

  1. Investigate this issue and escalate it to your engineering team?

  2. Confirm whether other iOS users have reported similar problems after the recent update?

  3. Check whether this could be related to image caching, rendering, or image asset delivery?

  4. Provide a temporary workaround if possible?

  5. Let me know whether a fix is being developed?

I can provide screenshots and screen recordings showing the incorrect images on my iPhone compared to the correct images on my Windows computer.

Please investigate this as a possible Figma bug rather than a device storage or image format issue, as I have already ruled out several common causes through extensive testing.

Thank you for your help.

Best regards,
Veronika

kat_figma
kat_figmaSolution
Figmate
Oct 15, 2026 12:25 AM UTC

Hi ​@ikhnm, ​@Amber Ou, ​@Filipp Bessolcin this should be mitigated. Can you please try to refresh to see if the images are now displaying correctly?

6 replies

Amber Ou
New Member
Oct 14, 2026 8:28 AM UTC

I'm experiencing the same issue.

Filipp Bessolcin
New Member
Oct 14, 2026 3:25 PM UTC

Can confirm from my side. Some our clients are getting weird results when opening prototypes.

For example: instead of marketplace app prototype we see a picture of some woman in the autumn - which is beautiful picture, but absolutely unrelated to our prototypes.

 

 

ksn
Figmate
Community Support
Oct 14, 2026 3:58 PM UTC

Oh no - thank you ​@ikhnm ​@Fil ​@AM 22 for flagging this.

As a first step, could you all share view access to the prototypes/files that are affected with support-share@figma.com? I can escalate those to our support and engineering team for investigation.

This would be super helpful. Once you’ve done that, please reply here and let me know. In the meantime, I’ll flag internally.

Thank you all so much!

ksn
Figmate
Community Support
Oct 14, 2026 8:26 PM UTC

Hey everyone - I wanted to drop an update:

Our engineering team is currently investigating this issue. I do not currently have an exact resolution time, but will continue to update this thread.

In the meantime, if anyone else seeing this has come across this problem, please share view-only access to the affected file with support-share@figma.com, and tag me in a reply so I can relay internally.

Thank you all again for your patience!

kat_figma
Figmate
kat_figmaSolution
Figmate
Oct 15, 2026 12:25 AM UTC

Hi ​@ikhnm, ​@Amber Ou, ​@Filipp Bessolcin this should be mitigated. Can you please try to refresh to see if the images are now displaying correctly?

Filipp Bessolcin
New Member
Oct 15, 2026 10:59 AM UTC

​@kat_figma Hi! Seems everything is ok now, thank you!