No, Divi 5 will be available free of charge to any Elegant Themes user with an active subscription.

We do not recommend using Divi 5 Public Alpha on a live website. It is an early preview and is not intended for use on live production sites.

Test it in a staging environment or on a local host installation. Since it’s still under active development, bugs and incomplete features are expected.

Not all features from Divi 4 are available in the Public Alpha. For example, certain modules like WooCommerce are not yet included. These features will be introduced in future updates as we move closer to the final release of Divi 5.

The Divi 5 Public Alpha will automatically update through your WordPress Dashboard as new versions become available. To ensure you have the latest stable build, we strongly recommend keeping your website up to date.

You can view a list of all changes made to Divi 5 in the changelog here.

Divi 5 was built to be backward compatible. Divi 4 modules will function on the front end using backward compatibility mode. However, pages using legacy modules will not benefit from Divi 5's front-end performance improvements.
​
Legacy modules can also be edited in the new Visual Builder. However, certain limitations exist, and some field types are not yet supported.
​
Backward compatibility mode is still a work in progress, and we'll be improving it and fixing bugs throughout the alpha phase.
​
Backward compatibility mode is a temporary solution to help bridge the gap while creators develop new versions of their modules in preparation for the final release of Divi 5.

No, plugin authors are not responsible for any compatibility issues during the Alpha phase. Divi 5 Public Alpha is still a work in progress, and any issues encountered will likely be resolved as we move closer to the full release.

Plugin authors are responsible for updating their plugins to provide full Divi 5 support. However, you shouldn't expect third-party modules to be ready for Divi 5 at this stage. Creators are working hard to create new versions of their modules in preparation for the final release of Divi 5.
​

Until then, legacy modules will function using Divi 5's backward compatibility mode.

The Divi 5 Migrator will parse all your website content and look for Divi 4 shortcodes. It will convert those shortcodes to the new Divi 5 format and update each post.

Modules that do not yet support Divi 5, such as modules from the Divi Marketplace, will not be converted and will continue to function using the legacy Divi 4 framework.

Pages that use such modules will not benefit from Divi 5's performance improvements.
​
The migrator makes sweeping changes to your entire site and should only be used for testing on non-production websites at this time.

Divi 5 is designed to prioritize backward compatibility, meaning most of your existing content and designs from Divi 4 should function correctly in the Public Alpha. However, some features and modules from Divi 4 are temporarily unavailable in this early version.

For more information, please check the Backward Compatibility and Third-Party Divi Module Support article.

Creators from the marketplace are hard at work updating their modules for Divi 5. However, most will not be ready during the Divi 5 Alpha.

Thanks to Divi 5's backward compatibility mode, you can still use legacy modules. However, this mode is still a work in progress and has some limitations.

Yes, you might experience a performance hit when using third-party Divi modules because they will run in compatibility mode.

This mode is temporary until full compatibility is ensured in later releases, particularly as we approach the Divi 5 Public Beta.

This warning will appear if a page contains an unconverted Divi 4 module or if one of your plugins uses the legacy Divi 4 framework.

We built Divi 5 to be backward compatible with Divi 4 plugins, such as modules from the Divi Marketplace. Until creators update their plugins for Divi 5, legacy plugins will continue to function using the legacy Divi 4 framework.

However, loading the Divi 4 framework comes at a performance cost. The orange warning informs you that a plugin you are using is tapping into the legacy framework, and the page is not benefiting from Divi's performance improvements.
​
It's not an error. It is just there for informational purposes during the alpha and beta phases.

During this period, creators from the Divi Marketplace are hard at work redeveloping their modules for Divi 5. You should expect third-party modules to be ready as we approach the final release of Divi 5, but not at this early stage.
​
In the meantime, legacy modules will continue to function using Divi 5's backward compatibility mode.

It is recommended that you do not use Divi 5 Public Alpha on live sites or critical projects, so rolling back should not be necessary. However, if you are testing Divi 5 on a staging site and wish to revert to Divi 4, you can use the Rollback option.

Please check the How to Rollback to Divi 4 article for more information.

As this is an Alpha version, some bugs may occur. However, the Migrator system is designed to ensure a smooth transition from Divi 4 to Divi 5 Public Alpha.

Since Divi 5 is still in its alpha stage, we don't recommend using it on production websites. Test it only on local and staging sites. For your convenience, you can also run a backup before you migrate.

Finally, the Divi 5 Migrator automatically backs up your post content, and you can restore that content and roll back to Divi 4 if you choose.

If you experience any bugs or issues while testing Divi 5 Public Alpha, please provide your feedback. This will help improve the final product and ensure a smoother transition when the full version is released.

Please check the How to Report a Divi 5 Alpha Bug article for more information.

While there is no specific release date for the final version of Divi 5, it is expected to follow several stages, including Public Alpha, Public Beta, and additional updates, leading to the full release.

Please check the Divi 5 Roadmap article for more information.