When its time to ask everybody to move to Brave (Chromium)?

Right now I am using Brave regular, Brave Chromium (Beta) and Brave Chromium (Dev). The Brave Chromium browsers I try to use most of the time and give feedback if I need to. But if Brave is going to be based on Chromium as in Brave Chromium (Beta and Dev) is there any use in reporting bug or giving feedback on Brave Regular which is based on muon? Or does it have a long term implication on the soon to be out Brave browser?
I just wanted to clear my doubt which I had for the past couple of weeks.



If users really need extension, specific features, etc then we can offer Brave Beta. But for general users, I believe the best when is when it’s hit Release version. Since this version will be more stable than Beta or Dev.

No direct connection from Brave stable release (Muon) and Brave Beta or Dev. But as long as Brave stable release is still there, I think it’s OK to report any issue. Because this version will still receive bug fix. At least until the migration day.


@nellaiseemai, excellent question! I will address this directly, but I’m going to broaden the scope of your question a bit as I think others would benefit from knowing these things.

This is both a very exciting time for Brave users (and staff!). The transition to the new build/1.0, a Beta release, Developer release, and live “stable” build (Muon) may be confusing to users who may not have been exposed to the concepts of an open source project or the software development process. So I’ll take a moment here to (hopefully) clear up any confusion surrounding the multiple Brave builds, requesting support, and giving feedback:

So many builds - which one should I use?
If you were to look in our GitHub repository, you’ll notice that we have a repo for Browser-laptop and one for Brave-browser. These are the repositories for the Muon build of Brave (v0.24.0) and for Brave 1.0/Beta (v0.55.11 as of writing this) respectively. Within these repositories, you can view the release channels for each build of the browser. Each channel is, essentially, its own install of Brave and can be run in parallel with any other Brave build you have on your machine. We technically have more than 4 total channels in which builds are released on but I’m going to stick to the ones relevant to this discussion:

  • Developer Channel - Dev channel builds are (for the purposes of this discussion) the first build some new feature or design implementation will hit. Features seen here are usually experimental/unstable. These are features that are being implemented that aren’t yet ready for daily use. Once they are, they’ll be added to the Beta build.

  • Beta Channel - Builds on the Beta Channel have the new recently implemented changes that seem stable and are ready for further testing with a broader audience. More use cases means more tests for whatever changes were made allowing us to further refine them before they’re pushed to the release channel.

  • Release Channel - Builds pushed through the Release Channel are live, stable, operational builds of Brave - the “Main” channel. If you go to the official download page, this is the build you’ll be downloading. This is where our previous Muon build lives used to live.

In a couple weeks, the Release Channel switch from Muon to Brave Beta and subsequently be the “official” The Muon build has since been depreciated and bumped down from the Release Channel in favor of our Brave Core build download link. Soon there after, when Brave-core is ready, it will be moved into the release channel and the current Dev/Beta channels will become Brave-core Beta and Brave-core Developer.

Should I still be reporting/giving feedback for the previous Brave build?
Sure! Brave will continue to provide support for the Muon build for those who want to continue using it all the way up until Brave-core goes live. However, Dev/Beta build support and feedback are currently our priority and we are frequently pushing users to move over to Brave Beta. Given how close we are to releasing Brave-core, it would be inefficient for us to continue logging new issues and providing the same level of support for the Muon build - especially since Beta build addresses many of the known problems present in it.

Community will undergo a redesign of its own right around launch time in an effort to keep support and feedback better organized and clearer for users to navigate. It’ll also look real slick!

Hopefully this clears some things up. If you have additional questions don’t hesitate to ask.


Thank you so much for your detailed explanation. I will keep reporting whenever I find something strange or give my feedback on any of the Brave I am using.
Yes its really exciting time to be a Brave user.
Its a difficult choice to leave Brave (muon) as it was the first love from Brave family.

I would also like to start a discussion (not here, somewhere else) about what are the privacy extensions which people normally use in other chromium based browsers are compatible or good to go with Brave Chromium. examples such as ublock origin, HTTPS Everywhere, Privacy Badger etc which of these are OK and which of these are redundant or conflict with Brave. I guess I asked this before somewhere. But when Brave chromium comes in to prominent this will help others too.

Eagerly waiting for Brave 1.0.

Hi @Mattches,

Thanks so much for this detailed explanation!! :smile:

Now some questions:
Is it then that since October 18, the official download is Brave Beta?

Also, is Brave-core the live/stable Brave? Confused about the Brave-core (Beta/Developer) thing :slightly_frowning_face:

Hi @Grace,

Brave-core is already hit stable release version. Brave that you download from brave.com/download will give you the latest stable which is now on 0.55.x. Except if you download it from the Beta or Dev download page. :sweat_smile:

Blog New Brave Browser Release Available for General Download on Brave.com | Brave Browser

Hope that clear for you.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.