Quick answer

Choose Flatboard if you're starting fresh and want a forum that works in 2026 without fighting a codebase built in 2004. No MySQL, no manual updates, actively maintained.

Stick with SMF if your community is already running on it and you have no compelling reason to move. SMF still works. It's just not going anywhere fast.

The SMF situation

Simple Machines Forum launched in 2004. SMF 2.0 came out in 2011. The next major release, SMF 2.1, shipped in 2022 — after eleven years in development. SMF 3.0 is in progress.
Running a community on SMF 2.1 today is fine. But if you're starting a new forum in 2026, that eleven-year release cycle is something to think about. Not a dealbreaker — but worth knowing before you commit.

At a glance

CriterionFlatboardSMF 2.1
Initial release20192004
Latest stable5.6 (2026)2.1.x (2022)
DatabaseNone (JSON) or SQLite (Pro)MySQL required
Installation3–5 min, browser wizard15–30 min, MySQL first
Mobile interface✅ Responsive⚠️ Partial
PHP 8.x support✅ Full✅ 2.1.x
UpdatesAdmin panel, one clickManual file upload
PriceFree / $49 ProFree
Active development✅ Regular releases⚠️ Slow cadence

Installation

Flatboard: upload files, set permissions on two folders, run a browser wizard. Five minutes, no MySQL, no credentials to configure.

SMF: create a database, create a user, assign privileges, upload files via FTP, run the installer with your database credentials, hope the MySQL version on your host cooperates, delete the install directory when done. It works — it's just a lot of steps for something that should be simple.

The MySQL dependency

SMF needs MySQL. That's manageable on most hosts, but it adds friction that's easy to underestimate. Backups aren't a folder copy — they're a MySQL dump. Moving hosts means exporting the database, importing it somewhere else, updating connection strings. Shared hosting plans limit your database count.
Flatboard's default storage is flat JSON files. A backup is a folder copy. Moving hosts is a folder copy. There are no connection strings. This sounds trivial until you've actually had to restore a forum from a broken MySQL dump at 11pm.
If you're migrating an existing SMF install, you're already on MySQL and this doesn't change anything. If you're starting fresh, it's worth asking whether you actually need a database.

Interface

SMF 2.1 updated the default theme — it's better than it was. It still looks like a traditional bulletin board from the early 2010s. Mobile works but wasn't the primary design target.
Flatboard's interface is responsive from the ground up. Dark mode is built in. It doesn't feel like it was designed around 1024px desktop monitors.
Neither product is going to win design awards. But first impressions from mobile matter more than they did in 2004, and there's a difference between "works on mobile" and "was designed for mobile."

Mods and plugins

SMF has thousands of mods built up over twenty years. A meaningful number haven't been touched since the SMF 2.0 era, which means PHP 8.x compatibility and SMF 2.1 behavior are untested. The catalog is large; the maintenance is hit or miss.
Flatboard's plugin ecosystem is smaller and newer. The core Pro plugins (private messaging, CMS/blog, moderation, analytics) are maintained with every release. If there's a specific SMF mod your community depends on, check whether a Flatboard equivalent exists before committing to a migration. That's the real question — not the platform in the abstract.

Updates

Keeping SMF updated means downloading a package, extracting it, uploading files via FTP, and running an upgrade script. For a minor patch it's manageable. For a major version it's more work.
Flatboard updates from the admin panel. When a security issue shows up, a patch releases quickly. One click to apply it. No FTP, no upgrade script.

Migrating from SMF

The ForumImporter plugin (Pro) handles SMF imports: users, categories, threads, posts. Hashed passwords can't be transferred, so members will need to reset on first login — that's standard for any cross-platform migration, not a Flatboard limitation.
For large installations or forums with a lot of mods, run the migration on a staging copy first. Heavy mod usage sometimes means data in non-standard tables that the importer won't know about.

Verdict

SMF isn't a bad product. A lot of communities ran on it for years with no real problems. The honest question is whether you want to build something new on a platform where the previous major release took eleven years.
Flatboard is a different bet. Newer codebase, active development, no MySQL required. The tradeoff is a smaller mod ecosystem and a shorter track record.

ProfileRecommendation
Starting a new forum⭐ Flatboard
Existing SMF community, no reason to moveStay on SMF
Existing SMF community wanting to modernizeFlatboard (test migration first)
Depend on a specific SMF modCheck equivalent exists before switching
Shared hosting, MySQL not available⭐ Flatboard only

Get started

Edited on  May 16, 2026  By  Fred .