Beaver Builder Pro is the page builder you reach for when you’ve been burned once. It’s not flashy. It doesn’t ship a new feature every week. It boots fast, the editor stays stable for hours, and the markup it produces is clean enough that swapping it out later isn’t a nightmare. That’s not nothing. Plenty of WordPress shops who started on Elementor or Divi quietly migrated to Beaver Builder after the third production layout broke during an update, and the consensus from those folks is the same: it’s boring, and that’s exactly why they use it.
This review is the long-form version of "what is it actually like to use?". We’ll build a page from scratch, walk every panel and screen worth knowing, look at how the 42 modules compare to what Elementor Pro ships, and then drop into the developer surface where Beaver Builder genuinely shines (the custom module API is the cleanest one in the page-builder market).
Table of Contents
- What is Beaver Builder Pro?
- How a page actually gets built
- Key features
- How it works (for users)
- Installation and setup
- Real-world use cases
- Beaver Builder Pro vs Elementor Pro
- Developer reference
- Performance, compatibility, and gotchas
- Pricing and licensing
- FAQ
- Final thoughts
What is Beaver Builder Pro?
Beaver Builder Pro is a drag-and-drop visual page builder plugin for WordPress, built by a small Florida-based team called The Beaver Builder Team. You install it like any other plugin, and once active, every page and post (and any custom post type you opt in) gets a new "Launch Beaver Builder" button. Click it and the front of your site flips into edit mode, with the page rendered exactly as visitors will see it, plus a content panel for adding rows, columns, and modules.
It is not a theme. You keep your existing theme (or use the optional Beaver Builder Theme, sold separately). It is not a block editor extension. Beaver Builder uses its own front-end UI, parallel to the Gutenberg block editor, and the two coexist on the same site without fighting. You decide per-page which one to use.
The Pro license adds 30+ premium modules on top of the free Beaver Builder Lite, plus saved row/column/module templates, full template export/import, and the white-label and multi-site features that make it production-friendly.
Three things matter about how the plugin is built. First, the markup it produces is plain HTML and CSS, very close to what a designer would have hand-written. Second, it has been around since 2014 and the same small team has shipped it the entire time. Updates are infrequent but careful. Third, the developer API for custom modules and integrations is the most stable one in the page-builder space; modules written in 2018 still work today.
If you’ve used Elementor Pro and felt overwhelmed, or used Divi and felt locked in, Beaver Builder is the calmer alternative.
How a page actually gets built
Before we touch settings, let’s follow what happens when you build one page. Knowing the loop helps every panel make sense.
You start in Pages → All Pages → Add New (or any existing page or post). At the top of the editor, you’ll see a "Launch Beaver Builder" button. Click it. The screen flips: WordPress admin disappears, your live theme renders, and a slim bar appears at the top with the page title, an "Edited" indicator, and a Done button.
You click the + icon on the bar. A panel slides in from the right with four tabs: Modules, Rows, Templates, Saved. Modules is the default, that’s where the page content comes from. You drag a "Heading" module onto the canvas. It drops in, the settings dialog opens, you type your headline, hit Save. The heading is now on the page.
Now you want a two-column section: photo on the left, text on the right. You drag a Row from the Rows tab onto the canvas, choose a "2-column" layout, then drop a Photo module into the left column and a Text Editor module into the right. Each module asks for its own settings: image picker for Photo, rich-text editor for Text Editor.
You click Done at the top-right and a small modal appears: "Publish, Save Draft, or Discard". You publish. The page now lives at its public URL, rendered exactly as you saw it in edit mode. No "preview vs published" surprises.
The whole loop is rows hold columns, columns hold modules, modules hold content. It scales from a single hero section to a forty-row landing page without changing the model.
Key features
These are the features that distinguish Pro from the free Beaver Builder Lite, and that come up most often in real use.
- 42 modules built-in. From basics (Heading, Photo, Button, Video) to layout helpers (Box, 3×2 Grid, 4×2 Grid, Flex Column) to content modules that pull from WordPress (Post Grid, Post Carousel, Post Slider) to ecommerce (WooCommerce, North Commerce) and conversion tools (Pricing Table, Subscribe Form, Countdown).
- Saved templates. Save any row, column, module, or whole layout as a reusable template. Use it across pages, across sites (with import/export), or share with your team. Categorize templates, attach a featured image, expose them in the editor’s Templates tab.
- Theme-independent. Beaver Builder doesn’t lock you to a theme. Use any theme you want, and the builder slots into its main content area. Migrating to a different theme later doesn’t rip your pages apart.
- White labeling. Rename "Beaver Builder" to whatever you want in the admin, change the icon, change the editor’s branding, hide the plugin from the Plugins list for non-admins. Useful if you’re an agency shipping client sites.
- User access control. Granular role-based permissions: who can use the builder at all, who can edit globals and components, who can manage templates, who can access the admin settings.
- Responsive editing. Three breakpoints (desktop, tablet, mobile) with independent settings per module. The editor itself simulates each viewport without leaving edit mode.
- Custom CSS and JS per layout. A code panel attached to every page lets you add layout-specific CSS or JS without leaving the editor.
- Multi-site, network-wide license. A single Pro license activates on unlimited sites under your control. No per-site reactivation hassle.
- Globally styled colors and typography. Set brand colors and font defaults once in Global Styles, and every module on every page reads from those. Change the brand color later and every page updates.
- Drag-to-resize columns. Grab a column edge and drag to resize. Same for row padding, margins, gutters. Less typing of pixel values.
How it works (for users)
We’ll build a real page step by step. By the end of this section you’ll know the editor well enough to ship a landing page in an evening.
Step 1: Launch the builder
Go to Pages → Add New, give the page a title ("Pricing", "About", whatever), publish or save as draft. Look for the Launch Beaver Builder button at the top of the editor. Click it. The screen flips to the front-end view.
If you don’t see the button, your theme might not declare support for the page builder on this post type. Fix in Settings → Beaver Builder → Post Types by ticking the post types you want the builder enabled on.
Step 2: Drop in your first row
Click the + icon in the top-right of the BB bar. The content panel slides in from the right. Switch to the Rows tab. You’ll see preset layouts (1 column, 2 column, 3 column, sidebar layouts, etc.). Drag the one you want onto the canvas. The row appears with empty columns.
Step 3: Drop in modules
Switch the panel to Modules. Drag a module (let’s say Heading) into one of the columns. As soon as you drop it, the settings dialog opens. Tabs at the top: General, Style, Advanced. Pick a heading text, pick H1/H2/H3, alignment, link if any. Click Save.
Drag a Text Editor into the second column. Same routine: settings panel opens, paste your content, hit Save.
Repeat for as many rows and modules as the page needs.
Step 4: Style globally, not per-module
This is the difference between a junior builder layout and a polished one. Instead of styling each module’s color and font, set them once globally.
Top-bar → menu → Global Styles (⌘G). A panel opens. Set your brand color (used by every module’s "Theme Color" picker), your default fonts, your default heading sizes, your button radius. Save. Now every Button on every page uses the brand color automatically. Change the brand color and every page updates.
Step 5: Save what you’ll reuse
When you build a row you’ll use again ("Testimonials carousel"), right-click → Save Row as Template. Give it a name, optionally a category, optionally a featured image. Now it appears in the Templates tab of the content panel, ready to drag into any future page.
Same for individual modules. Built a Callout you like the look of? Save it. The template carries every setting, including the responsive variants.
Step 6: Preview at each viewport
Top-bar → menu → Responsive Editing (r). The canvas shrinks to a tablet width. Switch again to phone width. Modules that need different settings per breakpoint get adjusted here, for example, you might want the headline to be 64px on desktop, 40px on tablet, 28px on phone. Each setting field in the module dialog has a small device icon: click it to set a different value per device.
Step 7: Click Done
Top-right → Done. A modal appears: Publish, Save Draft, Discard. Choose Publish. The page is live. Refresh the public URL in another tab to see it.
That’s the whole loop. Open the builder, drag rows/modules in, edit them, set global styles, save reusable pieces, click Done. Once you’ve done it a few times, building a five-section landing page is a 45-minute job.
Installation and setup
Install is fast. Most sites are running pages through Beaver Builder within fifteen minutes.
Prerequisites. WordPress 6.6+, PHP 7.2+. Works with virtually any theme. If you want a builder-aware theme, the optional Beaver Builder Theme is the one made by the same team, but you don’t need it.
Step 1: install the plugin. Upload the zip via Plugins → Add New → Upload, then activate. Beaver Builder will land in the admin sidebar.
Step 2: open Settings → Beaver Builder. This is the admin settings hub. Eleven tabs run down the left side: Welcome, License, Modules, Blocks, Post Types, Templates, User Access, Icons, Tools, Advanced, Import/Export.
The two tabs to visit before you build anything:
Post Types: tick which post types Beaver Builder is enabled on. By default, Pages and Posts are on. If you have a custom post type (Portfolio, Case Study, Product), tick it here.
Modules: every module ships enabled. If you know you’ll never use a particular module (BigCommerce, North Commerce, Login Form), untick it here to keep the editor panel tidy.
Step 3: paste your license key in the License tab if you have one.
Step 4: optional but useful, open User Access. Decide which roles can edit globally, manage components, and access the cloud-based template library. The defaults are sensible (Administrator + Editor can build), but on a multi-author site you’ll likely lock down Global Styles to admin only so a contributor can’t accidentally rebrand the site.
Step 5: go to Beaver Builder → Templates in the admin sidebar. This is where every saved layout, row, column, and module lives as a custom post type entry. Empty on a fresh install. The Categories sub-menu lets you organize them for larger teams.
You’re done with setup. Now you can go to any Page and click Launch Beaver Builder.
Real-world use cases
Five patterns where Beaver Builder Pro fits especially well:
The agency-built client site. White-label Beaver Builder so it appears as "[Agency Name] Builder" in the admin, restrict the client’s editor role to only the Modules tab (no Globals), build the site for them, and hand it over. The client can edit page copy, swap images, even add a new module to an existing row, without being able to break the design. We’ve seen many agencies use this exact pattern with thirty-plus clients on a single license.
The high-traffic landing page. Beaver Builder’s output HTML is plain and CSS is enqueued conditionally, so a Beaver Builder landing page loads almost as fast as a hand-coded one. Pair it with WP Rocket for caching and your Core Web Vitals stay green even on a 12-section page.
A documentation or knowledge-base site. Use BB on a few key landing pages and the home page, but keep the actual documentation entries on the block editor or a markdown-rendering plugin. BB doesn’t force itself onto every post. Mixed-mode editing works well, since the builder is opt-in per page.
A WooCommerce store front page. The WooCommerce module gives you flexible product grids, mini-cart, featured products, by-category lists, and product carousels, all themed to your site’s global styles. Pair it with Elementor Pro for advanced theme-building features, or stick with Beaver Builder and the Beaver Themer add-on for header/footer customization.
A multi-site network for an agency. Beaver Builder’s single-license-unlimited-sites policy means you can install it on every site in a WordPress multisite (or every separate client site) without per-seat counting. The Pro license is one of the few in the WordPress ecosystem that doesn’t punish you for scaling.
The pattern across all five: Beaver Builder rewards predictability. Sites that need a stable visual builder on long-running production work end up here.
Beaver Builder Pro vs Elementor Pro
Both plugins solve the same problem; the personalities are different. Quick comparison from a year of using both:
Editor speed. Beaver Builder boots faster. On a default WordPress + reasonable theme, the editor is interactive in 2-3 seconds. Elementor takes 4-6, sometimes more if you have a lot of widgets active. On long pages with 30+ sections, Elementor’s slowdown gets more visible than Beaver Builder’s.
Module count. Elementor Pro ships ~80 widgets to Beaver Builder’s 42 modules. Elementor wins on breadth. Beaver Builder’s modules are deeper, fewer of them, but each one has more settings. For most pages, both reach the same destination.
Output cleanliness. Beaver Builder’s HTML is closer to what a designer would hand-code. Fewer nested divs, simpler classes, less inline CSS. Elementor produces more markup overhead per module. For SEO and lighthouse scores, this matters slightly; for "the site looks correct", neither matters.
Template Builder (header/footer/archive layouts). Beaver Builder gates this behind a separate add-on (Beaver Themer, $147/year extra). Elementor Pro ships with its own Theme Builder built in. If you need full theme building, Elementor is the more economical pick. If you only need page-level layouts, Beaver Builder Pro alone is enough.
Developer API. Beaver Builder’s custom module API is much cleaner. Adding a custom module to Beaver Builder takes about 50 lines of PHP and an frontend.php template file. Adding a custom Elementor widget takes more boilerplate and the API has changed more often. If you’re a developer building custom modules for clients, Beaver Builder is the easier long-term bet.
Backwards compatibility. Beaver Builder ships infrequent updates and almost never breaks third-party modules. Elementor updates more often and has historically broken add-ons on major version jumps. Translation: Beaver Builder is the lower-maintenance pick.
Pricing. Beaver Builder Pro is one license = unlimited sites. Elementor Pro is tiered by site count. For agencies or anyone running >5 sites, Beaver Builder’s pricing wins. For a single small site, Elementor’s entry tier is cheaper. (Either way, on GPL Times the math changes, see Pricing below.)
If your priority is creative freedom and a huge widget library, Elementor Pro is the safer bet. We covered Elementor Pro in depth here. If your priority is stability, predictable output, and a developer-friendly customization story, Beaver Builder Pro is the pick. Many agencies use both: Elementor for design-heavy client sites where the breadth helps, Beaver Builder for production sites that need to stay boring.
Developer reference
Here’s where Beaver Builder genuinely shines. The plugin exposes one of the cleanest module-extension APIs in the WordPress ecosystem.
Custom module: the 60-second version
A custom module is a folder. Three files. That’s it.
my-plugin/
└── modules/
└── alert-box/
├── alert-box.php // module definition
└── includes/
└── frontend.php // the HTML rendered on the front end
alert-box.php:
<?php
class GPL_AlertBox_Module extends FLBuilderModule {
public function __construct() {
parent::__construct( array(
'name' => __( 'Alert Box', 'gpl' ),
'description' => __( 'A colored alert box with title and dismiss button.', 'gpl' ),
'category' => __( 'Content', 'gpl' ),
'dir' => plugin_dir_path( __FILE__ ),
'url' => plugin_dir_url( __FILE__ ),
) );
}
}
FLBuilder::register_module( 'GPL_AlertBox_Module', array(
'general' => array(
'title' => __( 'General', 'gpl' ),
'sections' => array(
'content' => array(
'title' => __( 'Content', 'gpl' ),
'fields' => array(
'title' => array(
'type' => 'text',
'label' => __( 'Title', 'gpl' ),
'default' => __( 'Heads up!', 'gpl' ),
),
'message' => array(
'type' => 'textarea',
'label' => __( 'Message', 'gpl' ),
'rows' => 4,
),
'tone' => array(
'type' => 'select',
'label' => __( 'Tone', 'gpl' ),
'default' => 'info',
'options' => array(
'info' => 'Info',
'warning' => 'Warning',
'error' => 'Error',
),
),
),
),
),
),
) );
includes/frontend.php:
<?php
$settings = $module->settings;?>
<div class="gpl-alert gpl-alert-<?php echo esc_attr( $settings->tone );?>">
<strong><?php echo esc_html( $settings->title );?></strong>
<p><?php echo wp_kses_post( $settings->message );?></p>
</div>
That’s it. The module shows up in the builder’s content panel under "Content". Users drag it in, edit it, save. The builder handles serialization, the responsive layer, the editor UI, the rendering, all for you.
Filter the builder’s behavior
Hundreds of filters are available; the ones you’ll actually use:
// Hide certain modules from non-admin users
add_filter( 'fl_builder_admin_settings_capability', function( $cap ) {
return 'manage_options';
} );
// Customize the module CSS class name
add_filter( 'fl_builder_module_attributes', function( $attrs, $module ) {
if ( $module->settings->id === 'my-module-id' ) {
$attrs['class'].= ' custom-wrapper';
}
return $attrs;
}, 10, 2 );
// Modify the Post Grid query
add_filter( 'fl_builder_loop_query', function( $query, $settings ) {
if ( $settings->meta_key === 'featured' ) {
$query->set( 'meta_key', 'featured' );
$query->set( 'meta_value', 'yes' );
}
return $query;
}, 10, 2 );
// Run code after the builder loads
add_action( 'fl_builder_loaded', function() {
if ( class_exists( 'FLBuilder' ) ) {
// register custom modules here
}
} );
Add a custom field type
The settings panel supports many field types out of the box (text, textarea, select, color, photo, link, etc.), and you can add your own:
add_action( 'init', function() {
FLBuilder::register_settings_form_field_type( 'my-rating', array(
'render' => function( $field, $name, $value ) {
echo '<input type="number" min="1" max="5" name="'. esc_attr( $name ). '" value="'. esc_attr( $value ). '" />';
},
) );
} );
The custom field type then becomes available to any module that opts in via its field definitions.
Hook into module render
Five lifecycle actions per module render:
fl_builder_before_render_modulefl_builder_render_module_htmlfl_builder_after_render_modulefl_builder_before_render_module_cssfl_builder_after_render_module_css
Use them for tracking, A/B test wiring, dynamic content swaps, etc.:
add_action( 'fl_builder_before_render_module', function( $module ) {
if ( $module->settings->id === 'cta-hero' ) {
do_action( 'analytics/cta_impression', $module->parent );
}
} );
Template loading and import/export
Templates are stored as a custom post type (fl-builder-template). Each entry stores the layout JSON in post meta (_fl_builder_data). You can query, modify, or migrate them programmatically:
// List all saved row templates
$templates = get_posts( array(
'post_type' => 'fl-builder-template',
'numberposts' => -1,
'tax_query' => array( array(
'taxonomy' => 'fl-builder-template-type',
'field' => 'slug',
'terms' => 'row',
) ),
) );
For full export/import, the Settings → Beaver Builder → Tools → Template Exporter UI gives you the click-button path. The Tools tab also has a "Duplicate Layout" feature for cloning whole pages.
User access gating
If you need a finer-grained capability check than role-based access:
add_filter( 'fl_builder_user_access', function( $access, $cap, $key ) {
if ( $key === 'global_styles' ) {
return user_can( get_current_user_id(), 'manage_global_styles' );
}
return $access;
}, 10, 3 );
Combine with WordPress’s standard capability system to build editor roles that can use the builder but can’t touch site-wide styles.
White-label hooks
White-label settings are admin-only by default, but you can override them programmatically (useful when distributing a client site as a one-click installer):
add_filter( 'fl_builder_white_label_data', function( $data ) {
return array_merge( $data, array(
'enabled' => true,
'plugin_name' => 'Acme Builder',
'plugin_short' => 'Builder',
'company_name' => 'Acme, Inc.',
) );
} );
WP-CLI
Beaver Builder does not ship its own WP-CLI command, but layouts are just post meta, so standard wp post meta works:
# Dump a page's layout JSON
wp post meta get 123 _fl_builder_data --format=json
# Re-import after edits
wp post meta update 123 _fl_builder_data "$(cat layout.json)" --format=json
For batch operations across many pages, write a small wp eval-file script.
Performance, compatibility, and gotchas
Things to know that aren’t obvious from reading the marketing:
Asset loading is conditional. Beaver Builder enqueues CSS and JS only on pages where it’s used. The site’s other pages (default WordPress pages, archives, etc.) load nothing extra. Good for performance.
The editor itself is heavy. First load of the editor on a fresh page is around 3-5 MB of admin assets. After the first visit, browser cache handles the rest. Don’t benchmark editor performance on a cold browser cache.
Cloud templates require a sign-in. The Cloud Templates feature (newer addition) requires logging in with a Beaver Builder account. On a GPL Times install, you can skip this entirely, local saved templates work without an account.
The page builder data lives in post meta. If you migrate a site, make sure to migrate the _fl_builder_data and _fl_builder_data_settings post meta keys. A "content-only" export (just post_content) loses the layout.
Theme compatibility quirks. Some themes inject their own wrappers around content in ways that interfere with full-width rows. If your full-width row shows up boxed-in, the theme is wrapping the content area. Most themes have a "Beaver Builder Compatibility" mode in their settings; if yours doesn’t, the workaround is a custom template that removes the wrapper, or use the Beaver Builder Theme.
Server-side caching plays nice. Beaver Builder pages cache cleanly via WP Rocket and any reputable cache plugin. The editor itself is admin-only (logged-in bypass takes care of it). Just don’t cache the ?fl_builder query string variant.
Translation strings live in languages/. The text domain is fl-builder. Drop your .mo file there if running a non-English site.
Database footprint is small. Beaver Builder doesn’t create its own tables. Everything is WordPress post meta + a custom post type for saved templates. Migration tools handle it without special steps.
Block editor coexistence. The block editor and Beaver Builder both work on the same site. Each page is in exactly one mode; you switch from one to the other via a button in the page’s edit screen. You will not accidentally use both on the same page.
Pricing and licensing
The official Beaver Builder Pro license is $147/year for unlimited sites. Renewals are automatic. The license unlocks Pro modules, premium support, and updates from wpbeaverbuilder.com. The separate Beaver Builder Theme is sold for $99/year, and Beaver Themer (theme builder add-on) is $147/year, bundling all three is around $399.
GPL Times sells the same Beaver Builder Pro plugin as a GPL download. The code is byte-for-byte identical, the same plugin file the official store ships. The pricing structure is different: you pay once for indefinite use across unlimited sites with no per-seat license check. Updates come from GPL Times rather than from the upstream auto-update endpoint. For agencies running multiple sites or anyone who values not renewing a subscription every year, the math heavily favors the GPL Times route.
The trade-off: official Beaver Builder support (ticket-based help from the team) is gated to paid customers. If you want guaranteed reply-within-24-hours support for production crises, the official subscription buys peace of mind.
FAQ
Is Beaver Builder Pro a theme or a plugin?
Plugin. You use it with any theme. The Beaver Builder Theme is a separate product, optional, and not required to use the plugin.
Does it require Gutenberg / the block editor?
No. Beaver Builder is independent of the block editor. The two coexist on the same site and you pick per-page which to use.
Can I switch from another page builder (Elementor, Divi, WPBakery) to Beaver Builder?
Manually, yes. There is no automatic migration tool because the content models are different. The recommended path: rebuild your core pages in Beaver Builder one at a time, leave the others alone, deprecate the old builder once the migration is complete.
Will my pages still work if I disable the plugin?
Pages built with Beaver Builder will fall back to whatever WordPress can render from post_content, which is usually a stripped-down version. The layout data is still in the database (in post meta), so re-enabling the plugin restores the page. But you should not run a production page with the plugin disabled.
Do I need Beaver Themer too?
Only if you want to build custom headers, footers, archive layouts, and singular templates with the visual editor. For "I just want to build the body of pages with the builder", Pro alone is enough.
Can I use Beaver Builder on custom post types?
Yes. Settings → Beaver Builder → Post Types lets you tick which post types are builder-enabled. Tick your CPT and it gets the Launch button.
Does it work with WooCommerce?
Yes. There’s a built-in WooCommerce module for product grids, mini cart, etc. For full theme-builder features (custom shop archive, custom single-product layouts), pair with Beaver Themer.
How does it compare to Elementor Pro for performance?
Beaver Builder’s output is lighter (fewer DOM nodes per module) and its editor boots faster. For a fresh-cache visitor, Beaver Builder pages typically score 5-10 points higher on Lighthouse than Elementor pages with comparable design.
Will my custom modules break on update?
Almost never. The custom module API has been stable since 2014 and the team treats backwards compatibility as a hard requirement. We have seen module code from 2018 still working on the current release.
Final thoughts
Beaver Builder Pro is what you pick when the boring answer is also the right one. It will not impress your friends with breadth or innovation. It will quietly produce clean, fast pages that don’t break when WordPress core updates, when the theme changes, or when the team behind it ships a new version.
Two specific recommendations if you’re picking it up. One: invest fifteen minutes in Global Styles before you build your first page. Every minute spent there pays off across every future page. Two: save templates aggressively. Saved rows are how Beaver Builder goes from "decent page builder" to "fast page builder". By the time you’ve built three pages with reusable saved rows, the fourth page takes a quarter of the time.
If you’re choosing between Beaver Builder Pro and Elementor Pro and you can’t decide, here’s the heuristic: pick Elementor if you build a lot of different design-heavy sites and value widget variety. Pick Beaver Builder if you build a handful of sites that need to stay running for years. Either way, both plugins are on GPL Times, so you can install both, build a quick page in each, and trust your hands more than a review (this one included).