# iFrame no longer working

**URL:** <https://community.baserow.io/t/iframe-no-longer-working/12736>\
**Category:** Uncategorized\
**Created:** [July 31, 2026, 3:09pm UTC](https://community.baserow.io/t/iframe-no-longer-working/12736 "2026-07-31T15:09:53Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![DavidCeulemans](https://community.baserow.io/user_avatar/community.baserow.io/davidceulemans/32/2342_2.png) [@DavidCeulemans](https://community.baserow.io/u/DavidCeulemans)\
**Post date:** [July 31, 2026, 3:09pm UTC](https://community.baserow.io/t/iframe-no-longer-working/12736/1 "2026-07-31T15:09:53Z")

</div>

hi,

is it me, or aren’t ‘iFrames’ no more working?

Something about using only links that you trust. Can I ‘trust’ them somewhere? Was working before.

‘embed’ seems to work, but then I’d have to recode…

thanks,

David

---

<div class="post-metadata">

**Author:** ![olgatrykush](https://community.baserow.io/user_avatar/community.baserow.io/olgatrykush/32/219_2.png) [@olgatrykush](https://community.baserow.io/u/olgatrykush)\
**Post date:** [July 31, 2026, 3:29pm UTC](https://community.baserow.io/t/iframe-no-longer-working/12736/2 "2026-07-31T15:29:38Z")

</div>

Hey @DavidCeulemans, I asked the dev team to check this issue. 🙌

---

<div class="post-metadata">

**Author:** ![jrmi](https://community.baserow.io/user_avatar/community.baserow.io/jrmi/32/5042_2.png) [@jrmi](https://community.baserow.io/u/jrmi)\
**Post date:** [August 3, 2026, 7:59am UTC](https://community.baserow.io/t/iframe-no-longer-working/12736/3 "2026-08-03T07:59:38Z")

</div>

Hey @DavidCeulemans

We recently improved the security for our IFrame element. This change may have impacted your existing integration. To help us identify the best solution, could you please clarify a few details?

- When you mentioned that something isn’t working, what exactly is failing (e.g., content not loading, script errors)?
- Are you using JavaScript within your embedded content to interact with the page?
- External URLs content are blocked in the editor but remain partially executed during preview and published versions. Is this issue also occurring in your live environment?
- If you are relying on JavaScript to access page content, have you considered hosting a custom external JavaScript file instead of accessing it directly from within the IFrame?

Looking forward to your answers so we can move forward with a fix.

---

<div class="post-metadata">

**Author:** ![DavidCeulemans](https://community.baserow.io/user_avatar/community.baserow.io/davidceulemans/32/2342_2.png) [@DavidCeulemans](https://community.baserow.io/u/DavidCeulemans)\
**Post date:** [August 3, 2026, 8:15am UTC](https://community.baserow.io/t/iframe-no-longer-working/12736/4 "2026-08-03T08:15:28Z")

</div>

Hi Jrmi,

thanks for looking into this.

I’ve been using iframes to show google-sheets charts. I’m using the interactive versions as opposed to flat images, so I assume there’s JS involved indeed.

if this kind of content is depreciated in frames, no problem, I can switch to embedding them instead. But if it’s a bug…

Edit: if you want to check: [https://spookycigars.baserow.site/statistics](https://spookycigars.baserow.site/statistics)

First chart = embedded, the others are iframes.

thanks again,

david

---

<div class="post-metadata">

**Author:** ![jrmi](https://community.baserow.io/user_avatar/community.baserow.io/jrmi/32/5042_2.png) [@jrmi](https://community.baserow.io/u/jrmi)\
**Post date:** [August 3, 2026, 12:24pm UTC](https://community.baserow.io/t/iframe-no-longer-working/12736/5 "2026-08-03T12:24:00Z")

</div>

Thansk for your answer and the link to the broken application, it helped.

I think it makes sense to add a property to unlock some security for URL when the user wants it. But these integrations will still only work in preview and published mode to not compromise the security.

What do you think?

Follow issue [IFrame element rejects previously working URLs as untrusted · Issue #5812 · baserow/baserow · GitHub](https://github.com/baserow/baserow/issues/5812) for more information.

---

<div class="post-metadata">

**Author:** ![DavidCeulemans](https://community.baserow.io/user_avatar/community.baserow.io/davidceulemans/32/2342_2.png) [@DavidCeulemans](https://community.baserow.io/u/DavidCeulemans)\
**Post date:** [August 3, 2026, 1:23pm UTC](https://community.baserow.io/t/iframe-no-longer-working/12736/6 "2026-08-03T13:23:33Z")

</div>

if you mean that the iframe won’t be ‘preview-able’ in the editor: that’s unfortunate, but the actual ‘Preview’ and ‘Published’ results are most important imo.

Just make sure the user is warned about it?

---

<div class="post-metadata">

**Author:** ![bgelbart](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/73ab20/32.png) [@bgelbart](https://community.baserow.io/u/bgelbart)\
**Post date:** [August 7, 2026, 11:47pm UTC](https://community.baserow.io/t/iframe-no-longer-working/12736/7 "2026-08-07T23:47:40Z")

</div>

I have also experienced issues with iframe content in the last month. It was looking and working totally fine, and then all of a sudden, the entire look as changed and there is no longer selection functionality for the baserow forms inside the iframe. I had not changed anything at all in the application and database during the time this changed happened.

Both of the iframes use a databases’ form for input (see form below)

What the iframes currently look like:

 ![iframe screenshot](https://community.baserow.io/uploads/default/original/2X/8/8eac0d0c2294a8e6bdfedc31e96a43539941e8ce.jpeg)

baserow form:

 ![database form](https://community.baserow.io/uploads/default/original/2X/e/e0331b5c35e64cc48a5a364452375e4f55a24389.jpeg)

 ![iframe screenshot](https://community.baserow.io/uploads/default/original/2X/8/8eac0d0c2294a8e6bdfedc31e96a43539941e8ce.jpeg)

---

<div class="post-metadata">

**Author:** ![olgatrykush](https://community.baserow.io/user_avatar/community.baserow.io/olgatrykush/32/219_2.png) [@olgatrykush](https://community.baserow.io/u/olgatrykush)\
**Post date:** [August 10, 2026, 12:29pm UTC](https://community.baserow.io/t/iframe-no-longer-working/12736/8 "2026-08-10T12:29:50Z")

</div>

Hey @bgelbart I assume this is related to the same issue: [IFrame element missing allow-same-origin breaks existing URL content · Issue #5812 · baserow/baserow · GitHub](https://github.com/baserow/baserow/issues/5812)

---

<div class="post-metadata">

**Author:** ![bgelbart](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/73ab20/32.png) [@bgelbart](https://community.baserow.io/u/bgelbart)\
**Post date:** [August 10, 2026, 5:11pm UTC](https://community.baserow.io/t/iframe-no-longer-working/12736/9 "2026-08-10T17:11:48Z")

</div>

yes it’s probably the same issue. Is this fixed? Or what do I need to do to fix it?

---

<div class="post-metadata">

**Author:** ![olgatrykush](https://community.baserow.io/user_avatar/community.baserow.io/olgatrykush/32/219_2.png) [@olgatrykush](https://community.baserow.io/u/olgatrykush)\
**Post date:** [August 10, 2026, 8:33pm UTC](https://community.baserow.io/t/iframe-no-longer-working/12736/10 "2026-08-10T20:33:17Z")

</div>

I see that it was fixed, but it probably hasn’t been merged yet. I’ll check with the team when the next patch release is scheduled.

---

<div class="post-metadata">

**Author:** ![olgatrykush](https://community.baserow.io/user_avatar/community.baserow.io/olgatrykush/32/219_2.png) [@olgatrykush](https://community.baserow.io/u/olgatrykush)\
**Post date:** [August 13, 2026, 9:36am UTC](https://community.baserow.io/t/iframe-no-longer-working/12736/11 "2026-08-13T09:36:53Z")

</div>

Can you try again @bgelbart? It should be fixed now 🙂

---

<div class="post-metadata">

**Author:** ![bgelbart](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/73ab20/32.png) [@bgelbart](https://community.baserow.io/u/bgelbart)\
**Post date:** [August 17, 2026, 3:42pm UTC](https://community.baserow.io/t/iframe-no-longer-working/12736/12 "2026-08-17T15:42:04Z")

</div>

It’s working now! It doesn’t look like it’s fixed when editing, but once it’s published, it looks right in the new published version (but still not in edit mode); I hope that makes sense. Thank you for fixing it!
