RumbleX

Open-source enhancement suite for Rumble

Your Rumble. Your rules.

Watch cleaner. Control more.

Block ads, reshape the player, download what you chose to watch, and tune the whole site to fit you. RumbleX brings 141 focused modules together without telemetry or an account.

Get RumbleX View the source

v3.61.0 current build Chrome, Edge, Brave, Firefox, userscript MIT licensed

141 feature modules

7complete themes

6languages

0trackers

One extension, four big upgrades

Start with a cleaner Rumble. Add only the tools that earn a place in your browser.

Clean the page before it distracts you

Scoped request blocking handles known ad hosts. Page cleanup removes overlays, premium prompts, Shorts, sponsored cards, and the empty space they leave behind.

Turn the player into a workspace

Theater Split puts video beside live chat, comments, or downloads. Add per-channel playback memory, chapters, transcripts, SponsorBlock, and a mini player when you want them.

Save media with useful fallbacks

Download direct MP4, convert HLS, export a clip, batch a feed, or queue a channel. Failure messages identify the stage that broke and point to the next practical option.

Keep your viewing data yours

Settings, watch activity, bookmarks, diagnostics, and undo snapshots stay local. The built-in Privacy Report shows every permission and network destination in plain language.

Designed for the whole session

The same dark visual system covers setup, deep settings, privacy, and controls on Rumble itself.

Searchable RumbleX settings editor — Search 141 modules from one editor.

RumbleX privacy report — See what is stored and why each permission exists.

RumbleX settings on a Rumble page — Change the essentials without leaving the video.

Install

Pick your browser. Every download comes from this project's Releases page.

Chrome, Edge, or Brave

Chromium 111 and newer. RumbleX uses color-mix() for themed translucent controls and the modern abort timeout API for bounded network work.

Download RumbleX-chrome.zip from the latest release and extract it.
Open chrome://extensions and turn on Developer mode.
Click Load unpacked and choose the folder you extracted.

Chrome shows a reminder about developer-mode extensions, and it won't update this install for you. Check back here or watch the repository for new releases. A signed RumbleX-chrome.crx is included for managed or policy-enabled browsers, but standard Chromium installs can reject direct CRX installation. The ZIP is the dependable route.

Firefox

Firefox 121 and newer. That release supports the :has() selectors and color-mix() styles RumbleX uses across its cleanup rules and themes. The current release provides an unsigned AMO submission for temporary testing. It is not a permanently installable add-on.

Download RumbleX-firefox-amo-unsigned.zip from the latest release and extract it.
Open about:debugging#/runtime/this-firefox and click Load Temporary Add-on.
Select manifest.json. Firefox removes the temporary add-on when it restarts.

A permanent RumbleX-firefox.xpi will appear only after Mozilla signs the submission. This page does not offer an unsigned ZIP as an installable XPI.

Userscript

For Tampermonkey, Violentmonkey, or ScriptCat. Two builds:

RumbleX.user.js is the complete build. It bundles the media workers, so downloads convert to MP4 in the browser.
RumbleX.lite.user.js is a smaller build without the bundled converters. Saving a raw stream still works, but MP4 remuxing doesn't.

Userscripts get most of the suite. The pieces that need a privileged background process stay out: the channel archive queue, alarms, native notifications, context menus, and the side panel.

Chrome and Edge need user scripts switched on.

A correctly installed userscript can sit there doing nothing until you give the manager permission to run user scripts. Nothing warns you on the page, so it looks exactly like RumbleX being broken.

Chrome 138 and newer: open chrome://extensions/?id=<your manager's ID>, or right-click the Tampermonkey icon and pick Manage extension, then turn on Allow User Scripts. It is per-extension and off by default on a new install. Chrome 137 and older use the global Developer mode switch at the top of chrome://extensions.
Edge: Edge has not shipped the per-extension toggle, and people still report it missing as recently as Edge 143. Use the Developer mode switch at the top of edge://extensions.

Reload the Rumble tab afterwards. If the RumbleX button still isn't there, a gated manager and a broken install look identical from the page. Open DevTools on any rumble.com page and run Object.keys(localStorage).filter(k => k.startsWith('rx_')). If it returns anything, RumbleX has run here before, so the match rules are fine and the problem is the toggle or a disabled script. An empty array proves nothing by itself, so check the manager's dashboard to see whether RumbleX is listed at all.

None of this applies to the extension builds. They have no userscript manager in the path.

Check what you downloaded

Every release ships SHA256SUMS.txt for the Chrome ZIP and CRX3, Firefox submission, source archive, and userscripts. This confirms the file arrived in one piece.

sha256sum -c SHA256SUMS.txt --ignore-missing

That proves the download wasn't corrupted or swapped in transit. It doesn't prove who built it, which is the part that matters if someone puts up a copy of this project somewhere else. When a release also carries SHA256SUMS.txt.sig, you can check the origin:

ssh-keygen -Y verify -f allowed_signers -I release@rumblex -n file \
  -s SHA256SUMS.txt.sig < SHA256SUMS.txt

Good "file" signature means the checksums came from the key published in the repository. If either check fails, don't install the files.

Only two official sources. This page, and github.com/SysAdminDoc/RumbleX. Copies of RumbleX hosted anywhere else aren't ours and we can't vouch for what's in them.

What it does to your data

Nothing leaves your browser unless you ask it to. There's no analytics, no remote logging, and no usage beacons anywhere in the code. Settings, watch progress, history, and bookmarks live in extension storage on your machine. Userscript installs keep activity in Rumble's site storage because a userscript has no extension store.

RumbleX only reaches the network for things you trigger: fetching a video you chose to download, checking GitHub for a newer release, and, if you switch it on yourself, syncing settings to a private Gist you own or posting to a Discord webhook you configured. The built-in Privacy Report lists every one of these, generated from the actual manifest rather than written by hand.

Permissions stay narrow on purpose. RumbleX asks for Rumble's domains, the ad hosts it blocks, and optional GitHub access for update checks or encrypted Gist sync.

Ad blocking, honestly

The request-level shield works differently on each runtime, so here's what actually happens:

Runtime	Early request blocking	What we claim
Chrome, Edge, Brave	Scoped Declarative Net Request rules	Enforced by the browser
Firefox	Scoped blocking webRequest	Enforced by the browser
Userscript managers	Only where the manager still offers the request hook	Depends on your manager, so we don't claim it

Current Chromium versions of Tampermonkey and Violentmonkey dropped that hook when they moved to Manifest V3. On those, the page cleanup still runs and still removes ads from the layout. It just can't cancel the request before it happens, and RumbleX says so in its own interface rather than pretending otherwise.