foobar2000 in the Browser: UI Loads, Audio Is Unreliable (Wine Guide)

Running foobar2000 in your browser — with your own copy Partial — UI loads, audio is unreliable

Guide updated July 2026 · Runs via Wine 1.7.55 (Win32) + WebAssembly · Requires your own copy

foobar2000 is the famously lightweight, no-nonsense audio player that power users have loved for over two decades — tiny, fast, infinitely configurable. This is a bring-your-own-copy compatibility guide: foobar2000's license doesn't let us host an extracted build, so you load your own copy below and it runs client-side. The catch for browser-based Wine is twofold: the current 2.x release is built for modern 64-bit Windows, and even the older 32-bit builds have a long history of audio-output trouble under Wine. The interface generally renders, so you can poke around the playlist and preferences, but treat actual music playback as unreliable rather than a daily driver. This is a "look how far emulation has come" demo more than a real listening setup.

Runs in your browser tab with WebAssembly + Wine — nothing is uploaded. Click the screen to capture input; press Esc to release the mouse.

We don't host foobar2000 here. It's freeware, but not open-source — its license only permits redistributing the unmodified official installer, and the build you'd run in-browser is an extracted program folder, which isn't covered. Get it from the official foobar2000 site (older 32-bit builds live at foobar2000.org/old), and only run a copy you obtained legitimately.

How it works & what to expect

What works, and what to expect

Two things matter here. First, version: foobar2000 2.x targets 64-bit Windows and a modern toolchain that browser-based Wine (Wine 1.7.55, 32-bit only) can't handle. You'll want a legacy 32-bit build from the 1.x series, available at foobar2000.org/old. Second, audio: even on full desktop Wine, foobar2000 is notorious for listing no output device, emitting static, or going silent depending on the audio driver. Boxedwine routes sound through Web Audio, which is an even narrower path, so playback is genuinely hit-or-miss.

What does tend to work is the UI: the main window, the playlist, the Preferences dialog and its dense option tree, and basic file browsing. That alone is enough to relive the interface — just don't count on hearing anything.

How to load it

foobar2000 ships as an installer, which won't run cleanly in-browser. The reliable approach is to install a legacy 32-bit 1.x build on a real Windows PC (or use a portable install option if the version offers one), then upload the resulting program folder — foobar2000.exe plus its components\, user-components\, and config files — using the folder picker. Drop a small test track (an MP3 or FLAC) into the same folder so you have something to try.

Once it's loaded, open Preferences → Playback → Output and try each device option (Primary / Default) — that's the single most useful knob if you get any sound at all.

Why audio is the weak link

foobar2000's whole design philosophy is a thin player with a pluggable output stack — and that stack is exactly what struggles under emulation. Output plugins probe for audio hardware and expect a specific driver model; Boxedwine presents an emulated path to Web Audio that those plugins weren't written for. The result, well-documented across years of WineHQ and Linux forum threads, ranges from clean playback (rare and version-dependent) to silence, stutter, or harsh static. Advanced features — ReplayGain scanning, DSP chains, visualizations, and anything touching networking or online services — are even less likely to behave.

Frequently asked questions

Can I really run foobar2000 in a browser?

You can load and explore it. A legacy 32-bit foobar2000 build will boot under ExeBrowser's Wine + WebAssembly and show its real interface, playlist, and preferences. Audio playback, though, is unreliable under emulation, so think of it as a working demo of the UI rather than a dependable music player.

Why doesn't the latest foobar2000 work?

The current 2.x releases are built for 64-bit Windows and a modern toolchain. ExeBrowser runs Wine 1.7.55 with a 32-bit x86 emulator, so it needs an older 32-bit build — grab one from the official old versions page.

Will my music actually play?

Sometimes, but don't count on it. foobar2000 has a long, well-documented history of audio problems under Wine — no output device listed, static, or silence — and the browser audio path is even narrower. The interface loads reliably; sound is the part that's hit-or-miss.

Do you host foobar2000 for me to click and play?

No. foobar2000 is freeware but closed-source, and its license only allows redistributing the unmodified official installer — not the extracted program folder you'd run here. Download it yourself from the official site and upload your own copy.

Is there a better-working media app to try in the browser?

For nostalgia, classic Winamp behaves similarly (UI yes, audio iffy). If you mainly want something that reliably runs, small Win32 utilities and the bundled classic games are a safer bet — see the compatibility guide for what holds up under emulation.