About
A playlist transfer tool built around trust.
Independent, review-first, and focused on one transfer direction.
PlaylistXfer started with one practical problem: moving Spotify playlists into Apple Music without accepting a black-box result. The first prototype proved that catalog matching was possible; it also made the harder problem obvious. Two services can describe the same recording differently, and a plausible search result is not always the song a listener intended.
The product is therefore intentionally review-first. It shows what Spotify link it could read, what Apple Music candidates it found, and what it could not safely match before asking for permission to create anything.
Three product principles
Evidence before automation
Recording identifiers and catalog metadata improve confidence, but alternate releases still need context. Ambiguous rows wait for review.
Permission near the action
Spotify preview and Apple Music analysis happen before Apple Music write access is requested.
Visible failure
Missing tracks, provider errors, and skipped rows belong in the result. A transfer receipt should not hide them behind a success percentage.
Narrow scope
The current web product focuses on public Spotify playlist and track links moving into Apple Music. It does not promise every service pair.
Current status
The web MVP supports public Spotify playlist and song previews, Apple Music match analysis, candidate review, and authorized playlist creation. The iOS app is in active development. Private Spotify account access, other streaming destinations, and local-file migration are outside the current scope.
Claims backed by reproducible tests
PlaylistXfer publishes dated production reports when a result can be reproduced from a public source. An August 2, 2026 audit found that one public playlist produced 340 readable tracks through the ingestion backend but only 46 through the original production Worker. The incomplete match report was rejected, the ingestion boundary was corrected, and the discrepancy was documented instead of being presented as a success metric. Read the incident method, fix, and verification checklist.
A follow-up on August 14 ran three public sources through production and analyzed 439 rows against the US Apple Music storefront. The published test ledger names every source, distinguishes full reports from a 50-row sample, lists the six unmatched rows, and explains why the combined total is not a universal success-rate promise.
Why the guides are part of the product
A useful transfer tool should explain its limits. The PlaylistXfer guides document playlist visibility, catalog matching, missing tracks, and troubleshooting with links to first-party Spotify and Apple references. They are written for people making an actual transfer, not as filler around the form.
Open project
The source and product decisions are documented publicly for people who want to inspect or reproduce the flow. Follow development, report reproducible problems, or review the implementation in the PlaylistXfer GitHub repository.