Elementor Not Working: Fix the Editor Not Loading, Not Saving, and Errors (2026)

Key facts at a glance

Elementor troubleshooting in 2026

Last updated July 1, 2026

Name the fault first: Loading, saving, and front-end mismatch are three different faults with three different fixes. The single most common wasted hour is treating a blocked save as a loading problem.
Two built-in tools: Safe Mode loads the editor with only Elementor and a default theme to expose a conflict. Switch Editor Loader Method splits the editor data so a weak server can read it. Both live in Elementor settings.
Why saving fails: The save posts to admin-ajax.php. A security plugin or a server mod_security rule returning a 403 on that request is the usual dead Update button. Whitelist the endpoint.
Why the front end lags behind: Elementor writes each page style to generated CSS files. After an update they go stale. Regenerate CSS and Data, renamed Clear Cache in 3.28, then purge every other cache layer.
The memory Elementor needs: A WordPress memory limit of 256MB minimum, 512MB recommended, 768MB best, and at least 512MB alongside WooCommerce. Under-resourcing is a frequent hidden cause of both loading and saving failures.
Editor broken, not the site: If the public site works and only the builder misbehaves, this is the right place. If the whole site is blank for visitors, that is a critical error to diagnose through the debug log instead.

Source: Elementor’s own help documentation on the editor not loading, Safe Mode, the advanced settings, the Update button, changes not appearing online, the preview and content-area errors, form server errors, and the system requirements, plus our hands-on page-builder repairs. Get a quote in 60 seconds →

Why Elementor breaks

Elementor is not a simple settings screen. When you open a page in the editor, your browser loads a live preview of that page inside a frame, and around it Elementor loads its own large bundle of JavaScript and styles plus a big block of JSON that describes every element on the page. To save, it sends that JSON back to the server. To render the design on the front end, it writes generated CSS files. That is a lot of moving parts, and a broken Elementor site is almost always one of those parts failing, rather than anything wrong with your design.

Because the editor leans this heavily on both the server and the browser, it is sensitive to things a normal WordPress page never notices. A server low on memory or slow to read a long block of JSON stalls the load. A security plugin or firewall that inspects requests can block the save. An optimization layer that minifies or defers scripts, or a CDN feature like Cloudflare Rocket Loader, can mangle the exact files the editor needs. Another plugin or your theme can collide with Elementor in the browser. And the theme itself has to give Elementor a canvas to render into, which is where the preview and content-area errors come from.

The good news is that the failure modes are finite, and almost all of them fall into three families. Getting clear on which family you are in is the fastest route to the fix, and it is what the rest of this page is organized around. Other page builders such as Divi and WPBakery fail in the same three families for the same underlying reasons, but the tools and settings here are Elementor specific.

The three faults

Nearly every Elementor problem is one of these three. They look alike from the outside but need opposite fixes, so name yours before you change anything.

The editor will not LOAD

A delivery problem, getting the editor to you. The loading or grey screen, err_content_decoding_failed, err_empty_response, the empty widget panel, Preview Could Not Be Loaded. Caused by a low-resource server, a plugin or theme conflict, an optimization or security layer, or a theme that gives Elementor no canvas. Start with the two built-in tools.

The editor will not SAVE

A submission problem, getting your work back to the server. The dead Update button, an unable to save message, a 403 in the console. The save posts to admin-ajax.php and a security plugin or server mod_security rule is blocking it, or a missing capability, bloated revisions, or a low memory limit is breaking it. Unblock the endpoint.

Changes will not SHOW on the front end

A caching problem, not a lost save. The save worked, but Elementor’s generated CSS files went stale after an update, and a caching plugin, host cache, or CDN is serving the old design. Regenerate CSS and Data, then purge every cache layer, and the front end matches the editor again.

Error and symptom reference

Find the exact message or symptom you see. Each row says what it means and where the fix is.

Error or symptom	What it means and how to fix it
Editor stuck on an endless spinner or a grey panel	The server cannot deliver the editor data, or a plugin or theme conflicts. Enable Switch Editor Loader Method, then test Safe Mode. The two built-in tools →
Console shows err_content_decoding_failed or err_empty_response	A low-resource server cannot read the long block of editor JSON. Switch Editor Loader Method splits it into readable pieces. Enable the loader method →
"Preview Could Not Be Loaded"	Usually no active or updated theme, a renamed or altered index.php, or a missing or corrupted .htaccess. Activate a working theme and restore the default .htaccess.
"Sorry, the content area was not found in your page"	The theme page template does not call the WordPress the_content function that Elementor renders into. Switch to an Elementor-compatible theme, or add the_content to a custom template. For a new page, set Permalinks to Plain and save.
The Update button does nothing, or "unable to save"	The save posts to admin-ajax.php and is being blocked, usually a 403 from a security plugin or a server mod_security rule. Whitelist that endpoint. How to unblock the save →
Changes saved but the front end still shows the old design	Stale generated CSS plus caching. Run Regenerate CSS and Data under Elementor then Tools, renamed Clear Cache in 3.28, then purge your caching plugin, host cache, and CDN.
Pro widgets missing, or they will not drag onto the page	Elementor and Elementor Pro versions are mismatched, or the Pro license has disconnected. Update the free plugin first, then Pro, and reconnect the license.
Internal server error or a 500 when you open the editor	A PHP fatal, a low memory limit, a plugin conflict, or too many stored revisions. Read the server PHP error log, raise memory, and test Safe Mode. Fix a 500 error →
Fatal error right after updating Elementor or Elementor Pro	A version incompatibility, or a beta build. Update WordPress, Elementor, and Elementor Pro to matching stable versions and revert any beta. Recover from a critical error →
Elementor forms save but the email never arrives	The default unauthenticated wp_mail is filtered by inbox providers. Send through authenticated SMTP, Site Mailer or WP Mail SMTP on port 587, and check the Submissions log. Fix email delivery →
The editor loads but is slow, or pages feel laggy to click	That is a performance problem, not a broken editor. Heavy builder JavaScript ties up the main thread and fails INP, the responsiveness Core Web Vital. Fix laggy Elementor pages →
The widget panel is empty or will not load	A conflict or a failed asset load. Test Safe Mode, enable the loader method, and clear any optimization plugin mangling the editor scripts. The two built-in tools →

What we fix in Elementor

Twelve problem areas cover almost every Elementor emergency. We diagnose which one is actually yours rather than guessing.

Stuck Loading or Grey Screen

The editor spins forever or shows a grey panel. A server that cannot read the long editor JSON, a plugin or theme conflict, an optimization layer, or a framing header. Safe Mode and the loader method resolve most of it.

Preview Could Not Be Loaded

No active or updated theme, an altered index.php, or a missing .htaccess. We restore a working theme and the default rewrite rules so the preview renders.

Content Area Was Not Found

The theme template does not call the_content, so Elementor has no canvas to render into. We switch to a compatible theme or add the_content to the custom template.

Update Button Not Working

The save to admin-ajax.php is blocked by a security plugin or a server mod_security rule returning a 403. We whitelist the endpoint and restore the unfiltered_html capability.

Changes Not Showing on the Front End

The save worked but stale generated CSS and caching hide it. We regenerate Elementor CSS and clear every cache layer so the front end matches the editor.

Missing or Undraggable Pro Widgets

Elementor and Elementor Pro versions are mismatched or the license disconnected. We align the versions, update in the right order, and reconnect the license.

Internal Server Error While Editing

A 500 when opening the editor, from a PHP fatal, low memory, or a plugin conflict. We read the server error log, right-size memory, and isolate the cause.

Fatal Error After an Update

An Elementor or Pro update collides with an incompatible version or a beta build. We recover the site and move it to matching stable releases.

Forms Not Sending Email

Elementor Pro form submissions save but the notification never arrives. We set up authenticated SMTP so the mail lands, and verify the field IDs and submission log.

Slow Editor and Laggy Pages

The editor is sluggish or the published page feels laggy to click. Heavy builder JavaScript on the main thread. We reduce and defer it, measured against INP.

Widget Panel Not Loading

The left panel is empty while the canvas loads. A conflict or a failed asset load. We test in Safe Mode and clear the optimization layer mangling the scripts.

Theme Builder and Global Kit

A header, footer, or global kit setting not applying sitewide. We check the theme location support, display conditions, and the active kit so the design takes effect.

The two built-in tools

Before you touch server settings or start deactivating plugins on a live site, Elementor ships two switches that resolve or diagnose most loading and saving failures on their own. Try these first, because they are safe, reversible, and take under a minute each.

Safe Mode, to expose a conflict

Safe Mode loads the editor with only Elementor and Elementor Pro active and a default theme, ignoring every other plugin and your theme, and it changes nothing visitors see. Enable it from the stuck loading screen when Elementor offers it, or from Elementor then Tools. If the editor loads normally in Safe Mode, a plugin or your theme is the cause, and you reactivate them one at a time until the editor breaks again, which names the culprit.

Switch Editor Loader Method, for a weak server

Under Elementor then Settings then Advanced, enable Switch Editor Loader Method and reload. It changes how the editor requests its data, splitting the long JSON into pieces a low-resource server can read, which resolves stuck grey screens and the err_content_decoding_failed and err_empty_response errors, and sometimes a white screen. Elementor states it does not hurt performance and can improve it, so it is safe to leave enabled.

When the save is blocked

If the editor loads but the Update button is dead and the console shows a 403 on admin-ajax.php, the block is a security layer, not Elementor. Put your security plugin into learning mode or whitelist the endpoint, and if it is server-side, ask your host to whitelist admin-ajax.php in mod_security. Also confirm your user role keeps the unfiltered_html capability, which Elementor needs to save markup, and raise the memory limit if the console shows a memory error.

When the front end will not update

Go to Elementor then Tools and click Regenerate CSS and Data, labelled Clear Cache in Elementor 3.28 and later, to rebuild the generated CSS. Then purge your caching plugin, host page cache, and CDN such as Cloudflare, and hard refresh the browser. The save was never lost, the old CSS was just being served.

Why specialist Elementor work helps

Most Elementor emergencies are a chain, not a single cause. A new security plugin blocks the save and sets a framing header that also breaks the load, on a server whose memory limit was already too low for a heavy page. Fix one link and the editor is still broken, which is why do-it-yourself Elementor troubleshooting so often turns into a lost afternoon of toggling plugins with no clear signal. The skill is reading the browser console and the server log, separating the load fault from the save fault from the cache fault, and fixing the actual chain in order.

We do this all day, so the process is the same every time. Confirm the public site still works, which tells us this is an editor problem and not a whole-site critical error. Open the console while the editor loads and while it saves, which names whether the fault is delivery, submission, or caching. Apply the built-in tools, unblock the endpoint, right-size memory, or regenerate the CSS, then test that the page still renders and saves. We charge a flat rate because we are fast at finding the one or two changes that matter, rather than billing hours against guesswork.

The 2-hour guarantee and the money-back promise are the enforcement. We do not get paid if we cannot get your editor loading and saving for the agreed scope. If the real limit is your hosting plan or a plugin that has to be replaced, we tell you that up front rather than charging for a fix that cannot hold.

Related fixes and hubs

Elementor problems often sit next to a broader WordPress issue. These are the pages for the ones that reach past the builder itself.

Elementor pages slow or laggy to click

Heavy page-builder JavaScript ties up the main thread and fails INP, the responsiveness Core Web Vital. A field metric you cannot read in the lab.

Fix high INP →The block editor will not save either

If Gutenberg also fails with Updating failed, the REST API is blocked or contaminated, a security plugin, broken permalinks, or a loopback timeout.

Fix publishing failed →The whole site is down, not just the editor

A blank page or a critical error for every visitor is a PHP fatal error, diagnosed through the debug log, not an Elementor-only problem.

Recover a critical error →500 internal server error while editing

A PHP fatal past the error handler, an .htaccess problem, or a hosting resource limit. The server error log shows the real cause.

Fix a 500 error →Elementor form emails not arriving

Submissions save but the notification never lands, because the default wp_mail is unauthenticated. We set up authenticated SMTP so it delivers.

Fix email delivery →Everything WordPress repair

The parent hub for plugin, theme, update, and critical-error repairs across WordPress, with Elementor as one part of it.

Visit the WordPress hub →

View the full WordPress and platform error library →

Pricing and process

Send your site and the symptom

Use the quote form with your URL and what Elementor is doing, will not load, will not save, or the exact error message. A senior engineer replies with a flat-rate quote, usually within 30 minutes during business hours.

Approve, we start immediately

No scheduling step, no kickoff call. Approve the quote and we begin. You provide WordPress and hosting access through a secure link. The clock starts on the 2-hour guarantee.

Editing restored and tested

We fix the real fault, confirm the editor loads and saves and the page still renders, and tell you what caused it. Money back if we cannot get Elementor working for the agreed scope.

Elementor troubleshooting FAQ

Why is my Elementor editor stuck on the loading screen or a grey screen?

The editor loads a live preview inside a frame and needs the server to hand it a large block of JSON plus every script and style, and a hang means something is interrupting that handoff. The common causes are a plugin or theme conflict, a server that struggles to read the long JSON on low resources, an optimization layer like Cloudflare Rocket Loader delaying the scripts, a theme preloader that never clears, a security header set to block framing, or a browser add-on blocking scripts. The two fastest tests are built into Elementor. Enable Switch Editor Loader Method under Elementor then Settings then Advanced, which splits the JSON so a weaker server can read it, and enable Safe Mode, which loads the editor with only Elementor and a default theme so you can see whether a conflict is to blame.

What is Elementor Safe Mode and how do I use it?

Safe Mode is a built-in switch that loads the Elementor editor with only Elementor and Elementor Pro active and a default theme, temporarily ignoring every other plugin and your active theme, without changing anything visitors see on the live site. If the editor loads normally in Safe Mode, a third-party plugin or your theme is the cause, and you then reactivate your plugins one at a time until the culprit shows itself. You can turn Safe Mode on from the stuck loading screen when Elementor offers it, or from Elementor then Tools. It is safer than blindly deactivating plugins on a live site because it only affects your own editing session.

What is the Switch Editor Loader Method and when should I enable it?

It is a setting under Elementor then Settings then Advanced that changes how the editor requests its data. Servers with limited resources sometimes cannot read the single long block of JSON that Elementor sends, which shows up as a stuck grey screen or console errors like err_content_decoding_failed and err_empty_response. When you enable this option, Elementor splits that data into smaller pieces the server can handle, and it can also resolve some white-screen cases. Elementor states the switch does not hurt performance and can improve it, so it is safe to leave enabled. It is one of the first things to try when the editor will not load and Safe Mode has ruled out a plugin conflict.

Elementor will not save. The Update button does nothing. Why?

Saving in Elementor sends the page data to the server through admin-ajax.php, and when that request is blocked or rejected the Update button appears to do nothing or you see an unable to save message. The usual cause is a security layer returning a 403 on that request, either a security plugin such as Wordfence or a server firewall rule like mod_security. The fix is to put the security plugin into learning mode or whitelist admin-ajax.php, and if it is server-side, ask your host to whitelist that endpoint. Other causes are a user role missing the unfiltered_html capability, a database bloated with too many stored post revisions exhausting memory during the save, and a WordPress memory limit below what Elementor needs. Check the browser console while you click Update, because a 403 or a memory error there names the real problem.

I saved in Elementor but the changes do not show on the front end. What is wrong?

This is almost always caching, not a lost save. Elementor writes the styling for each page to generated CSS files stored under the uploads folder, and after an update to Elementor, a theme, or an add-on those files can go stale, so the front end keeps serving the old design even though your edits saved correctly. Go to Elementor then Tools and click Regenerate CSS and Data, which is labelled Clear Cache in Elementor 3.28 and later, to rebuild those files. If it still looks old, the layer holding the old version is a caching plugin, your host page cache, or a CDN such as Cloudflare, so purge each of those and do a hard browser refresh. Once the generated CSS is rebuilt and every cache layer is cleared, the front end matches the editor.

Why does Elementor say "Preview Could Not Be Loaded" or "the content area was not found"?

These two errors are about the page the editor tries to build inside. Preview Could Not Be Loaded usually means there is no active or updated theme, the index.php file was renamed or altered, or the .htaccess file is missing or corrupted, so activate a working theme and restore the default .htaccess. The content area was not found means the page template your theme uses does not call the WordPress the_content function, which Elementor needs as the canvas to render into. The fix is to switch to an Elementor-compatible theme, or, if you or your developer built a custom template, add the_content to it. For a brand new page you can often clear it by setting Permalinks to Plain, saving, and reopening the editor.

My Elementor Pro widgets disappeared or I cannot drag them onto the page. How do I fix that?

When the free Elementor widgets work but the Pro widgets are missing or will not drag, it is usually a version mismatch between the two plugins or a license that has disconnected. Elementor and Elementor Pro are separate plugins that must stay compatible, and running a newer core with an older Pro, or the reverse, breaks the Pro widgets. Update both to their latest versions, and always update the free Elementor plugin first, then Elementor Pro, because Pro depends on core. If you see a message that Elementor Pro requires a newer version of Elementor, update the free plugin from Dashboard then Updates. If the widgets are missing because the license shows inactive or disconnected, reconnect it from Elementor then License.

My Elementor forms are not sending email. How do I fix it?

Elementor forms send through the WordPress mail function, and the default wp_mail is unauthenticated, so providers like Gmail and Yahoo filter or drop it, which is why submissions save but the email never arrives. The reliable fix is to send through authenticated SMTP: install an SMTP plugin such as WP Mail SMTP or use Elementor Site Mailer, connect it to a real mail provider, and use port 587 first with 465 as a fallback. Also confirm each form field has an ID set in its Advanced tab, and check the Form Submissions log in the editor to confirm the submission is being recorded, which separates a form problem from a delivery problem. Once the mail is authenticated, the notifications land in the inbox.

What server resources does Elementor actually need?

Elementor lists a WordPress memory limit of 256MB as the baseline for Elementor and Elementor Pro alone, 512MB recommended, and 768MB for best performance, and if you also run a heavy plugin like WooCommerce it suggests at least 512MB so the editor does not run out of memory mid-load. It also requires PHP 7.4 or newer, with a current PHP 8 release recommended, WordPress 6.5 or newer, and MySQL 5.6 or newer or MariaDB 10.5 or newer. A page that will not load or save on a technically working site is very often just under-resourced, so raising the memory limit and giving PHP enough execution time to build a complex page resolves a large share of these cases.

Is an Elementor problem the same as the WordPress white screen of death?

No, and telling them apart saves time. An Elementor problem is usually confined to the editor: the front end of your site still works for visitors, and only the Elementor edit screen hangs, fails to save, or shows a grey panel. The white screen of death is a whole-site failure, a blank page or a There has been a critical error message on the front end, caused by a PHP fatal error rather than anything specific to Elementor. If your live pages are down for everyone, that is the critical error to diagnose through the debug log, which we cover on the white screen page. If your live pages are fine and only the builder misbehaves, you are in the right place. They overlap only when a fatal happens to fire inside Elementor code, but the starting question is always whether the public site works.

Sources and further reading

Every technical claim on this page traces back to Elementor’s own help documentation.