> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wpbevel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Working next to Elementor Pro

> What the Kit switches off when Elementor Pro is active, and what carries on.

Bevel Kit does not need Elementor Pro, and Pro does not need to be removed. When both are active, the parts of the Kit that Pro also provides stay out of the way, because two theme builders on one site would compete for the same header, the same hooks and the same panel space.

## With Elementor Pro active

Pro keeps these, and the Kit's versions do not load:

* Theme Builder, locations and display conditions
* Popups
* Loops (Loop Item, Loop Grid, Loop Carousel, Taxonomy Filter)
* WooCommerce templates and widgets
* Dynamic tags
* Custom Code
* Element options (sticky, motion effects, per-device custom CSS, attributes, wrapper link, display conditions)
* Page Transitions

The Plugins screen shows a one-line notice saying so.

## What carries on regardless

* The **Bevel widgets**, forms and the submissions inbox
* **Nav Menu** and mega menus
* **Site Settings**, the settings tabs, tools and account
* **Custom Fonts** and **Custom Icons** (Pro's own custom fonts also get the Kit's font-display setting)
* The **page cache**, WebP conversion, database optimizer, import and export
* SVG uploads, meta descriptions, the light logo, tooltips, mask shapes, post duplication, front-end edit buttons, shortcodes, font preloading, the admin bar

## Moving from Pro to the Kit

Type names, control ids and markup follow Elementor Pro's wherever the Kit replaces a Pro feature, so templates, popups and loops built with Pro keep working when Pro is deactivated:

* Theme templates keep their type (`header`, `footer`, `single`, `archive` and the rest) and their display conditions.
* Popup markup and class names are Pro's, so Pro-built popups keep their styling.
* Loop widgets use Pro's control ids, so a page keeps its query settings.
* Custom code snippets are stored the way Pro stores them.
* Sticky, motion effects and page transitions use Pro's control ids, CSS variables and class names.

Deactivate Pro, open **Bevel → Theme Builder** and check the "Shows on" column. Nothing needs to be rebuilt.