Elementor hosting is two different things. One is the builder company’s own managed WordPress product, which bundles hosting with the editor and a domain connection. The other is running the Elementor plugin on any WordPress host, which is what most of the sites built with it do. Both work. The difference is who controls the site, what happens when you want to leave, and whether the host is sized for a page builder that produces heavier pages than a plain theme.
The top result for this term is the vendor’s product page, and the second is a forum thread about how hard it is to migrate away from it. That pair is the whole decision in miniature. This post explains what an Elementor site actually demands of a host, which is the same list whoever the host is, then compares the bundle against bringing your own host on the questions that matter: licence, portability, performance and price.
Table of contents
- Two things called Elementor hosting
- What Elementor actually demands
- Speed: the DOM, the cache and the host
- The lock-in question
- Choosing the plan size
- Migration in, migration out
- How this fits the rest of the stack
- FAQ
Two things called Elementor hosting
The bundled product is managed WordPress with the builder pre-installed, sold by the builder’s own company. It is aimed at agencies and freelancers building many client sites, and the pitch is one login, one support desk and no setup. Reading the vendor’s own FAQ carefully matters here: the hosting plans do not include an editor licence, which is connected or purchased separately, and the plans are tiered by site count, storage and bandwidth.
The other Elementor hosting is any WordPress host with the plugin installed. That is most Elementor sites in existence. The plugin is free, the Pro version is a yearly licence, and the host is whoever you choose. The rest of this post is written for that choice, because the requirements are the same either way and the bundle is one option among several.
What Elementor actually demands
A page builder is a heavier WordPress than a theme with a few widgets. It loads a larger editor in the admin, stores page layouts as serialised data in the database, and renders a deeper DOM on the front end. The host has to give it room.
- PHP memory. The plugin’s own requirements ask for at least 128MB and recommend 256MB. The editor times out and saves fail below that, which is the WordPress memory limit problem with a specific cause.
- A current PHP version. PHP 8.x, with the host able to switch versions from a dashboard rather than a ticket. Old PHP is slow and unpatched.
- Execution time and upload limits. Template imports and large image uploads hit default limits of 30 seconds and 2MB on stingy hosts.
- A database that keeps up. Elementor stores layout JSON in
wp_postmeta, and the revisions table grows fast. MySQL 8 with sane limits and a way to clean revisions. - Server-side caching you control. Page caching helps the front end enormously; it also serves stale layouts if you cannot purge it after an edit.
None of this is exotic. It is the difference between a host built for WordPress and a host that happens to run PHP.
Speed: the DOM, the cache and the host
Elementor sites have a reputation for being slow, and the reputation is half earned. The front-end DOM is larger than a hand-coded theme’s, every section is a nested set of wrappers, and a page with many widgets loads more CSS and JS than it needs. The builder has improved this over the years with lazy-loading and reduced wrappers, but the ceiling is lower than a lean theme.
The other half is hosting. A heavy page on a fast server with page caching and an image CDN scores fine; the same page on an oversold shared host with no cache is the site the forum threads complain about. CPU per PHP request is the metric that matters for uncached hits, the editor and WooCommerce, and it is the one shared hosting never publishes. The WordPress speed optimisation post covers the plugin-side fixes; the host-side fix is a plan with a real vCPU.
The lock-in question
The bundle’s convenience is real: one dashboard, the builder ready, support that knows both halves. The forum complaint is also real: leaving is harder than arriving. The site is standard WordPress, so migration is possible, but the environment, the domain connection and the workflow are the vendor’s, and an agency with thirty client sites inside it has a large project on its hands if the pricing or the product changes.
On your own host the site is portable by default. Elementor templates export and import as JSON, the whole site moves with a migration plugin, and the licence follows the account rather than the server. The All-in-One WP Migration post is the common tool for the move. The cost of portability is that you choose and size the host yourself, which is the next section.
Choosing the plan size
Size by what the site does, not by how many pages it has. A brochure site with Elementor, page caching on and a handful of forms is light once cached and needs a small plan with enough PHP memory for the editor. A WooCommerce store built with Elementor is a different animal: cart and checkout pages are never cached, product pages are heavy, and the admin is busy all day.
On RunxBuild managed WordPress, the Starter plan at $3 a month (0.2 vCPU, 1GB) runs a small Elementor brochure site with caching on, and Mini at $5 (0.5 vCPU, 1GB) is the comfortable size for one with regular editing. An Elementor WooCommerce store belongs on Medium at $22 (1 vCPU, 2GB) or above, with autoscaling to a higher plan during a sale. Two dashboard features matter specifically for a builder site: the file manager, for editing wp-config.php to raise the memory limit or fixing a broken plugin without SFTP, and the database browser, for clearing bloated revisions and postmeta without phpMyAdmin. The managed WordPress post explains what else the managed part covers, and the WordPress file manager docs show the editing workflow.
Migration in, migration out
Moving an Elementor site between hosts is the standard WordPress move with one extra step. Export the database and the wp-content folder, or use a migration plugin to package both. Import on the new host. Then, in Elementor’s tools, regenerate CSS and replace the old URL with the new one, because the builder stores absolute URLs inside its serialised layout data and a plain search-and-replace can corrupt the serialisation. Point the domain, wait for the certificate, and check the editor opens on a heavy page before calling it done. The deploy WordPress in five minutes guide is the setup half of that on a managed host.
How this fits the rest of the stack
Elementor needs PHP memory, a current runtime, a database that can carry its layout data, and a server with enough CPU for the pages caching cannot help. Any WordPress host that provides those runs it well; the bundled product provides them too, at the cost of portability. The RunxBuild hosting calculator shows what a WordPress plan sized for a builder site costs beside the domain and the licence, so the monthly figure for the whole site is one number. Build on a host you can leave, and size the plan for the pages that never cache.
Useful related references:
- Managed WordPress: What the Word Managed Actually Covers, Who It Is For, and What It Should Cost
- WordPress Speed Optimization: The Order That Actually Moves the Number
- WordPress Memory Limit: Raising It Properly and Finding What Ate It
- Managed WordPress on RunxBuild
FAQ
Does Elementor hosting include the Elementor Pro licence?
According to the vendor’s own FAQ, the hosting plans do not include an editor licence. An existing licence can be connected to a hosted site, or a new one purchased separately. Budget for hosting and the licence as two lines whichever host you choose.
Can I use Elementor on any WordPress host?
Yes. Elementor is a WordPress plugin and runs on any host that meets its requirements: PHP 8.x with at least 128MB memory (256MB recommended), MySQL or MariaDB, and reasonable execution and upload limits. Managed WordPress hosts meet these by default; some cheap shared hosts do not.
Why is my Elementor site slow?
Two causes stack. The builder renders a larger DOM and more assets than a lean theme, and many Elementor sites run on shared hosting with little CPU and no page cache. Enable page caching, optimise images, reduce widgets on heavy pages, and move to a host with a dedicated vCPU if the uncached pages are still slow.
How much PHP memory does Elementor need?
The plugin requires 128MB and recommends 256MB. Below that the editor fails to load or save on complex pages. On managed hosting the limit is usually set correctly; on other hosts it is raised with define('WP_MEMORY_LIMIT', '256M'); in wp-config.php, provided the host allows it.
Can I move away from Elementor hosting later?
Yes, because the site is standard WordPress. Export the database and wp-content, import on the new host, then use Elementor’s replace-URL tool and regenerate CSS. Forum reports say the process is more work than arriving was, which is a reason to keep a migration plugin tested and a recent export on hand.