Spotify to YouTube Music Playlist Transfer: Why We Paused It (and What to Do Instead)
We love the idea of a simple “transfer my Spotify playlist to YouTube Music” button. We built a bunch of it. Then we ran into a hard wall: strict daily API quotas that can stop big transfers mid-way. Here’s what we were building, why we paused it, and what you can do right now.
Published February 15, 2026 · Updated February 15, 2026
If you’re searching for a Spotify to YouTube Music playlist transfer, you’re usually hoping for something like:
- “transfer my Spotify playlist to YouTube Music for free,”
- “convert Spotify playlist to YouTube Music from a link,”
- or even “Spotify to YouTube Music transfer unlimited / no limit.”
We wanted that too.
We started building YouTube tools and a proper Spotify → YouTube Music transfer workflow inside MyPlaylist.Tools — including smarter matching for things like live versions, remasters, and clean/explicit variants.
Then we hit a hard constraint we couldn’t responsibly paper over: YouTube API quotas (limits on how much an app can do per 24 hours). For larger playlists, those limits can stop a transfer mid-way — and “try again tomorrow” is not a great experience.
So we paused the feature.
This article is a transparent look at what we were building, why we had to remove it, and what we recommend doing instead.
The transfer workflow we were building
Our rough “happy path” looked like this:
- Connect Spotify (and a YouTube/Google account).
- Pick a Spotify playlist to move.
- Match each track to the closest YouTube Music equivalent.
- Preview matches (and fix edge cases before writing anything).
- Create a new YouTube Music playlist and add the tracks in order.
The part we cared about most was step 3 — matching — because that’s where transfers usually fall apart.
The matching problems we were solving (live versions, remasters, and messy metadata)
If you’ve ever used a playlist transfer tool, you’ve probably seen the pain:
- “Song Title” matches the wrong artist.
- A studio track gets replaced by a live version (or the opposite).
- The clean version becomes explicit (or vice versa).
- Remasters and re-releases create “duplicates” that aren’t truly duplicates.
We were building a matching layer that tried to be honest and helpful:
- Confidence scores (“this looks like the same song” vs “this is a guess”).
- A “prefer studio vs prefer live” style of tuning (because people actually care).
- Artist + duration checks to reduce bad matches.
- A preview step so you can correct weird matches before the playlist gets written.
It was genuinely fun to work on — and it made transfers noticeably better in testing.
Why we paused it: YouTube’s daily API quotas make big transfers unreliable
YouTube’s official API (YouTube Data API) uses a quota unit system:
- Most projects start with a default allocation of 10,000 units per day.
- Different actions cost different amounts.
- Example costs from Google’s docs: a write operation can cost 50 units, and a search request can cost 100 units.
You can read the official quota overview here:
Here’s why that matters for transfers:
- To move a playlist, you typically need to search for each track (matching) and then insert each track into a playlist (writing).
- Even if you optimize and cache, “real-world” playlists often contain tracks that need extra searches (multiple versions, ambiguous titles, regional availability).
So a transfer that sounds small — say 100–200 tracks — can become quota-expensive quickly.
And it gets tougher when you consider scale:
- A single user might be okay on a quiet day.
- Multiple users transferring multiple playlists can blow through shared project quota fast.
We could have shipped it anyway and let it fail for big transfers — but that felt unfair. People come to transfer tools because they want the problem gone, not because they want a half-finished playlist and an error message.
“Can’t you just request more quota?”
Sometimes you can — but it’s not as simple as flipping a switch, and it’s not something we can promise as a stable foundation for a consumer “transfer unlimited” feature.
Google documents quota extensions and compliance requirements here:
We’d rather pause than build a feature that depends on quotas we can’t reliably guarantee.
What to do instead (right now)
Even though we paused Spotify → YouTube Music transfers, we can still help in a practical way: get your Spotify playlist into a clean, transfer-friendly shape.
That’s useful whether you’re staying on Spotify or moving the playlist with another service.
1) Remove duplicates first (it helps matching a lot)
Duplicates and near-duplicates are one of the biggest reasons transfers feel messy.
2) Fix greyed-out / unavailable tracks (or remove them)
If a song won’t play in Spotify, it often won’t match cleanly elsewhere either.
- Spotify Playlist Unavailable Track Repair Tool
- Short guide: Fix greyed-out songs in Spotify playlists
3) Sort or standardize the playlist before you export/share it
If you’re trying to keep the “feel” of a playlist consistent, a stable order helps — especially when you’re comparing “before vs after.”
- Spotify Playlist Sort Tool
- Short guide: Sort Spotify playlist
4) If your real goal was “fresh listening,” don’t transfer — reshuffle
A lot of “transfer” searches are really “I’m bored of this playlist.”
If that’s you, you’ll probably get more value from a saved shuffle:
If shuffle modes are confusing, these help:
5) (Optional) Merge a few playlists before you move them
If you have tracks spread across multiple small playlists, merging first can make the rest of the process simpler.
6) (Optional) Filter out tracks you don’t want to take with you
If you’re aiming for a “clean” version, or you just want to drop very short tracks, filtering helps.
Will transfers come back?
We’d like them to — and we’ll keep revisiting the idea as policies, quotas, and implementation options evolve.
But until we can offer a transfer workflow that’s reliable for normal people with normal playlists (not just tiny test lists), we’d rather be upfront than ship something flaky.
If you want to start with the tools that exist today, the hub is here: