spotifyd/spotifyd

A spotify daemon

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 20 minutes ago
Added to GitGenius on September 5th, 2026
Created on December 10th, 2014
Open Issues & Pull Requests: 75 (+0)
GitHub issues: Enabled
Number of forks: 517
Total Stargazers: 10,770 (+0)
Total Subscribers: 50 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Spotifyd is a Spotify daemon that runs as a lightweight background service to enable Spotify playback on devices and systems where the official client is unavailable or impractical.

The tool solves the problem of accessing Spotify on headless systems, embedded devices, and Linux machines by implementing a daemon that connects to Spotify's service and handles playback without requiring a graphical interface. It works by running as a background process that can be controlled through Spotify Connect, allowing users to cast audio to the device from their phone, desktop app, or web player. The daemon handles authentication, maintains the connection to Spotify's infrastructure, and manages audio output through the system's sound hardware.

Spotifyd suits users running Linux servers, Raspberry Pi installations, NAS devices, or other systems where installing the official Spotify application is not feasible. It is particularly valuable for those building multi-room audio setups or wanting to repurpose older hardware as Spotify endpoints. The project is written in Rust, which provides memory safety and efficient resource usage—important characteristics for long-running daemons on resource-constrained devices. Anyone considering adoption should expect to configure the daemon through configuration files and manage it as a system service, rather than interact with a graphical interface.

Development activity shows consistent engagement with the codebase. The project receives regular pull requests addressing bug fixes, feature additions, and dependency updates. Issues are actively triaged and discussed, with maintainers providing feedback and guidance to contributors. The repository demonstrates ongoing maintenance through periodic releases that incorporate community contributions and address reported problems. Code review appears thorough, with pull requests receiving substantive comments before merging. The project maintains documentation and examples to help users get started, and the community discussion in issues reflects a healthy ecosystem of users troubleshooting and extending the tool's capabilities.