Black FridayCyber Monday 2026
13Days
14Hrs
18Mins
41Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
Elementor

Elementor Changes Not Showing on Live Website? How to Fix It

Elementor changes not showing on the live site? Find out whether the cause is the wrong page, browser or page cache, a CDN, generated CSS or a device-specific setting.

wpallsolution Updated 11 min read

Elementor changes not showing on the live website usually means one of three things: you edited a different page than the one visitors see, an old copy of the page is being served from a cache, or Elementor’s generated files and device settings are not what you expect. According to Elementor’s help centre, once you click Update and the page is published, your changes should appear on the live site straight away, so a delay is a clue that something sits in between. This guide helps you find which layer it is by changing one thing at a time.

Quick answer

First, make sure you are editing the exact page that visitors see. Then look at the live page in a private window on another device. If you still see the old version, purge caches in order (your caching plugin, your host, your CDN), then use Elementor’s Clear Files & Data tool. If a change shows on desktop but not on mobile, check the tablet and mobile values, because they can override desktop settings.

How this guide was prepared: the steps follow Elementor’s help articles and WordPress documentation listed under Sources, read on October 19, 2026. We did not reproduce the problem on a live Elementor site for this guide, so treat the steps as research-based. Menu names and options differ between Elementor versions, themes, caching plugins and hosts, and no single fix works everywhere.

Before you change anything

  • Back up first. Elementor’s own article on clearing files and data starts with a warning to back up. If you are unsure your backup works, read Is your WordPress backup really safe?
  • Test risky changes on staging, such as switching permalinks, deactivating plugins or changing features. Elementor recommends testing updates on a staging site before the live site.
  • Change one variable at a time and write down what you did, so you know what worked.

Elementor changes not showing: the decision tree

Five questions, asked in order, narrow the cause quickly.

Flowchart of five questions to find why Elementor changes are not showing on a live site: wrong page, browser cache, cache layers, generated Elementor files and device-specific settings
Five questions, asked in order, point to the right step.
  1. Did you edit the exact page or template that visitors see? If not, nothing else matters yet (Step 1).
  2. Does a private window on another device show the change? If yes, the cause is your browser (Step 2).
  3. Is it fixed after purging plugin, host and CDN caches (Step 3)?
  4. Is it fixed after Clear Files & Data or the CSS print method switch (Steps 4 and 6)?
  5. Does the change show on desktop but not on tablet or mobile? That points to device-specific values (Step 5).

Likely causes at a glance

What you seeLikely causeStart with
Page looks the same, but the editor shows your changeWrong page or template, or a cached copySteps 1 to 3
You see it, a colleague on another device does notCache between the server and that deviceSteps 2 and 3
Design looks broken or old after a plugin or theme updateStale Elementor files and dataStep 4
Desktop changed, mobile or tablet did notDevice-specific value or a hide settingStep 5
Front end is blank, but the editor and text are fineA layout feature switched off, or a cache not cleared after a feature changeStep 6
Changes stop after adding custom codeUnclosed HTML or broken CSSStep 8
Changes appear in non-Elementor sections onlyElementor caching of its own elementsStep 9

9 steps to fix Elementor changes not showing, safest first

Step 1: Confirm you edited the right page, template and site

This is the most common and cheapest check. Elementor’s quick checks include:

  • Open the live URL while logged in and choose Edit with Elementor from the front end. That proves you are editing that exact page.
  • Confirm the page is Published, not Draft or Pending, and that you are not looking at a staging copy, a translated version or a cached mobile or AMP variant.
  • If a header, footer or other template is involved, check that you edited the template that is actually assigned to the page.
  • Make sure Elementor, Elementor Pro, WordPress and PHP are all up to date. Our guide to updating WordPress plugins safely covers the routine.

Step 2: Rule out your browser

Open the page in a private window, and ideally on a second device or network. Elementor’s documentation says to clear the browser cache or test in incognito mode. If the private window shows your change, clear your browser’s cache and reload the normal window. If it does not, move on to the cache layers.

Step 3: Purge every cache layer, in order

A page can be cached in several places, and each has its own purge button. Work from the site outwards:

  1. Your caching plugin: purge the page cache and the object cache if you use one.
  2. Your hosting provider’s cache, usually in the hosting control panel. Elementor suggests asking your host if you are not sure how.
  3. Your CDN, for example by purging the cache in its dashboard.

Elementor’s article also suggests temporarily disabling third-party optimisation and cache plugins as a test. If your change appears, switch the plugin back on and re-enable its options one at a time to see which one holds on to old files. Settings that combine, minify or delay CSS and JavaScript are common suspects, but the names differ by plugin.

Step 4: Clear Elementor’s generated files and data

Elementor stores generated CSS and data. Elementor’s help says clearing it can fix mismatches after theme or plugin updates, and that you should back up first.

  1. In WP Admin, open Elementor, then Tools, and click Clear Files & Data. Click Save Changes. (Elementor’s articles place this under Elementor → Editor → Home → Tools or Elementor → Tools, depending on the page and version.)
  2. Open any page in Elementor, make a small change so the Update button becomes active, and click Update.
  3. Purge your other caches again (Step 3) and retest.

You can also use Clear Cache from the Edit with Elementor menu in the black admin toolbar on the front end.

Step 5: Check tablet and mobile values and hide settings

If your change appears on desktop but not on a phone, the phone may have its own value. Elementor’s responsive editing article explains that settings are inherited from larger screens to smaller ones by default, but a value you set for tablet or mobile replaces the inherited one. Widescreen is the exception and does not affect other devices.

  • Switch the device icon in the editor to Tablet and Mobile, select the element and look at the control. A greyed placeholder means the value is inherited, while a normal value means it was set for that device.
  • Check whether the element is hidden on a device. Elementor’s responsive editing article describes hiding elements on mobile devices.
  • Check Display Conditions on the element. Elementor says display conditions do not take effect until you Save or Publish the page.
  • If an element seems to have disappeared in the editor, open the Structure window. Elementor notes that negative margins, z-index or absolute positioning can hide an element behind another.

Step 6: Review Elementor features and the CSS print method

Elementor’s article on changes that do not appear online suggests two checks. Both are best tested on staging.

  • Features. In Elementor’s Settings, open the Features tab. Temporarily switch off performance features such as Inline Font Icons and Improved CSS Loading to rule out an experimental feature. Do not switch off layout features such as Flexbox Container or Grid if your pages use them, because Elementor warns that this can leave the front end blank.
  • CSS print method. In Elementor’s Settings, open Performance and look at CSS Print Method. If it is External File, try Internal File, and the other way round. Retest after clearing caches.

Step 7: Check server and WordPress settings

  • Under Settings → General, make sure the WordPress Address and Site Address match and both use http:// or both use https://. A mismatch after adding SSL is a known trigger in Elementor’s article.
  • Check that there is free disk space and that the uploads folder and its Elementor CSS folder are writable. Elementor mentions read-only permissions as a cause.
  • Re-save your permalinks under Settings → Permalinks without changing anything. Elementor’s article also suggests testing with the Plain structure. On a live site, switching to Plain changes every URL, so do that only on a staging copy and put the original structure back afterwards.
  • If you have custom server configuration or custom code in .htaccess, check it, or ask your host to.

Step 8: Look for broken custom code or CSS

Elementor lists unclosed HTML tags and broken CSS as a reason changes do not appear. Check custom CSS in Global Settings and the Theme, and inline styles in Heading, Text Editor or HTML widgets. In the Structure window, highlighted elements indicate custom CSS, motion effects or absolute positioning. If you use HTML widgets with scripts, a security plugin can strip inline scripts, and Elementor notes the unfiltered_html capability matters here (administrators have it by default).

Step 9: Plugin conflicts, Element Caching and corrupted elements

  • Plugin conflict. On staging, deactivate every plugin except Elementor and Elementor Pro and test. Then reactivate them one by one. How to find the plugin that broke your site explains the method.
  • Element Caching. Elementor’s Element Caching is an experimental feature that stores rendered widget HTML in the database. Elementor says it should only be active on static elements, and that it caches only Elementor elements. If you see changes in non-Elementor sections but not in Elementor widgets, try disabling it.
  • Front end differs from the editor. Elementor says an element’s stored styling can become corrupted. Find an element that renders correctly, copy its style, and paste the style onto the broken one.
  • Popups. Check the popup’s conditions, publish it, clear caches and regenerate the files as in Step 4.

If the editor itself will not load, see Elementor stuck on loading screen.

Version and hosting differences

  • Some hosts add their own page cache and CDN. A purge in the WordPress dashboard does not always clear it.
  • Element Caching, features and menu locations change with Elementor versions. Elementor’s articles describe the current editor and may differ from an older install.
  • Elementor Hosting, shared hosting and managed WordPress hosting expose different cache controls.

How to verify the fix

  • The live page shows your change in a private window, on a second device and on mobile data.
  • Tablet and mobile layouts match what the editor shows for those devices.
  • Anything you switched off for testing (optimisation options, features, plugins) is back on, one item at a time, with a check after each.
  • You noted what the cause was.

How to prevent it from happening again

  • Purge page cache and CDN as part of every design update, and add that to your checklist.
  • Keep Elementor, Elementor Pro, WordPress and PHP current, and update on staging first.
  • Keep custom CSS and code tidy and test it after changes.
  • Keep third-party add-ons to a minimum. How to keep Elementor sites fast explains the trade-offs.

Frequently asked questions

Why can I see my change but visitors cannot?

Often a cache is serving an older copy to visitors. Test in a private window and on another device, then purge your plugin, host and CDN caches (Step 3).

Do I need to clear Elementor’s files every time I edit?

No. Elementor describes it as a troubleshooting step for mismatches, for example after theme or plugin updates. Back up before you use it.

Why did only my mobile layout stay the same?

The mobile value may have been set separately, or the element may be hidden on that device. Check the device-specific controls (Step 5).

Is Element Caching the problem?

It can be, if it is active on an element that shows changing content. It is experimental, so treat it as a suspect only after the simpler steps.

Related guide: Elementor Mobile View Broken? Fix Responsive Layout Problems

Related guide: WordPress Caching Explained: Page Cache, Object Cache, Browser Cache and CDN

What to do next

Work through the steps in order and stop at the first one that fixes it. If Elementor changes are still not showing, note the page URL, the Elementor and WordPress versions and which steps you tried, then ask your host or Elementor support. If you would like a person to look, wpallsolution offers independent plugin support, and our Elementor development page explains how we build and tidy Elementor sites. We cannot promise a fix without seeing your site.

Sources and official documentation

Last reviewed: October 19, 2026. Elementor is a trademark of its owner. wpallsolution is not affiliated with or endorsed by Elementor.

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us