Spooty

Self-hosted web app that builds a local music library from Spotify URLs by reading Spotify's metadata and downloading the matching audio from YouTube. Captured here as a high-engagement signal — not an endorsement; the workflow carries clear copyright/ToS risk. Source: Raiper34/spooty, https://github.com/Raiper34/spooty, 2026-06-12

What it actually does

Spooty (by Raiper34, ~1.2K GitHub stars, MIT) is a NestJS + Angular app shipped as a single Docker image (SQLite for state, Redis for the job queue, FFmpeg for conversion). The key mechanic: Spooty downloads nothing from Spotify. You paste a Spotify track/album/playlist URL; it calls the Spotify API (you supply your own developer client ID/secret) to get track names and artist info, then searches YouTube and downloads the closest match via yt-dlp, converting to MP3 (or another FFmpeg format) with metadata and album art. It can also subscribe to a playlist or artist page and auto-download new releases. Rate limiting and optional YouTube cookies handle restricted content. Source: Raiper34/spooty README, 2026-06-12

The viral framing was ownership-flavored: "Spotify just lost its grip… rips your entire library to your own machine. Permanently. As MP3s. With full metadata, album art, the works." Source: X/@heygurisingh, 2026-05-14

Legal and security risk (read first)

• Copyright / ToS. Using Spotify metadata to pull the corresponding audio off YouTube circumvents both Spotify's terms and YouTube's terms, and reproducing commercial recordings without a license is copyright infringement in most jurisdictions. "Self-hosted and open-source" changes the distribution model, not the legality of the output.
• Account exposure. It runs against your Spotify developer credentials; the YouTube side is subject to the usual yt-dlp anti-bot churn (hence the cookies/rate-limit options).
• Position vs ReClip - Self-Hosted Video Downloader. ReClip is a general-purpose downloader for content the user may have rights to (their own uploads, public domain, permissively-licensed media). Spooty is purpose-built to reconstruct a paid streaming catalog, which is the legally riskier end of the same yt-dlp family. Treat it as a signal about demand for digital ownership, not as tooling to adopt.

This page exists because the launch cleared the notability bar (5,730 likes, 7,525 bookmarks) and the "own your media" sentiment recurs across the corpus — documented neutrally so the wiki's coverage is complete, with the risk stated plainly.

2026-07-03 Source Status

The original Raiper34/spooty GitHub repository now returns 404, and the bookmark's pbs.twimg.com image returns 403 during local media repair. Keep Spooty as a historical/high-signal digital-ownership bookmark, not as an adoption candidate or current tool recommendation. The legal/ToS caveat above remains the main durable lesson. Source: GitHub API check, 2026-07-03; x-bookmark media repair, 2026-07-03

---

Timeline

• 2026-05-14 | @heygurisingh surfaced Spooty as an open-source self-hosted Spotify downloader (full library → MP3 with metadata/art). 5,730 likes, 7,525 bookmarks. Source: X/@heygurisingh, 2026-05-14
• 2026-06-12 | Dedicated, risk-framed page created from dev-tools bookmark absorption; researched repo (Raiper34/spooty, MIT, ~1.2K stars; Spotify-metadata + YouTube-audio architecture). Recorded the copyright/ToS caveat; not recommended for adoption. Source: x-bookmark-absorb, 2026-06-12
• 2026-07-03 | Artifact review found the original repository unavailable via GitHub API and the X image unavailable via pbs.twimg.com 403. Kept the page as a historical signal with explicit non-adoption status. Source: GitHub API and media repair, 2026-07-03