WordPress page builder — what a visual editor costs and when it stops paying

A WordPress site starts with a decision that looks aesthetic and is financial: what you are going to assemble it with. WordPress itself is free, and that is the only line in this bill everyone agrees on.

This is for you if you already run WordPress, or soon will, and want to know what the layer you operate it with costs over a year. It is not about which platform to choose; that is a separate decision. Nor is it about builders like Wix or Squarespace, where you rent the site — different rules, their own article.

Every price below was read by hand from the vendor's own pricing page on 25–26 August and 9 September 2026, for our report on the cost of the tools around a company website. We quote each in the currency the vendor charges and add the złoty amount at the NBP rate of the same day (tables 165/A/NBP/2026 and 175/A/NBP/2026) — the source price ages more slowly than the conversion.

Three layers that go by one name

A conversation about "a WordPress site" mixes three things that cost separately and break separately.

The third layer is what people mean by a page builder: Gutenberg, Elementor, Divi. It is not compulsory — and that is where we start, because almost nobody asks.

If at this stage you are wondering whether you need WordPress at all rather than a system built around content structure, that is a different decision with its own article on no-code systems. Here we assume WordPress is already chosen.

Start with Gutenberg — the free WordPress page builder you have already paid for

Gutenberg is the editor built into WordPress. In the 2018 version you remember it assembled post content only, and it deserved its bad press. Today it is called the Site Editor and it does the job people usually buy a builder for.

According to WordPress's documentation — updated in August 2026 for version 7.1 — the Site Editor lets you design "your entire site, including the header, footer and everything in between": global styles (colours, typography, site-wide layout), templates and template parts, navigation and page management. You can export the theme with its templates and styles as a zip.

There is one catch most articles leave out, and it is decisive: the Site Editor works only on a block theme. If your site runs a classic theme — and most existing installations do — the Site Editor simply is not in your admin panel. Switching to a block theme is not a toggle; it is a rebuild of the design.

That splits readers in two:

• Starting from scratch — begin with a block theme and the Site Editor. No subscription, no extra plugin layer, and you change page layouts yourself. Buy a builder later if it turns out you need one, and you will know what for.
• Running a live site on a classic theme — for you the Gutenberg question is a question about a rebuild, not about an editor. Then a builder, or a straight decision about scope, makes more sense.

That answer is missing from most articles about page builders for a simple reason: there is nothing to sell on it.

What Elementor actually costs

Elementor is the page builder you are most likely to be quoted, and its price list has one virtue worth naming: it prints the renewal price next to the promotional one. Wix does not. The full ladder, read 26 August 2026:

So the plan you buy at €180 (PLN 774) costs €228 (PLN 981) from the second year — 27% more. Same mechanism as in the builder market, only stated honestly and up front.

Elementor does one more thing worth using: it prints what the add-ons bundled into higher plans are worth on their own — image optimisation €60/yr (PLN 258), accessibility €120 (PLN 516), mail deliverability €60 (PLN 258). A ready-made list of what you will pay for separately if you stay on a lower plan. Move it into your own arithmetic before comparing plans.

A detail that says something about the whole category: the metadata of Elementor's pricing page reads "from 49 USD/year" while the rendered table starts at €5/month. Two different numbers on one page, depending on whether a human or a robot is reading it.

Divi sells the same thing differently — and the difference has a number

The second builder that genuinely matters is Divi — not because it does something Elementor does not, but because it has a different payment model, and that is the only difference visible in the bill after three years.

Price list checked at the vendor on 9 September 2026:

Set that over three years, counting the editor licence only — hosting, domain and plugins are the same whichever you pick:

Two caveats without which this table would be dishonest. These are not functionally identical products — Elementor One bundles things Divi puts in Pro, and the reverse. We compare the cost of the editor licence, not the scope. And the złoty figures are conversions at the NBP rates of the capture days, so a Polish buyer also carries an exchange-rate and card-fee margin on the euro and dollar rows that appears on no price list.

In złoty the spread is the whole point: PLN 0 against PLN 2,736 over three years, for exactly the same site — the line most implementation quotes omit.

The practical conclusion is not "buy Divi". It is: before you pick a builder, check whether the vendor sells a one-off licence, and count three years rather than the first one. No implementation quote asks that question, because the licence is usually transferred to you when the project ends — renewal included.

Hosting and theme — two lines that get counted wrong

Two items outside the editor wreck the bill for a WordPress site, both for the same reason: the price you see is not the price you pay.

Hosting is priced on the first year. Renewal prices read on 26 August 2026: LH.pl 5 GB runs at PLN 50 in the first year and PLN 199 on renewal. home.pl Hosting Start is PLN 39.90 net, then PLN 678.99 a year — a seventeenfold step. OVH Starter is PLN 6.79 net a month on promotion and PLN 11.09 on renewal. A .pl domain at OVH costs PLN 16.69 to register and PLN 58.99 net to renew. Three of these providers print the renewal price next to the promotional one, which deserves credit — it is not standard in this trade. We break this down further in the article on what a domain and hosting cost.

The theme often gets bought twice. A company buys a paid premium theme for its looks, then adds a builder that replaces those looks anyway — two layers doing the same job, and the site loads the scripts of both. The rule that sorts this out: if you assemble page layouts with a builder, the theme should be light and neutral. If the theme is meant to do the design, the builder is redundant.

Plugins — the line that is not in the quote

The bill for a WordPress site goes wrong not on the builder licence but one floor below. Plugins look free until you need a specific function.

We do not have to estimate this, because the vendor prices it. On its own pricing page WooCommerce states: the core is free, no subscription, no cut of turnover — and extensions cost $29–299 per year each (PLN 107–1,102). Hosting, on WooCommerce's own estimate, runs $25–350 a month (PLN 92–1,290).

Three paid extensions — and three is not many if you need payments, shipping and invoicing — is $87 to $897 a year, or PLN 321 to 3,306. That single line is wider than all the others put together.

The conclusion to take into a conversation with a supplier: ask for a list of plugins with a price and a renewal date against each one, before you sign. Not "around PLN 200 a month for maintenance" — a list. If the supplier does not have one, it has not been counted, and you are the one who pays.

Three thresholds where a WordPress page builder costs more than it saves

You buy a builder so you do not have to wait for a developer. It stops paying at three moments — each of which you can measure instead of guessing at.

Threshold one: the site stops fitting in its performance budget. Every builder widget adds its own scripts, styles and layers of div. The effect is measurable: Lighthouse warns above roughly 800 nodes in `body` and fails the audit above roughly 1,400 (Chrome documentation). The same documentation gives the reasons: invisible nodes still cost transfer and load time, the browser has to keep recalculating their position and styles, and scripts holding references to many nodes can exhaust a phone's memory. How to check: run the page speed test on your own address and read the DOM size section.

Threshold two: updating becomes a risk rather than a routine. Your layout is produced by a plugin with its own author and release cycle — and so is the theme, and so is every extension. The more independent authors take part in how your homepage looks, the higher the chance that one update moves something nobody touched. How to check: count how many separate plugins would have to work correctly for the homepage to look the same tomorrow. If you do not know the number, that is the first answer. It happens often enough to have its own article on updates.

Threshold three: clicking takes longer than writing. This is the point where the builder stops doing what you bought it for. You recognise it by the sentence "it's easier to copy an existing page and swap the text" — which means the tool has nothing left to assemble a new one with. How to check: time the next new page. Do not estimate it, time it.

The first threshold has a solution inside the tool — fewer widgets, a lighter theme. The second and third usually do not.

Whose licence is it when the build ends

This question does not exist in the world of closed builders, where you open the account in your own name on day one. On your own WordPress the licences are usually bought by the supplier, mid-project, on the supplier's card. And very often it stays that way.

The consequence shows up at the first renewal or at the parting. The site keeps working — a plugin does not suddenly stop assembling a layout — but it stops receiving updates, because the licence key belongs to someone else. Nothing happens for months, and then a security fix arrives that cannot be installed.

Divi makes this particularly easy to miss, and it follows directly from its price list: the annual plan covers an unlimited number of sites. An agency can therefore run your site on its single licence, entirely legally and with no signal on your side. While the relationship lasts, that suits both parties. The day it ends, your site is left without a key.

Four things to settle in writing, before the build ends — all free if you ask in time, expensive if you ask later:

• Whose name the domain is registered in. The most important of the four and the only one that can be impossible to recover without the other party's consent.
• Whose name the hosting account is in, and who receives the renewal email.
• Whose account the builder and theme licences were bought on, and what happens to them when the contract ends.
• Who has administrator access — and whether you do too, rather than only an editor account.

If the answer to any of these is "the supplier", that is not in itself a problem — as long as it is written down and you know what changing it costs.

Leaving — why the exit here is different from a builder's

This is where your own WordPress beats a closed builder, and the reason is concrete rather than ideological.

The content and the database are yours. Posts, pages, media, users and addresses sit in a database you have access to. There is nothing here like Wix, whose own documentation states outright that the site must run on its servers. The Site Editor additionally lets you export the theme with its templates and styles.

The layout does not travel. A page assembled in Elementor is stored in Elementor's own markup. Switch the plugin off and the content stays, the layout does not — a real cost, but one measured in design work rather than in retyping content. That is exactly the half of the job you do not save when leaving a closed builder.

What the operation costs is broken down in the article on the real cost of a cheap website. If instead you are wondering whether to stay on WordPress at all, that is settled by the comparison with a headless approach or a short quiz.