# Best practices using the Meeting SDK in an iFrame

<!-- WARNING: THIS FILE WAS AUTOGENERATED! DO NOT EDIT! -->

Zoom recommends using the [Meeting SDK for
web](/docs/meeting-sdk/web/) directly on
the webpage it is being used in. However, certain use cases could
require the Meeting SDK to be embedded in an
[iFrame](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe) on
a webpage.

Here are the best practices for using the Meeting SDK in an iFrame:

1.  Both the parent webpage, and the [iFrame
    src](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#attr-src) need
    to be served over **https**.

2.  The [allow
    attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#attr-allow)
    on the iFrame needs to include the **camera**, **microphone**, and ** display-capture**
    permissions. For example:

        ```js
        <iframe src="https://example.com/meetingsdk" allow="camera; microphone; display-capture"></iframe>
        ```

3.  If you are wanting to use features like virtual
    background, [sending 720p video](/docs/meeting-sdk/web/720p/),
    and Gallery View,
    the [SharedArrayBuffer API](/docs/meeting-sdk/web/sharedarraybuffer/) is
    required on both the parent webpage and the iFrame source.

4.  Responsive iFrames require [additional CSS
    styles](https://www.w3schools.com/howto/howto_css_responsive_iframes.asp).

5.  Stay up to date on [browser
    compatibility](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#browser_compatibility).