# Zoom Web Video SDK Virtual Background (COEP requirement) conflicts with third-party iframe

**URL:** <https://devforum.zoom.us/t/zoom-web-video-sdk-virtual-background-coep-requirement-conflicts-with-third-party-iframe/144671>\
**Category:** Web\
**Tags:** video-sdk\
**Created:** [July 9, 2026, 9:10am UTC](https://devforum.zoom.us/t/zoom-web-video-sdk-virtual-background-coep-requirement-conflicts-with-third-party-iframe/144671 "2026-07-09T09:10:52Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thong1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/thong1/32/69093_2.png) [@Thong1](https://devforum.zoom.us/u/Thong1)\
**Post date:** [July 9, 2026, 9:10am UTC](https://devforum.zoom.us/t/zoom-web-video-sdk-virtual-background-coep-requirement-conflicts-with-third-party-iframe/144671/1 "2026-07-09T09:10:53Z")

</div>

* * *

**Description**  
We are integrating the Zoom Web Video SDK into a Flutter Web (Single Page Application). To support the WebAssembly and `SharedArrayBuffer` features such as the **Virtual Background** (and optimal video/audio processing), we have configured our server to return headers for Cross-Origin Isolation:

- `Cross-Origin-Opener-Policy: same-origin`
- `Cross-Origin-Embedder-Policy: credentialless` (or `require-corp`)

However, our application also needs to embed a third-party partner’s application inside an `iframe`. Since this third-party server cannot add HTTP response headers like `Cross-Origin-Resource-Policy: cross-origin` (CORP) to their resources, the browser blocks the iframe due to COEP violations.

If we change our headers to `COEP: unsafe-none` to allow the third-party iframe, Zoom’s virtual background module fails to load because `SharedArrayBuffer` becomes unavailable.

We would like to ask:

1. Is there any way/workaround to utilize the Zoom Web Video SDK (including the Virtual Background feature) without requiring Cross-Origin Isolation (`COEP: credentialless` or `require-corp`)?
2. Or is there a recommended architecture/workaround to embed a third-party cross-origin iframe without CORP headers while keeping Zoom’s `SharedArrayBuffer` features active in a Single Page Application context?

**Which Web Video SDK version?**  
`2.2.12`

**To Reproduce(If applicable)**  
Steps to reproduce the behavior:

1. Deploy the host web application with the following HTTP response headers:
  - `Cross-Origin-Opener-Policy: same-origin`
  - `Cross-Origin-Embedder-Policy: credentialless`

2. Initialize Zoom Web Video SDK and try to enable Virtual Background (it works as expected).
3. Try to embed a cross-origin `<iframe>` pointing to a website that does not return the `Cross-Origin-Resource-Policy: cross-origin` header.
4. See the `net::ERR_BLOCKED_BY_RESPONSE` error in the browser console, and the iframe content is blocked from loading.

**Troubleshooting Routes**

1. **Tested setting `COEP: unsafe-none`:** The third-party iframe loaded successfully, but the Virtual Background feature in the Zoom SDK failed to initialize because `SharedArrayBuffer` was disabled.
2. **Attempting route-specific headers in SPA:** Since it’s a Single Page Application, dynamic header changes per route require a full browser reload when transitioning between pages, causing flickering and state management issues.

**Device (please complete the following information):**

- Device: [e.g. Windows PC / iPhone]
- OS: [e.g. Windows 11 / iOS 17]
- Browser: [e.g. Chrome / Safari]
- Browser Version [e.g. 120.0.0.0]

**Additional context**

- The web app is built using Flutter Web (compiled to JS).
- Changing headers on the third-party partner’s server is completely out of our control.

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [July 9, 2026, 12:06pm UTC](https://devforum.zoom.us/t/zoom-web-video-sdk-virtual-background-coep-requirement-conflicts-with-third-party-iframe/144671/2 "2026-07-09T12:06:05Z")

</div>

Hey @Thong1

Thanks for your feedback.

> 1. Is there any way/workaround to utilize the Zoom Web [Video SDK](https://developers.zoom.us/docs/video-sdk) (including the Virtual Background feature) without requiring Cross-Origin Isolation (`COEP: credentialless` or `require-corp`)?

Since Video SDK version 2.4.0 , Virtual Background no longer requires `SharedArrayBuffer`. We recommend upgrading to the latest version to resolve this issue. Also, when `SharedArrayBuffer` is not available, we will use the WebRTC video solution by default, which provides a better user experience as well.

Thanks  
Vic

---

<div class="post-metadata">

**Author:** ![Thong1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/thong1/32/69093_2.png) [@Thong1](https://devforum.zoom.us/u/Thong1)\
**Post date:** [July 10, 2026, 6:38am UTC](https://devforum.zoom.us/t/zoom-web-video-sdk-virtual-background-coep-requirement-conflicts-with-third-party-iframe/144671/3 "2026-07-10T06:38:58Z")

</div>

Hi @vic.yang,

Thanks for pointing that out!

Just to clarify, was that change introduced in version 2.3.14?

> **[Version 2.3.14 - Zoom Developer Changelog](https://developers.zoom.us/changelog/video-sdk/web/2.3.14/)**
>
> Fixes errors to improve virtual background CPU optimization, hardware capability detection, video detachment stability, and add proper error handling for audio operations during session transitions.

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [July 10, 2026, 2:20pm UTC](https://devforum.zoom.us/t/zoom-web-video-sdk-virtual-background-coep-requirement-conflicts-with-third-party-iframe/144671/4 "2026-07-10T14:20:41Z")

</div>

Hi @Thong1

> Just to clarify, was that change introduced in version 2.3.14?

Yes. It also works in version 2.3.14.

Thanks  
Vic

---

<div class="post-metadata">

**Author:** ![Thong1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/thong1/32/69093_2.png) [@Thong1](https://devforum.zoom.us/u/Thong1)\
**Post date:** [July 13, 2026, 3:38am UTC](https://devforum.zoom.us/t/zoom-web-video-sdk-virtual-background-coep-requirement-conflicts-with-third-party-iframe/144671/5 "2026-07-13T03:38:58Z")

</div>

Hi @vic.yang,

I noticed that the updates from version 2.2.12 to 2.4.5 include changes to WebRTC and the core SDK.

Could you please confirm if this upgrade might impact performance? Specifically, I would like to know if there is any risk of increased resource consumption, lag, or degradation in audio/video quality.

Any confirmation or additional details regarding performance changes after the update would be greatly appreciated.

Thank you very much!

---

<div class="post-metadata">

**Author:** ![Thong1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/thong1/32/69093_2.png) [@Thong1](https://devforum.zoom.us/u/Thong1)\
**Post date:** [July 13, 2026, 4:39am UTC](https://devforum.zoom.us/t/zoom-web-video-sdk-virtual-background-coep-requirement-conflicts-with-third-party-iframe/144671/6 "2026-07-13T04:39:39Z")

</div>

Hi @vic.yang,

Besides the Virtual Background feature, could you please let us know what other SDK features will be impacted or limited if we configure COEP to unsafe-none (such as gallery view limits, background noise suppression, etc.)?

Thank you very much for your help!

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [July 13, 2026, 6:23am UTC](https://devforum.zoom.us/t/zoom-web-video-sdk-virtual-background-coep-requirement-conflicts-with-third-party-iframe/144671/7 "2026-07-13T06:23:37Z")

</div>

Hi @Thong1

> Could you please confirm if this upgrade might impact performance?

Our versions are backward compatible, and they will not increase resource consumption or cause any audio/video quality issues.

In addition, for features such as gallery view and background noise suppression, when `SharedArrayBuffer` is not enabled and the WebRTC video solution is automatically used, these features are not degraded and are still fully supported.

Thanks  
Vic

---

<div class="post-metadata">

**Author:** ![Thong1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/thong1/32/69093_2.png) [@Thong1](https://devforum.zoom.us/u/Thong1)\
**Post date:** [July 13, 2026, 8:56am UTC](https://devforum.zoom.us/t/zoom-web-video-sdk-virtual-background-coep-requirement-conflicts-with-third-party-iframe/144671/8 "2026-07-13T08:56:21Z")

</div>

Hi @vic.yang

Thanks for your clarification!

One quick follow-up: What if the client’s network blocks WebRTC (forcing a fallback to WebAssembly) AND SharedArrayBuffer is also disabled?

In this fallback scenario, what is the expected impact on:

- **Virtual Background** : We noticed it still works. Does it run on GPU/WebGL2, and fall back to single-threaded CPU Wasm if WebGL2 is not supported?
- **Gallery View & Noise Suppression** : Are these features degraded or completely disabled?
- **Other Features** : Are there any other SDK features (e.g., Screen Share optimization) that will be impacted or disabled in this case?

Thanks!

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [July 13, 2026, 10:32am UTC](https://devforum.zoom.us/t/zoom-web-video-sdk-virtual-background-coep-requirement-conflicts-with-third-party-iframe/144671/9 "2026-07-13T10:32:17Z")

</div>

Hi @Thong1

> In this fallback scenario, what is the expected impact on

> **Virtual Background**

WebAssembly supports Virtual Background even without `SharedArrayBuffer`. The only impact is that if **hardware acceleration is not enabled on the device** , for example if Chrome’s “Use graphics acceleration when available” setting is turned off, or if you are using a cloud VM without a dedicated GPU, such as Amazon EC2, then Virtual Background will not be available in those cases, and `isSupportVirtualBackground()` will return `false`.

Technically, though, we already support this scenario. It’s just that this feature is still in beta and is only available to a limited number of customers at the moment.

> **Gallery View & Noise Suppression**

Noise suppression is supported as well.  
Gallery View can be supported in the WebAssembly + no `SharedArrayBuffer` case by specifying the `enforceMultipleVideos` option in the `init` method.

> **[InitOptions | Zoom Video SDK for Web - 2.4.5](https://marketplacefront.zoom.us/sdk/custom/web/interfaces/ZoomVideo.InitOptions.html#enforceMultipleVideos)**
>
> Optional Enforces multiple videos if true (up to 3 videos of others and 1 video of self) on platform without SharedArrayBuffer. If false, limits the view to one video. This may result in high CPU and memory usage. To increase the limit to up to 25...

Thanks  
Vic

---

<div class="post-metadata">

**Author:** ![Thong1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/thong1/32/69093_2.png) [@Thong1](https://devforum.zoom.us/u/Thong1)\
**Post date:** [July 14, 2026, 8:34am UTC](https://devforum.zoom.us/t/zoom-web-video-sdk-virtual-background-coep-requirement-conflicts-with-third-party-iframe/144671/10 "2026-07-14T08:34:25Z")

</div>

Hi Vic,

Thank you for the detailed explanation. This information is very helpful!

Just to summarize and confirm my understanding of the fallback behavior:

- **If SharedArrayBuffer (SAB) is unavailable:** It falls back to WebRTC, where Virtual Background and Gallery View will continue to operate normally.

- **If both SAB and WebRTC are blocked:** It falls back to WebAssembly without SAB. In this scenario, Virtual Background still works (provided hardware acceleration is enabled), but Gallery View will be limited to a maximum of 4 video frames (up to 3 others + 1 self).

Please let me know if I missed anything. Thanks again for your support!

Best regards, Thong

---

<div class="post-metadata">

**Author:** ![declan1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/declan1/32/51940_2.png) [@declan1](https://devforum.zoom.us/u/declan1)\
**Post date:** [July 14, 2026, 10:03am UTC](https://devforum.zoom.us/t/zoom-web-video-sdk-virtual-background-coep-requirement-conflicts-with-third-party-iframe/144671/11 "2026-07-14T10:03:30Z")

</div>

Hi Vic,

We are having similar issues with our application and using virtual background on FireFox. Without SAB headers enabled the performance of the virtual background when enforced is very poor and choppy but we are unable to enable the SAB headers needed due to integrating with 3rd party iframes.

Is there a known work around for this or do we just have to disable virtual background on Firefox and Safari?

Thanks,

Declan

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [July 14, 2026, 10:25am UTC](https://devforum.zoom.us/t/zoom-web-video-sdk-virtual-background-coep-requirement-conflicts-with-third-party-iframe/144671/12 "2026-07-14T10:25:14Z")

</div>

Hi @declan1

Thanks for your feedback.

For the performance issue when using virtual background without `SharedArrayBuffer`, you can choose to use the default WebRTC video solution.

At the moment, Firefox’s WebRTC video support is still in beta and is being rolled out to only a small number of accounts, but other browsers include Safari should have WebRTC video enabled by default.

Thanks  
Vic

---

<div class="post-metadata">

**Author:** ![declan1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/declan1/32/51940_2.png) [@declan1](https://devforum.zoom.us/u/declan1)\
**Post date:** [July 14, 2026, 10:29am UTC](https://devforum.zoom.us/t/zoom-web-video-sdk-virtual-background-coep-requirement-conflicts-with-third-party-iframe/144671/13 "2026-07-14T10:29:13Z")

</div>

Yea Safari seems to perform fine with the current set up and it is just FireFox right now that is giving us issues.

The default fallback is happening with FireFox using WebRTC but this does not fix the performance issues when virtual background is enabled.

Is this a case of potentially just disabling the option for virtual backgrounds with FireFox for the time being until the browser fully releases full WebRTC video support? Do you know if they have any time line on this?

Thank you for the reply,

Declan

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [July 15, 2026, 6:07am UTC](https://devforum.zoom.us/t/zoom-web-video-sdk-virtual-background-coep-requirement-conflicts-with-third-party-iframe/144671/14 "2026-07-15T06:07:28Z")

</div>

Hi @declan1

> Is this a case of potentially just disabling the option for virtual backgrounds with FireFox for the time being until the browser fully releases full WebRTC video support?

If you think the performance is not meeting expectations, you can temporarily disable virtual background on Firefox.

As for WebRTC video support, there is not yet an exact timeline. We will move it to GA once we have completed sufficient testing, and it should not take too long.

Thanks  
Vic
