
WordPress's built-in block editor is free and already handles most page layout. A page-builder plugin like Elementor, Divi, or Beaver Builder adds a more visual, drag-and-drop canvas plus extra design widgets — usually for a paid subscription. Whether you need the extra plugin depends on how much visual control you want and whether your current theme already supports full-site editing. This guide checks WordPress.org's own documentation against each builder's own pricing and support pages, checked September 2026.
The block editor — also called Gutenberg — has been WordPress's default editor since WordPress 5.0 in December 2018. WordPress's own documentation describes it as "the new way of publishing content in WordPress," and says it "offers an array of blocks that can be used to create media-rich pages and posts" (WordPress.org, "WordPress Block Editor", checked September 2026). You build a page or post out of individual blocks — paragraphs, images, headings, galleries, and more — arranged top to bottom, with more block types installable through plugins.
It's part of WordPress core, so it costs nothing beyond your existing WordPress install, and it's available on every WordPress site regardless of theme.
The Site Editor goes further than page-by-page editing. WordPress's documentation describes it directly: "The Site editor allows you to design the entire site including the header, footer, and everything in between, with blocks. It gives you greater control over how your site looks" (WordPress.org, "Site Editor", checked September 2026). It includes a Styles panel for colors and typography sitewide, a way to browse and edit templates and template parts, and a Pages section for managing content without leaving the editor.
The catch: WordPress is explicit that "The Site Editor is only available when you install and activate a Block theme on your site" (same source) — a theme built specifically for it. A classic (non-block) theme doesn't get a Site Editor at all, block-based page builder or not.
Page builders replace or extend WordPress's own editing screen with a different visual canvas, and each one is a separate product with its own cost, on top of your host and theme.
Elementor. WordPress.org's own plugin listing confirms Elementor's free version includes a "no-code, drag-and-drop Editor," "40+ free widgets" (headings, images, video, galleries, and more), a template library, and responsive design tools; the free plugin requires "WordPress 6.8 or greater" and "PHP version 7.4 or greater" (WordPress.org, Elementor plugin page, checked September 2026). Elementor's own pricing page lists a paid Elementor Pro "Essential" tier at "$49/year" for one site, adding "57 Editor Pro widgets, Theme Builder, and Dynamic Content" over the free version, with higher tiers scaling to more sites (Elementor Pricing, checked September 2026).
Divi. Elegant Themes markets Divi as "the ultimate WordPress theme and page builder," bundling a theme and a visual builder together rather than selling them separately. Its pricing page listed an annual plan at "$70 billed yearly" (about $5.83/mo) at the time of this check, alongside a higher "Divi Pro" tier at "$199 billed yearly" adding AI tools and cloud storage, and a one-time "Divi Lifetime" option at "$199" (Elegant Themes, Divi, checked September 2026). That page also displayed a limited-time "Anniversary Sale" discount, so treat the exact number as a snapshot and check the current page rather than the number quoted here.
Beaver Builder. Beaver Builder's own pricing page lists a "Starter" plan at "$89/year" for one site (Page Builder Plugin, Beaver Builder Theme, and the Beaver Themer add-on), a "Plus" plan at "$179/year" for three sites that adds Beaver Builder AI, a "Professional" plan at "$299/year" for 50 sites, and an "Unlimited" plan at "$546/year" with white-labeling and priority support (Beaver Builder Pricing, checked September 2026).
None of these plugins remove the block editor — they run instead of it (or alongside it, for content the builder doesn't touch), and each needs its own license renewed to keep getting updates and support.
This varies by builder, and it's worth checking before you commit, because it isn't the same story for all three.
Beaver Builder documents this directly, and it's good news. Its own knowledge base states: "You can safely uninstall or deactivate the Beaver Builder plugin without losing any of your layouts." Its walkthrough of what actually happens adds: "A stripped-down HTML version of your layout is copied to the native WordPress editor. Your content layouts may not look exactly the same as when the plugin was active, but you won't lose your content" (Beaver Builder Knowledge Base, "Uninstall or deactivate the Beaver Builder plugin", checked September 2026).
Divi documented real lock-in for its older version, and has since moved away from it. Elegant Themes' own blog explains that Divi 4 and earlier stored every design element as a WordPress shortcode: "If you have ever disabled Divi and visited a page you built with the Divi Builder, you would have seen these shortcodes" as raw bracketed text instead of your design (Elegant Themes, "Divi 5 Waves Goodbye To Shortcodes", checked September 2026). Divi 5, the current version, uses a different storage format instead and includes a migrator for older sites. If you're still on Divi 4, or unsure which version a site runs, back up before deactivating and check Elegant Themes' own migration documentation for your specific version first.
Elementor doesn't publish a page describing what happens to your content on deactivation. Its own support article on activating and deactivating plugins gives only a general warning — "Deactivating plugins can cause issues. Create a backup before deactivating" (Elementor Help Center, "Activate & deactivate plugins", checked September 2026) — without describing the specific outcome for page content. Since it isn't documented, don't assume either way; back up the site and test deactivation on a staging copy before you rely on the answer.
| Block editor (core) | Site Editor (core) | Page-builder plugin (Elementor/Divi/Beaver Builder) | |
|---|---|---|---|
| Cost | Free, built into WordPress | Free, built into WordPress | Free tier (Elementor) or paid from ~$49–$89/year up |
| What it edits | One post or page at a time, block by block | Whole site: header, footer, templates, global styles | A visual canvas layered over (or replacing) the block editor's page-building UI |
| Requires a specific theme | No | Yes — a block theme only | Varies; Divi bundles its own theme, Elementor and Beaver Builder work with most themes |
| Content after deactivation | N/A — it's core, not removable this way | N/A — core | Beaver Builder: documented, content stays editable. Divi: documented lock-in in v4, resolved in v5 with a migrator. Elementor: not documented either way |
A page builder is not necessary if your theme already supports the Site Editor and gives you the layout control you need — you'd be paying for and maintaining a second editing system on top of one WordPress already includes for free.
A page builder is a real fit if you want a more visual, live-preview design process, extra widgets (forms, sliders, pricing tables) your theme doesn't include, or you're standardizing a design workflow across many client sites and want one consistent tool regardless of which theme each site uses.
Figment isn't a WordPress plugin at all — it publishes a Figma design as a live website through its Figma plugin, for a marketing site or portfolio designed entirely in Figma rather than assembled from blocks or widgets inside WordPress. If your project is already a WordPress site and the real question is which in-WordPress editing tool fits, this comparison — not Figment — is the one that matters. For what AI tools can and can't do on an existing WordPress site, including the block editor itself, see Can ChatGPT or Claude edit your WordPress site?
Bottom line: WordPress's block editor and Site Editor already cover a lot of ground for free, and only need a compatible block theme. A page-builder plugin adds real capability on top, at a real cost, and what happens if you ever remove it is worth checking per builder rather than assuming.