✅ 🔥 Elementor v3.34 Beta Release 🔥

[avivu]

===========

Beta Version Updates - Please Read Below!

===========

 

Hey Beta testers, 👋

Elementor 3.34 Beta is now live, continuing the journey towards version 4 and the evolution of the atomic editor, with new capabilities that strengthen layout flexibility, introduce lightweight motion, and refine core workflows.

This release adds one of the most requested Atomic Elements: Nested Tabs. It also includes the first stage of Entrance Interactions along with several foundational improvements that make working with Atomic Elements more consistent and predictable.

Make an impact by testing Elementor 3.34 Beta and sharing your impressions on the latest additions:

• Nested Tabs
• Entrance Interactions
• & more!

Looking forward to hearing your feedback on these updates!

 

Elementor 3.34: new atomic capabilities

All features in this version are built for the atomic editor (V4), the ongoing re-architecture of Elementor that introduces CSS-first styling, atomic design principles, and a class-driven workflow.

Because these capabilities are currently still in alpha, please keep in mind:

• Features are still in development, so future updates may break or change your website. Don't treat Alpha as production ready.
• We’re actively collecting feedback to shape what V4 becomes.
• Expect ongoing refinements throughout the Alpha period as we evolve and respond to early feedback. It is experimental and not production-ready. Updates may change or break existing sites.

During the first quarter of 2026, a production-ready Beta version will be rolled out, followed by the full release shortly after.

How to activate Editor V4 Alpha

1. Update to the latest Elementor version (now 3.34 beta).
2. Go to WordPress > Elementor > Settings > Editor V4 tab.
3. Click "Activate." You can return here to deactivate if needed.

Important: The alpha should be tested in controlled environments only. Containers, Nested Elements, and the Top Bar will automatically be enabled. For best results, use V4 with the Hello Theme.

 

Nested Tabs: flexible, atomic, and fully customizable

 

This version introduces Nested Tabs, a core addition to the atomic editor that gives you full control over the structure, styling, and behavior of tabbed interfaces. Built entirely with Atomic Elements, Nested Tabs allow you to design custom tab layouts without relying on presets.

Build fully custom tab interfaces

Nested Tabs break the traditional widget structure into independent elements you can style and configure individually:

• Tabs - main wrapper
  • Tabs menu - secondary wrapper, row containing tab triggers
    • Tab trigger - each individual trigger
  • Tabs content area - secondary wrapper, container for all content panels
    • Tab content - panel content of each individual tab

Designed for the atomic styling system

You can nest any type of content inside tab triggers or content panels, unlocking tab designs that were not possible before.

Nested Tabs fully support Atomic Editor features:

• Assign Global Classes to any part of the structure and build reusable design systems that update consistently.
• Apply styles that cascade cleanly through the hierarchy.
• Understand the layout through a clear structure panel with built-in guardrails.

New Selected State for active tabs

This version also introduces a dedicated Selected state for tab triggers, appearing conditionally only in Nested Tab Elements, letting you style selected tabs with any styling control. This provides a clean, CSS-aligned way to define interactive behavior without custom code.

How to test it

1. Create a new page and insert the Tabs element from the Atomic Elements panel.

2. Confirm the main structure includes:

   • Tabs (main wrapper)
     • Tabs Menu (row)
       • Tab Trigger (each trigger)
     • Tabs Content Area (container)
       • Tab Content (each content panel)

3. Add multiple Tab Triggers and confirm each trigger automatically creates a connected Tab Content panel.

4. Add different Atomic Elements inside:

   • A Tab Trigger
   • A Tab Content panel
   • Confirm any element can be nested (text, images, buttons, etc.)

5. Apply visual styling from the Style tab to:

   • Tabs wrapper
   • Tabs Menu
   • Individual Tab Triggers
   • Tab Content panels

6. Select a specific Tab Trigger and check the Selected state:

   • Apply a visual change (color, background, border, etc.)
   • Confirm it applies only to the selected tab

7. Switch between tabs in the editor and validate:

   • Selected state updates per trigger
   • Correct panel is shown
   • Hidden panels don’t visually interfere

8. Preview on frontend and verify:

   • Clicking a trigger opens the correct content panel
   • Selected state updates instantly

9. Test across responsive breakpoints:

   • Tabs remain functional
   • Layout adjusts
   • Triggers stay clickable

10. Add multiple Tabs on the same page:

    • Confirm each instance behaves independently

 

Entrance Interactions: lightweight motion for Atomic Elements

 

Entrance Interactions introduce the first stage of the new atomic Interactions, bringing subtle, performance‑minded motion into the atomic editor. These interactions are designed for clarity and control, without the complexity of timeline systems or large presets.

A third tab introducing lightweight motion for Atomic Elements

Until now, Atomic Elements included two tabs, General and Style, which focused on HTML structure and CSS styling. Interactions required a dedicated space, because they introduce behavior that does not align with the first two tabs, including future JavaScript-driven capabilities. This separation ensures clarity for users while keeping each tab focused on a single, consistent purpose.

Add motion with simple, atomic controls

This first stage supports the two most common entrance patterns:

• On page load - animation plays as the page initializes.
• On scroll into view - animation plays once the element enters the viewport.

Instead of selecting pre-baked effects, you configure motion using small, granular properties:

• Effects: Fade, Slide, Scale.
• Type: In, Out.
• Directions: Up, Down, Left, Right.
• Duration: 0.1s–3s.
• Delay: 0–2s.

Each interaction includes a Preview button that replays the animation on the canvas, giving you immediate feedback as you adjust properties.

You can also stack multiple entrance effects inside the same element. Each effect is added as its own entry, allowing you to layer Fade, Slide, and Scale together for more advanced motion.

In future versions more interaction types will be added using the same atomic approach.

How to test it

How to test Entrance Interactions

1. Select any Atomic Element and open the Interactions tab.

2. Click Add Interaction and confirm that the settings panel appears.

3. Choose a trigger type and confirm the correct options are available:

   • On page load (animation runs when the page initializes)
   • On scroll into view (animation runs when element enters viewport)

4. Set animation properties and confirm values change in real time:

   • Effect: Fade, Slide, Scale
   • Type: In / Out
   • Direction: Up, Down, Left, Right
   • Duration: 0.1s–3s
   • Delay: 0–2s

5. Preview the animation and verify the element plays the motion as set.

6. Add additional interactions on the same element and confirm:

   • Each effect is added as a separate entry
   • Stacking multiple effects plays them sequentially
   • Example: Fade + Slide + Scale

7. Switch to the frontend and verify:

   • Animations trigger correctly
   • Scroll-based animations wait for viewport visibility

8. Test different devices and responsive breakpoints to confirm:

   • Animations remain functional
   • Scroll behavior still triggers as expected

 

Additional updates

Elementor 3.34 delivers several more improvements that strengthen consistency and reduce friction across the atomic editor.

Atomic Flexbox wrapper for Atomic Elements

Atomic Elements are now automatically wrapped in an Atomic Flexbox container, replacing the previous V3 Container wrapper. This ensures:

• Clean, predictable markup.
• Consistent spacing and layout behavior.
• A fully atomic layout structure from the moment an element is added.

Display Conditions for Atomic Elements

Display Conditions are now supported directly in the General tab of Atomic Elements, providing a unified and accessible workflow for controlling when elements appear.

Media queries in Custom CSS

You can now write media queries directly within the Custom CSS panel while editing in Desktop mode. While the recommendation is to set styles per device using the responsive controls, this option is now available for users who prefer to work with media queries and custom breakpoint logic.

New support in the Paragraph Element

The Paragraph Element now includes a Span option for applying semantic inline markup. This allows refined text styling without workarounds or additional HTML widgets.

---

More Improvements

Free version

• New: Introducing Atomic Tabs - enabling flexible and fully customizable tab layouts with nested Atomic Elements - Editor V4
• New: Introducing Entrance Interactions to add lightweight motion and bring elements to life as they appear - Editor V4
• Tweak: Replaced the legacy V3 container wrapper with the optimized V4 wrapper for improved markup - Editor V4
• Tweak: Improved frontend link control output to ensure consistent rendering - Editor V4 (✈️ Internal links not using permalink structure #32233)
• Tweak: Improved dropdown folder behavior and resolved related UI issues in Template Library
• Tweak: Added reset option inside popovers - Editor V4
• Tweak: Updated Border control layout for a clearer and more consistent editing workflow - Editor V4
• Tweak: Applied CSS logical properties in Icon Box widget
• Tweak: Merged “Import/Export Customization” feature into the version
• Tweak: Applied CSS logical properties in Icon List widget
• Tweak: Applied CSS logical properties in text alignment controls and fixed RTL rendering in the Editor
• Tweak: Added span option inside the Paragraph atom - Editor V4
• Tweak: Improved transitions to better support logical properties - Editor V4
• Tweak: Added builder_content_data filter for extending Template Library and Global Widget content (Props @dgwatkins)
• Fix: Local Transform values overridden Class-level Transform defaults even when unchanged - Editor V4
• Fix: Fatal error when opening pages containing atomic elements while the V4 experiment is deactivated - Editor V4
• Fix: Hover Scale transform set through Class did not save correctly - Editor V4
• Fix: PHP 8.4 deprecation notices related to deprecated E_STRICT constant
• Fix: Missing CSS regeneration after clearing cached files on pages containing dynamic tags

Pro version

• New: Added support for Display Conditions for Atomic Elements - Editor V4
• Tweak: Enabled media queries for the Desktop breakpoint only in Custom CSS - Editor V4
• Tweak: Added support for ACF field in Dynamic Tags Editor V4
• Tweak: Added support for Google Calendar in Contact URL Dynamic Tag Editor V4
• Tweak: Added support for Tel link in Contact URL Dynamic Tag Editor V4
• Tweak: Added support for ACF Image field in Dynamic Tags - Editor V4
• Tweak: Removed icon from the accessibility tree in Flip Box widget
• Tweak: Applied CSS logical properties in text-align controls and improved RTL rendering in the Editor
• Fix: Website Template library displayed in English instead of the translated language
• Fix: Custom CSS field breaks when using certain characters - Editor V4

---

How to Install the Beta Version

If you still haven't enabled beta testing in Elementor, please follow these steps:

1. Go to Elementor > Tools > Versions
2. Enable the beta tester feature
3. Go to Dashboard > Updates and update to the latest beta version.
4. This will get you set up to test the new Elementor 3.34 Beta.

Notes

As we make changes to our GitHub in an effort to keep it organized, improve the way we deliver information to you, and our ability to review your feedback, please follow the instructions below when reporting bugs, or making feature requests:

• To report a bug related to V3 features - open a new 🐞 Bug Report
• To report a bug related to V4 features - open a new 🐛 Editor V4 Bug Report
• For feature requests - open a new 🚀 Feature Request
• For other comments specifically about this beta version - comment here

Designated time for release: December 22nd, 2025 (Estimated)

Many thanks for your support and help!

Cheers,
Elementor Team

[crispee2000]

Will we be able to deep link to a specific tab so it is open upon loading?

[nicholaszein]

Hi @crispee2000!

Thank you for joining the discussion! 🙏

This is not something currently possible, but we do understand this is something a few users are requesting. For now we are just releasing the basic structure for tabs to check for reliability and performance. We want to make sure the infrastructure is solid before we enhance functionality.

Let us know how it works for you, and if you find any issues using the new Atomic Tabs. You can follow the instructions above to test it out.

Kind regards

[crispee2000]

This comes up constantly for us as we put intake forms in tabs. Please add this into the roadmap.

[nicholaszein]

We will consider this for a future release @crispee2000.

Thank you for sharing your feedback! 🙏

[steveindzine]

Will it perform better in the editor than the existing nested tabs?

[nicholaszein]

Hi @steveindzine!

Welcome to the discussion! Tank you for sharing interest in Editor V4. 🙏

This is a question we are eagerly hoping you could answer for us. We would love to learn from your feedback. Give the new Atomic Tabs a try and don't hesitate to share your experience with us! 💪

[contrastxxx]

Thank you for the update. I’m glad to see every new feature. I have a note regarding the entrance animations. I believe more options will be added, but right now it has the same issue as in V3: the object moves along a very long path, which looks amateurish. The animation should be subtle, with a short path, just a slight movement. For now, I’m using a script to correct it. Thank you. (It is translated using GPT.)

@keyframes fadeDown {
    from {
        opacity: 0;
        transform: translate3d(0,-30px,0)
    }

    to {
        opacity: 1;
        transform: none
    }
}

[nicholaszein]

Hey @contrastxxx!

Welcome back! Thank you for sharing your feedback! 🙏

You make a good point. We will discuss this further!

Thank you

[doronwolf]

Hi @contrastxxx - thank you for your feedback 🙏 !
We are aware of that and are planning to release an option to further customize the animations (by choosing custom values), hopefully in the next version 😊

[aznalfl]

Nice tip, thanks.

[siteclickssahil]

Motion is no longer a “nice to have” in web design. With AI tools spitting out clean layouts in seconds, the real differentiation for builders and developers is now interaction design – cohesive motion, scroll experiences, and behaviour that actually feels designed, not just styled. I appreciate that you have been moving into Atomic development and this was needed, but I see a clear lack in interaction.

We were looking forward to the motion effect update for a while.

For years, people have been asking for GSAP-level control and scroll-based animation in Elementor. There are threads going back to at least 2020 asking for this. Instead, Entrance Interactions feel like a rebranded Motion Effects: the same fade/slide/scale patterns with slightly more granular controls, but still no real step-change in what we can actually build.

You wrote:

These interactions are designed for clarity and control, without the complexity of timeline systems or large presets.

The thing is: your users have already moved past that fear of “complexity”. We want timelines. We want more advanced control. Webflow has had this for years:

• Triggers: click, hover, page load, scroll, custom event
• From/To animation logic, just like After Effects
• The ability to stack and orchestrate multiple animations in a single interaction

Slider Revolution has been doing this forever as well.

Right now, Elementor still forces us into a very basic interaction layer. Anything beyond simple entrances usually means custom GSAP, custom CSS, or giving up and telling the client “we can’t do that natively”. Meanwhile, most of our clients now send references built on Webflow and talk specifically about how the site feels, not just how it looks. Our Figma files and moodboards are full of scroll-based animations and choreographed sequences that we then have to hand off to devs to custom code because Elementor can’t handle them out of the box.

I understand GSAP licensing might have been a blocker in the past, but since the Webflow acquisition the licensing has changed and it’s now free to use commercially. That removes a major excuse. At this point, not having a native timeline / advanced animation system in Elementor is becoming a competitive disadvantage.

What many of us are asking for is pretty clear:

• Native GSAP integration or a first-class timeline-based animation system
• Scroll-based triggers and effects (containers, and atomic elements)
• Trigger types similar to Webflow: click, hover, page load, scroll, custom events
• Proper “from / to” control and chaining for more sophisticated micro-interactions

My whole dev team has seriously considered moving more projects to Webflow purely because it makes modern interaction design first-class, not an afterthought. Price is literally the only thing holding us back.

Here are just some of the existing requests for GSAP / advanced animation that have been sitting there for years:

• https://github.com/orgs/elementor/discussions/31839
• https://github.com/orgs/elementor/discussions/27748#discussioncomment-9865509
• https://github.com/orgs/elementor/discussions/23303
• https://github.com/orgs/elementor/discussions/23834
• https://github.com/orgs/elementor/discussions/28219

Elementor is so close to being the default choice for serious teams, but motion is where it’s clearly lagging. This release is a step, but it’s not the step your power users have been asking for.

[nicholaszein]

Thank you for the feedback @siteclickssahil! We really appreciate your cander and point of view! 🙏

Please take a moment to re-read the first paragraph of the description of this new feature layer:

Entrance Interactions introduce the first stage of the new atomic Interactions, bringing subtle, performance‑minded motion into the atomic editor.

As we've been mentioning for quite some time, this is just the first phase, the Alpha phase, when we are in the full development mode of the new builder. Some features may be missing, and some may be incomplete. Nothing is fully set in stone yet. We have a pretty solid base, and it's become more stable on each release. Whatever we introduce, doesn't mean it's the final implementation. We may very well improve or enhance each feature with more options and power in a future phase.

We will definitely discuss your feedback and the other requests. We just ask you to keep an open mind, and consider this the beginning of the future of Elementor.

Also, our goal is to introduce parity in features compared to v3 as V4 evolves. You should be able to use the same, or equivalent features as the existing ones, but built for the new Editor, for a seamless transition. So these are the equivalent to Entrance Animations in V3. From here there is room to improve! 😉

Hope this clarifies we are not done yet, but we are grateful for your feedback! 💪

[jlemonz]

Thank you for the new update. Are site settings like global width and Components and Presets getting introduced in the next version? It's a lot of work without some pre made css classes. Global site settings etc

[nicholaszein]

Hey @jlemonz! Welcome back! Great to have you here! 😊

This is something that we are still preparing to work with. There are other features that need to be released first before we can consider implementing compatibility between the new elements and global styles in the Site Settings. This will ensure we have everything covered before we can work on global styles.

Components are shaping great, and we are doing our best to release them as soon as they are ready.

However, as a temporary suggestion, you can technically edit any default values for any Atomic element just by targeting their base classes using Global Classes. You can create a Global Class with the same name as an elements base class, and simply apply the values you prefer. You don't even need to add it to each element to make it work.

Anyway, we would love to learn from your experience with the new tabs and interactions. Have you tried them yet? How did it go?

Let us know! 🙏

[contrastxxx]

One of the things I really liked was changing values using drag and drop in value fields. It made my work much easier. Yes, I know I can type manually or just tap the value up and down, but drag and drop is on a completely different level. Thank you.

[nicholaszein]

Hi @contrastxxx!

I confess I am not sure what you are talking about. You mean the "Number Scrubber"? Where you can “scrub“ horizontally and the value changes up or down depending on the direction you are "scrubbing"?

[contrastxxx]

Yes, exactly that.

[pshaughnessy88]

Are the new tabs keyboard accessible or will that be available sometime soon? Keyboard accessibility of our Elementor Tabs and Accordions are one issue keeping us from full compliance.

[nicholaszein]

Hi @pshaughnessy88, they are. But we would love to hear your feedback about it too. Let us know if you find any issues! 🙏

[Daveden2]

Hi everyone! Thanks for the updates.
I tested out the new Atomic Tabs on my live stream and noticed a few things that need to be improved.

1. There's a missing role="tablist" on the tabs menu.
2. The event listener on the up/down arrow keys should be removed; otherwise, a keyboard user would not be able to access content in the tabpanel when the content is longer than the page.
3. When I add a class to the tab trigger, I can't change the text colour, and in fact, the tab trigger doesn't work well with classes.

[nicholaszein]

Hey @Daveden2! Nice to see you here!

Thank you for joining the discussion! 🙏

We also appreciate your feedback. There is definitely room to improve! Our team was already notified about the points you raised. We will be discussing them thoroughly!

Kind regards

[avivu]

Hi all,

We just released Elementor Free v3.34 Beta 2.

The versions include the following:

Free version

• Fix: Duplicating issues in Tabs element - Editor V4
• Fix: HTML attribute issues in Tabs element - Editor V4
• Fix: Classes do not apply as expected in atomic elements - Editor V4
• Fix: Improved accessibility support in Tabs element - Editor V4

Pro version

No changes.

–

Thank you!

[conradomd]

I'm thinking about the use of the ::before and ::after pseudo-elements in custom CSS, since the block already starts with _element.style { ... }. Will there be a way to do this in the future, or is the main idea to use the Page Settings > Advanced > Custom CSS field instead?

[doronwolf]

Hi @conradomd, we are planning to add the ::before and ::after as states, so you will be able to customize them from the style tab
For now, you can still add using the custom CSS field, for example:

element.style { 
color: black; 

&::before { 
content: '★'; 
color: gold; } 
}

[kameleon-th]

@doronwolf so does that mean the custom CSS field supports SASS/SCSS?

[m1ga]

@kameleon-th CSS can do nested CSS for a while now: https://caniuse.com/css-nesting It's not the same as SCSS/SASS

[avivu]

Hi all,

We just released new Beta versions.

The versions include the following:

We just released Elementor Free v3.34 Beta 3.

• Fix: Duplication issues in Tabs element - Editor V4
• Fix: Element appears before interaction animations start - Editor V4

Pro version

No changes.

–

Thank you!

[mcrowell]

Loving the latest version! I have a question about the inline JavaScript code added to the DOM, specifically the <script id="elementor-interactions-js-extra">. It's adding 482k characters. What's the purpose of this code?

[nicholaszein]

Hi @mcrowell,

This would be part of the new Interactions layer we have added to Atomic Elements. It is responsible for applying the constants and default values that are used by these interactions.

If you are worried this can affect your site's performance, please don't forget this is just the first introduction of this feature, it's just an MVP. There are no optimizations applied for this feature yet.

Nonetheless, we appreciate your concerns. As this feature matures, we will be finalizing the infrastructure for it, and will make our best to ensure it follows the same optimization principles we have been implementing for all assets in the past few years.

😉

[NordSueden]

thanks for the beta release. I love editing with it.

• sometimes I have multiple "local" classes

[doronwolf]

Hi @NordSueden thank you for your feedback!
Did you notice if the multiple "local" classes issue occurs after deleting a class?
If so, a fix for that will be included in the GA version

[mcrowell]

Same thing on my end sometimes. If I close the browser tab and reload the page it goes back to normal.

[doronwolf]

Hi @mcrowell can you describe the steps to reproduce the issue?
Did you notice if the multiple "local" classes issue occurs after a specific set of actions?
It can really help us to debug it 🙏

[nicholaszein]

Hi @mcrowell and @NordSueden.

If you can reproduce this issue consistently, please open a new 🐛 Editor V4 Bug Report. As @doronwolf mentioned, we have identified this happening in some cases when deleting a global class, and we want to make sure we are covering all bases, including the cases you reported here.

We just released Elementor v3.34 (Core and Pro), and we are closing this discussion, so you won't be able to answer here anymore. But we would really appreciate if you could share more detail on this issue.

Thank you for joining the discussion! 🙏