Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Attempting to download either the "liked videos" or "liked music" playlists on Youtube using cookies from both youtube.com and accounts.google.com results in a 404 #25175
Comments
Youtube has now removed access to liked videos and watch later playlist. Your download failed just because the url for liked videos and watch later playlist even when logged in are not actual physical addresses that can be accessed on internet.
|
|
I'll definitely give this a try, thanks. Although, I did mention that I wasn't having any trouble with my watch later playlist, youtube-dl is able to access it perfectly fine, it's just the liked videos and liked music playlists that I'm having trouble with. Plus I've seen others say that they were able to download their liked videos by switching from using login credentials to cookies, though I'm not sure whether that was before Youtube changed whatever it was that they did or not. |
|
If it's your own videos that you're downloading then don't bother with youtube-dl at all, Google Takeout is the best way because you get the full metadata and the original source quality videos that you uploaded, not the re-encoded stream derivatives that are available publicly. |
Checklist
Verbose log
Description
I've been trying to download my liked videos playlist (LL) from youtube using the cookies that I use to download pretty much everything else, including my watch later list (WL), but I keep getting a 404 error on both LL and my liked music playlist (ML). These cookies work for my other private playlists and have never caused errors downloading other playlists either. I've tried logging in using my youtube account ID and an app password, but I keep getting a 400 error from that. I've tried this on multiple machines and the results were the same across them all.