Elementor 3.32 sharpens the editing experience, improves accessibility, and unlocks performance gains. This update continues the Editor V4 journey with new design and workflow tools, merges experiments into core features, and ensures compatibility with the latest PHP version. This update provides a better building experience today and a stronger foundation for tomorrow.
Editor V4
Elementor 3.32 continues the Editor V4 journey with new styling tools and workflow improvements. This release introduces Transform, Transitions, Size Variables (Pro), and Class management upgrades. Since it’s still in alpha stage development, these features are experimental and not production-ready, with possible breaking changes. We recommend only using them on staging sites.
Transform Controls
The new Transform feature lets users visually move, scale, rotate, and skew elements in both 2D and 3D. It includes stacking per state, perspective controls, and repeaters for organization. Combined with States, Transforms enable dynamic micro-interactions like hover scaling or rotating cards for tactile effects.
Transitions Controls
Transitions bring polished animations when elements shift between states like hover and focus. Free users get a single transition, while Pro users gain advanced control over individual properties, durations, and stacked animations. Combined with Classes, Transitions ensure consistent, reusable effects across your website.
Size Variables
Size Variables expand the Variables system, joining Color and Font Variables to unify spacing and sizing across designs. They work on margins, typography, layouts, and borders, storing both value and unit. Designers can update one variable (e.g., button radius) and apply consistent changes sitewide.
Class Management
New tools improve Class workflows with conversion and filtering. Users can instantly convert local styles into reusable Global Classes, streamlining design scalability. Filters in the Class Manager help spot unused, empty, or page-specific classes, making it easier to maintain a clean and efficient style library.
Accessibility Improvements
Elementor continues to invest in improving your website accessibility, with every release improving additional accessibility issues. Our commitment is emphasized in the latest WordPress Page Builder Accessibility Comparison, by Equalize Digital. With an increase in our accessibility score from 70.13% in 2024 to 75.55% in 2025, Elementor continues to make measurable progress towards being one of the most accessible page builders.
This release focuses on two objectives: removing decorative elements from the accessibility tree, and respecting the reduced-motion preference in multiple widgets and features. We’re happy to share that some accessibility issues fixed in this release were actually detected with the help of Ally, our free accessibility plugin.
Decorative Icons
Various Elementor widgets display icons. In most cases, these icons are decorative elements. According to accessibility best practices, decorative elements should not be visible to assistive technologies. To solve this issue, Elementor 3.32 removed icons from the accessibility tree, keeping only the screen-reader text.
Furthermore, depending on the “Inline Font Icons” experiment status, Elementor uses either the <i> or <svg> tag to display these icons. When icons are displayed as SVG, many accessibility tools recognise these SVG files as images and warn that they lack a proper alt attribute. Removing decorative icons from the accessibility tree fixes this issue, too.
For example, the Animated Headline widget highlights texts with animated SVG shapes behind the text; these SVG shapes are now completely hidden from the accessibility tree as they are purely decorative elements. Both the Social Icons and Share Buttons widgets have their icons removed from the accessibility tree, as well, keeping only the screen-reader text with the social media name. And finally, the dropdown indicator in WordPress Menu widget is now removed from the accessibility tree, as it’s not a separate interactive element, rather a decorative indicator.
Motion Effects
The Motion Effects feature adds the ability to integrate various “Scrolling Effects” and “Mouse Effects” directly into the page. These effects can be applied to individual widgets or to the backgrounds of containers, creating highly immersive and visually stimulating designs.
However, operating systems include a “reduced-motion” preference, allowing users to explicitly signal their desire for less animation and visual movement. When this preference is activated, websites should respect this setting, ensuring a comfortable and accessible browsing experience for all.
Elementor 3.32 now fully respects the user’s reduced-motion preference. Meaning that no “Motion Effect” is activated when the reduced-motion preference is enabled.
Animated Headline
The Animated Headline widget is a versatile tool that allows designers to create engaging and dynamic text elements with “highlighted” and “rotating” animation effects.
Previously, the widget didn’t respect reduced-motion preferences in operating systems. The animations within the widget would always remain active, regardless of the user preferences.
Elementor 3.32 no longer activates the “highlighted” animation when users activate the reduced-motion preference on their OS. This release ensures “highlighted” animation now respects the user’s operating system’s reduced-motion preference.
Looking ahead, future releases further improve accessibility, adding support for reduced-motion to “rotating” text animations, as well.
Experiments and Features
In this release, Elementor continues to improve and merge features and experiments, laying the groundwork for Editor V4. Elementor 3.32 merged and updated the following features:
Merged Features
The “Cloud Library” feature, originally introduced in v3.29 and enhanced in v3.30, adds the ability to save and reuse design elements across multiple projects, by saving them in the cloud and loading them on other websites you manage. Now, this feature is merged into Elementor.
The “Element Caching” feature, originally introduced in Elementor 3.22, stores the HTML of each element/widget in the database. When the page is loaded, rather than rendering fresh elements each time, it uses cached HTML, boosting performance. Originally introduced in Elementor 3.22, and after a long data collection period, it is now safe for all websites and merged to Elementor 3.32.
Upgraded Features
The “Optimized Markup” feature, originally introduced in Elementor 3.25, is a performance feature that reduces unnecessary HTML tags and causes the page DOM size to decrease, thus decreasing the browser’s parsing and rendering time. Already marked as stable and active on new websites, this feature is now enabled by default on all websites, ensuring better performance out of the box.
UPDATE: The Optimized Markup change was reverted.
Performance Improvements
With the release of Elementor 3.32, websites may experience noticeable performance improvements. These gains are not the result of introducing new features, but rather from merging and activating existing performance experiments. Websites are affected differently based on the status of the experiments on their websites.
The sites that will benefit the most are those where experimental features were disabled. Starting with this version, Optimized Markup is enabled on all websites, reducing the overall HTML DOM size. At the same time, Element Caching is now merged to Elementor and active by default on all websites, storing HTML in the database and reducing the amount of server-side computation required. Together, these changes contribute directly to a faster Time to First Byte (TTFB) on the frontend.
Websites that left experiments in their “default” state may also see improved performance, thanks to the activation of Optimized Markup on all existing websites.
The only case where website performance will remain unchanged is for websites that had already enabled these experiments manually.
UPDATE: The Optimized Markup change was reverted.
PHP 8.4 Compatibility
Elementor has long supported PHP 7.4 and higher. However, running WordPress with wp_debug enabled on PHP 8.4 revealed a number of deprecation notices. These were mostly related to nullable parameters. When a function had a parameter using null as its default value but null was not explicitly declared in the type definition, PHP 8.4 flagged it as deprecated.
In Elementor 3.32, these issues have been addressed across dozens of files in both Elementor and Elementor Pro. The fixes cover the Frontend, the Elementor Editor, and the WordPress Admin, ensuring that nullable parameters are properly declared and compatible with PHP 8.4.
By resolving these deprecations, Elementor removes obstacles for websites migrating to newer PHP versions, unlocking performance improvements that benefit the entire WordPress and Elementor ecosystem.
Elementor remains committed to full compatibility with new PHP versions, and we encourage developers to report any remaining issues on our GitHub repository, so they can be resolved quickly.
Developer Advisory
With the merge of the Element Caching feature to Elementor, it will be activated by default on all websites.
Websites facing issues after the upgrade can either clear cache from WordPress Admin > Elementor > Tools screen. Or, disable the Elements Caching feature from WordPress Admin > Elementor > Setting screen > Performance tab. This is useful when debugging compatibility issues with other caching plugins.
For high-traffic or infrequently updated websites, consider increasing the cache duration from the default one day to a longer period (three days, a week, a month, or more). A longer cache duration reduces resource usage, improving website speed and performance.
To Conclude
Elementor 3.32 is a step forward in evolving the Editor V4 experience, strengthening accessibility, and boosting performance across all websites. By merging performance experiments, enhancing compatibility with PHP 8.4, and introducing new design tools, this release ensures developers can build faster, more accessible, and future-ready sites. As always, we encourage testing experimental features in staging environments and sharing feedback to help shape the next generation of Elementor.
