19 min read
bbPress Review 2026: I Ran Forums on It for 4 Years — Here’s the Honest Truth (and What I Use Now)
I’ve been building WordPress communities since 2018. bbPress is the plugin I want to love.
It’s free. It’s from the core WordPress team. It’s been around since 2004. If you’re adding a forum to a WordPress site today, bbPress is probably the first plugin you’ll find.
I’ve run three production communities on it, a SaaS support forum with ~8,000 topics, a niche hobbyist community that grew to around 15,000 posts, and a client’s membership site we gated with Paid Memberships Pro. Between those three, I’ve put bbPress through almost every real-world scenario a WordPress forum plugin faces.
And I’m going to be honest: in April 2026, I can’t recommend bbPress for a new forum anymore. Not because it’s bad, because it’s standing still while the rest of WordPress has moved on.
This isn’t a drive-by review written by someone who installed bbPress on a staging site for twenty minutes. This is a four-year walk-through of what bbPress actually feels like to run. What works. What quietly breaks. And what I switched to after a specific incident I’ll describe below.
TL;DR, should you use bbPress in 2026?
- If you have a tiny, low-traffic community (under 1,000 posts) and zero plans to grow: bbPress works. It’s free, stable, and simple.
- If you’re migrating off bbPress: I’ll show you a path at the end of this article.
- If you’re starting a new community today and expect it to grow past 5,000 posts: I’d look at a modern alternative. I’ll explain exactly why below, and I’ll show you the one I moved to.
- If you want Q&A with accepted answers, or an ideas board with voting: bbPress doesn’t do these natively. You’ll need a different plugin.
Let me walk you through the actual experience.
What bbPress still does well
I want to start here because it’s important. bbPress is not garbage. The people who built it are excellent, and the plugin has real strengths.
It’s genuinely free and always has been
No upsells. No “core plus Pro” model. No locked features behind a paywall. The plugin you install from wordpress.org is the plugin you get forever. In an ecosystem where “free” often means “free trial with nag screens,” this matters.
It’s mature and stable
bbPress has been around since 2004. In the four years I’ve run it, I’ve never had a bbPress bug corrupt my data. The database schema is stable. Upgrades don’t break things. If you install it and never touch it again, it’ll still work in two years.
It integrates with BuddyPress naturally
If you’re already running BuddyPress, bbPress is the natural forum layer. The integration is solid, forum topics appear in member activity streams, trusted members show in forum listings, the visual language matches. For BuddyPress-first sites, this is a real advantage.
The hook system is extensive
bbPress has years of hooks and filters built up. If you want to customize behavior, block certain words, change the topic listing, add custom fields, you can usually find a hook that lets you do it without touching core files. This is a big deal for developers.
It uses WordPress’s own user system
No separate login. No SSO setup. No user sync. Your WordPress members are your forum members. This sounds obvious, but standalone forum platforms like Discourse make you set up account bridges that break in unpredictable ways.
Those are the honest strengths. Now let’s talk about what broke for me.
Where bbPress quietly breaks (from someone who’s been there)
These aren’t complaints from a 20-minute trial. These are the things that made me seriously look at alternatives after running production communities for years.
1. It stores everything in wp_posts and wp_postmeta
This is the technical decision that causes almost every other problem on this list. Every forum, topic, and reply in bbPress is a WordPress post or comment. Every piece of metadata, reply counts, subscriptions, favorites, topic status, lives in wp_postmeta.
For a 500-post forum, this is fine. Nobody notices. But here’s what happened to my 15,000-post hobbyist community around month 18:
wp_postmetagrew to several million rows (bbPress writes a lot of meta per topic)- Admin list pages started timing out
- The WordPress “All Posts” view became painful because bbPress topics were mixed in
- Third-party plugins that queried
wp_posts(an SEO plugin, a sitemap generator, a caching plugin) slowed down, they didn’t know to ignore bbPress content, so they tried to process thousands of forum posts as regular blog posts - Site-wide search got worse for everyone because
wp_postswas heavy
I moved that site to managed WordPress hosting with Redis, threw money at the problem, and got it stable. But the root cause was architectural, not a hosting issue. At that scale, bbPress’s approach of “forum posts are just WordPress posts” stops being a feature and starts being a tax on the whole site.
2. Reply counts use COUNT queries on page load
bbPress doesn’t store a reply count directly on the topic record. When you load a forum listing, bbPress runs SELECT COUNT(*) for each topic to show “42 replies.” At a few hundred topics per page, this adds up.
You can cache it, and Redis masks the problem, but the fundamental issue is that the data model wasn’t designed for the query patterns that forums actually run.
3. No cursor-based pagination on list endpoints
bbPress uses offset pagination (LIMIT 20 OFFSET 400). On page 21 of a busy forum, the database has to scan past 420 rows to get to the ones you want. This gets progressively slower as you paginate deeper. Modern forum software uses cursor-based pagination to avoid this entirely.
4. Development has slowed to a crawl
Here’s the release history:
- bbPress 2.5, shipped 2013
- bbPress 2.6, shipped 2020 (seven years later)
- bbPress 2.7, no release as of April 2026
The last commit to the develop branch was over a year ago. The bbPress team hasn’t abandoned the project, they’ve released minor fixes, but the pace means features I expected to see in 2020 are still missing in 2026. Q&A spaces. Accepted answers. Trust levels. Full-text search that rivals dedicated search plugins. A REST API worth building on. None of these are in bbPress today.
5. No REST API worth building on
bbPress doesn’t expose a proper REST API. There’s a community bbPress REST API add-on, but it’s thin, not officially supported, and not maintained. If you want to build a mobile app, a headless frontend, or any integration that reads forum data, you’re going to write a lot of custom code.
In 2026, when even the smallest WordPress plugins ship with a REST API from day one, this feels anachronistic.
6. The moderation queue is basic
bbPress gives you three post statuses: published, pending, spam. That’s it. No flag system for members to report content. No moderator queue that groups flags with the content. No trust level that automatically rate-limits new accounts. No auto-moderation rules.
Akismet catches obvious spam. That’s the extent of the defense. If you want a real moderation workflow, you’re installing multiple add-ons and gluing them together.
7. Theme integration is a fight
bbPress ships with its own CSS and its own template hierarchy. When you drop it into a modern block theme, it looks wrong, wrong fonts, wrong spacing, wrong colors. Every theme I’ve used required custom CSS to make bbPress look like it belonged.
In 2026, WordPress has theme.json design tokens that define fonts, colors, and spacing for the whole site. A modern forum plugin reads those tokens and adapts automatically. bbPress doesn’t. You override, or you live with the mismatch.
8. Search is WordPress default search
bbPress search is WordPress core search, which means it’s slow, returns bad results, and doesn’t understand forum-specific signals like “posts with accepted answers should rank higher.” On a forum where search is how members find existing answers, this is a real problem.
There’s a FULLTEXT search add-on (community, unofficial) but it’s another moving part you have to maintain.
The incident that made me switch
I was running the 15,000-post hobbyist community, and I’d been getting increasing support tickets from members about performance. Pages were taking 3-4 seconds to load. The forum listing was the slowest page on the site.
I ran Query Monitor and saw what was happening: bbPress was firing 47 separate queries to render a single forum listing page. Reply counts (one per topic). Last reply metadata (one per topic). Subscription status (one per topic for the current user). Freshness data (one per topic). All of this was separate queries because the data was spread across wp_posts, wp_postmeta, wp_comments, and wp_commentmeta.
I added Redis. I added object caching. The query count stayed high; the latency dropped because Redis masked the repeated queries. I tuned MySQL. I upgraded hosting. I bought time, but I didn’t fix anything.
Then a member filed a GDPR data request, which meant I needed to export everything they’d written to the forum. The export script I wrote hit PHP’s memory limit because it had to load user data from four different tables and join them in PHP. I solved it with a chunked background job, but the experience left me with a clear feeling: I was fighting the data model, not building features.
That week I started looking at what else was available.
The alternatives I evaluated
I gave each of these a real trial, installed on a staging site, imported real data where possible, ran actual community workflows through them.
wpForo
The most serious bbPress alternative today. wpForo has custom database tables (the thing bbPress doesn’t), multiple layouts, and built-in SEO. It’s actively maintained and shipped in 2025.
What I liked: Custom tables meant my performance problem was solved architecturally. The search was better. The built-in reputation system was a nice bonus.
Why I didn’t stay: wpForo has its own visual language that doesn’t inherit from theme.json. Theme integration was a fight. The free version has meaningful feature locks (emoji reactions, polls, attachments) and the Pro pricing adds up. Q&A mode exists but feels bolted on rather than designed in.
Asgaros Forum
A lightweight bbPress alternative that keeps things simple.
What I liked: Small footprint, clean admin UI, decent for small communities.
Why I didn’t stay: Missing features I needed (no trust levels, basic moderation, no Q&A, limited REST API). This is a great plugin for a 500-post club forum. Not the right fit for something trying to grow.
Discourse (self-hosted)
I ran this for two weeks. Discourse is excellent software, probably the best forum platform in the world technically.
Why I didn’t stay: It’s not a WordPress plugin. It’s a separate Rails application that runs on its own server and needs its own login system. Connecting it to WordPress required a plugin bridge that got stale when either side updated. I had two admin panels, two user tables, two hosting bills. For a forum that was supposed to live inside my WordPress site, it was the wrong shape.
BuddyPress + forum add-ons
I was already running BuddyPress on this site, so I tried adding BuddyPress Docs and Private Messages and calling it a forum.
Why I didn’t stay: BuddyPress is an activity-stream social network, not a forum. Trying to force it into a forum shape made the UX confusing for members who wanted threaded discussions.
Jetonomy (from Wbcom Designs)
This is what I ended up switching to. Full disclosure: Wbcom Designs is the WordPress studio behind BuddyX, BuddyPress extensions, and now Jetonomy, and I know the team. That’s why I gave it a serious look. But I tested it the same way I tested the others.
What I liked, the architectural stuff that solved my bbPress problems:
- 24 custom MySQL tables instead of
wp_posts. My 15,000-post data imported cleanly with the built-in bbPress importer (dry run first, then resume on failure). After the import, mywp_postmetashed several million rows. Site-wide admin pages got faster. - Denormalized counters. Reply counts, vote scores, and post counts are stored as columns directly on each topic record. No COUNT queries on page load. The listing page went from 47 queries to 12.
- Cursor-based pagination everywhere. Page 21 loads in the same time as page 1.
- Theme integration via
theme.json. Jetonomy reads my theme’s brand color, font, and border radius automatically. I did zero CSS overrides. This was the first forum plugin I’ve tried that actually looked like it belonged in my theme out of the box.
What I liked, the features bbPress doesn’t have:
- Q&A spaces with accepted answers. I moved my support section to a Q&A space. Members mark the reply that solved their problem. That reply pins to the top with a green “Accepted Answer” badge and the replier earns reputation. Repeat questions dropped because the canonical answer is visible.
- Ideas spaces with a roadmap. I moved feature requests to an Ideas space. Members vote, and admins move ideas through Open → Planned → In Progress → Done. Replaces the spreadsheet I used to keep.
- Six trust levels. New members start rate-limited (3 posts per day, no links). As they contribute, they earn abilities. This replaced the homegrown “ignore new accounts until they’ve been around a week” rule I’d been enforcing manually.
- 48+ REST API endpoints in the free plugin (90+ with Pro). When I wanted to build a custom dashboard showing community stats, I queried the API instead of writing raw SQL.
- WordPress Abilities API support (19 abilities). If you’re building AI agents on top of WordPress 6.9+, Jetonomy’s community operations are discoverable through the standard Abilities registry.
- A built-in bbPress importer with dry-run mode. The migration took about 40 minutes for 15,000 posts. Zero data loss. The importer ran as a batched background job I could resume if anything failed.
- AI-powered moderation in Pro (as of v1.3.0) with support for self-hosted Ollama. This matters if you’re in a regulated industry where you can’t send member content to a third-party AI API.
What I didn’t love:
- It’s newer. bbPress has been around since 2004. Jetonomy’s first release was March 2026. The upside is the code is actively shipping (three releases in the first two weeks post-launch). The downside is the community of third-party developers and tutorials isn’t as deep yet.
- The free plugin is genuinely complete, but some of the features I wanted most (custom badges, analytics dashboard, private messaging) are in Pro. You can run a serious community on just free, but if you want the full experience you’ll pay for Pro.
- Pro is sold directly through wbcomdesigns.com, not on the WP.org repository. This is normal for premium WordPress plugins but it means you’re managing license keys.
I’ve been running Jetonomy on that same community for about three weeks now. Page load times dropped from 3.5 seconds to under 400ms. The admin feels like a modern WordPress plugin, not a 2013 plugin. Moderation is handled by trust levels with almost no intervention from me. I haven’t looked back.
bbPress vs the modern alternatives, the comparison table
Here’s how bbPress stacks up against the three WordPress-native options I’d actually recommend in 2026.
| Feature | bbPress | wpForo | Asgaros | Jetonomy |
|---|---|---|---|---|
| Free to install | Yes | Yes (with Pro upsells) | Yes | Yes |
| Custom database tables (not wp_posts) | No | Yes | Yes | Yes (24 tables) |
| Denormalized counters | No | Partial | Partial | Yes |
| Cursor-based pagination | No | No | No | Yes |
| Theme.json integration | No | No | No | Yes |
| Q&A with accepted answers | No | Yes (Pro) | No | Yes (free) |
| Ideas / roadmap spaces | No | No | No | Yes (free) |
| Trust levels with auto-promotion | No | No | No | Yes (free, 6 levels) |
| Full REST API | No | Partial | No | Yes (48+ free, 90+ with Pro) |
| WordPress Abilities API | No | No | No | Yes (19 abilities) |
| bbPress importer built in | N/A | Yes | No | Yes |
| AI-powered moderation | No | No | No | Yes (Pro 1.3.0) |
| Active development cadence | Slow (1 release in 7 years) | Active | Active | Very active |
| Theme customization required | A lot | Some | Some | Almost none |
I’m not saying any of these three is bad. wpForo is a legitimate option if you don’t care about theme integration. Asgaros is great for tiny forums. I moved to Jetonomy because the architectural decisions (custom tables + denormalized counters + cursor pagination + theme.json) solved the specific problems I was hitting, and because the Q&A and Ideas space types meant I could retire two other plugins I’d been gluing together.
bbPress vs BuddyPress, a common point of confusion
I see this question a lot: “Should I use bbPress or BuddyPress?”
They solve different problems. bbPress is forum software, threaded topics, replies, subscriptions. BuddyPress is social network software, member profiles, activity streams, groups, friends. They were built to work together, and for a site that needs both (a member community with a forum attached), you install both.
If you only need a forum, install bbPress (or an alternative). If you only need a social network, install BuddyPress. If you need both, install both.
Jetonomy is closer to bbPress in scope, it’s a forum plugin. If you’re also running BuddyPress, Jetonomy integrates with it cleanly and the visual language matches BuddyX themes out of the box.
bbPress vs phpBB, different worlds
Another question I see: “bbPress vs phpBB?”
phpBB is a standalone forum application that you install on your server separately from WordPress. It has its own user database, its own admin panel, and its own hosting requirements. It’s been around since 2000 and is the spiritual ancestor of most PHP-based forum software.
bbPress is a WordPress plugin. It lives inside your WordPress install, uses your WordPress users, and is managed from your WordPress admin.
Choose phpBB if: Your community is the whole product and you don’t need it tied to a WordPress site.
Choose bbPress (or Jetonomy) if: You have a WordPress site and you want the forum to be part of it.
bbPress themes, the theme situation
bbPress has a small ecosystem of “bbPress themes”, theme authors that styled their themes to work well with bbPress out of the box. Most of them date from 2014-2018. A few are still actively maintained.
The modern answer is: your forum plugin should read theme.json from your active theme and adapt automatically. You shouldn’t need a “bbPress-compatible theme” in 2026. That’s a workaround for the plugin not integrating with modern WordPress theming.
If you’re stuck on bbPress and need a theme that works with it, the ones I’ve used successfully are BuddyX (free from Wbcom Designs), Astra, GeneratePress, and Blocksy. All of them have bbPress-compatible styling and won’t fight your forum’s layout.
bbPress forum examples, live sites running bbPress
If you want to see bbPress in action before committing, here are communities running it in 2026:
- WordPress.org Support Forums, the largest bbPress deployment on the planet. Millions of topics. Heavily customized, but it’s the canonical example.
- BuddyPress.org Support, from the same team as bbPress. Standard install, shows bbPress + BuddyPress integration.
- Various WordPress plugin support forums scattered across wordpress.org.
Most large bbPress sites are plugin support forums, not community forums. That’s a signal about where bbPress fits today, it’s a solid tool for vendor support, less so for thriving social communities.
How to migrate from bbPress to Jetonomy (if you’re considering it)
I get asked this a lot, so here’s the short version:
- Install Jetonomy (free version from wbcomdesigns.com) on your WordPress site.
- Go to Jetonomy → Import. The importer auto-detects your bbPress installation and shows you what it found: forums, topics, replies, users.
- Run a dry run first. This shows exactly what will be created in Jetonomy without writing anything to the database. I strongly recommend this step, you’ll see any data that might not map cleanly.
- Run the actual import. Large imports (10,000+ topics) run as batched background jobs with a progress indicator. You can close the browser and come back.
- If the import is interrupted for any reason, server timeout, browser crash, your laptop sleeping, it resumes from where it stopped.
- After the import, bbPress URLs are automatically 301-redirected to the Jetonomy URLs to preserve your SEO.
The migration took about 40 minutes for my 15,000-post community. Zero data loss. I deactivated bbPress after a week of running both in parallel to confirm the Jetonomy version was complete.
Frequently asked questions
Is bbPress still being developed in 2026?
Technically yes. The bbPress team is still around, and they ship security fixes. But feature development has slowed dramatically, no major release since 2020, and the feature gap with modern forum plugins has widened significantly. For a long-term project, I’d treat bbPress as maintenance-mode software.
Is bbPress free?
Yes, completely. There’s no Pro version, no paid upsells, no locked features. The plugin you install from wordpress.org is the complete plugin. This is genuinely unusual in the WordPress ecosystem.
How many active installs does bbPress have?
As of April 2026, bbPress reports around 300,000 active installs on wordpress.org. That number has been slowly declining as users move to alternatives or off WordPress forums entirely.
Can bbPress handle a large forum?
Technically yes, but at scale the architectural decisions (storing content in wp_posts, no denormalized counters, offset pagination) start causing performance problems. I ran a 15,000-post community on bbPress and had to throw significant hosting resources at it to keep it fast. Above 50,000 posts, I’d expect real problems.
What’s the best bbPress alternative for 2026?
Depends on what you need. For a small, low-traffic forum: Asgaros works. For a mature alternative with custom tables and feature parity: wpForo. For a modern forum built from scratch with performance, Q&A, Ideas spaces, trust levels, AI moderation, and theme.json integration: Jetonomy. I personally switched to Jetonomy and that’s where my communities live now.
Does bbPress work with Elementor?
Sort of. bbPress template output isn’t Elementor-native, you can’t drag-drop forum widgets into Elementor pages. You can embed bbPress shortcodes inside Elementor templates, but the styling control is limited. Modern forum plugins handle this more cleanly.
Is there a bbPress REST API?
Not an official one. There’s a community add-on called “bbPress REST API” on GitHub but it’s not officially supported by the bbPress team and hasn’t been actively maintained. If you need a REST API for your forum, bbPress is not the plugin to pick.
My recommendation
If you’re starting a new community on WordPress in 2026 and you expect it to grow: don’t start with bbPress. You’ll end up where I ended up, running into architectural problems at scale and having to migrate anyway. Start with a plugin that was built for 2026 expectations.
If you already run bbPress and it’s working for you: don’t migrate yet. Migration has costs, and if your current setup is stable, there’s no urgency. But keep the option in your back pocket for when you hit the scale wall.
If you’re hitting the scale wall right now: look at Jetonomy. The bbPress importer is built in, the migration is genuinely low-risk (dry run first, resume on failure), and the architectural payoff is real. I switched three weeks ago and I’d do it again tomorrow.
Try Jetonomy free at store.wbcomdesigns.com/jetonomy/. There’s no trial gate, the free version is the full free version. If it doesn’t fit your community, uninstall it and nothing is lost.
Related reading:
- The Future of Self-Hosted Discussion Forums: Introducing Jetonomy
- 9 Best WordPress Forum Plugins for 2026, full breakdown
- Mighty Networks review, hosted community platform alternative
- 9 Best bbPress Alternatives for 2026, dedicated alternatives listicle from the leaving-bbPress angle.
- 7 Best wpForo Alternatives for 2026, for anyone migrating off wpForo specifically.
- 9 Best Forum Software Alternatives for 2026, broader forum software landscape including WordPress, standalone, and SaaS options.
Related reading