✅ 🔥 Elementor Editor v3.35 Beta Release 🔥

[avivu]

===========

Beta Version Updates - Please Read Below!

===========

 

Hey Beta testers, 👋

Version 4 Beta is now available in Elementor 3.35 and ready for production use!
The alpha phase is complete. Version 4 is no longer experimental. It is stable and ready for real sites.

This marks a huge milestone as we get very close to officially moving the Editor to version 4.0, activating the features automatically on new sites, and becoming the default editing experience in Elementor.

Make an impact by testing the beta and sharing your impressions on these latest additions:

• Components: a new reusable building block in version 4
• Inline Editing for Atomic Heading and Paragraph Elements
• New Elementor menu in the WordPress Admin
• & more!

Looking forward to hearing your feedback!

 

Version 4 Beta is here!

 

Version 4 introduces a new architectural foundation that separates structure, styling, and content more clearly, enabling more predictable layouts, safer reuse, and better collaboration across teams. While the editor experience may feel familiar, many of the underlying systems are new and designed to support larger, more complex sites.

This Beta of version 4 is considered production-ready for real projects. This means that core editing workflows are stable and suitable for live sites, and that the output is predictable and compatible with existing Elementor sites.
 

---

💬 Want to share your feedback directly with the Elementor Editor team?

👉 Book a 1:1 session

---

 

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

Follow these next steps to activate version 4 features:

1. Update to the latest Elementor version (currently 3.35 beta).
2. Go to WordPress > Elementor > Editor > Settings > Version 4 tab.
3. Click activate.

The beta is the last big step before moving to version 4.0 and activating atomic features by default on new sites. Important to note that existing sites and features aren’t going anywhere. New features will continue to live alongside existing ones and you’ll be able to use version 4 and version 3 together. More on that will be communicated soon.

 

Components: build once, reuse everywhere

 

Introducing Components, a primary building block of version 4 and a major step toward a more scalable, production-ready editing experience.

Components let you create reusable layout sections that stay synchronized across your site, while still allowing controlled per-instance customization. They are designed for real projects, real workflows, and real teams - not just isolated pages.

This version positions Components as a core capability of version 4, and a key part of the upcoming shift.

Create reusable layout blocks with full site sync

You can turn any container into a Component and give it a clear, reusable identity. Components appear in a dedicated Components tab, next to the Elements tab and can be added to the canvas just like native elements.

When a Component is edited, all instances update automatically across the site. Structure and styling stay in sync, making Components ideal for shared sections such as banners, CTAs, feature grids, headers, and repeated layout patterns that need to remain consistent over time.

Control variation with Component properties

Components also support Component properties for content, allowing you to expose specific parts of a Component’s content for per-instance editing.

As the admin, you decide which content properties can be customized: text input, media, links and HTML tags. Editors can adjust only those exposed properties, while the layout and structure remain protected and globally synced.

This balance between consistency and flexibility makes Components especially useful for professional workflows, team collaboration, and client handoff.

A core capability of version 4

Components are built specifically for version 4 and reflect its direction as a system designed for larger, more structured projects:

• Layout-level reuse instead of widget-level globals
• Clear separation between structure, styling, and editable content
• Central management for scalable site building

Together with Variables, Classes, and the new styling architecture, Components introduce a more systematic way to build and maintain websites as projects grow in size and complexity.

Version 4 is now in beta, and Components are intended for real-world use, including production projects, with the understanding that the system will continue to evolve as feedback comes in.

How to test it

Creating a Component

1. Create a Component by right-clicking any Flexbox or DIV Block and selecting Create Component from the context menu.
2. Give the Component a name and confirm creation.
3. Once created, the Component automatically enters Edit Mode.
4. Add elements inside the Component and adjust the layout and structure to match the intended design.
5. Exit Edit Mode by clicking outside the Component or using the Back button in the Component header in the panel.
6. Confirm the new Component appears in the Components tab under the Components list.
7. In the Component Manager, verify you can search, rename, or delete Components.
8. Add multiple instances of the Component to the page.
9. Enter Edit Mode for any instance (double-click the Component or right-click → Edit Component).
10. Change the Component’s layout or structure.
11. Exit Edit Mode and confirm that the update is reflected across all Component instances.
12. Validate consistency in the canvas, in preview mode, and on the frontend.

Exposing Component properties

1. Enter Edit Mode for a Component.
2. Select any element inside the Component (e.g., a Heading).
3. Open the Content tab and note the new icon next to editable content properties (e.g., Text, HTML Tag, Link). At this stage, only content properties can be exposed.
4. Click the icon to expose a property.
5. Assign a property name when prompted.
6. Repeat for all content properties you want to expose across all elements in the Component.
7. Verify that each exposed property is listed in the Properties panel.
8. Open the Properties panel (top right in Edit Mode).
9. Create Groups and organize exposed properties into clear, structured sections.
10. After defining all properties and groups, exit Edit Mode.
11. Select any instance of the Component and verify that all exposed properties now appear in its Component panel.
12. Add several Component instances to the page.
13. Modify the exposed properties on each instance and confirm that changes apply only to that instance (per-instance content).
14. Re-enter Edit Mode, modify the Component’s layout or structure, exit Edit Mode, and confirm the layout updates apply globally, while instance-specific content remains unchanged.
15. Validate behavior across the editor, preview, and frontend.

 

Inline Editing: edit text directly on the canvas

 

Introducing Inline Editing for Atomic Heading and Paragraph Elements, allowing you to edit text directly on the canvas without shifting focus to the panel.

When you click on an Atomic (version 4 elements) Heading or Paragraph, the text becomes editable directly on the canvas. Changes are applied instantly and stay fully synchronized with the panel inputs. This makes quick copy updates, layout reviews, and content refinements faster and more intuitive, especially when working across multiple sections or pages.

Contextual formatting controls

Formatting options appear as a floating toolbar near the selected text, giving you quick access to common inline actions directly on the canvas.

The inline toolbar currently supports: Clear formatting, Bold, Italic, Underline, Strikethrough, Superscript and Subscript, and Links (including opening links in a new tab).

The toolbar is contextual, so it appears only when text is selected, stays within viewport boundaries, and supports keyboard shortcuts for faster editing. All formatting is applied visually, without exposing raw HTML or requiring code-level interaction.

How to test it

1. Add a Heading or Paragraph element to the canvas.
2. Click directly on the text inside the element to enter inline editing mode.
3. Confirm that the text becomes editable on the canvas and updates instantly.
4. While editing, verify that a floating inline toolbar appears near the selected text.
5. Use each option in the toolbar—Clear formatting, Bold, Italic, Underline, Strikethrough, Superscript, Subscript, and Links—and confirm each one applies correctly.
6. Ensure that all formatting changes appear both on the canvas and in the Text panel.
7. Use keyboard shortcuts for formatting (Cmd/Ctrl + B, I, U) and confirm they work.
8. Confirm undo and redo work during inline editing.
9. Preview the page and verify that the formatted text appears correctly on the frontend.

 

A unified Elementor menu in the WordPress Admin

Introducing a refreshed Elementor menu in the WordPress Admin, designed to make site management clearer, more consistent, and easier to navigate under a single Elementor entry.

🎥 Watch a full walkthrough of the refreshed menu here

At the top of the Elementor menu, you’ll now find a new Elementor homescreen. This serves as a central dashboard with shortcuts to commonly used actions and a clearer overview of your Elementor setup. Below the Elementor homescreen, all editor-related settings and tools are now grouped under a new Editor submenu.

The notable changes are:

• New “Editor” submenu under Elementor, containing all your familiar menu functionalities.
• Templates are now part of the Editor menu instead of being a separate section in the WP Admin.
• Custom Fonts, Custom Icons and Custom Code are now grouped together as “Custom Elements” inside the Editor menu.
• System Info, Element Manager and Licence/Connect are now grouped together as “System” inside the Editor menu.

Learn more about the changes here

 

Additional updates

Dynamic tags in color controls

Dynamic tags are now supported in color-related controls, including text color, background color, border color, box shadow color, and drop shadow color. This allows colors to be driven dynamically by retrieving them from ACF or WordPress native custom fields.

Improved HTML semantics for links and actions

To further improve accessibility, keyboard navigation, and screen reader behavior, link behavior has been refined to better reflect semantic roles. Elements that trigger actions now use the appropriate tag, while navigation continues to use tags.

---

More Improvements

Free version

• New: Introducing Components - reusable layout building blocks with global sync and per-instance content overrides - Editor V4
• New: Introducing Inline Editing - edit Atomic Heading and Paragraph text directly on the canvas - Editor V4
• New: Introducing a contextual formatting toolbar for inline text editing, including links and common text styles - Editor V4
• Tweak: Version 4 status updated to Beta - Editor V4
• Tweak: Children perspective controls available only for relevant parent elements - Editor V4
• Tweak: :hover styling automatically applies to :focus-visible for improved accessibility - Editor V4
• Tweak: Dynamic tags support added to color picker controls - Editor V4
• Tweak: Link and Button accessibility improvements in Dynamic Tags - Editor V4
• Tweak: Nested Accordion optimizations with Grid in Chrome browser
• Fix: Size link-unlink operations not applying consistently - Editor V4
• Fix: Div Block and Flexbox base styles overriding user settings when viewed from another document - Editor V4
• Fix: Container handles not visible when “Overflow: Hidden” is enabled

Pro version

• Tweak: Extended the color picker to support ACF fields - Editor V4
• Tweak: Enabled size variables with custom units across relevant controls - Editor V4
• Tweak: Enabled size variables in border radius controls - 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 > Editor > Tools > Version Control
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.35 Beta.
5. Go to WordPress > Elementor > Editor > Settings > Version 4 tab.
6. Click activate.

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: February 2nd, 2026 (Estimated)

Many thanks for your support and help!

Cheers,
Elementor Team

[nicholaszein]

Uhuuull!! Let's goooo Components! 🎉 🙌 🥳 💪

[alexanderpankart]

Components. Deeply in love.

[nicholaszein]

Me too! 🫶

Welcome to the discussion @alexander-pankart! 🙌

[alexanderpankart]

I created an entire section with three boxes (each containing one image, H3, text, and button) as a component. I'm really impressed with how quickly the editor loads when you incorporate reusable sections.

[nicholaszein]

Awesome @alexander-pankart! 🙌

[toineenzo]

Wowww!!!! Didn't expect that we would already be so close to v4! Amazing!
I'll be sure to try out the components. Can't wait for the official stable v4 release

[nicholaszein]

Hey @toineenzo!

Us too! 🤩

Let us know how it goes! We are eager to learn from your experience! 👀

[toineenzo]

Hi @nicholaszein ,

I found a few things I already wanted to share about the new settings pages

1. As an Elementor Pro Expert Legacy license holder, an “Upgrade” button is now shown in the Elementor menu, along with multiple promotional messages about Elementor One. This shouldn't happen with paid users right?
2. When a root menu item in the Elementor WP admin menu is selected, the Editor sub-menu items no longer appear.
3. When opening an item in the Submissions menu, there is no visible Back button. The only way to return is by clicking Submissions again.
4. Ideally, all Elementor settings menu pages should load dynamically without a full page refresh, similar to how tab navigation currently works.
5. When creating or saving a new custom font, custom code, or icon pack, the sidebar settings panel does not appear. This panel DOES appear when editing an existing item.
6. The search field in the Element Manager appears to have a double border (see attached image).

That's all for now, and like how Ziv would say: Ciao for now! ;)

[toineenzo]

This is what I meant with point 2 in my previous message. As you can see at 1 in the above image, when a menu item is selected, the submenu of Editor does not show. At 2 you can see the upgrade button. EDIT: i see 3.34.2 has already fixed the upgrade button, still not sure if this really was a bug or a change of plans 🤔

[nicholaszein]

Hi @toineenzo,

Apologies for the lack of response in this one. 🙏

1. Elementor One's Upgrade button in the Admin Menu

This was solved with the release of Editor Pro v3.34.2, and the "Ubgrade" button was removed for users with an active license.

2. Editor submenu doesn't appear when inside any Elementor root Admin Page

You are correct, there is no option to jump right into the Editor pages. We will discuss that internally. Thank you for raising this issue!

3. No "Back Button" in View Submission Page

There was never a back button for this interface. You have to click on the Submissions to go back to the submissions list, or use your Browser's "Go Back" button.

4. Suggestion to load Elementor Settings pages dynamically without page refresh.

Currently this is not possible, but this is an interesting idea. We will consider it for the future!

5. Side Panel doesn't appear when adding Custom Elements (Fonts, Icons, Code)

This doesn't happen for me in the latest stable version. So this is likely an issue on your end or that was resolved already.

6. Element Manager UI Search Field has double borders

Thanks for pointing this out. I will escalate it to the responsible team.

Thanks for the feedback! See you in the next beta! 💪

[nicholaszein]

Activating and installing the Elementor Editor Beta within the new Elementor One Admin Interface

Hey Beta testers! 👋

Welcome to this beta discussion! 🙌

We are finally here! The new Atomic Editor (V4) is entering its Beta phase, and we are super excited to introduce the new Components and Inline Editing features!

Since the interface changed, I prepared this short tutorial explaining how to activate and install this new Beta version 3.35 within the new Elementor One Admin interface.

🤓 Here's how to do it:

Tip

You don't need to install any additional plugin to enable beta testing.
(Including installing the Elementor Developers Edition plugin)

1. In your WordPress Dashboard navigate to the Elementor → Editor → Tools.
2. Select the Version Control tab.
3. Under the Become a Beta Tester section change the value of the Beta Tester select field from Disable to Enable.
4. Click Save Changes.
5. Navigate to Dashboard → Updates in the WP Admin Menu.
6. Confirm the 3.35.0-beta versions of both Elementor Editor Core and Editor Pro are available for update. If they aren't, click on the
   Check again link at the top of the Updates page, or wait a few minutes and Refresh the page again.
7. In the Plugins list, select both Elementor Editor Core and Editor Pro, and click Update Plugins
8. Once the plugins have been updated, navigate to Elementor → Editor → Settings and make sure the Elementor Data Updater has been executed. If you see a blue Update Now button, click to perform the update.

9. Finally, if you haven't activated Version 4, you can do so by navigating to Elementor → Editor → Settings → Version 4, and click Activate V4.

We can't wait to learn about your experience with the new features!

Happy testing! 😉 💪

[m1ga]

Will the paragraph styling options be also visible in the editor pane? At the moment it looks like you can't do any formatting unless you click on the text in the preview area

[nicholaszein]

Hey @m1ga, welcome back! 💪

The Inline Editing toolbar will only be visible in the editor canvas when you select text directly inside those widgets. Were you expecting to have a toolbar in the Widget Panel as well?

[m1ga]

either that or some kind of tinymce like before. The clients will see that there is textarea in the editor panel and will start to add/edit text there since you don't know that there will be a styling toolbar in the preview area.

[nicholaszein]

Good point @m1ga. There is indeed no indication that you could use the toolbar to edit the text.

As an advanced user, I would argue that I prefer, and tend to use the panel for inputting content more often than selecting the text directly in the canvas. Probably because of the old frontend-backend WordPress way. But when it comes to beginners, and non-technical users such as the majority of clients, there is an argument to be made that they may be more inclined to select the texts directly in the canvas intuitively (just as it's possible on the Block Editor, Wix, Squarespace, Wbflow, Framer, etc.), and the toolbar would automatically appear as expected.

But unless we have an onboarding tutorial for real novice users, this is as hidden as the old toolbar in V3. So it makes total sense to expect one in the Widget Panel too. 👍

As for the TinyMCE editor, we are not going to use it in V4. For several reasons, most importantly security (3.33.5 sends its regards 🎩) and technical debt due to backward compatibility.

[Topicimes]

Hello,

I can't wait to try out this new version! I'll definitely give you my feedback sometime next week.

When do you plan to publish the 2026 roadmap? I have to admit, I check the page every day, but there's nothing there yet.

The components are clearly a game changer. But I'm eagerly awaiting all the features that make Elementor so powerful today, especially some of the basics like loops, mega menus, accordions, etc.

In short, I know it will take time, but I can't wait for the equivalent of V3 in V4.

See you soon!

[nicholaszein]

Hey @Topicimes! Welcome back! 😉

Let us know how it goes, we want to make sure there are no bugs in the components. Try them everywhere and anywhere! 😁

The Roadmap will go live after our next event, which I can't say when it will happen yet. There is definitely more to come, and we will get there! 💪

Thank you for sharing your feedback! 🙏

[toltechinternet]

Loving this release!!!! Components = Game Changer!!! This has been on my wish list for so long, so thank you, Elementor, for finally getting around to this.

Also, a massive congratulations to the team for coming out of Alpha into Beta!

I will give this a whirl and come back if there are any bugs.

[nicholaszein]

Hey @toltechinternet!

Thank you for sticking with us and sharing your feedback! 🙏

Let us know how it goes, make sure to take it to a stress test! Don't hold it back! 👊

Hope to hear from you soon! 🤓

[loucasl]

Can't wait to test out components! Just curious, since V4 is now in Beta, any word on converting V3 containers / design systems to V4?

[nicholaszein]

Hey there @loucasl! Welcome back! 👋

We can't wait to hear from your feedback! 🙏

Things like import/export, copy & paste, and a conversion tool are things that rely on having a defined infrastructure for consistency behavior. Now that we are entering the Beta phase, the goal is to finally squash bugs in this foundation we created, so we can start working on implementing these missing pieces. So we don't now exactly yet when these will be available, but we will let you know when they do! 😉

Let us know how is your experience with the components. Take them for a strong spin! 🌪️

[doronwolf]

Hi @loucasl, we do plan an option to enable the users to control v3 and v4 design systems from one place (one source of truth), and later on, also enable migration of v3 styles into it. It is in our road map, it's gonna take some time, but I believe it will be worth the wait 😊

[nicholaszein]

Hi @mcrowell, welcome! 🙂

Given the community feedback, we are already looking into modifying this button. I'm not sure what will be done. I'm just sure something will be done with it.

Thank you for sharing your feedback! 🙏

[murrinmedia]

@nicholaszein I actually have zero idea how anyone thought that button was a good idea to start with (For paid accounts)

[nicholaszein]

Hey @mcrowell and @murrinmedia!

We released a patch for Editor Pro version 3.34.2 that removes this button for Pro users.

Feel free to update! 😉

[caleb-bright]

Hey @mcrowell and @murrinmedia!

We released a patch for Editor Pro version 3.34.2 that removes this button for Pro users.

Feel free to update! 😉

Thank you, glad to hear that this was removed for pro users.

[mcrowell]

Great! @nicholaszein Thank you!

[caleb-bright]

Yay, glad to hear that v4 is stable now for production testing! I will definitely be trying out the new features and give any feedback.

[doronwolf]

Hi @caleb-bright, are you asking for the 'insert from URL' option V3 had?🤔

Let me check it

[caleb-bright]

Yes, that's correct.

[caleb-bright]

Are there any known issues of atomic elements and their styles? I've experienced some issues where the default styles will be present, and not the ones connected to the class. The fix seems to be regenerate elementor css files and clear cache multiple times.

[nicholaszein]

Hi @caleb-bright ,

as far as we know, there aren't any issues anymore, as long as you're editing a new document not an existing one from before this beta as we applied breaking changes, old documents may not save or load styles correctly.

If you are still experiencing this issue and can reproduce it consistently, please open a new Editor V4 Bug Report with detailed steps to reproduce (a video recording helps a lot!) and we will investigate it further!

As for the "Insert from URL option", we will address this in a future release.

Thanks for joining this beta, hope to see you in the next! 🙏 💪

[caleb-bright]

Hi @nicholaszein, nice to hear from you. I'll have to see if I have anymore issues in the future with the styles. Sounds good with the image URL option. Thanks!

[minty-owen]

Hi, thanks again for the incredible update.

I experimented with the components and love them but managed to break them. I placed a component inside another and broke the fields and properties. This isn’t ideal. I noticed the flex grow and shrink options aren’t available in the parent div of a component because it behaves like a parent div. However, I used it for some cards so it’s essentially a child. Additionally, I used the SVG widget within a component and created a property or field but it doesn’t change in the editor. Furthermore, I have multiple components in a parent with justified content set but the components ignore this. Edit: I am running into another problem. The components sometimes dissapear in the editor, but are still on the page. I cannot edit them enymore than. Overall, it has a lot of potential!

I was wondering why we can’t give a direction in a fade or scale transition. Is it logical to remove the direction and simply stack the entrances like a slide and a fade? For example, using a slide entrance and a fade entrance with a direction breaks it.

Thanks a lot for the efforts.

[nicholaszein]

Hi @minty-owen,

thank you for sharing your experience! 🙏

1. Breaking Component fields

I've tried to reproduce your issue by creating a component within a component, and all fields work as expected. If you think you found a bug in that regard please create a new Editor V4 Bug Report with more detailed information (a video recording would be awesome) so we can investigate your issue further.

2. Missing Flexbox Child Controls

We are aware of the missing Flexbox Child Controls for components, and we will implement a solution in a future release.

3. SVG content not updating inside the Editor

Indeed there is a problem with the SVG element when applying styles in the Editor. Thank you for raising this issue. We will investigate it and solve it in a future release! 🙏

4. Child Component Justified Text does not apply

Please, open a separate Editor V4 Bug Report for this issue. We cannot reproduce this issue on our end. We need more detailed information and steps to reproduce.

5. Components disappearing from the Editor but still present in the page

Please, open a separate Editor V4 Bug Report for this issue. We cannot reproduce this issue on our end. We need more detailed information and steps to reproduce.

6. Interactions - Applying direction to Fade or Scale Entrance Animations

We cannot reproduce the issue you're reporting here. Directions work as expected in both scenarios for us. Are you sure you don't have Animation or Motion Effects disabled on your Operating System's Accessibility settings? Elementor will not play animations if these settings are disabled. It respects Reduced Motion preferences. If you think you found a bug with these animations, please open a separate Editor V4 Bug Report for this issue. We cannot reproduce this issue on our end. We need more detailed information and steps to reproduce.

Thank you! 🙏

[alexanderpankart]

Thanks, awesome update, a few questions straight from the editor, that popped up so far on my side:

As I am currently converting my entire site to V4 areas and/or elements as best I can, I have noticed a few things.

• The global style is no longer used, right? I can't (yet) use my custom font in the typography variables (?)

• What is your internal workflow for “us” to set size variables for H1-H6 on all device sizes? Of course, you could create 6 H1-H6 variables for each device size, but that would be a nightmare when selecting classes.

• Inline text can have a link in the V4 paragraph widget, but here I miss the option to add a link title (accessibility, SEO). Also, the search for existing pages is not active here. (Solution: I guess I'll have to use the WYSIWYG V3 widget for classic content here).

• Grid is not available, so I guess I'll have to wait until it is. Or is there a workaround for a grid of say 3x3 boxes layed out?

• Is there a plan to allow icons to be added to the Atomic Buttons, or is this a case where you should create your own component?

• The button text cannot be selected if no link url has been defined. Not really useful, but I noticed it.

Thanks :)

[alexanderpankart]

And a MASSIVE shoutout to the devs, that made my whole JetEngine meta fields dynamic content setup completly obsolete with the new components properties feature:

[doronwolf]

Hi @alexander-pankart, this is great feedback - thank you!🙏

1. true, global styles don't apply to v4 elements (however, in the future, we do plan to enable v4 vars to apply v3 elements, but it's going to take some time), regarding custom fonts not working with typography variables - let me check that
2. Regarding setting style for H1-H6 using V4 vrs/classes - this is also in our road map
3. This is a good point. We do intend to add the 'type to search' capability to find pages quickly - I'll also check regarding adding support for link title
4. Yes, v4 grid is also in our road map. Right now, you can still seta 3x3 grid using custom CSS or set 3 x 3 flexbox containers
5. atomic button with an icon inside is no longer atomic (it's more like a molecule..) so yes, take a flexbox and turn it into a link, and throw inside this flexbox a paragraph + svg and you get the same result (obviously you will need to style them to have a 'button' look) - we do have plans to create ready-made presets like that in the future
6. Yes, support for inline editing for the button's text is currently missing, but it's coming very soon. But if you want to link a button, it's better to use the link control in the settings tab on the left panel (so the whole button will become linkable and not just the text)

[alexanderpankart]

Thank you for your detailled response. Sounds great :)

*and i use a variable font, that is not displayed - didn't test it on a "regular" font file.

[alexanderpankart]

Thank you with your "button tip". That worked very well.

The button adapts in size to the elements inside it, when you change the max-width to "max-content" with the css formula.

Also the code for the new "icon button" is very clean that way.

[nicholaszein]

Hi @alexander-pankart!

Just to clarify about Custom Fonts:

We are aware they are currently not working, both Static and Variable fonts. Variable font's can't be selected, and so far Static Fonts are not loading on the frontend. We will be addressing compatibility with Custom Fonts in a future release.

[Nomex1337]

when i create a component like a custom button and insret the button in a flexbox container with elements to the left then my heading is left the paragraph is left but the component is to the center so in editor is showing wrong. In the Frontend is all fine. In chrome dev is staying display: contents !important in elmentor editor, when i disable the style then is it in editor even correct. Think there is a issue with styling.

[nicholaszein]

Hi @Nomex1337! Welcome to the discussion!

Thank you for the feedback!

Would you be able to take a PrintScreen/Screenshot of this issue so we could understand what the problem is better?

[Nomex1337]

Frontend

Backend

[alexanderpankart]

I also created a custom svg icon button component.
Everything is aligned to the left, but the component won't move in the backend.

Backend:

Frontend:

I mean, that's good, that the frontend is rendering it just fine, but yeah :)

[alexanderpankart]

There is only one error shown; don't know if that's related:

In order to set a max-width of that element i use:

[nicholaszein]

Hi @Nomex1337 and @alexander-pankart!

Thank you for sharing your feedback! 💪

We fixed the problem with the Component alignment inside the editor in the Core v3.35.0-beta3! 🙌

[contrastxxx]

Thank you for the great update. I have a question right away. Previously, in the Text Editor I had the option Visual or Code, which allowed me to add HTML code. The same applies to the Heading, where I often use <br> and other HTML tags.
Thank you

[doronwolf]

hi @contrastxxx, now you can simply add a line break on the canvas by clicking the text and pressing 'enter'. no need to write down code

[contrastxxx]

Thank you for the reply. The new line option is great, but what if I want to add a span with a class? I use it quite often.
text <span class="pink">TEXT 2</span>

[nicholaszein]

Hey @contrastxxx! Welcome back! 💪

Thank you for joining the discussion! 🙏

For the time being, we aren't including full HTML support for the Heading and Paragraph widgets, only formatting tags. Atomic Elements are supposed to be single html tags, following the concept of Atomic Design (check this video to understand the concept) to allow full design control.

We will consider allowing more tags in the future. Thank you for sharing your feedback!

Let us know how your experience goes with the new features! 🤓

[doronwolf]

Hey @contrastxxx! continuing from what Nicholas wrote - the option is also on our road map - stay tuned 😉

[contrastxxx]

Thank you for the reply. It would be great to have this option in the future. Thank you.

[welmartins]

Wow, this looks amazing!

Do you know if there are any plans to transform this component not just into a single one, but also into multiple ones? Like a repeater?

This would help to further reduce the component tree and speed up the content editing process.

In the editing panel, each item/loop could appear as if it were an accordion.

Or create another widget that reads this component as a template and transforms it into a loop item.

👀🔥 @avivu @nicholaszein

[nicholaszein]

Hi @welmartins! Welcome! 🤗

Thank you so much for the kind words! This really motivates us! 🙏

This is an interesting idea! 💡 We will definitely discuss it. Thank you for sharing!

Have you tried using Components yet? How was your experience? Did you find any issues?

Please, don't hesitate to test and share anything! 🙏

[welmartins]

This would be a very good feature, along with the already amazing ones. 🔥

Furthermore, it would be interesting to have the possibility of adding a link that wraps around the entire component.

I haven't tested v4 yet, but as soon as the beta version comes out, I want to put it in a real project. The gain from the clean HTML structure will be important, especially considering AI bots.

[nicholaszein]

@welmartins regarding wrapping elements with links:

Both Div Block and Flexbox Atomic Elements allow you to apply links to them, the same way it's possible with the Container.

However, I need to advise that there are limitations.

In HTML nesting anchor tags <a> (what links are made of) generates invalid code. This is a limitation of HTML.

Editor V4 has a really nifty mechanism that detects when you try to nest links, and will warn you if you try to do so.

So yes, you can add a link to the outer wrapper of a component if you want, as long as you don't add internal links, otherwise your layout would completely break.

Just a nifty little nugged to be aware of! 😉

[michelleist]

I can not see my custom fonts in the typography dropdown, only system fonts are there. Any idea what I am doing wrong?

[PhilippeGHB]

Haha, thank you @doronwolf :)
It's pretty weird. The font is labeled SF Pro, but the font we see in the viewport is some kind of serif font. SF Pro is a sans-serif like in the screenshot below. It happens only on tablet and mobile. It works on the desktop, even when I minimize the window. I'm confused.

[doronwolf]

Hi @PhilippeGHB, only if I disable the 'SF Pro' font via the inspect panel, then I get the same look that is in your screenshot... which actually looks more like the 'Apple system font' and not the 'SF Pro' font. This is really weird. Maybe there is an issue with the font file itself?

[PhilippeGHB]

Hi @doronwolf

Okay, I really have no idea.

I tried it again with a completely fresh installation of wordpress. Installed Elementor and Elementor Pro and the Hello Elementor Theme. Created a page, header and footer, and uploaded the static woff2 font «Proxima Nova». No additional plugins or css.

Desktop: Chrome, Arc > OK > Proxima Nova
Desktop: Safari, Brave, Firefox > wrong font
Mobile: Chrome, Arc, Safari, Brave, Firefox > wrong font

Same reverse behavior: when i disable Proxima Nova via inspect panel, Proxima Nova appears. If Proxima is activated, it displays the wrong (system) font.

Am I the only one with this problem? 😂 I don't get it.

https://philippejost.ch/stage/seventysix/

[doronwolf]

Hi @PhilippeGHB, which theme are you using? Can you switch to 'hello' and then test again?

[doronwolf]

I think you are already using 'Hello' ..I'll ask our team to investigate

[nickdgreen]

Am I missing something here?

Old School:
Example 1 - You can create a button called "Call Me Now", style it, and add a Link to the phone number. Save this as a global widget. You can then use this button site-wide. If you select the widget on one page, you can edit it, and all buttons will change. Or you can disconnect it and use the styling and change the text and/or usage.

Example 2 - You create a container as a column with an image, a title, some text, and a button. Save it as a template. Insert the template wherever you need it on the site and edit the contents accordingly.

Version 4:
For example 1 above, you can create a button style to give you consistent styling across the site, but not the button "content". You can't save the button as a global widget; you have to add the content every time. You also can't save it as a component.

For example 2 above, you can now create a "Component" this has the advantage that you can select it from the Component Panel rather than having to use the templates. BUT this behaves like a global widget in the respect that changing the component on one page changes all of them, and when a component is on the page, you can't "disconnect" it to edit it.

So, unless someone can explain what I'm missing, Version 4 removes really useful Global Widgets and introduces Components that I can't see any use for. I can see that a component that you can individually edit is a step up from a template or global widget, but as it stands, that's not the case. Also, losing global widgets is a step back for workflow.

[alexanderpankart]

Example 1: Once disconnected, all changes to the global button won't affect that button anymore.

Example 2: If you edit a template, all other templates change as far as i know.

Once you created that component out of V4 elements, you have to set properties, that you want you or your client to change.
Only those elements with that black square "Override Property" will be affected.

• You still can keep the original text of that component, if you want it to be same on every site.

[nickdgreen]

Example 1 - I stated that if you left it as a global widget, you made global changes, BUT if you wanted, you could just keep the styling and edit this new single instance. In version 4, you only have the styling option; you don't get the content like a page link.

Alexander - Ah! Now the component makes sense. Thank you.

[benyten9]

Hi, Congratulations on launching the Beta v4, I have been playing around with v4. The one issue I have been facing is when I use Atomic button. It is not giving option to add elementor icons inside the button which looks very annoying. Can you please fix that? Thank You. And I have created some pages and tested it out. Website loads very fast as compared to older version.

[doronwolf]

Hi @benyten9 👋 first of all - thank you so much for your feedback🙏
regarding the button - atomic button with an icon inside is no longer atomic (it's more like a molecule..) so this is why, unlike V3, there isn't a built in option to add an icon to but, you can still get it: take a flexbox and turn it into a link, and throw inside this flexbox a paragraph + svg and you get the same result (obviously you will need to style them to have a 'button' look) - we do have plans to create ready-made presets like that in the future

[benyten9]

Hi @doronwolf Thank you for letting me know.

[benyten9]

Hi @doronwolf In Elementor v3, the Text Editor widget made it very easy to create bulleted and numbered lists using the built-in formatting toolbar. After moving to Elementor v4 and using the Paragraph widget, those list formatting options no longer appear.

Was this feature intentionally removed from the Paragraph widget, or is there a setting we need to enable to access bullet and numbered list formatting? If it’s been replaced, what is the recommended way to create properly formatted lists in v4?

[doronwolf]

Hi @benyten9 - yes, the option to create lists is currently missing,
Since the V4 editor uses the atomic approach, each list item should be an atom on its own, which makes it problematic to be contained inside the paragraph atom (it's like one atom inside another), so... for now, we are still thinking this out, but, fear not, it is on our to-do list and will happen eventually

[avivu]

Hi all,

We just released new Beta versions.

The versions include the following:

We just released Elementor Editor v3.35 Beta 3.

• Tweak: Updated import and export flow for Website Templates
• Fix: Inline editing enters an infinite delete loop - Editor V4
• Fix: Flex and Div blocks lose selection when deleting an assigned class via the Class Manager - Editor V4
• Fix: Importing a site containing elements with dynamic tags fails - Editor V4
• Fix: Component alignment issues inside the editor - Editor V4
• Fix: Renaming components breaks autosave - Editor V4

Pro version

• Fix: Shortcodes overflow the screen on Saved Templates screen in WordPress Admin
• Fix: Avoid Multiple Popups control does not work in Popups

–

Thank you!

[dannSPM]

My interactions aren't working.

[doronwolf]

nope.. I can't reproduce the issue
Are you sure you are using v3.35.0 beta3?
Can you check the console and screenshot it for us (for any errors)?

[dannSPM]

There are no errors in the console, and yes, I'm on version 3.35.0 beta3.

[dannSPM]

The only interaction that works is fading.

[doronwolf]

Hi @dannSPM, is this a staging site we can access to try to debug it?

[dannSPM]

I used it locally on my machine using XAMPP.

[alexanderpankart]

Will there be an option to export and import classes and variables?
(or maybe even synch via cloud?)

[doronwolf]

yes! It's on our road map 🚀

[pumadog]

I'm on 3.35 Beta 3, but:
• The inline text formatting toolbar doesn't appear for me. For heading or paragraph. But the box gets tall when clicked in.
• There's no "boxed" option for Flexbox or Div box content width. Is this intended? How to set?
• I don't find any gap setting for the Div box. Why?
• V4 widgets don't have any handle/icon on the canvas. So drag and drop is only possible in the navigator.

I'm currently testing with Local WP, Safari and Chrome on Mac in German.

[dannSPM]

Regarding the spacing of the div, at the code level, it's a display block div, so it's not a flex item; its spacing will be determined by margins.

[doronwolf]

Hi @pumadog - those are important points🙏 I'll try to address them one by one:

• The inline text formatting toolbar doesn't appear for me... This is really weird, we haven't faced any user with this issue up until now, can you share your system info? I'm wondering if this could be the result of a plugin conflict

• There's no "boxed" option for Flexbox or Div box content width... Yes, this is intended. The V3 'boxed' option used 2 Divs, one inside another (in which the inner one is there although it has no representation in the navigator panel). It was easy for the users who wanted it, but at the same time, it created excessive DOM when not needed, so now in V4, we prioritize cleaner code. If you want to reach the boxed layout very easily simly by dragging another flexbox into your parent flexbox and setting the width of the inner flexbox to your liking, but this way fewer users are going to use a redundant div when they don't need it

• I don't find any gap setting for the Div box. Why? - The 'Gap' property is a 'Flex' capability, the Div block uses 'display = block' so it can't have the gap options, but you can still use padding & margin etc. ot simply go to the style tab and change the div 'display' settings to 'display = Flex'

• V4 widgets don't have any handle/icon on the canvas. So drag and drop is only possible in the navigator. - not accurate, you can still drag and drop also from the canvas, simply click and drag any v4 widget, the only widgets that have a bit of an exception are the paragraph and heading widgets, if you just click without dragging right away, they will enter into 'inline editing mode' to let you edit (type, delete, line break, bold/ italic/underline, etc..) from the canvas, so only then you need to first, getout from the 'editing mode' before dragging

[pumadog]

Hi @doronwolf!

Toolbar: I just updated to Beta 4, still them same behavior.

System Info

== Server Environment ==
Operating System: Darwin
Software: nginx/1.26.1
MySQL version: MySQL Community Server - GPL v8.0.35
PHP Version: 8.4.10
PHP Memory Limit: 256M
PHP Max Input Vars: 4000
PHP Max Post Size: 1000M
GD Installed: Yes
ZIP Installed: Yes
Write Permissions: All right
Elementor Library: Connected

== WordPress Environment ==
Version: 6.9
Site URL: http://test-editor-v4-2025.local
Home URL: http://test-editor-v4-2025.local
WP Multisite: No
Max Upload Size: 300 MB
Memory limit: 40M
Max Memory limit: 256M
Permalink Structure: /%postname%/
Language: de_DE
Timezone: 0
Debug Mode: Inactive

== Theme ==
Name: Hello Elementor
Version: 3.4.6
Author: Elementor Team
Child Theme: No

== User ==
Role: administrator
WP Profile lang: de
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0.1 Safari/605.1.15

== Active Plugins ==
Elementor
Version: 3.35.0-beta4
Author: Elementor.com

Elementor Pro
	Version: 3.35.0-beta3
	Author: Elementor.com

== Elemente Verwendung ==

wp-post : 0
	container : 2
	e-component : 2
	e-div-block : 4
	e-flexbox : 3
	e-heading : 3
	e-image : 1
	e-paragraph : 4
wp-page : 2
	e-button : 2
	e-div-block : 1
	e-flexbox : 2
	e-heading : 2
	e-paragraph : 2

== Einstellungen ==

cpt_support: post, page
allow_tracking: yes
font_display: swap

== Eigenschaften ==
Custom Fonts: 0
Custom Icons: 0

== Integrationen ==

== Elementor-Experimente ==
Inline-Schriftarten-Symbole: Standardmäßig aktiviert
Zusätzliche individuelle Breakpoints: Standardmäßig aktiviert
Container: Aktiv
Optimized Markup: Aktiv
Standard ist der neue Theme Builder: Standardmäßig aktiviert
Header und Footer: Standardmäßig aktiviert
Pro Free Trial Popup: Standardmäßig deaktiviert
Verschachtelte Elemente: Aktiv
Seiten Panel: Standardmäßig deaktiviert
Elementor Home Screen: Standardmäßig aktiviert
Atomic Widgets: Aktiv
V4-Indikations-Popover: Standardmäßig deaktiviert
Berechtigungen für Atomic Widgets erzwingen: Standardmäßig aktiviert
Editor MCP für Atomic Widgets: Standardmäßig aktiviert
Backward compatibility migrations: Standardmäßig aktiviert
Globale Klassen: Aktiv
Erzwinge globale Klassen-Berechtigungen: Standardmäßig aktiviert
Variablen: Aktiv
Variables Manager: Standardmäßig aktiviert
Cloud-Sammlung: Standardmäßig aktiviert
Editor V4 (Opt-in-Seite): Standardmäßig aktiviert
Editor V4: Aktiv
Components: Standardmäßig aktiviert
Interaktionen: Standardmäßig aktiviert
Editor one: Standardmäßig aktiviert
Import-/Export-Anpassung: Standardmäßig aktiviert
Elementor-Editor-Ereignisse: Standardmäßig deaktiviert
Atomic Form: Standardmäßig deaktiviert
Menü: Aktiv
Size Variables: Standardmäßig aktiviert
Pro Interactions: Standardmäßig deaktiviert
In-Editor Feedback: Standardmäßig deaktiviert

== Protokoll ==

Log: showing 20 of 382026-01-28 15:01:51 [info] elementor-pro::elementor_pro_updater Started
2026-01-28 15:01:51 [info] Elementor Pro/Upgrades - _on_each_version Start
2026-01-28 15:01:51 [info] Elementor Pro/Upgrades - _on_each_version Finished
2026-01-28 15:01:51 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor Pro',
'from' => '3.34.0',
'to' => '3.34.3',
)]
2026-01-28 15:01:51 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor Pro',
'from' => '3.34.0',
'to' => '3.34.3',
)]
2026-01-28 15:06:39 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor',
'from' => '3.34.3',
'to' => '3.35.0-beta3',
)]
2026-01-28 15:06:39 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor Pro',
'from' => '3.34.3',
'to' => '3.35.0-beta3',
)]
2026-01-28 15:06:39 [info] elementor::elementor_updater Started
2026-01-28 15:06:39 [info] Elementor/Upgrades - _on_each_version Start
2026-01-28 15:06:39 [info] elementor-pro::elementor_pro_updater Started
2026-01-28 15:06:39 [info] Elementor Pro/Upgrades - _on_each_version Start
2026-01-28 15:06:39 [info] Elementor Pro/Upgrades - _on_each_version Finished
2026-01-28 15:06:39 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor Pro',
'from' => '3.34.3',
'to' => '3.35.0-beta3',
)]
2026-01-28 15:06:40 [info] Elementor/Upgrades - _on_each_version Finished
2026-01-28 15:06:40 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor',
'from' => '3.34.3',
'to' => '3.35.0-beta3',
)]
2026-01-29 14:41:07 [info] elementor::elementor_updater Started
2026-01-29 14:41:07 [info] Elementor/Upgrades - _on_each_version Start
2026-01-29 14:41:07 [info] Elementor/Upgrades - _on_each_version Finished
2026-01-29 14:41:07 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor',
'from' => '3.35.0-beta3',
'to' => '3.35.0-beta4',
)]
2026-01-29 14:41:07 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor',
'from' => '3.35.0-beta3',
'to' => '3.35.0-beta4',
)]

PHP: showing 3 of 3PHP: 2026-01-15 15:17:40 [notice X 8][/Users/sascha/Local Sites/test-editor-v4-2025/app/public/wp-content/plugins/elementor/includes/base/controls-stack.php::230] hexdec(): Passing null to parameter #1 ($hex_string) of type string is deprecated [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2026-01-28 16:22:21 [notice X 1][/Users/sascha/Local Sites/test-editor-v4-2025/app/public/wp-content/plugins/elementor-pro/core/database/model-base.php::66] ElementorPro\Core\Database\Model_Base::query(): Implicitly marking parameter $connection as nullable is deprecated, the explicit nullable type must be used instead [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2026-01-28 16:22:21 [notice X 1][/Users/sascha/Local Sites/test-editor-v4-2025/app/public/wp-content/plugins/elementor-pro/modules/notes/database/models/user.php::96] ElementorPro\Modules\Notes\Database\Models\User::query(): Implicitly marking parameter $connection as nullable is deprecated, the explicit nullable type must be used instead [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]

JS: showing 1 of 1JS: 2026-01-28 15:02:10 [error X 4][http://test-editor-v4-2025.local/wp-content/plugins/elementor/assets/js/import-export-customization-admin.min.js?ver=3.34.3:2:32602] Can't find variable: elementorAdmin

== Elementor - Compatibility Tag ==

Elementor Pro: Kompatibel

== Elementor Pro - Compatibility Tag ==

No boxed option anymore: Ok, so I use a class now to keep the width in sync, right?

Div box: As this has limitations over flexbox and makes styling more complicated: Can you explain when and why it should be used and has advantages over flexbox? For a me it just looks like the less capable choice.

V4 element handles: Ok, drag and drop functions. But they really have no handle? Wouldn't that be helpful for less experienced users?

[doronwolf]

No boxed option anymore...
Yes, using a class is very recommended to keep style consistency

Div box...
This was actouly a user request, back in V3, when we only had container (which is equivlent to the V4 flexbox) user were asking a way to remove the 'display = flex' for cases they want just a simple div, we also added it to the widget panel as way to drag a widget that has 'display = block' without needing to manualy set it so, but other than that, you are correct, the div block, once you set it to 'display = flex', is not really different from the flexbox

V4 element handles...
I agree it's diffrent form what our users are used to, we are still gathering feedback about this, and accordingly we will decide which option is better

[murrinmedia]

Will there be a way to just copy and paste variables? And it creates them in the Elementor system? I want to add 3 colors, and their 7 shades, that's 21 variables. I have to copy and paste 42 times (variable name and color).

It's extremely time consuming

Or, I can add that to the custom CSS, and paste it in

BUT - I can't reference those variables in atomic elements? For example I made --primary variable, and set the colour.

When I type in var(--primary) into the box next to the color, it actually changes the color on the screen, but as soon as I click off of it, it disappears.

[dannSPM]

Is it possible for the parent element, when hovering, to make a change to its child?

I couldn't find an option.

[doronwolf]

Not at the moment, but it is a part of our future road map for our interactions👍

[nickdgreen]

Just had a first look at creating variables, and although I created a colour variable and a text variable, I couldn't save them. Clicked on the save button didn't work. Tried the exit and got a pop-up "cancel or save" Save didn't work. The Variable Manager a) needs to work b) needs an icon in the elementor panel for easy access and a shortcut key.

[Danitsh]

Hey @nickdgreen

We are aware of this issue and implemented a fix in the GA version.

[alexanderpankart]

Sticky Header won't work on my header.
Just that on my outer div (that should be sticky)

Am i doing anything wrong?

[doronwolf]

Hi @alexander-pankart, note the V4 'sticky' is CSS sticky (not JS sticky like in V3)
meaning:

1. You must enter a value (like 0 or more that will serve as the offset) in the 'top' field (or in 'bottom/left/right field', depending on which type of sticky you want)
2. The sticky will always have the 'stay in column' behavior (this is how CSS sticky behaves), so in the case of a Header, it will probably fit better to use the 'Fixed' option (and again, you must add some value (like 0 or more) for it to become effective

[nickdgreen]

Can the atomic button be made so it can be saved as a component on its own so it can be used like a global widget across the site instead of having to resort to using a V3 button.

[ellipertzov]

Hi @nickdgreen - currently only v4 containers can be used for components. you can create your custom button using div block and save it as a component.