Your Input Matters

The "YouTube Control Center" is a lightweight, yet highly efficient extension for Firefox that controls various YouTube playback parameters in order to enhance your experience. The extension has two primary building blocks. First one is the control center panel. When a new YouTube music is streamed, different playback parameters can be controlled right from the panel without the need to switch to the actual YouTube tab. The second part of this extension is the controls that are injected in YouTube pages to change the UI and control volume, quality, and theme of the player.

Features

Set preferred playback quality for all videos
Set preferred video playback volume for all videos [XUL version only]
Control autoplay behavior of the YouTube player
Control autobuffer behavior of the YouTube player
Auto pause all YouTube players when a new player starts playing [XUL version only]
Show video annotations on the player
Show video controls on player [XUL version only]
Autohide video controls after a video begins playing [XUL version only]
Play a single video in loop mode [XUL version only]
Change video player theme [XUL version only]
Hide/Show "video comments" pane
Hide/Show "video views info" pane
Hide/Show "action buttons" pane ("like", "dislike", "share", ... buttons)
Hide/Show details" pane (published info, buy video, ...)
Show video controls even in full-screen mode
Disable auto play next track from playlist
Load requested features from GitHub

Top+1000+hindi+songs+of+90s+zip+file+download+hot+free May 2026

(Insert Call-to-Action button: Download Now)

Matched Content

Preview

Reviews

Please keep reviews clean, avoid improper language, and do not post any personal information. Also, please consider sharing your valuable input on the official store.

What's new in this version

Change Logs:

Last 10 commits on GitHub

Hover over a node to see more details

Need help?

If you have questions about the extension, or ideas on how to improve it, please post them on the support site. Don't forget to search through the bug reports first as most likely your question/bug report has already been reported or there is a workaround posted for it.

Editorial Review