Skip to content
WPJury
No. 00385 Design & Layout

Next Bricks: worth it for polished Bricks sites, not basic builds

The verdict Next Bricks is worth buying if you build Bricks sites that need distinctive animations, interactive sections, advanced menus, or page transitions without repeatedly writing custom JavaScript. It is not a must-have for ordinary brochure sites, and its dependency on a third-party addon makes it a poor choice when long-term portability matters more than visual polish.
Situational The ruling
Get v3.0.0

via WorldPressIT · complete package

Best for
  • Bricks agencies building interactive sites
  • freelancers who need reusable animated elements
  • designers creating Webflow-style experiences
  • developers who want GSAP controls inside Bricks
  • teams building multiple Bricks websites
Skip it if
  • basic business websites
  • sites that avoid animation dependencies
  • developers who prefer custom code
  • projects requiring maximum plugin portability
Version 3.0.0 Updated 13 Sep 2026 Licence GPL

Next Bricks is a specialist Bricks Builder addon, not a general-purpose WordPress enhancement. Its core appeal is a large library of visually opinionated elements for text effects, buttons, menus, sliders, media, cursors, backgrounds, and interactive content. The developer’s site currently advertises more than 192 elements and seven templates, while the changelog shows frequent additions such as portfolio, chart, workflow, looping-logo, materials, and interactive button elements.

The strongest reason to buy it is that it turns effects that normally require custom CSS, JavaScript, and GSAP work into configurable Bricks controls. Animator provides timelines, folders, themes, custom properties, and triggers such as page load, scrolling, and custom events. The Page Transitions feature integrates Barba.js and can automatically trigger timelines from Next Bricks elements and Animator. For an agency producing modern landing pages, creative portfolios, and brand sites, that can save meaningful implementation time and make effects easier for non-developers to adjust.

Its element architecture is also better than a collection of shortcodes or prebuilt images. The documentation describes the components as native Bricks elements with normal Content and Style controls, and the dashboard lets you enable or disable elements, features, and shared assets. The developer says element CSS and JavaScript load conditionally when an element is used on the front end. That is a sensible approach, although it should not be treated as a guarantee that an animation-heavy page will be lightweight.

The main weakness is scope. Many elements are highly stylized and solve narrow design problems rather than common site-building needs. If you only need tabs, accordions, forms, conditions, or utility features, Next Bricks is an expensive way to add them. BricksForge is the broader alternative when you want interactions, dynamic tools, forms, and developer utilities; BricksExtras is usually the more practical choice for common UI extras and conditions. Motion.page is the closer alternative when animation control is the priority but you do not need Next Bricks’ large catalog of ready-made visual elements.

There is also a real maintenance cost. Once a page relies on Next Bricks elements, removing the plugin means rebuilding those components. The Page Transitions documentation specifically warns that third-party scripts and custom scripts are not automatically included after a transition; those scripts must be added in the plugin’s custom JavaScript area. That is manageable for experienced Bricks developers but an easy source of broken interactions and confusing debugging.

Pricing is clear but deliberately variable: the complete Next Bricks package is listed at €259 one-time for unlimited websites and lifetime updates, while Elements and Features are sold separately. The price increases as new versions and features are released, and the stated refund window is 30 days if the team cannot make the product work for you. That makes the package good value for agencies, but excessive for a one-off site that will use only one or two effects. Try the temporary playground first, then buy it for a real project rather than for the size of the element count alone.

Questions people ask

Is Next Bricks worth buying for Bricks Builder?
Yes, if you regularly build animated or highly interactive Bricks websites. For simple business sites, its specialized elements and plugin dependency are usually not worth the cost.
Does Next Bricks slow down WordPress websites?
The developer documents conditional loading for element CSS, JavaScript, and shared assets. That helps, but pages using multiple animation libraries and effects can still require careful performance testing.
What is the difference between Next Bricks and BricksForge?
Next Bricks focuses more on polished visual elements, animations, menus, and page transitions. BricksForge is broader and generally stronger for forms, dynamic interactions, and developer-oriented utilities.
Can Next Bricks create page transitions?
Yes. Its Page Transitions feature integrates Barba.js, supports transition timelines, and can trigger timelines from Next Bricks elements and Animator.
What happens if I deactivate Next Bricks?
Any page content built with its custom elements or features may lose its structure or functionality. That plugin dependency is the main long-term drawback for sites that need maximum portability.

Get Next Bricks: worth it for polished Bricks sites, not basic builds 3.0.0

Complete package, ready to install, via WorldPressIT.

Download

Other rulings

Citadela Pro: worth it only for Citadela sites Citadela Pro is worth buying when you have already committed to the CitadelaWP theme and want more control over headers, typography, layouts, WooCommerce styling, and Gutenberg blocks. It is not a strong general-purpose design plugin because the developer documents that it works only with CitadelaWP, while alternatives such as Kadence, Astra, GeneratePress, and Elementor offer broader ecosystems and easier theme switching. Situational GutenBricks: worth it for controlled client editing, not general page building GutenBricks is worth buying if you build sites with Bricks and need clients or editors to assemble pre-designed sections in Gutenberg without touching the Bricks interface. It is not a general-purpose page builder, and its extra setup, rendering quirks, and still-evolving 2.0 branch make ACF, Meta Box, or native Bricks editing the safer choice for many projects. Situational Thrive Theme Builder: worth it for marketing sites, not flexible WordPress builds Thrive Theme Builder is worth buying if you want a conversion-focused business site and prefer visual control over coding, especially when paired with Thrive Architect or the wider Thrive Suite. It is not the best value for ordinary blogs, developers, or anyone who wants a lightweight theme with open-ended compatibility. The main trade-off is that it replaces your entire theme with Thrive’s proprietary system, so switching away later takes more work than moving from GeneratePress, Kadence, or Astra. Situational Technix: worth it for a fast Elementor IT site, but not a polished long-term pick Technix is worth considering if you need a ready-made IT or SaaS brochure site and already plan to build with Elementor. It is not the strongest value for a serious long-term site because the demo content feels unfinished, the theme depends on its TP Core plugin, Gutenberg is not a focus, and the public evidence of adoption is very limited. Situational