Perplexity Space Embed iframe Not Loading: Fix

You embedded a Perplexity Space on your website or intranet using an iframe, but the space shows a blank area, a loading spinner that never finishes, or an error message instead of your content. This usually happens because the Space’s embed settings restrict access to specific domains, or because your browser blocks cross-origin content. This article explains the technical cause of the problem and provides three step-by-step fixes to get your embedded Space working again.

Why the Perplexity Space iframe Does Not Load

Perplexity Spaces are designed with security restrictions that prevent unauthorized websites from embedding them. When you embed a Space using an iframe, the browser sends a request to Perplexity’s servers. The server checks the Referer header of the request to see if the embedding domain is allowed. If the domain is not in the Space’s allowed list, the server returns a blank page or a cross-origin error. Additionally, if the Space is set to private or restricted to logged-in users only, visitors who are not authenticated will see an empty iframe. The browser’s Content Security Policy (CSP) or third-party cookie blocking can also prevent the iframe from rendering.

Cross-Origin Resource Sharing (CORS) Blocking

Modern browsers enforce CORS policies that restrict how a web page can request resources from a different domain. If your website is example.com and Perplexity’s server is perplexity.ai, the browser treats this as a cross-origin request. The Perplexity server must include the Access-Control-Allow-Origin header with your domain. This header is only added when your domain is in the Space’s allowed list. Without it, the browser blocks the iframe content.

Authentication Requirement

Spaces that are set to “Only specific people” or “Anyone with the link (sign-in required)” will not load for anonymous visitors. The iframe attempts to load the Space, but Perplexity redirects to a login page. The login page cannot render inside the iframe because of X-Frame-Options headers. The result is a blank iframe or a redirect error.

Steps to Fix the Perplexity Space Embed iframe

Follow these steps in order. Test the iframe after each step to see if the issue is resolved.

1. Verify the Space’s embed settings
   Open the Perplexity Space you want to embed. Click the Share button in the top-right corner. In the Share dialog, click Embed. Under Allowed Domains, make sure your website’s domain is listed. For example, if your site is www.example.com, type www.example.com and click Add. If you use multiple subdomains, add each one separately. Click Save.
2. Set the Space to public access
   In the same Share dialog, check the Access setting. Choose Anyone with the link and disable the Require sign-in option. This allows all visitors to view the Space without logging into Perplexity. Click Save.
3. Copy the embed code again
   After changing the settings, click Copy Embed Code. Replace the old iframe code on your website with the new one. The new code includes the updated domain allowlist and access settings.
4. Clear your browser cache and test
   Open a private or incognito window. Navigate to the page where the iframe is embedded. If the Space loads, the fix is complete. If it still fails, proceed to the next step.
5. Check browser console for errors
   In your regular browser window, press F12 to open Developer Tools. Click the Console tab. Reload the page. Look for error messages containing Access-Control-Allow-Origin, CORS, or X-Frame-Options. These messages tell you exactly which domain or policy is blocking the iframe.

If the iframe Still Does Not Load After the Main Fix

Some websites have their own Content Security Policy that blocks iframes from external sources. You may need to adjust your website’s CSP headers to allow iframes from perplexity.ai and all subdomains. Add the following directive to your server configuration or .htaccess file:

Content-Security-Policy: frame-src 'self' https://perplexity.ai;

If you use a CMS like WordPress, install a security plugin that lets you modify HTTP headers. Add the same frame-src directive to the plugin’s CSP settings.

If Perplexity Space Embed Still Has Issues

If the iframe remains blank after following all steps, check these additional factors.

Third-Party Cookies Are Blocked

Perplexity uses cookies to maintain session state. Some browsers block third-party cookies by default. Instruct your site visitors to add perplexity.ai to their list of allowed third-party cookies in browser settings. Alternatively, you can direct visitors to log into Perplexity in a separate tab before viewing the embedded Space.

Iframe Sandbox Attribute Restricts Content

If you added the sandbox attribute to the iframe tag, it may block scripts or forms needed by Perplexity. Remove the sandbox attribute or add the value allow-scripts allow-same-origin allow-forms. The updated iframe tag should look like this:

<iframe src="https://www.perplexity.ai/s/your-space-id" allow="clipboard-read; clipboard-write"></iframe>

Space Contains Large Files or Long Conversations

Spaces with many pages or large attached files may take longer to load. The iframe may appear blank until the content finishes loading. Wait at least 10 seconds. If the Space still does not appear, reduce the amount of content in the Space by removing unused pages or files.

Perplexity Space Embed: Public Access vs Restricted Access

Item	Public Access (Anyone with the link)	Restricted Access (Sign-in required)
Visitor authentication	Not required	Required — visitor must log into Perplexity
Iframe loading on external sites	Works if domain is allowed	Fails — login redirect is blocked by X-Frame-Options
Best use case	Public websites, blogs, knowledge bases	Internal wikis where all users have Perplexity accounts
Security risk	Anyone with the link can view the Space	Only authenticated users with access can view

If you need to embed a Space on a public-facing site, always use Public Access. For internal tools where every visitor has a Perplexity account, Restricted Access is acceptable but requires users to log in first in a separate tab.

Conclusion

You can now fix a Perplexity Space iframe that does not load by adding your domain to the Allowed Domains list and setting the Space to Public Access. Always copy the embed code after changing these settings. For persistent issues, check browser console errors and adjust your site’s Content Security Policy to allow frames from perplexity.ai. If your website uses a strict CSP, the frame-src directive is the most reliable way to ensure the iframe renders correctly.