Embed not loading

If you open a linkembed link and see a blank area, an “access denied” message, or the content never appears, the embed isn’t loading. Here are the most common causes and what to try.

The source blocks embedding

Many platforms decide whether their pages can be shown inside another site. If they block embedding, we can’t override that. Your link will either stay blank or show an error from the source. See Limitations & platforms for notes on Google Drive, Dropbox, Notion, Untitled.stream, pCloud, and others. For platforms that don’t allow embedding, use a redirect link instead so visitors are sent to the content when they click.

Common browser errors include iframe-blocking headers like X-Frame-Options: DENY or restrictive frame-ancestors policies. If you are embedding a direct file URL (for example a .gif or .png), linkembed renders it as native media (img/video/audio) instead of framing the source page.

Sharing or permissions

For Google Drive, Dropbox, and similar services, the file or folder must be shared so that “anyone with the link” can view it (or shared with the right people). If the link is restricted, the embed will often show “access denied” or a blank screen. Check the sharing settings on the original file or folder and open the same URL in a normal browser tab to confirm it loads when not embedded.

Wrong link or embed code

Some platforms need their embed code, not the normal share URL. Untitled.stream is one example: use their Embed option and paste the embed code into linkembed, not the regular share link. If you pasted a plain URL and it doesn’t work, check the platform’s docs or share menu for an “Embed” or “Embed code” option and try that in the embed code field.

Browser or device limits

Embeds are shown inside a secure “sandbox” for safety. Some browsers or strict privacy settings can block or limit that. Try opening the linkembed URL in a different browser or device. If it works there, the issue is likely with the first environment (e.g. corporate firewall, strict cookie/iframe settings).

Protected links (password or email)

If the link is protected, visitors must verify access before seeing the content:

• Password protection — Visitors must enter the correct password.
• Email protection — Visitors must request access with an allowed email and open the access email link on the same device/browser.

If they don’t complete that step, they’ll keep seeing the protection form instead of the embed.

For more on platform-specific behavior and sandbox/iframe limits, see Limitations & platforms and Sandbox / iframe limitations. For the full email access flow (setup + troubleshooting), see Email protection in Core Features.