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

I can confirm this is happening for me as well when looking at my own figma prototype embeds on behance, and looking at other user’s figma prototype embeds.

Response in chrome developer tools is {"error":true,"status":401,"message":""}

Hey ​@Tonson Back , thanks for confirming! To help narrow this down, can you share:

1. OS (Windows / Mac / Linux) and browser.
2. When did you first notice it — was it Monday, Tuesday, or earlier?
3. Does it stop in incognito or after fully logging out? For me, incognito and signed-out both work; only signed-in fails.
4. Plan tier of the affected Figma account — free / Starter / Professional / Organization / Enterprise?
5. Other browsers — does Safari (or any non-Chromium browser) work for you on the same embed?
6. Is the affected account in the same org as the embedded file's owner, or is it any logged-in account on any embed?

I'd also love to swap quick details on the failing request — for me it's GET /api/user/state returning 401, then the iframe's outer response is 500. You're seeing the same 401 body. Do you see __Host-figma.embed cookies in the request headers?

The two answers I'd most want:

• When it started — pins the timeline.
• Plan tier / org — confirms it's not org- or plan-specific (he's a different org from yours, so if both fail, that's a global signal).

​@Tonson Back I get the same iframe error screen as you do, we are in New Zealand time, and it stopped working on Tuesday morning :) 

1. OS/Browser - Mac/Chrome
2. A few hours ago
3. Icognito works
4. Professional
5. Safari works, but I’m not signed into figma there
6. I only have my own account to test, sorry!

all headers attached, __Host-figma.embeddoesnt appear to be one

Thanks heaps ​@Tonson Back , this is really useful! A few quick takeaways from your data:

• Your __Host-figma.embed.mac cookie decodes to {"plan":"pro", expires_at: Jul 2026} — valid, unexpired, plan-stamped. Chrome is even sending it (sec-fetch-storage-access: active). Figma is just rejecting a valid embed session server-side. So it's not cookies or storage.
• You're Professional, I'm Enterprise, different orgs, different files, both failing the same way. So it's not plan-tier or org-specific.

One more apples-to-apples test if you don't mind: could you sign into Figma in Safari and retry the same Behance embed there? Would be great to know if Safari behaves the same as Chrome for you when signed in.

One workaround heads-up if you're tempted to try it: setting iframe.credentialless = true (Chrome only) does avoid the 500 by stripping cookies, but it breaks Figma's password-protected file form (the in-iframe password submission silently fails because the credentialless iframe can't persist Figma's session).

So it's not a viable general fix if any of your prototypes are password-protected.
 

I'll add your data to the bug report I filed, different account, different org, same exact 401/500 is the strongest signal yet that this is server-side at Figma. 🙏

I’m having the same issue. The  figma prototypes I have embedded in SharePoint are returning the “HTTP/1.1 500 Internal Server Error”. I’ve also tested with a different account, in different device, browser and internet connection, and I’m still getting the same error… It stopped working yesterday morning (CET).

I hope they can fix this soon🙏

We are having the same issue. Embedded in Confluence. I will try and see if I can get more background info.

EDIT:
For us it also seems like some users can and some cannot access. These users have the same viewing access as each other. 
Direct links to the same wireframe (not embed) can be viewed by all users but we need to use it in our documentation system.

Same here. It stopped working Tuesday 12 May. 
Users with or without an account get the same error, even when the mock-ups provide access to all. 

It seems like the issue is resolved.

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

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.

​@Celyn_L , thank you for checking in, it seems to have been resolved for our team! 

Hi ​@Celyn_L , thank you! Everything is working normally again on our side.