Solved

Embed iframe returns HTTP 1.1 500 when viewer is logged into Figma

Forum|Forum|4 months ago
May 12, 2026
14 replies
273 views

We're seeing a consistent HTTP 500 from https://www.figma.com/embed?embed_host=share&url=... when the viewer's browser is logged into Figma. Same embed URL, same file:

Logged out → works
Logged in → 500

Repro is just: open a prototype embed iframe while logged in to Figma on the affected account. The 500 happens during what looks (from devtools) like an internal refreshOnReadyForEmbed reload triggered by the auth-aware code path.

Reproducible across Chrome, Firefox, and Safari. Setting iframe.credentialless = true (Chrome only) avoids it by stripping cookies, but breaks Figma's password-protected file form, so it isn't a viable general fix.

Could someone from Figma confirm and/or give an ETA on a fix? Happy to share file IDs and HAR captures privately.

Thanks.

Note: we can reproduce reliably on some accounts but not others. We initially suspected it was specific to full-seat (paid) accounts, but we haven't fully confirmed that — login state is the only consistent differentiator we've isolated so far.

Best answer by Jaycee Lewis

Hey, @Emre Simtay 👋 Thanks for flagging. That sounds unexpected. You can report this and generate a bug report by following this guide — What to share in a bug report to Figma Support. — Jaycee

Show previous replies

Gav G

New Member

It seems like the issue is resolved.

Unfortunately, not yet for me in the UK. Perhaps the fix has to be rolled out globally.

Celyn_L

Figmate

Hi @Tonson Back, @Pris_r, @LisaMichelle, @Gav G — I work closely with Jaycee and I’m happy to help here.

It looks like this may have already been resolved for @Emre Simtay, but just checking in - are you still running into this issue?

If you are, the best next step would be to submit a bug report so the team can take a closer look at what might be happening in your specific setup.

You can do that by:

Going to the Support Hub - Clicking Start a chat -Typing “Report a bug”

When submitting, it would be really helpful to include:

A direct link to the affected file
Invite support-share@figma.com with “Can View” access (Note that this will not impact your billing and allows us to reproduce and investigate the issue with Engineering)
A screen recording showing the issue, if possible

Let me know if you’re still seeing this or if anything else comes up, happy to take a closer look.