opened 07:39AM - 03 Mar 25 UTC
New Chrome version (133.0.6943.142) doesn't support violentmonkey anymore. Can y… ou make it support new Chrome version?
Seems like between the last nightly version and this one, the manifest v2 code was removed from chromium which caused Violetmonkey to stop working
Will Brave continue working with Manifest V2 support?
the flag (brave://flags/): Brave Extensions manifestV2 is still enabled
Brave 1.93.75 (Official Version) nightly (arm64)
Another thread about manifest v2
opened 07:08AM - 20 May 26 UTC
closed 09:00PM - 13 Jun 26 UTC
discussion
TL;DR: Regular Google Chrome removes support for distribution of MV2 extensions.… Users wishing to continue using MV2 extensions should consider either (1) migrating to Google Chrome Enterprise & Education extension distribution mechanisms, (2) migration to a non-Chromium browser like Firefox or Apple Safari, or (3) Chromium fork which still supports MV2 extensions.
This is not a specification question or standards discussion, I just think that WECG might find these news interesting.
Google Chrome team just started removing the flags responsible for MV2 availability in Google Chrome. Specifically, here is a copy of [message from Devlin](https://chromium-review.googlesource.com/c/chromium/src/+/7813942):
> MV2 extensions are no longer allowed in any supported version of Chrome, and we are removing support for them and the associated functionality. We won't be able to provide / maintain this functionality indefinitely due to the complexity and tech debt, as well as the security risks it entails (we've actually found a number of bugs that are specific to MV2 lately). Of course, other browsers can continue supporting these if they so desire.
> Unfortunately, we won't be putting code behind a compilation flag ... We won't be removing all the MV2 code wholesale right away, so many of these things will continue working for awhile (but they will go away eventually, and some may go away sooner than others).
>
> I can certainly understand the desire to keep using these extensions, and IIRC, many of the Chromium forks plan to continue supporting MV2 indefinitely.
Chromium 150 lost `kExtensionManifestV2Disabled` flag ([commit](https://chromiumdash.appspot.com/commit/e768ae9db49404408d13d22a4e9f7d81b095dab8)) and will not be able to install MV2 extensions from Chrome Web Store. In Google Chrome, Blocking WebRequest permission is available only to MV2 extensions or policy-installed extensions. Users will still be able to load extensions in debug mode via "allow legacy MV2 extensions" flag. Other Chromium-based browsers will be able to relatively trivially continue support for MV2 and blocking WebRequest, at least for now.
As of 9 June 2026:
Chromium 150 lost `ExtensionManifestV2Disabled` option ([commit in Beta 150](https://chromiumdash.appspot.com/commit/e768ae9db49404408d13d22a4e9f7d81b095dab8))
Chromium 151 will loose `ExtensionManifestV2Unsupported` option ([commit in Canary 151](https://chromiumdash.appspot.com/commit/dd11f12d82d243ff834a6949a9346392820f2a0a))
Chromium 151 will loose `ExtensionManifestV2Availability` option ([commit in Canary 151](https://chromiumdash.appspot.com/commit/993e57a3e1af70dcad63122ef1ea98835cf8a1f2))
Chromium 151 will loose `AllowLegacyMV2Extensions` option ([commit in Canary 151](https://chromiumdash.appspot.com/commit/df12ca035ced7f8026c717eea14a4b406e9df574))
Patching `g_allow_mv2_for_testing` is still effective for enabling MV2 extensions.
There is plenty of Chromium-based browsers which pledged to support MV2 extensions going forward.
This doesn’t help because Violetmonkey isn’t a AdBlocker, and Brave is not self-hosting that extension.
just today, violentmonkey and MyJDownloader also not working on my Windows machine
Brave 1.92.134 (Official Build) (64-bit)
Ah this is really unfortunate, hopefully some sort of support comes back for userscript extensions. For power users its utility is amazing. Off to firefox in the meantime I suppose!
Awesome! Another alternative recommended and starred by fmhy is ScriptCat
ScriptCat is a powerful open-source browser script engine that lets you easily customize web functionality, eliminate ads, automate tasks, and enhance your browsing experience. Compatible with Tampermonkey with more features.
been using since the initial post, but will switch back to a minimal lightweight extension when mv3 support is out
here’s a table comparison using gemini, the v3 support is wrong on violentmonkey, but hopefully not for long
iqbalsp:
MyJDownloader
It’s unlikely that Brave will do anything about it, try other download managers such as AB Downloader Manager , IDM (See fmhy link below which will lead to others apps)
Today, my Brave was updated to Brave 1.92.134, and now many extensions have stopped working. Of course, I can still enable Ublock Origin through V2 settings, but then i lost all of my custom filters, and i still can’t enable other extensions. It’s sad, I guess I’ll have to switch to FireFox until the Brave developers fix compatibility again.
289wk
July 3, 2026, 8:49am
10
According to Brave Search (Answer with AI ):
OLD NEWS:
Official Stance : The official Violentmonkey website states that a Manifest V3 rewrite “is not planned for the foreseeable future ” due to the “considerable effort involved and the potential for losing existing features.”
GitHub Activity : The primary feature request for Manifest V3 support (Issue #1934 ) has been open since October 2023 with over 150 comments but no commits or branches indicating active migration work. Recent issues (e.g., #2340 from July 2025) confirm the extension remains stuck on Manifest V2 and is now disabled in modern Chromium browsers.
Developer Sentiment : Community discussions and forum posts indicate the developers are reluctant to update , citing technical hurdles such as Manifest V3’s ban on remotely hosted code (a core feature for userscript managers) and the complexity of rewriting the extension without losing functionality.
‘https://violentmonkey.github.io/ ’
That last line in there? No longer applies. Brave is not a V2 alternative.
Temporary workaround:
A temporary solution is to revert to a previous version. 1.91.178 does not have this issue. This version can be downloaded from Brave’s GitHub Release section. You should also disable Brave’s auto updater. On Windows this can be done by removing all Brave entries from the Task Scheduler I believe.
I also use the Violentmonkey extension and the scripts were not lost in the process.
Brave Browser stable release v1.91.178:
‘https://github.com/brave/brave-browser/releases/tag/v1.91.178 ’
20260704 Saturday UPDATE
tophf is working on ViolentMonkey ManifestV3
H/T @e7b6143f0312273c004b
Thanks, it’s works for me
Why would you post this outdated info after I just posted that MV3 is being worked on?
opened 07:39AM - 03 Mar 25 UTC
New Chrome version (133.0.6943.142) doesn't support violentmonkey anymore. Can y… ou make it support new Chrome version?
Switch to Microsoft Edge, they still support MV2, even in their development branch whereas Brave joined the google bandwagon.
