Keep your music local
Your audio files stay in your own libraries. MusicShareProtocol coordinates playback state, not audio delivery.
An open protocol for local music experiences
What if your music
could follow you?
Your music library. Your devices. One shared listening experience — without being tied to a streaming platform or a single player.
Shared listening session / Local network Peer-to-peer concept
01 / Independent players02 / Shared session state03 / Local files stay local
The idea
Your library shouldn't
lock you into one device.
Streaming services make music incredibly convenient. But many listeners still build and maintain their own local music libraries — and want the freedom to use the players and devices they choose.
Move between devices
Start listening on one device and continue on another player using its own local copy of the track.
Keep players independent
No replacement player or mandatory ecosystem. The goal is interoperability between applications that already exist.
The idea in one sentence: independent music players, sharing one listening session over your local network.
Under the hood / 02
A small protocol.
A connected experience.
MusicShareProtocol is designed as an integration layer between music players. Each application remains responsible for its own library and playback engine.
01
Independent music players
Existing applications and their native playback engines
02
MusicShareProtocol
Peer discovery · Session state · Playback handoff · Conflict awareness
03
Local network
Device discovery and direct peer-to-peer communication
04
Local music libraries
Each device resolves and plays its own local copy of a track
How it works
From discovery
to handoff.
The intended experience is simple for listeners. Underneath, participating players coordinate a shared session.
01
Discover peers
Players find other compatible devices on the local network.
02
Share session state
Participants exchange the current track, playback status, position and active device.
03
Hand off playback
The receiving player locates the matching local file and resumes from the shared position.
04
Surface conflicts
If participants disagree about the session, the protocol makes that conflict visible instead of silently choosing a winner.
The device diagram illustrates the intended experience, not a claim of universal device support. Compatibility depends on player integrations. The protocol and integrations are actively evolving.
Open source / In development
Help connect the players.
Explore the protocol, follow development, or build an integration for your music player.