You don't need a Chrome extension for a Spotify visualizer

Why extensions seem like the obvious answer

If you're using the Spotify web player, a browser extension feels like a natural fit. Extensions can read page content, inject scripts, and modify the DOM. So tapping into the audio seems like a short step.

The problem is that DOM access and audio access are completely different things. An extension can see that a song is playing, read the track title, add a button to the interface. But it can't capture the raw audio data that a visualizer actually needs. Spotify's web player renders audio in its own isolated context, and that audio stays locked there, extensions included.

What about the extensions that seem to work?

Some extensions use the Spotify Web API to read metadata about what's playing: tempo, energy level, key. This lets them animate something in rough sync with the music. It's not real-time frequency analysis. You're working from a database description of the song, not the actual audio. The result looks scripted because it is.

Others hook into visual elements of the Spotify web player itself, extending existing animations or adding canvas overlays on top of the DOM. These work until Spotify updates their interface, which breaks them. Most have a graveyard of one-star reviews from users who installed after the last update broke everything.

Neither approach gives you what the old iTunes or Winamp visualizer had: true real-time frequency analysis that reacts to the actual audio content as it plays.

What actually works

The approach that actually delivers real-time audio visualization is capturing your system audio: the raw stream of everything your computer is playing. Spotify desktop app, web player, doesn't matter. The browser gets full access to that audio, which means genuine real-time frequency analysis, not a metadata approximation.

The easiest way is built right into Chrome, Edge, and Brave: screen sharing with system audio. Share the Spotify window (or your entire screen), turn on “Also share system audio”, and the visualizer reacts to a direct, full-quality feed. No extension, no extra software, just a few clicks. Our screen sharing guide walks through it with screenshots.

The other route is a virtual audio device, the same technique used by streamers, DJs, and recording studios. It appears to your browser as a microphone input, but instead of capturing from a physical mic, it captures your system audio. It's a one-time setup that takes a few minutes: BlackHole or Loopback on macOS, VoiceMeeter or VB-Audio Virtual Cable on Windows. Our system audio setup guide has step-by-step instructions for both platforms, and it works in every browser, including Firefox.

Why this approach is better anyway

Beyond just working correctly, capturing system audio gives you something a Chrome extension never could: a full-screen, GPU-accelerated visualizer running in its own window. Not a small overlay clipped to the Spotify web player tab. Not a bar graph crammed into a browser extension popup.

vizz.fm uses WebGL for rendering, the same technology behind browser-based 3D games. You get dozens of visualizers: particle systems, 3D meshes, custom shaders, waveform displays. All reacting to real frequency data from your actual Spotify audio. Customize colors, speed, and intensity. Stack post-processing effects. Save presets. Run it on a second monitor or cast it to your TV.

And since it works at the system audio level, it doesn't care whether you're using the Spotify desktop app, the web player, or any other music source. Switch apps mid-session and the visualizer keeps running.

Getting started

The short version: open vizz.fm in Chrome, Edge, or Brave, pick System audio as your source, share the Spotify window with “Also share system audio” turned on, and press play. That's the whole setup; the screen sharing guide has screenshots of each step. Prefer the virtual audio device route (or need Firefox)? Follow the setup guide and select the device as your microphone input; it takes about five minutes.