Find answers to common questions, or report a bug directly on GitHub. We aim to respond within a few days.
Report it on GitHub Issues. Include what happened, what you expected, and which browser/version you're using. If the extension stopped working after a Rumble update, the fix is usually quick — see the guide below.
Open an Issue on GitHub →Rumble occasionally changes the HTML class names in their chat, which breaks the selector the extension uses to find usernames. This is the most common issue and is usually an easy fix. See the "How to fix broken selectors" guide below — it takes about 2 minutes.
You can also open a GitHub issue and we'll push a selector update.
Messages that loaded before you clicked Mute will still be visible — the extension only hides new messages going forward. To clear them, reload the page. All future messages from that user will be hidden immediately.
Open Chrome DevTools on any Rumble stream (press F12, then click the Console tab). About 5 seconds after the page loads, you'll see one of two messages:
✅ [Rumble Chat Muter] Selectors OK — container found, X message rows... — everything is working.
⚠️ [Rumble Chat Muter] One or more selectors failed... — followed by a table showing exactly what broke and what to fix.
Not automatically — mutes are stored locally on the device where you installed the extension. To move your list to another device, use the Export button in the extension popup to download a JSON file, then Import it on the other device.
Yes. Edge is built on the same Chromium engine as Chrome and supports all Chrome extensions natively. Install it from the Microsoft Edge Add-ons store for the best experience, or you can load it manually in developer mode using the same zip file.
No. Muting is entirely local — it only affects what you see in your browser. The muted user's messages still appear normally for everyone else. They have no idea.
No. Your mute list is stored locally using Chrome's built-in storage API only. Nothing is ever transmitted to any server. There are no analytics, no tracking, and no servers of any kind. See the full privacy policy for complete details.
This guide is for when the extension stops finding usernames after a Rumble site update. It takes about 2 minutes to fix.
Any live stream works. Make sure the chat panel is open and showing messages.
This opens DevTools with the username element highlighted. Note the class name on the element — something like .chat-history--username or whatever Rumble is now using.
In DevTools, click the parent elements upward from the username until you find the element wrapping the entire message (usually a <li> or a <div> with a distinctive class). Note that class name too.
content.js and update the SELECTORS object
At the top of the file, find the SELECTORS object and prepend the new class names to the front of each array. Keep the old ones as fallbacks.
Go to chrome://extensions, click the ↻ refresh icon on the Rumble Chat Muter card, then reload your Rumble tab. Check the console for the ✅ confirmation message.
Open a GitHub issue with the new class names and we'll push a proper update for everyone.