The Video Controls Plus features page is a complete catalog of every capability the extension ships with — speed control from 0.1x to 16x, A-B looping with saveable presets, audio boost up to 400%, six CSS-based video filters, one-click frame screenshots, timestamped notes, more than forty keyboard shortcuts, and optional cloud sync. Each feature is listed with its keyboard shortcut, the platforms it works on, and any limits imposed by the browser or the streaming service. Use this page to decide whether the extension covers the workflows you care about before you install it.
Before installing, scan the catalog for the specific capability — for example, does the extension support per-site speed defaults, can it normalize audio across episodes, does it expose a public keyboard binding API. The answer is on the features page; you do not need to install first to find out.
Each feature lists its scope (which platforms, which file types, which DRM tiers). Pair this page with the comparison hub at /compare/extensions to see how Video Controls Plus stacks up against single-purpose tools.
The page documents settings that are not obvious from the popup — for example, custom keybindings, overlay opacity, audio-boost cap, and the events the extension exposes for keyboard automation tools.
Send the link as a single self-contained reference. Every claim has the keyboard shortcut and the limitation in the same line, so the reader can decide which features matter without back-and-forth.
Yes. Speed, loop, audio boost, filters, screenshots, and notes work fully offline with no sign-in. Cloud sync, learning paths, and shared collections require sign-in because they need a backend.
Audio boost is capped at 400% by browser audio policy and may sit lower on DRM-protected services. Screenshots return a black frame on some Widevine-protected titles. Speed is capped at 16x because most decoders skip frames above that point.
Yes. The features page links to Settings → Features where every capability has a toggle; disabled features stay out of the overlay, the right-click menu, and the keyboard binding registry.
No. Filters are CSS-based and apply to the rendered video element only. The underlying stream is unchanged, so nothing in your network history changes when filters are on.
Yes for any iframe that hosts a real HTML5 video element on the same origin policy. Some embedded players (sandboxed iframes from third parties) restrict extension access; in those cases the overlay does not appear.
Yes — the public roadmap lives at /feature-requests where you can vote on which feature ships next. Confirmed work-in-progress items are tagged "in development".
Last updated 2026-05-06 by Ahsan Mahmood, maintainer.