phpBB vs MyBB

Put these two side by side on any comparison site and the ticks line up almost perfectly. Categories, threads, private messages, attachments, permission groups, moderation queues, themes, plugins — both, for twenty years. Anybody claiming a decisive feature difference is describing an extension rather than the software.

Which is why this page is about the three things that do separate them, none of which appear in a grid: the licence, the way modifications are applied, and what each project's track record says about the board still working in five years.

The licence, which matters more here than anywhere else on this site

phpBB is GPL-2.0. MyBB is LGPL-3.0. On most of this site the licence line is dull until it suddenly is not; here it has a routine consequence.

Under the GPL, a modified copy you distribute carries the obligation to offer the modified source. That is fine for a board you run yourself and becomes a live question the moment somebody builds a product on top of it. The LGPL is more permissive about linking, which is the practical reason MyBB turns up more often inside things that are not forums.

For an ordinary community running an unmodified board, neither obligation is ever triggered. If a developer is going to build something on the board rather than in it, read both licence files first — that takes ten minutes and is skipped almost universally.

How modifications are applied, and why it decides the board's lifespan

This is the row that actually matters and it is not on any comparison table.

phpBB moved to an extension system: extensions live in their own directory and hook into the application without editing core files. An upgrade replaces the core and the extensions either continue working or announce that they do not. The board stays close to stock, which means the upgrade stays routine.

MyBB has an established plugin system with the same virtue, and it also has a long tradition of theme and template edits made directly through the admin panel. That flexibility is genuinely useful and it accumulates: after a few years the installation has drifted from the release it claims to be, and an upgrade that should be routine becomes an afternoon of reconciling changes nobody documented.

Boards die of this far more often than they die of a security hole. The version stops being upgradeable, the upgrade is postponed, and eventually the board is running something unsupported with a migration nobody scheduled. It is not a criticism of either project — the same drift is possible on both — but the shape of the tooling makes it likelier in one.

Track record and what it predicts

Both have shipped for two decades, which is the strongest thing that can be said about community software. The useful distinction is in cadence rather than age.

phpBB is the larger project by some distance: more installations, a bigger extension catalogue, and more people who have already solved whatever you are about to hit. Its releases are deliberate to the point of slow, which is a virtue in a board and a frustration when you are waiting for something.

MyBB is smaller and has historically moved in bursts — periods of steady releases separated by quieter stretches. The activity band in the table above reads the last commit to each public repository, which is the cheap version of this check; the fuller one is to look at how quickly a question gets an answer in each project's own support forum, since both run on their own software.

The interface, and who your members are

Both look like forums. That is the point of both, and for a membership that is not technically inclined it is worth more than any modern alternative.

MyBB's default is a little lighter and its admin panel is the friendlier of the two — noticeably so for somebody administering a board for the first time. phpBB's administration is more thorough and correspondingly denser, which pays off on a board with real permission complexity and gets in the way on one without.

If a volunteer will be running this, spend an hour in each admin panel before deciding. That hour predicts more of the next three years than any feature comparison, because the person who finds the interface tolerable is the person who will still be applying updates in year three.

Hosting, spam and the ordinary running of it

Identical, essentially. Both install on shared hosting with PHP and MySQL, both are cheap to run, both are found by automated signups within days of going live, and both defend against it the same way: approval for first posts, a registration question a script cannot answer, and a rate limit.

All three settings exist on both and both get them switched off during the quiet early months because they add friction — which is exactly when the board is least able to absorb the consequence. That failure is universal and has nothing to do with which one you pick.

Search, and the archive nobody can retrieve

Both hand search to the database, and both are adequate up to a few tens of thousands of posts before degrading into something members stop using. Neither has an advantage worth stating.

What matters more than the difference between them is the consequence they share. When internal search stops being useful, members go to a search engine instead — which works only if the board is public and indexable. A board behind a login with weak internal search has lost access to its own history while still storing it, and that is a configuration decision rather than a software one.

Themes, and the number that misleads

Both advertise large theme catalogues, and the count is the least useful figure either project publishes. What matters is whether the one you end up using survives the next major release, and a platform with six maintained themes is in better shape than one with two hundred abandoned ones.

The practical difference is where the customisation lives. MyBB's templates are edited through the admin panel, which is quick and puts the changes in the database — convenient, and easy to lose track of. phpBB's styles are files, which is slower to work with and much easier to keep in version control, back up and reason about when an upgrade goes wrong.

For a board that will be customised at all, that difference compounds. A theme kept in files can be diffed against the release it was built for; one accumulated through an admin panel usually cannot.

Mobile, which is most of the room

Both ship responsive default themes and both were designed before phones were the main way people read a forum. Neither is unusable and neither is pleasant in the way software built for a phone is pleasant.

What to test, on an actual phone rather than a resized window: whether the reply box is reachable without scrolling past the whole thread, whether quoting works with a touch keyboard open, and whether the category list is one tap away rather than three. The differences between the two boards here are smaller than the differences between their themes, which is a good argument for choosing the theme deliberately rather than accepting the default.

Moving, in either direction

Discourse ships maintained importers for both, so either board can leave for a modern platform along a well-trodden path. Between the two, migration tooling exists but is less formal, and the honest advice is that moving from one to the other is rarely worth it — they are close enough that the migration costs more than it resolves.

If a move is happening anyway, the addresses are the part thrown away by accident. Both boards number topics in the address, and an importer that renumbers them discards every link ever made unless the mapping is captured during the import. That procedure is in the migration guide.

What neither of them will do

Both are boards, and a board is one shape of conversation. If what the group actually needs is coordination that scrolls, a chat server fits better and nobody has to pretend threads are useful. If it is reactions under articles you publish elsewhere, a comment server is a fraction of the work and does not create a second place that has to look alive.

That sounds obvious and it is the most common expensive mistake in this category — a board adopted because a board is what communities have, then quietly abandoned because the group was never going to write threads. Deciding the shape before the software is covered in the picker.

Deciding

Take phpBB if the board will be large, if permissions will be complicated, or if the reassurance of the biggest ecosystem matters — the answer to your question probably already exists.

Take MyBB if a volunteer is administering it and the friendlier admin panel is what keeps them doing it, or if something will be built on top of the board rather than inside it.

Whichever you choose, the decision that actually determines whether the board is alive in five years is made afterwards: keep the installation close to stock, and apply the point releases. Every modification is borrowed against a future upgrade, and on a small board the feature is rarely worth the debt.