Forums made simple. Modern, fast, and free!


Elegant UI

Mobile First


Fast & Light



Localised into many languages with 34 translation packs

bahasa melayu
brazilian portuguese
swedish for flarum
bosnian language pack for flarum core and multiple extensions
flarum lolcat



A perfect example of Flarum's customizability. This highly customised Dutch developer community has a unique layout, with beautiful elements like a custom loader. Created by the author of the popular SEO and Support Platform extensions.

Ten Digit Grid

An avid adventurer and hiker, Mike has found Flarum to be an excellent platform for blogging about his trips, discussing gear, and meeting fellow hiking enthusiasts while slowly increasing engagement.

UPC Switzerland

Leading provider of communication and entertainment in Switzerland. Their Flarum community creates a framework for healthy togetherness while supporting their customers with an appealing, user-friendly community experience.


Flarum 1.1.0 Released

v1.1.0 - Platypus

  • ‼️ New spoiler and strike-through buttons for Markdown
  • 🦶 Post footers are now hidden when empty, reducing whitespace
  • 🗜️ Code blocks now have a maximum height
  • 🤖 Accessibility improvements for search, checkboxes, and icons
  • 🎨 New theme extenders to override entire Less files
  • ⏱️ New frontend asset preloading extender, used by default to preload FontAwesome, JS and CSS
  • 🙈 New no-JS admin dashboard, for when that pesky extension breaks everything
  • 🙆 Replaced usernames with display names in more places
  • 💻️ Various frontend typing improvements for developers
  • ℹ️ php flarum info now shows your forum MySQL version
  • 🐛 Loads more bug fixes
  • 🆕 ...and much more!

📣 The release

Woah, how time flies! It feels like just last week that we hit Flarum's 1.0 stable milestone. But now another release cycle has passed, and we're happy to welcome to the stage (trumpet noises)... Flarum 1.1! 🎺 🎉
A fair bit has changed with Flarum in 1.1. We've been mainly focusing on bugfixes, extensibility and developer improvements, along with a sprinkling of accessibility.
Most extensions should face no breaking changes, but those with deep integration into the frontend may have some slight hiccups before they're updated for 1.1.
For a full list of changes, check out our changelog and upgrade guide.

👨‍💻 For Developers

Most extensions should be ready-to-go on Flarum 1.1 out of the box. If you're overriding component views, or directly manipulating the DOM, you might need to implement some minor changes in some areas.
For theming, we have switched to CSS custom properties wherever possible. You can finally remove your horrible !important properties from your colour modifications, and switch to the applicable custom property overrides. Check out the pull request for more info.

⤴️ Upgrading

Before you upgrade, make sure to create a backup of your public/assets directory, your composer.json and your database!
Before starting the upgrade process, ensure you are on Flarum 1.0.0 or above in your Admin Dashboard or by typing php flarum info. If you're not, use the previous release notes for upgrading from an earlier version.
To upgrade from 1.0 to 1.1, take a look at our upgrade guide documentation. The process should be much easier compared to previous major version upgrades, due to the lack of breaking changes.
If you run into any issues, please open a new discussion under the Support tag. Ignore similar discussions, and open a new one anyhow. Make sure to mention the output of php flarum info, composer why-not flarum/core v1.1.0 and any errors in their fullest.

🙇‍♀️ Acknowledgements

Flarum wouldn't be the same without our over one hundred contributors, along with their generous time commitments! For this release we specifically thank these wonderful people:

🆘 Support the Project

We need your support to:
  • Guarantee continued development on the software.
  • Create a valuable ecosystem around the project.
  • Ensure healthy extensions are available.
You can support us:
  • 👕 By getting some swag from our merchandise store!
  • 💵 By backing us on Open Collective or on GitHub.
  • 👩‍💻 By contributing to the source code, hop onto any of our open issues.
  • 📈 By creating your own Flarum extensions and sharing them with the world!
  • 🌎 By translating Flarum and extensions into your own language.
  • 💝 By sharing your love for Flarum with friends, family and on the internet.
  • 💬 By hanging out with us, here on discuss!
If you're looking to get coding, make sure to check out our documentation.

🔮 What now?

We're currently planning our kick-off meeting for build 19 (v1.2), as well as discussing future roadmaps and strategy ready for v2. Hopefully, we'll have a roadmap for v2.0 up soon!
There might be a couple of minor patches between v1.1 and v1.2 where we address minor bugs, so keep an eye out for those.
Dev Diary: Build 19
v1.1 was just released 🥳
Time for a new dev diary, with the hopes of making this a bit more active than the last one 👍️
Flarum v1 Release Announcements
This discussion acts as a way for people to subscribe to announcements on releases. Before stable we would announce releases as separate discussions, because all changes were bundled and released as one beta.
Having passed that milestone we have already released several patch releases for v1.0. These releases were announced either in the v1.0 release announcement or in the Dev Diary. We felt this is not the right place.
From now on we will announce ALL releases, no matter the size, in this discussion. 🔔 So make sure to follow.
  • ⏰ Releases for Flarum and all bundled extensions are announced here and/or linked to.
  • 🔇 Comments are disabled. Please open a discussion for feedback or support.
Previous Release Announcements
Community Updates 09/2021

📖 Introduction

For this community update we once again want to focus on supporting community administrators by showing possibly solutions to tackling the spam problem most communities deal with. If you are new to our Community Updates format, we hope that you also check out the last edition - including a stunning interview with a leading Flarum community.

🤦 Tackling "the spam problem"

Every community out in the public will eventually have to face the problem with spam. Both automatically and manually created content can have a big negative impact on a community and to other community members. Therefor as a community administrator fighting spam is always a high objective. But what options do you have using Flarum? Today we are going to look at different approaches tackling the "spam problem".

®️ Registration of new users

Every spam contribution starts with the registration of a new users. The ultimate border of course is closing registration all together - but this is not what most communities strive for. Here are several ways to optimise the signup of new users:

Doorman - making your community invite only

Although this solution might only be applicable for some communities, you have the option to make your Flarum invite-only quite easily. The extension in question is called Doorman. It will allow signup only for people holding an invitation code.

Captcha - making a bots' live so much harder

Some (not all!) spam is created automatically by bots. Making live harder for them registering in your community can improve spam a lot. Captchas have been some of the well established forms of getting rid of this kind of spam. There are two different solutions available for Flarum reCaptcha and hCaptcha. Besides the possibility to integrate it into the registration process it can also be used for discussion / post creation.

StopForumSpam - using the collective knowledge of many communities

StopForumSpam holds a database of potentially spammers that have been caught on other communities already. With the according StopForumSpam extension for Flarum you can profit from this vast data. In the context of this extension the Spamblock extension has to be highlighted as well. On the one hand it automates blocking and removing content, on the other hand it contributes to the StopForumSpam database (if both extensions are used).

Blocking access - tightening the target audience

Another option you have is to manage who is able to access / join your community. Banning IPs can be done on server level - or also with a Flarum extension. During registration you can use both E-Mail and Username black/whitelists to narrow the audience.

🔒️ Managing access rights

The second line of defence for your community starts with the spammer being already a member, passing the registration obstacles. Although your community most likely wants to be as inclusive as possible to new members you want to keep control over the spam problem.

AutoModerator - introducing trust levels

Auto Moderator is a extension allowing complex validations for automatic group assignments. This allows you to easily build trust levels. This allows you to keep new users from spreading spam too quickly. For example they could be required to use Captcha for posting, are not allowed to edit their user bio, are not allowed to use private discussions, etc. A secondary group that is automatically assigned after a certain number of posts, received likes, etc. could then allow extended rights - as spammers have already been sorted out by moderation staff and do not reach such milestones. The possibilities to use this are sheer endless.

Akismet - verifying the content

Running posted content against a spam analysis is also a popular option. Wordpress has been using this for it's commenting system for a long time. There is also a Flarum extension to allow running content against the Akismet service.

First Post Approval - keeping a tight moderation

If you are willing to make a tradeoff for people being able to jump into your community right away (or have a very active moderation team) you can also require first posts of new users approval first. With the FirstPostApproval extension you can most likely block out a lot of spam.

👮 It has happened - what now?

Eventually some spam will make it through all your defensive lines that you have built. Now your focus will shift to handling the spam and making work of your moderation wonders.

Spamblock - automate the obvious

As mentioned above, the Spamblock extension will help you automate the indefinite suspension and deleting of all posted content with one click. Also (if used) it will submit the spammers data to the StopForumSpam database.

Shadowban - keeping it from happening again

Especially for human spammers it might be a valid option to make them unaware you have caught onto their spammy behaviour. In this case there is a sneaky extension called ShadowBan allowing for a different kind of suspension behaviour.

🛫 Conclusion - is there a solution?

As you can see from the large list of available options - tackling the spam problem is something you will share with most community administrators. Every community needs to find their own fitting way to approach the spam issue. This list of possibilities hopefully is a good starting point to you.

📰 Other News

Blomstra (managed Flarum hosting) company has launched it's service to the public. You can learn more about Blomstra and the offering here: https://discuss.flarum.org/d/25875-blomstra-development-services-scalable-managed-flarum/90.

🕸️ Extension Highlights

New additions

🏁 Final words

The Flarum team is extremely grateful for its great community. We hope to have given you a comprehensive overview of some highlights. Next time we will feature one of our own core developers in an interview format. Read you next time!
Dev Diary: Build 18
Welcome to the next cycle, the first post-stable release.
Share in our excitement of releasing stable on the Announcement 🥳
We'll post information about our plans soon ™️ , but first we'll take a bit of time off to relax after our months of effort in releasing stable. We'll follow up with support and bug reports in a timely manner.



Learn how to harness the extensibility of Flarum to create your own extensions and customize your community.



Help us make Flarum even more powerful and customizable! Every bug report, pull request, and documentation improvement is a huge help.


Built with the best tools

Have you ever changed tires with a spoon? Using the right tools for the job is key to success. We thank our technology partners for their generous product donations!