Bevel Kit

No. Bevel Kit is built for the free Elementor editor, and everything described above works without Pro on the site.

Nothing breaks. You keep managing headers, footers and other templates in Bevel → Theme Builder, and Elementor Pro displays them: their conditions stay in step with Pro's in both directions, so a change made on either screen shows on the site. Bevel's widgets, dynamic tags, fonts, icons, site settings and form submissions keep working. Popups, page transitions, element options and WooCommerce templates switch to Pro's own. Templates you built before stay where they are, and turning Pro off again hands everything back to the kit.

Because everything in this plugin is built for the element model Elementor has today. Elementor 4 ships its V4 work — atomic widgets, global classes, variables, components and the V4 editor — turned on by default, and marks it hidden, so it does not appear under Elementor > Experiments and there is no setting to turn it off. Most of it is still marked alpha or dev by Elementor's own release status. Bevel Kit puts those defaults back to off. Nothing is converted and nothing is deleted. If you had already built something using V4's own features — a global class, a variable, an atomic widget — it will render differently while they are off, because those features are what render it; returning false from the bevel/elementor/pin_to_v3 filter leaves Elementor entirely alone and puts it back.

Yes. While Pro is not on the site, each of these widgets also answers to the name Pro used for it, so a page built with Pro keeps rendering with its settings intact. Those older names are hidden from the widget panel, so you never see two of anything — you build with the Bevel ones.

The content stays — it is stored in WordPress, not in the plugin. Pages keep their text and images, but anything drawn by a Bevel widget or a Bevel theme template stops being drawn until the plugin is active again, the same as with any widget plugin. Nothing of yours is deleted on deactivation — the page cache clears its stored copies and takes its drop-in back out, which is what it should do.

Yes, and it does not need the Bevel theme. A theme that calls elementor_theme_do_location() (Hello Elementor, the Bevel theme) gets the header and footer through that; every other theme, block themes included, is handled through Elementor's own header/footer page template, so the templates print either way and the theme's own header and footer step aside. The free Bevel theme is simply the lightest match.

No, and nothing in this plugin is behind one. An account pays for two things that run on Bevel's servers rather than on your site — generating pages with an AI assistant, and the premium half of the Starter Sites library. Every feature listed on this page works exactly the same connected or not, now and after any plan ends. The free starter sites import with no account at all.

Yes. Custom Fonts takes WOFF2, WOFF, TTF and OTF files and serves them from your own site; Custom Icons takes an IcoMoon or Fontello zip. Both then appear in every typography and icon control.

No icon font is loaded for visitors. Every icon is drawn as inline SVG, and the seven bundled libraries are only read in the editor's icon picker, each behind its own switch.

SVG upload is off until you switch it on under Site Settings → Settings → Security. When it is on, every SVG entering the media library is stripped of scripts, event handlers and remote references first. It is still a file format that can carry code, so only enable it if you trust who can upload.

Yes. Product and Product Archive templates appear in the Theme Builder when WooCommerce is active, with twenty-one widgets to build them from. Pages you have not built a template for are dressed to match the site anyway.

In your own database, on a screen under the Bevel menu, with a filter per form, a search, a date range, read / unread / spam / trash, resend and a CSV export. Nothing is sent to Bevel.