Lightweight Spotify Extension for Dual-Monitor Power Users: Zero Polling
An observer-based design that leaves your CPU alone.
💡 Overview
Anything running in the background should be nearly invisible. Two screens still run out of room for a music window.
Instead of checking the player every few hundred milliseconds, the extension uses a MutationObserver and updates its UI only when the page changes. The developer describes the footprint as near-zero CPU and memory overhead, which matters if you are already running heavy applications.
🧭 A Day of Dual-Monitor Power Users
Two screens still run out of room for a music window.
The problem: Tab-switching on one screen can reorder your whole layout.
The fix: Keep the Web Player on the second monitor and control it from either screen.
🚀 Try It in Three Steps
- Open Chrome Task Manager to see what your extensions use.
- Install the extension and compare over a session.
- Keep what feels invisible.
✨ What You Get
- Shortcut profiles: Standard, one-handed WASD, compact Alt+arrows and function-key presets.
- Sleep timer: Presets of 15, 30, 45 and 60 minutes with a live countdown that auto-pauses playback.
- Mouse-wheel volume: Scroll over the player for fine volume steps, plus one-tap mute memory.
| Task | Switching tabs | Spotify-Web Playback Controller |
|---|---|---|
| Focus impact | Context switch every time | Your work window keeps focus |
| Skipping a track | Switch window, click next, switch back | Shift+Alt+Right from any window |
| Pausing music | Find the tab, click pause, return | One keystroke |
| Privacy | Depends on the tool | No credentials collected, local analytics |
Note: it works with the Spotify Web Player at open.spotify.com only, and does not control the desktop app.
📸 See It in Action

Mini-Player

Dashboard

Shortcuts
Control Spotify Without Leaving Your Work
Global-capable hotkeys, a mini-player and local-only analytics for the Spotify Web Player.
❓ Frequently Asked Questions
It updates when the page changes instead of repeatedly checking, saving CPU.
It is designed for minimal overhead, and the developer describes near-zero CPU and RAM use.
It can be if you spend your day working on dual monitors. Keep the Web Player on the second monitor and control it from either screen.