What Elementor V5 should ship next: a wishlist from the field

What V4 got right

Before the wishlist, credit where it is due. V4 atomic solved real problems. The DOM output is dramatically better. Per-element CSS loading reduced page weight by 70-90%. Flexbox Containers give us native CSS layout controls instead of Elementor's proprietary column system. Variables and Classes enable actual design systems inside the visual editor. These were the right priorities, and Elementor delivered them.

But V4 also revealed the next set of problems. When you fix the foundation, you see what the floors need. Here is what the community is asking for, based on forum discussions, agency feedback, and real project experience.

1. Component-level linked updates

V4 Components are independent after insertion. This is safer for client editing but slower for agency maintenance. What agencies want is an option: "Link this instance" or "Detach this instance." Let the developer choose per instance whether it stays connected to the source Component or becomes independent.

This gives agencies the V3 Global Widget sync behavior when they want it and the V4 safe-independence behavior when they need it. Both use cases are valid. V4 currently only serves one of them.

2. Native design token export/import

Variables and Classes are per-site. There is no built-in way to export a design system from one site and import it to another. Agencies building multiple sites with the same brand guidelines (franchise clients, multi-location businesses) recreate Variables and Classes from scratch on every new site.

What we want: export design tokens (all Variables + all Classes) as a JSON or equivalent file. Import that file on a new site to set up the entire design system in one click. This also enables version-controlled design systems where you store the token file in a Git repository and deploy it to client sites.

3. Conditional Classes

Apply a Class only when certain conditions are met. A dark-mode Class that activates based on user preference. A sticky-header Class that applies when scroll position exceeds 100px. A highlighted Class that applies when a dynamic field value meets a threshold.

Currently, conditional visual changes require custom CSS or JavaScript. Native conditional Class support in the editor would make dynamic designs accessible to non-developers.

4. CSS Grid layout (alongside Flexbox)

Flexbox Containers handle one-dimensional layouts (row or column). CSS Grid handles two-dimensional layouts (rows AND columns simultaneously). For grid-based designs (masonry galleries, dashboard layouts, magazine templates), CSS Grid is the right tool.

V4 is Flexbox-only. You can achieve grid-like results with nested Flexbox Containers and flex-wrap, but true two-dimensional placement control requires CSS Grid. Adding a Grid Container option alongside the existing Flexbox Container would give developers the right tool for each layout type.

5. Real-time collaboration

Two people cannot edit the same page simultaneously in Elementor. This is a significant workflow bottleneck for agencies with design and content teams. A designer works on the hero section while a copywriter updates the body text. Currently, one has to wait for the other to save and close.

Real-time collaboration (similar to Google Docs or Figma) would require significant architectural changes to Elementor's editing system. This is a long-term ask, but it is the single feature that would change how agencies staff projects.

6. Built-in version control for design changes

Elementor has revision history (undo/redo), but it is page-level and session-based. There is no way to see who changed what, when, across the site. If a client edits a page and something breaks a week later, tracing the change requires guesswork.

What we want: a changelog that records changes at the element level. "On April 14, user 'client-editor' changed the heading text on homepage from X to Y and changed the background color of section 3 from #ffffff to #f3f4f6." This is technically a WordPress audit log feature, but integrating it into Elementor's UI would make it far more useful.

7. Performance devtools panel

A built-in panel that shows the performance impact of your design decisions as you make them. "This page loads 340KB of CSS from 12 element types. Adding this carousel widget will add 45KB of JavaScript." Currently, you build the page, publish it, run PageSpeed, and then debug. Real-time performance feedback in the editor would prevent problems instead of diagnosing them.

Bricks Builder has taken steps in this direction with its performance indicators. Elementor could go further by integrating Lighthouse metrics directly into the editor preview.

8. Better responsive breakpoint controls

V4 supports custom breakpoints, but the responsive editing experience is still toggle-and-switch. You set properties at each breakpoint individually. There is no visual preview of how a layout responds across a continuous range of widths.

What would be better: a responsive timeline that lets you drag through screen widths and see the layout respond in real time. When it breaks, you add a breakpoint at that width and adjust. This is how browser DevTools responsive mode works. Bringing that experience into the Elementor editor would make responsive design faster and more intuitive.

9. Native form improvements

Elementor Pro forms cover basic use cases, but anything complex (multi-step with conditional logic, file uploads with validation, payment collection, user registration) requires a third-party form plugin.

Three improvements would cover 90% of what third-party forms provide:

• Multi-step forms with visual step configuration
• Conditional field logic with OR/AND operators (not just simple show/hide)
• Spam protection beyond reCAPTCHA (honeypot, time-based checks, Turnstile support)

Forms are the most common interactive element on client sites. Getting them right in core Elementor reduces plugin dependencies and simplifies maintenance.

10. Container-level animations

V4 element-level entrance animations work (fade in, slide up). But container-level animations (animate a group of elements together as they scroll into view) are limited. Scroll-triggered animations with staggered child reveals (first element fades in, then the second, then the third) require GSAP or custom JavaScript.

A built-in scroll animation system that works at the container level with stagger controls would eliminate a major reason developers add custom JavaScript to Elementor sites. GSAP ScrollTrigger-level functionality, accessible through the visual editor, would be a significant differentiator.

11. AI-assisted design suggestions

Elementor introduced AI features for text generation and image creation. The next step is design suggestions. "These two sections have inconsistent padding. Would you like to update section 3 to match section 2?" Or: "This heading does not use any Class. Five similar headings on other pages use text-heading-lg. Apply it?"

AI that helps maintain design consistency (not AI that generates designs) is immediately useful for agencies where multiple team members edit the same site. The system already has the data. Variables, Classes, and element properties are all structured. Pattern detection on that data is a tractable AI problem.

12. Better WooCommerce integration

Elementor Pro's WooCommerce builder handles basic shop customization (product pages, archive pages, cart, checkout). But styling WooCommerce with Elementor still feels like a workaround rather than a native integration. Cart and checkout pages have limited element-level control. Product variation displays are hard to customize.

WooCommerce powers 40% of online stores. Tighter integration (full element-level control over every commerce surface, including mini-cart, product quick-view, checkout fields) would make Elementor the default choice for WooCommerce design, which it currently is not for complex stores.

What is realistic for V5

Not everything on this list will ship in a single version. Based on Elementor's development pace and stated priorities, here is a rough prediction:

Likely in V5 (next major release): Design token export/import, CSS Grid containers, improved responsive controls, form improvements.

Possible in V5: Conditional Classes, container animations, performance devtools panel, linked Component option.

Longer-term (V5.x or V6): Real-time collaboration, AI design consistency, comprehensive WooCommerce rebuild.

The V4 foundation (atomic rendering, Flexbox Containers, Variables, Classes) was the hard part. What comes next is building on that foundation. V4 gave Elementor a modern architecture. V5 should give us the tools that architecture makes possible.