Divi or the WordPress block editor? We built the same site in both.
This is the comparison with the most at stake, because one side is free and already installed. I built the same 13-section homepage in Divi 5 and in Twenty Twenty-Five using the Site Editor, copying one stylesheet and one JavaScript file into both without editing either.
Core WordPress reproduced the design exactly. It also took six separate workarounds to get there, where two other themes in this project needed none, and four of those six were WordPress’s doing rather than the theme’s.
This is one of six builds of the same page. The full comparison with every measurement in one place is in the main write-up.
Divi or the block editor: which one is better?
The block editor reproduced the design. Zero divergence at every width, with page heights exact at all seven and 52 measured elements matching to the pixel. The markup is identical apart from two wrapper elements WordPress forces into every block theme page.
So did Divi. Zero differing pixels at every width tested, from the same prototype files.
Divi scored higher on Lighthouse with a perfect 100 across all four categories, and the same design on the page.
The real difference is structural, and it is the finding of the whole project. A classic theme lets you own the page template and simply not emit the theme’s markup. A block theme gives you no such escape:
A classic theme can avoid the wrappers; a block theme can only neutralise them.
Three things core does that you cannot switch off:
You cannot own the document. The outer wrapper is hard-coded in WordPress with no filter. Its presence was measured as layout-neutral here, but that is a measurement rather than a guarantee, and it only holds because everything that would style it had been stripped.
The usual content filters do not apply. In a block theme, core calls its text and image filters directly on the assembled page rather than through the hook everyone knows. Removing that hook is a silent no-op. You have to reach the narrower filters inside those functions instead.
A child theme cannot switch its parent off. Turning off every setting removes the presets and leaves 9,997 bytes of the parent’s styles intact, because styles are merged rather than gated by settings. The most dangerous of those is body padding, which would inset every full-bleed section on the page. Fixing it one key at a time would have taken about thirty overrides. One core filter emptying the inherited styles before the merge did it instead.
There is one more that will catch anyone building blocks without a compiler. Skip the asset manifest file and your editor script loads with no dependencies, a core function is undefined at run time, and the block fails to register with no error at all.
What do the block editor and Divi cost in 2026?
The block editor costs nothing. It ships with WordPress, needs no third-party theme and no builder, and this build used no plugin of any kind.
Divi is $89 a year for unlimited websites, or $249 once for unlimited websites forever. Divi Pro adds the AI and cloud services and is $277 a year.
All prices checked on the vendors’ own pages on 13 September 2026: Twenty Twenty-Five and Divi.
What core costs you is not money, it is the six workarounds above and the fact that you cannot delete what you do not like. That is a real budget line on a bespoke build, and it is invisible until you are in it.
Who should pick the block editor, and who should pick Divi?
Pick core WordPress if you are porting a fixed design and you have a developer. In that build’s words, if you have a designer who has already decided what the page looks like and a developer who can write the block code, this is an excellent choice and the cheapest one available. There is no vendor. The only dependency is WordPress, which matters if the site has to still work in five years.
Do not pick it if you have no developer, and the build was blunt that this is the easy one to soft-pedal. The editing experience here is good because someone wrote 362 controls by hand. Out of the box core gives you nothing resembling it, and the honest comparison then is not this theme against Divi, it is core blocks against Divi, and core blocks lose.
Do not pick it if you need to change the design in the browser with a client watching. Every change here is a code change.
Pick Divi if you want the shortest route to a working page with a builder your client can use.
The distinction worth holding onto: a block theme has nowhere to put the parts of a site that are not page content. On this build the announcement bar, the skip link, the main element, the footer, the menu scrim and the mobile drawer all had to live inside blocks, because a block theme has nowhere else to put them. Two blocks even open and close the main element between them as a matched pair. That works and it is ingenious, and it is also the sort of thing you should know you are signing up for.
The rest of the comparison
This page covers one pairing. The same design was built in five other stacks, measured the same way:
Along the way the six builds hit the same kinds of problem over and over, and none of them announced themselves. Those are collected in ten silent failures we hit building this.
Zealous Sites will build on whichever theme you want to use, and Divi is what we reach for first. There is more on how we work on the Divi developer page. If you are weighing the two for a project rather than reading the measurements, the Divi versus the block editor decision page is the shorter version with the pricing on it.
Divi vs the block editor questions, answered.
Is Divi better than the WordPress block editor?
For a bespoke design, they reach the same place by different routes. Core reproduced the design exactly and needed six workarounds. Divi reproduced it too and needed none of them, because it lets you own the page outright.
Can you build a custom design with just WordPress, no page builder?
Yes. This build did it with no plugin and no third-party theme, and hit zero pixel divergence. Budget time for neutralising what core and the parent theme emit, rather than for the design itself.
Do you need a page builder at all?
Not for fidelity. Every build in this project reproduced the same design, including the one using nothing but core. What a builder buys you is the editing experience and the speed of getting there.
How much does the block editor cost compared to Divi?
The block editor is free and already installed. Divi is $89 a year or $249 once for unlimited websites, with Divi Pro at $277 a year.
Can you move a site from Divi to the block editor?
Not automatically. Divi stores layouts in its own format, so a move is a rebuild. Your design transfers if the CSS and markup are yours rather than the builder’s.
Is a block theme harder to work with than a classic theme?
For a bespoke design, on this evidence, the honest answer is yes. Two classic themes in this project needed no workarounds at all. The block theme needed six, and four of those were core’s behaviour rather than the theme’s. So budget for the escape hatches, because you’ll be writing them before you write any design code.
Would you rather just hand this to someone?
That is the job. Zealous Sites has been building websites since 2010, which is more than sixteen years of handing finished sites to people who then have to live in them. We will work in whichever theme you want to use, and Divi is what we reach for first.
New sites start at $2,400, and you get a fixed price to approve before anything starts, so there’s no hourly meter running while we work out the scope. You can scope your own project on the pricing page, see what we have built, or tell us what you have in mind.