phpBB

Last reviewed Sep 13, 2026 · 891 words

Hosting cost decides most phpBB installs before features get a vote. phpBB runs on PHP and a MySQL, MariaDB, PostgreSQL or SQLite database, on 256 MB of RAM, on the same shared hosting plan that serves a WordPress blog for a few dollars a month. Discourse, the forum everyone compares it against, wants a dedicated box with 2 GB and Docker. If your community is a hobby, a club or a game's players and the budget is the shared host you already pay for, that gap is the answer. If you have a VPS and want the forum people expect to see in 2026, the gap closes and the comparison becomes fair, which is where phpBB starts to lose.

Twenty-five years, and the installer still fits on a USB stick

phpBB first shipped in 2000 and the 3.x line has been the stable branch since 2007. Installation is unchanged in spirit: download the zip from phpbb.com, upload it, create an empty database, open /install/ in a browser, fill in 5 forms, then delete the install directory. There is no official Docker image, though several community ones exist; the project's assumption is a LAMP host with FTP access, and its documentation and support forum are written for that person. The Administration Control Panel exposes everything from permissions to cron, and upgrades are "upload the changed files, run the updater", which is exactly as reliable as it sounds when you have a backup and exactly as terrifying when you do not.

The permission system is the reason institutions still run it

phpBB's permissions are built on roles applied to groups applied to forums, with granular overrides at every level and a "permission trace" tool that tells you why a particular user can or cannot see a particular forum. Moderators can be given specific powers on specific subforums, LDAP authentication is built in for organisations with a directory, and it all works without an extension. This is the feature set that keeps university departments, national hobby associations and support forums with 20 years of posts on phpBB: the archive stays searchable, the moderation model maps onto how volunteer teams actually work, and nobody has to relearn anything after an upgrade. Twenty years of posts is also a migration liability nothing else imports cleanly, which is a less flattering reason the same institutions stay.

Extensions and styles: 3 to install, 2 to avoid

The extension database on phpbb.com is curated and every listed extension passes a code review, which is rarer than it should be. The ones I would add on day one are a SEO or "pretty URL" extension for readable links, a spam-fighting extension that adds a question or honeypot to registration (bot registrations remain phpBB's most common operational problem), and a modern style such as one of the responsive prosilver derivatives, because the default prosilver theme is functional and dated. Avoid extensions that promise a "modern reactive" interface; they fight the page-load architecture and break on upgrades. Also avoid anything unmaintained since the last minor release, because the ACP will happily let you install it and then quietly disable it after the next update.

The interface is the honest weakness

Every action is a page load. Posting, quoting, paging through a thread, and checking notifications all round-trip the server, and there is no live update, no infinite scroll and no reactions out of the box. Search is the database's full-text search unless you configure Sphinx. Email notification works; push does not exist. Users who came from Reddit or Discord notice within a minute. On the other side of the ledger, the whole thing renders without JavaScript, is indexed perfectly by search engines, and loads in well under a second on hardware that Discourse would not boot on.

Discourse and Flarum are the modern siblings

Discourse is the default recommendation for a new community with a real server: live updates, excellent moderation tooling, a plugin ecosystem, and the best mobile experience of the three, at the cost of 2 GB of RAM and a Docker-only deployment its own team supports. Flarum is the middle path, a PHP forum with a single-page interface that still runs on shared hosting, though its extension ecosystem is smaller and its permission model simpler than phpBB's. NodeBB is the Node.js option with real-time everything and a Redis or Mongo dependency. The forums category lists more. Against vBulletin, phpBB has been the free replacement for two decades and the migration tools reflect it.

What I'd do

Shared hosting and a community that reads more than it chats: phpBB, with an anti-spam extension installed before the first public link, weekly database dumps, and a note in the calendar to check for a point release monthly. A VPS with 2 GB and a community that expects to feel like a chat app: Discourse, and accept the operational weight. Flarum only if I wanted a modern look on cheap hosting and could live with fewer extensions. What I would not do is choose phpBB for its ease and then spend 6 months trying to make it behave like Discourse; it is the best forum of its kind, and its kind is a bulletin board.