Release Overview
Bricks 2.3 is a major release for 2026, centered on three priorities: AI-assisted site building, continued performance optimization, and a more complete component system. This post walks through the official changelog point by point to help you decide whether the upgrade is worth it.
⚠️ Before you upgrade: run it on a staging site first. Bricks 2.x upgrades are generally rock-solid, but you shouldn’t push a major release straight to production.
Highlight 1: Paste AI-Generated HTML Straight Into the Builder ⭐⭐⭐⭐⭐
This is the biggest feature in 2.3.
Now you can:
- Generate HTML in ChatGPT / Claude / any AI tool
- Paste it directly into the Bricks editor
- Have Bricks automatically parse it into editable element structure (containers / text / buttons…)
Why it matters: Previously, AI-generated HTML was either unusable or required heavy manual rework. Now the pipeline AI draft → Bricks edit → ship is fully connected — a quantum leap in build speed.
Best for: landing pages, component drafts, and fast marketing page generation.
Highlight 2: Performance Improvements ⭐⭐⭐⭐
2.3 continues to refine performance:
- Faster editor loading (on pages with lots of elements)
- Leaner front-end CSS output
- Optimized dynamic data queries (large Query Loop lists)
Hands-on impression: Editing large pages (hundreds of elements) feels noticeably smoother. Front-end speed was already fast and stays that way after upgrading.
Highlight 3: A More Complete Component System ⭐⭐⭐
- New component types (depending on your Frames/ACSS version)
- Improved component nesting logic
- Enhanced conditional logic
Why it matters: Bricks is increasingly behaving like a design system tool — components plus style variables plus conditional logic brings it closer to code-level control.
Upgrade Checklist
| Watch out for | Recommendation |
|---|---|
| ACSS (Automatic CSS) compatibility | ⚠️ Important: Bricks and ACSS have a history of version coupling (class chaining settings). Confirm ACSS version compatibility before upgrading |
| Third-party plugins | Check whether your Bricks plugins (Frames/WPCodeBox, etc.) declare 2.3 support before upgrading |
| Custom code | If you use hooks or filters, run a full pass on the staging site to confirm |
| Rollback | Keep the previous version’s zip so you can downgrade if needed (the Bricks member area keeps historical versions) |
Should You Upgrade? The Verdict
Yes, upgrade. The core additions in 2.3 (AI-to-HTML paste + performance) are strictly positive — low risk, clear payoff.
The one exception: if your site heavily depends on a third-party plugin that hasn’t been adapted for 2.3 yet — wait for the plugin update before upgrading.
First Things to Do After Upgrading
- Upgrade the staging site → run a full-site pass (focus on dynamic data pages and WooCommerce pages)
- Confirm ACSS/Frames compatibility
- Upgrade production → clear caches → full-site check
- Try AI-to-HTML while you’re at it: have an AI generate a hero section, paste it into Bricks, and see how it parses
Release Cadence Reference
Bricks release frequency: 1–2 major versions per year plus frequent minor releases. The right way to stay current:
- Minor versions (2.3.x): upgrade without thinking (bug fixes)
- Major versions (2.x → 3.x): verify on staging first, then upgrade
- Watch the breaking changes section of the official changelog
This site automatically monitors the official Bricks changelog via a cron job and breaks down each new release the moment it ships — stay tuned to keep your knowledge current.
Related Reading
- [Bricks 2.2 Hidden Gems: Color Manager + Style Manager Explained](2.2 color-style-manager link)
- Bricks Installation & Basic Setup Guide
- 5 Bricks Pitfalls You’ll Want to Avoid
Upgrading is really “trading stability for new capabilities” — these two highlights (AI + performance) are worth the 30 minutes it takes to test the upgrade.