Stream Deck Native: Seventeen Actions, Zero Drivers
Plug a Stream Deck into Chrome and control your show instantly. No Companion, no drivers, no configuration files.
· Hardware · 9 min read
The shortest path between a physical button and a software action is the path with the fewest intermediaries. In broadcast engineering, this principle drives every decision about transport controls, from the hardware play button on a tape deck to the GPI triggers on a production switcher. Every layer of software between your finger and the result adds latency, adds a potential failure point, and adds something that needs to be updated, configured, and maintained. Timers Studio's native Stream Deck integration was built on this principle, eliminating every unnecessary layer between your physical button and the command that reaches every screen in the venue.
The integration uses WebHID, a browser API that allows web applications to communicate directly with Human Interface Devices connected via USB. When you plug an Elgato Stream Deck into a computer running Chrome or Edge, and navigate to a Timers Studio session, the browser detects the device and offers to connect it. No driver installation. No companion software. No middleware application running in the background. The browser becomes the driver, turning your Stream Deck into broadcast grade transport controls for your entire show [Try the zero drift experience].
The signal path is instructive. You press a physical button on the Stream Deck. The USB controller sends an HID report to the operating system. The operating system passes the report to the browser through the WebHID API. Timers Studio receives the report, identifies which button was pressed, and executes the mapped action. The total latency of this chain is sub frame, meaning the action completes before the display can update to show the next frame. For practical purposes, the button press and the result are simultaneous, exactly as a show caller expects when firing a cue from a physical cue list controller.
Seventeen actions are available through the native integration. The core transport controls are present: start, pause, stop, and reset for individual timers, plus next cue and previous cue for navigating the rundown. Beyond transport, you can send flash messages to the speaker's confidence monitor, toggle blackout mode across all connected players, adjust the time warp offset, and trigger custom actions defined in the rundown. There is also a dedicated "identify" action that makes all connected player screens flash briefly, which is invaluable during setup when you need to verify which physical screen corresponds to which browser tab.
The device compatibility covers the full Elgato Stream Deck family. The MK.2 with its fifteen buttons is the most common unit in production environments. The XL with thirty two buttons provides more surface area for complex shows. The Plus adds rotary encoders and an LCD touchstrip for continuous controls. The Mini with six buttons serves as a compact secondary control surface. The Pedal provides three foot operated buttons for hands free operation, which is remarkably useful for stage managers who need their hands free for other tasks. The Neo provides eight buttons with an integrated display strip. You can test this right now [Launch your first studio].
Button feedback is bidirectional, working like tally lights on broadcast cameras. The Stream Deck has physical LCD screens behind each button, and Timers Studio renders dynamic icons on those screens in real time. When a timer is running, the corresponding button shows a green play indicator. When it enters the warning zone, the button turns yellow. When it enters overtime, the button turns red. The button's visual state always reflects the current timer state, which means the operator can assess the show status by glancing at the Stream Deck without looking at a monitor, just as a camera operator reads tally lights without checking the program feed.
Timers Studio ships a Producer layout template that maps the most common actions to a logical button grid for each supported device. The template places transport controls in the left column, cue navigation in the center, and utility actions on the right. You can apply this template immediately after connecting the device and begin operating within seconds. For operators who want a custom layout, the button mapping is fully configurable through the Studio interface.
The reliability advantage of the native approach is difficult to overstate. In a traditional setup with Bitfocus Companion as the middleware layer, there are three software systems that must all be running correctly. If Companion crashes, if the module loses its API connection, or if the operating system puts Companion to sleep, the Stream Deck becomes unresponsive. With native WebHID, the only software system that matters is the browser. If the browser is open and the Stream Deck is plugged in, the integration works. The failure surface is reduced to its absolute minimum, which is exactly the kind of reliability that a broadcast Master Control Room demands [See it in action].
WebHID is a Chromium feature that works in Chrome, Edge, Opera, and Brave. It does not work in Safari or Firefox. If your production environment requires Safari, you should use Companion instead. In practice, this is rarely a constraint because production environments overwhelmingly standardize on Chrome.
For productions that use other software alongside Timers Studio, such as vMix for video switching or OBS for streaming, the native integration creates a clean separation. The Stream Deck connected to Chrome controls Timers Studio natively. A second Stream Deck, or the same deck through Companion, controls the other systems. This hybrid approach is increasingly common among technical directors who want the fastest possible response for show critical timer controls while maintaining broad integration for their wider production stack.
The setup time for native WebHID integration is measured in seconds, not minutes. Plug in the device, approve the connection prompt in Chrome, apply the Producer template, and you are live. You can test this right now with any Stream Deck device and a Chromium based browser [select your plan here].