Is Demus Breaking Spotify Terms? Why Your Playlists Won't Import and How to Fix It
Even when a playlist is completely public and formatted cleanly, server-level restrictions can halt the process. Spotify enforces strict rate limits on its Web API to prevent mass data harvesting. Third-party developers who exceed their allotted query bucket receive an HTTP 429 Too Many Requests response, locking out queries for minutes or hours.
Because Demus serves hundreds of thousands of active mobile users, its shared server scrapers frequently hit these ceilings. When a user pastes a massive playlist containing 500 or more tracks, Demus must request metadata in paginated blocks of 50 or 100 items. If Spotify flags this rapid burst of calls as automated scraping, it terminates the connection midway through the list.
| Transfer Method | API Authentication | Success Rate | Common Failure Point |
|---|---|---|---|
| Demus Direct Import | Anonymous / Web Scraper | 60%, 75% | Rate limiting (HTTP 429), private playlists, metadata mismatches |
| Third-Party Tools (Soundiiz/TuneMyMusic) | Official OAuth 2.0 User Token | 95%, 99% | Free-tier monthly transfer quotas (typically 500 songs) |
| Manual CSV / Text Export | None (Local File Processing) | 90%, 95% | Missing regional metadata, obscure acoustic versions |
Once metadata is retrieved, Demus faces secondary matching hurdles. The app searches YouTube for corresponding audio tracks. If an artist has published an obscure b-side, an unreleased demo, or a track under non-Latin typography, the automated search query often returns irrelevant tracks or no results.
The song appears in Demus as grayed out or vanishes from the parsed playlist entirely. When a 100-song playlist arrives in Demus showing only 82 tracks, metadata matching failures account for the missing 18 entries.
