> For the complete documentation index, see [llms.txt](https://docs.customiframe.com/llms.txt).
> Use it to discover all available pages before exploring further.

# Elementor Compatibility

Fix Custom iFrame widget issues in Elementor. Covers plugin activation requirements, widget not appearing, PHP and WordPress version requirements, and plugin conflicts.


## Overview

Most Custom iFrame compatibility issues in Elementor come from one of four things: Custom iFrame Free is inactive when Pro is installed, the widget cache needs regenerating, a third-party plugin is conflicting, or the server does not meet the minimum requirements. This guide covers each with a specific fix.

---

## Cause 1: Custom iFrame Free Is Not Active (Pro Users)

Custom iFrame Pro is an add-on plugin. It requires Custom iFrame Free to be installed and active at the same time. Pro does not work as a standalone plugin.

**Symptom:** Pro features do not appear, or the widget is missing entirely after installing Pro.

**Fix:**
1. Go to **WordPress Admin > Plugins**.
2. Confirm **Custom iFrame** (Free) shows as **Active**.
3. Confirm **Custom iFrame Pro** also shows as **Active**.
4. If either is inactive, click **Activate**.

Both plugins must be active simultaneously for Pro features to appear in the Elementor widget.

---

## Cause 2: The Custom iFrame Widget Does Not Appear in Elementor

If you search for "Custom iFrame" in the Elementor widget panel and it does not appear, Elementor may be serving a cached widget list that does not yet include Custom iFrame.

**Fix:**
1. Go to **WordPress Admin > Elementor > Tools**.
2. Under the **General** tab, click **Regenerate Files & Data**.
3. After regeneration completes, reload the Elementor editor.
4. Search for **Custom iFrame** in the widget panel again.

If the widget still does not appear after regeneration, confirm the plugin is active (see Cause 1) and that the server meets the requirements below.

---

## Cause 3: Server Does Not Meet Minimum Requirements

Custom iFrame requires:

| Requirement | Minimum version |
|---|---|
| WordPress | 5.8 |
| PHP | 7.4 |
| Elementor Free or Pro | 3.4 |

If the server runs an older PHP version or WordPress installation, the plugin may fail silently or partially.

**Fix:** Check your current versions:

- **PHP:** Go to **WordPress Admin > Tools > Site Health > Info > Server**. Look for the PHP version.
- **WordPress:** Go to **WordPress Admin > Dashboard > Updates**.
- **Elementor:** Go to **WordPress Admin > Plugins** and check the Elementor version number.

Upgrade any component that is below the minimum version. Contact your host if you need to update PHP.

---

## Cause 4: A Third-Party Plugin Is Conflicting

Some plugins that modify the Elementor editor (other widget libraries, page builders, or JavaScript optimization plugins) can interfere with Custom iFrame widget registration or rendering.

**Symptom:** The widget appears but does not save settings correctly, shows errors in the editor, or displays incorrectly on the frontend.

**How to isolate:**

<Steps>
  <Step title="Deactivate all plugins except Elementor and Custom iFrame" icon="toggle-left" title-type="p">
    Go to **WordPress Admin > Plugins**. Select all plugins except Elementor (Free or Pro) and Custom iFrame (Free and Pro if applicable). Choose **Deactivate** from the bulk actions menu.
  </Step>
  <Step title="Test the iFrame widget" icon="search" title-type="p">
    Open a page in Elementor and test the Custom iFrame widget. If it works correctly, a previously active plugin was causing the conflict.
  </Step>
  <Step title="Reactivate plugins one at a time" icon="toggle-right" title-type="p">
    Activate each deactivated plugin one at a time. After each activation, test the Custom iFrame widget. The plugin that breaks the widget is the source of the conflict.
  </Step>
</Steps>

Common conflict sources: JavaScript concatenation or minification plugins (Autoptimize, WP Rocket JS optimization), other Elementor widget libraries that register conflicting scripts, or caching plugins that serve stale editor assets.

**Fix:** Exclude Custom iFrame scripts from JavaScript optimization in your optimization plugin's settings, or configure your caching plugin to exclude the Elementor editor from caching.

---

## Cause 5: The Widget Behaves Differently in the Editor Versus the Frontend

Elementor's editor runs inside its own iframe context. Embedded content that uses JavaScript to initialize (such as some map widgets, form providers, or media players) may behave differently in the editor than on the published page.

This is expected behavior. The editor iframe context can affect how some scripts calculate dimensions or initialize.

**Fix:** Always check the published page directly at its frontend URL. The frontend rendering is the accurate view. Do not rely on the editor preview for final visual verification.

---

## Cause 6: After a Plugin Update, the Widget Stopped Working

A plugin update (Custom iFrame, Elementor, or WordPress core) can sometimes leave the Elementor widget cache in a stale state.

**Fix:**
1. Go to **WordPress Admin > Elementor > Tools**.
2. Click **Regenerate Files & Data**.
3. Also clear your caching plugin's cache if you use one.
4. Reload the Elementor editor.

---

## FAQ

<ExpandableGroup>
  <Expandable title="Do I need Elementor Pro to use Custom iFrame?" default-open="false">
    No. Custom iFrame works with Elementor Free. Elementor Pro is not required. Custom iFrame Pro is a separate add-on for Custom iFrame itself, not a requirement for Elementor Pro.
  </Expandable>
  <Expandable title="Custom iFrame Pro is installed but Pro features are not showing. Why?" default-open="false">
    Custom iFrame Free must be installed and active at the same time as Pro. Pro is an add-on and cannot run without Free. Go to WordPress Admin > Plugins and confirm both Custom iFrame and Custom iFrame Pro are active.
  </Expandable>
  <Expandable title="The widget was working and stopped after an Elementor update. What do I do?" default-open="false">
    Go to WordPress Admin > Elementor > Tools and click Regenerate Files & Data. This rebuilds Elementor's widget registry and clears the cached file list. After regeneration, reload the editor and search for Custom iFrame again.
  </Expandable>
  <Expandable title="My PHP version is below 7.4. What happens if I use Custom iFrame?" default-open="false">
    The plugin may not activate, may activate with PHP errors, or may activate but fail to render correctly. PHP 7.4 is the minimum supported version. Upgrade PHP through your hosting control panel or contact your host. WordPress itself also recommends PHP 8.0 or higher for best performance and security.
  </Expandable>
  <Expandable title="The iFrame works in the editor but is blank on the published page. Why?" default-open="false">
    Clear all caches first: your caching plugin, CDN cache, and browser cache. A caching plugin may be serving a stale version of the page that does not include the Custom iFrame output. If clearing caches does not fix it, check the browser console on the frontend page for errors.
  </Expandable>
</ExpandableGroup>

---

## Related Guides

- [iFrame Not Showing](/troubleshooting/iframe-not-showing)
- [iFrame Height Fix](/troubleshooting/iframe-height-fix)
- [Set Up Custom iFrame in Elementor](/getting-started/elementor-setup)
- [Auto Height Adjustment](/features/auto-height)