Elementor Not Loading or Not Saving

Page Builders & Themes

The editor spins forever, and your changes have nowhere to go.

datacram.com/fix/elementor-not-loading
Likely causes, ranked
Elementor Not Loading or Not Saving
PHP memory limit too lowmost likely
A JavaScript conflictcommon
The REST API is blockedcommon
A theme incompatibilitypossible
Fix steps in this guide5
the causes explained below, most likely first
What you’re seeing

The Elementor editor sticks on the loading screen, shows “Sorry, the content area was not found”, or lets you edit and then fails to save. The published page usually still works.

What it actually means

The Elementor editor is a heavy application running inside your WordPress admin. It loads its own scripts, fetches your page over the REST API, renders a preview in an iframe, and saves back through the API again. Any one of those links can break independently.

That the live page still works is the useful clue. Your content is safe in the database — what has failed is the editing environment, which is far less alarming and usually fixed by resources or a conflict rather than by anything structural.

What usually causes it

Most likely first.

  1. 1

    PHP memory limit too low

    Elementor needs considerably more than a basic WordPress page. Anything under 256M struggles on real layouts.

  2. 2

    A JavaScript conflict

    Another plugin loading an incompatible script into the editor. The console names it directly.

  3. 3

    The REST API is blocked

    A security plugin restricting the API stops the editor loading or saving, exactly as it does with the block editor.

  4. 4

    A theme incompatibility

    Missing the content area Elementor expects, which produces the “content area was not found” message specifically.

  5. 5

    Server limits on large pages

    max_input_vars set too low truncates the data sent when saving a complex page, so the save silently fails.

How to fix it

Work through these in order. Take a backup before you change anything.

  1. Step 1Raise the limits first

    PHP memory to 256M and max_input_vars to at least 3000. Between them these resolve most Elementor loading and saving problems.

  2. Step 2Read the browser console

    Open developer tools while the editor loads. A named script error points straight at the plugin responsible.

  3. Step 3Use Elementor's Safe Mode

    It loads the editor with plugins and theme disabled. If it works in Safe Mode, you have a conflict rather than a fault.

  4. Step 4Check the REST API

    Visit yoursite.com/wp-json/ and confirm it returns JSON. If a security plugin is blocking it, allowlist rather than disable.

  5. Step 5Regenerate CSS and clear caches

    Elementor, Tools, Regenerate Files, then clear every cache including the CDN. Stale generated CSS causes a range of odd behavior.

When to stop and call someone

Call someone if Safe Mode also fails, which points at the server rather than a plugin, or if saving fails on one large page while others work — that usually means an input limit that needs raising at the host and is easy to get wrong.

Frequently asked

Most often a PHP memory limit that is too low, or a JavaScript conflict from another plugin. Raising memory to 256M resolves a large share of cases, and the browser console names any conflicting script directly.

A built-in mode that loads the editor with all other plugins and your theme disabled. If the editor works in Safe Mode, the problem is a conflict with something else on the site rather than Elementor itself, which narrows the search immediately.

Usually because saving sends far more data than loading. A max_input_vars limit set too low truncates that data and the save fails silently. Raising it to at least 3000, and checking the REST API is reachable, normally fixes it.

No. Your content is stored in the database and the published page continues to serve normally. What has failed is the editing environment, which is recoverable without touching the content itself.

It adds more CSS and JavaScript than a hand-built theme, and heavy layouts compound that. It is workable with disciplined use, caching, and regenerated CSS, but a page built from dozens of nested sections will never be as fast as purpose-built markup.

Free · AI-powered · Emailed to you

See exactly what’s holding your website back.

Get a free audit of your site — speed, SEO, mobile, and security — with the fixes that matter most, delivered as a PDF to your inbox.

Get my free audit
CallGet a quote