If your page shows old styles, missing formatting or a different layout from the Visual Builder, start by clearing cached files.
This is especially useful after updating Divi or Divi Review Builder.
Step 1: Save your changes
Save the page or Theme Builder template, then exit the Visual Builder.
Confirm that you are checking the correct page.
Step 2: Clear Divi’s CSS cache
In your WordPress dashboard:
- Go to Divi → Theme Options.
- Click Clear CSS Cache at the top-right of the panel.
Divi will regenerate its cached styles. This does not delete your page content or design settings.
Step 3: Clear other website caches
If you use a caching or optimization plugin, clear its cache, including any separate CSS and JavaScript caches.
Then clear the affected page from your hosting cache and CDN, if applicable.
The controls may be called Purge Cache, Clear Cache or Flush Cache. Your hosting provider can help you locate them.
Step 4: Check in a private window
Open the page in a fresh private or incognito window.
Check the frontend while logged out, including desktop and phone views.
A private window helps avoid your browser’s existing cache, but it does not bypass hosting or CDN caches.
Step 5: Check the saved design
If the problem remains, inspect the affected section, row and module.
Check:
- Responsive sizing and spacing.
- Visibility settings for desktop, tablet and phone.
- Fixed heights or overflow settings that may clip content.
- Custom CSS that overrides the module’s styles.
Make targeted changes and check the result after saving.
Older Starter Layout copies
Updating the plugin does not replace layouts already inserted into pages.
If an older page copy needs a newer layout correction, import the current Starter Layout and insert a fresh copy, or apply the documented correction manually.
Preserve your customizations before replacing an existing section.
Still having problems?
Contact support with the page URL, your Divi and plugin versions, and screenshots showing both the builder and frontend.
Mention which caches you cleared and whether the problem affects logged-out visitors.