What's new in Elementor 4.3: MCP, Default Styles, Accordion

Elementor 4.3 is the release that brings AI into the editor, but the features I use most from it are the quieter ones. Here’s what each new piece does, how it works in practice on V4 sites, and what’s still rough, release by release up to 4.3.5. Everything here is from Elementor’s changelog and my own builds. Tested on Elementor 4.3, October 2026.

What’s new in Elementor 4.3?

Five things matter, and all of them are for V4 (atomic) sites. If you’re new to V4, Elementor V4 and the atomic editor covers the basics first.

Feature	What it does	My take
Elementor MCP	Lets AI tools like Claude and Codex build and edit V4 pages	Useful, but no magic: plan on a lot of direction
Accordion	An atomic accordion whose items can hold any element	The best new element in 4.3
Default Styles	Styles an HTML tag (h2, p, div) across the whole site	Use it on every new V4 site
Background Video	A container with a video behind its content, plus play and pause buttons	Not tested yet
nav and main tags	New tag options on the Div Block and Flexbox	Small, but good for page structure

Elementor Pro 4.3 adds to the MCP (Theme Builder templates, popups and Components) and to the atomic Loop (taxonomy filters, alternating templates and empty states).

If you want to see V4 elements in finished sections, the Elementor V4 components in Element UI, the Elementor component library, are built entirely from them.

What is the Elementor MCP, and is it ready?

The Elementor MCP connects an AI tool to a WordPress site, so the AI can read pages, build atomic elements, and create and use classes and variables. It’s ready to use on V4 sites, as long as you treat it as a fast assistant that needs clear direction, not a designer that works on its own.

You switch it on under Elementor > Elementor MCP, pick your tool (Claude Code, Claude Desktop, Codex or Cursor), and paste the setup prompt it generates into that tool. The AI gets the same permissions as the WordPress user who connected it, and you can revoke it under Users > Profile > Application Passwords.

It works, and I’ve used it heavily. But it isn’t magic. It still takes a lot of human effort: finding the right reference, writing a clear brief for each section, then several rounds of changes before a section is right. And an AI building from a bare prompt, with no design system to follow, produces pages that look generically AI. The output is only as good as the starting point and the person directing it.

Two practical notes. It only builds V4 atomic elements, so V3 pages are out of reach until Elementor adds V3 support, which is on its roadmap for late 2026. And most of the 4.3 patch releases (4.3.2 to 4.3.4) are MCP fixes, so update to the latest patch before you try it.

This is also why I’ve built V4 website templates designed to give an AI a proper starting point: a finished site on a real design system. They’re out now: see the V4 website templates.

Why is the atomic Accordion such a big step?

Because each item’s content is a container you can fill with any element. Older accordions gave you a title and a text box. The V4 Accordion lets you put headings, images, buttons, even a whole layout inside an item, and you can nest one accordion inside another. That’s a lot of flexibility to put things exactly where the design needs them, without custom CSS.

The settings are simple: Default State sets whether the first item starts open or all start closed, and Max Items Expanded sets whether one or several items can be open at once. There’s also an Enable FAQ Schema toggle. One limit in 4.3: an SVG icon in the item header always rotates when the item opens, and you can’t turn that off.

What are Default Styles in Elementor 4.3?

Default Styles let you style an HTML tag once for the whole site. Open the Design System panel, go to Defaults, pick a tag such as h2, p or div, and style it. Every V4 element that uses that tag picks up the style, and any class or local style you add still overrides it.

The first job I use it for is padding. The Div Block, Flexbox and Grid all start with 10px of padding, which is never what you want, and Default Styles can set it to 0 for every container on the site in one go. After that, it’s the natural place for your heading and paragraph fonts and sizes. Elementor V4 Classes and Variables shows where Default Styles sit in a full design system.

What else changed in 4.3?

A handful of smaller changes, most of them quality-of-life fixes for building V4 pages. None of them changes how you work, but two are worth knowing: the new HTML tags help page structure, and the WordPress widgets have left the panel, so look for them before you assume something’s broken.

• Background Video: a container that plays a video behind its content, with start and end times, autoplay, mute, loop and play and pause buttons you can style. Mute it if it autoplays, or browsers may block it.
• nav and main tags on the Div Block and Flexbox, so a page’s main content and menus get the right HTML.
• The WordPress widgets section is gone from the widget panel.
• Nested elements are wrapped in a Flexbox automatically when you drop them on the page, and the Grid layout presets now use the atomic Grid.
• Inline text editing in Heading and Paragraph gained text decoration.
• Fixes: Components nested inside Components, duplicate IDs in Tabs, the Divider disappearing in row containers, and form select values.

The patches since then (4.3.1 to 4.3.5) fix dropdown menus not opening on the front end, an editor freeze in large nested layouts, and page editing failing with Internal CSS Embedding turned on.

What still doesn’t work in 4.3: importing V4 template kits

If you build V4 sites and move them with Elementor’s Website Templates (kit) export and import, test it before you rely on it. In 4.3, importing a V4 kit doesn’t bring everything across: Component instances are stripped, images and SVGs in atomic elements arrive empty, and Components lose their properties. The pages look broken until you reconnect everything by hand.

It’s reported to Elementor (#37735 and #35422), but there’s no fix yet. I hit it while preparing my V4 templates, so I built a small import helper plugin that reconnects the components, images and properties after the import, and it’ll ship with the templates.

Should you update to Elementor 4.3?

Yes, to the latest patch. 4.3.5 fixes most of the early MCP and editor issues, and nothing in 4.3 changes how existing V3 or V4 pages render. As with any update, test it on a staging copy of a client site first, especially if you move sites with kit export and import.

You’re running	My advice
A V3 site	Update for the fixes. None of the new features apply to V3 elements
A V4 site	Update, then set Default Styles and start using the Accordion
Curious about the MCP	Try it on a test site with a design system already in place, and expect to direct it closely
Moving V4 sites with kit export and import	Test the import first; components, images and properties may need reconnecting

Next up is 4.4, which Elementor’s roadmap says brings an atomic List, an atomic Carousel and an SVG icon library. I’ll cover what it changes when it ships.