Open source · Free · Runs on your own computer
capy moves your playlists
to another music service.
Nothing to rebuild by hand: capy is a free, open-source tool that reads a playlist from Spotify or Apple Music, finds the same songs on another service, and puts them there in the original order. It also searches music and controls playback. It is installed on your own computer, with a terminal version and a web interface, and your accounts never pass through anyone's server.
To sync or transfer playlists, capy asks you to sign in with Google. It only stores the master copy of your playlists in your own Google Drive, in an application data folder that only capy can read, and it cannot see any of your other files. Why, and which permissions
macOS and Windows. Playlists can currently be read from Apple Music, Spotify or a music folder on your computer, and written to Spotify or the music folder. Apple Music is read-only.
What it does
capy is a cross-platform music tool: search, playback remote control, and playlist sync and transfer. Most playlist-transfer services charge a fee and need you to hand your accounts to their servers. capy is free, and everything happens between your computer and the music services directly.
Transfer
Move a playlist from one service to another. Songs are matched by ISRC (the international code of each recording) first, and by title, artist and duration only when that fails. Uncertain matches are listed for you to decide. The source playlist is never modified.
Sync
One playlist can be linked to several services. When songs are added on either side, capy shows the differences as a table and writes only after you confirm. Playlist order is your memory: capy never sorts or shuffles it.
Search and remote control
Search, play, pause, seek, change the volume and see what is playing, from the terminal. This part does not need Google sign-in.
Web interface
Prefer clicking? Run
capy --web. It opens a page on your own computer that only you can reach (127.0.0.1) and walks you through a transfer.
How a transfer works
Three steps. Before every write, capy lists what it is about to do and waits for your confirmation.
Connect your accounts
Sign in to the source and destination music services, then to Google. Credentials are stored only in your computer's keychain (macOS Keychain or Windows Credential Manager).
Pick a playlist
capy reads every song in it, looks each one up on the destination service, and tells you how many were found and which were not.
Confirm, then move
Only after you review the list and confirm does capy add the songs to the destination. Songs that were not found stay in the report; capy does not substitute a different version.
Why capy asks you to sign in with Google
Syncing and transferring playlists needs a place to keep your master copy of each playlist: which songs, in what order, and which track they map to on each service. That is what lets a second computer, or the next sync, pick up where you left off. capy runs no server, so this data lives in your own Google Drive, in an application data folder that only the capy application can read.
Google sign-in is optional: search and playback control work without it. When you do sign in, capy requests exactly these three permissions and nothing else:
| Permission | What it is used for | What it cannot do |
|---|---|---|
| openid | Confirms which Google account signed in. | Cannot read your profile, contacts or any content. |
| userinfo.email | Shows the signed-in email address in capy auth status so you can notice a wrong account. The address is written only to a settings file on your computer. | capy never emails you, cannot read your Gmail, and never sends the address to anyone. |
| drive.appdata | Reads and writes a few JSON files that capy itself creates in your Drive's application data folder (playlists, track mappings, device list; if you connect a music folder on your computer, also the relative paths of those music files and the playlist file names). | Cannot see or change any other file in your Drive: no documents, no photos, no shared folders. |
Full details are in the Privacy Policy. You can revoke access at any time under third-party access in your Google Account.
Where your data lives
capy has no backend. This table is the whole picture.
- Playlist master copy
- Your own Google Drive (application data folder), plus a cache on your computer.
- Sign-in credentials
- Your computer's keychain. Never written to settings files, never uploaded anywhere.
- What you play or search
- Stays between your computer and that music service. capy keeps no log and has nowhere to report to.
- Our servers
- There are none. This website is a few static pages.
Get started
Download the file for your computer from GitHub Releases, unpack it, and put capy on your PATH. Full installation and usage notes are in the README (in Traditional Chinese).
# connect your accounts $ capy auth login spotify $ capy auth login google # transfer with the web interface $ capy --web # or straight from the terminal $ capy migrate "Commute" --from apple --to spotify
Spotify requires you to create your own free developer app (capy walks you through it). Apple Music is currently read-only and relies on a method Apple does not officially support. Writing to Spotify playlists follows the official documentation and is still being verified on real accounts; please report problems. See the README for details.