Snapcast
A client-server audio system that plays the same stream in perfect sync across rooms, turning existing players into a Sonos-like setup.
Snapcast at a glance
What is Snapcast?
Snapcast is not a standalone player. Its server takes audio from sources such as a named pipe fed by MPD or Mopidy, ALSA line-in or loopback, TCP or the output of a process, encodes it as FLAC, PCM, Vorbis or Opus, and sends it to Snapclients on the network. Every client keeps its clock in sync with the server and adjusts playback speed slightly, so speakers in different rooms play exactly together. Several sources can run in parallel, and clients can be grouped to share a stream.
Good fit if
- You want multiroom audio with cheap hardware like Raspberry Pis instead of buying a proprietary system.
- You already use MPD or Mopidy and want it in every room.
Look elsewhere if
- You need the music player and library in the first place: Mopidy pairs well with it.
Before you adopt it
Snapcast is GPL-3.0 and contains no paid parts. One developer writes most of the code, and the last release came out in March 2026. Linux and Windows builds and a Docker image are provided; setting up sources usually means editing configuration files.
Drafted with AI from the project's README and repository data, then checked against that data on 31 October 2026. Report a correction
How to run Snapcast yourself
- Docker
- Dockerfile or compose file in the repository
- Compose file
- None in the repository
- Setup effort
- Not rated: no compose file to judge from
- Kubernetes
- No Helm chart in the repository
- Desktop and mobile
- Builds for Linux, Windows, including ARM in GitHub releases
- Interface languages
- English only
Install instructions: the README on GitHub.
Snapcast health: is it still maintained?
47 of 100, actively developed
Read from GitHub on 5 November 2026. How the score works
Snapcast license: is it open source?
Snapcast uses GPL-3.0, an open-source license approved by the OSI.
- January 2015First published on GitHub.
- TodayGPL-3.0.
Snapcast for developers
Written in
- C++ 90%
- Python 7%
- CMake 2%
- Shell <1%
- Roff <1%
- Other <1%
Getting involved
Language shares are GitHub’s count of the code in the repository.
Alternatives to Snapcast
- koelMusic streaming solution that works. 74 health · MIT · 17.3k stars
- NavidromeYour Personal Streaming Service 84 health · GPL-3.0 · 24.5k stars
- Beetsmusic library manager and MusicBrainz tagger 82 health · MIT · 15.9k stars
- SRSSRS is a simple, high-performance, AI-driven real-time media server supporting RTMP, WebRTC, HLS, HTTP-FLV,… 74 health · MIT · 29.4k stars
- MediaMTXReady-to-use Media-over-QUIC / SRT / WebRTC / RTSP / RTMP / LL-HLS / MPEG-TS / RTP live media server and… 79 health · MIT · 20.6k stars
Questions about Snapcast
Is Snapcast open source?
Yes. Snapcast is published under GPL-3.0, an OSI-approved open-source license.
Is Snapcast still maintained?
Its health score is 47 of 100 (actively developed). It had 30 commits in the last 90 days, the latest on 3 November 2026, and its latest release came out on 10 March 2026.
How do I run Snapcast?
You can run it with Docker, as an app for Linux, Windows, including ARM. The README on GitHub has the exact steps.
What is Snapcast written in?
Snapcast is written mainly in C++ (90% of the code), with Python (7%), by GitHub’s count of the repository.
What are the alternatives to Snapcast?
Close alternatives in the Media servers & streaming category include koel, Navidrome, Beets.