Skip to main content

yt-dlp-yandex-music-plugin

A yt-dlp plugin (plus standalone tools and research notes) for downloading from Yandex Music (music.yandex.ru) in 2026.

The built-in yt-dlp Yandex Music extractor is broken upstream: it calls the retired handlers/*.jsx endpoints and crashes. This project reverse-engineered the current web API and replaces the extractor.

Just want to download something? → QUICKSTART.md (3 steps: install, cookies, one command.)

What it does

  • Fixes https://music.yandex.ru/album/<albumId>/track/<trackId> (shadows the broken built-in YandexMusicTrackIE).
  • Adds support for shared playlists: https://music.yandex.ru/playlists/<uuid> (not supported by upstream), including charts (https://music.yandex.ru/playlists/ch.<uuid>).
  • Adds support for the "liked"/favorites playlist: https://music.yandex.ru/playlists/lk.<uuid> (tested with 1500+ tracks).
  • Adds support for user-playlist URLs: https://music.yandex.ru/users/<login>/playlists/<id> (uuid or numeric kind) — shadows the broken built-in YandexMusicPlaylistIE.
  • Adds support for artist pages: https://music.yandex.ru/artist/<id> — all of the artist's tracks, fetched via the paginated GET /artists/<id>/tracks API (20/page). Also fixes the broken built-in https://music.yandex.ru/artist/<id>/tracks sub-route and the https://music.yandex.ru/artist/<id>/albums album list (via GET /artists/<id>/direct-albums).
  • Adds support for album pages: https://music.yandex.ru/album/<id> — all of the album's tracks (incl. multi-disc box sets), from the page's preloaded data; shadows the broken built-in YandexMusicAlbumIE.
  • Downloads the best available audio: FLAC where the server offers it, otherwise MP3 320 kbps (falls back to MP3 192). Unencrypted raw transport — no client-side decryption.
  • Requires a logged-in (paid) account — see Session (cookies). Without a valid session the API silently returns smart_preview streams — downloads "succeed" but files are ~13–30 s.

Available qualities

The API has no "what qualities does this track have" metadata — the plugin requests the best level and takes what the server serves. Valid levels are lossless / nq / lq; the server falls back to the best available. In practice (~1,700 tracks probed, 2026-09): most tracks are MP3 320 kbps, a few are MP3 192 kbps only, and FLAC is not offered for many accounts (the web UI has no FLAC badge or setting either) — so expect MP3. The plugin's lossless → nq fallback covers the 192-only tracks. Details: research/api-notes.md.

Install

Option A — PyPI (recommended):

pip install yt-dlp-yandex-music

If your yt-dlp lives in a pipx install, the plugin must go into the same environment:

pipx inject yt-dlp yt-dlp-yandex-music

Option B — from this repo:

pip install --user .
# if your yt-dlp is a pipx install:  pipx inject yt-dlp <repo>
# (not `pipx/uv tool install .` — that creates an isolated venv where no
#  yt-dlp runs, so the plugin would never be discovered)

Option C — drop-in (no build, no pip):

mkdir -p ~/.config/yt-dlp/plugins/yandex-music-v2/yt_dlp_plugins/extractor
cp yt_dlp_plugins/extractor/yandex_music_v2.py \
   ~/.config/yt-dlp/plugins/yandex-music-v2/yt_dlp_plugins/extractor/

All options install into a location yt-dlp scans for the yt_dlp_plugins.extractor namespace automatically.

Verify (all lines should say OK):

python3 tools/check_install.py
# OK:  yandexmusic:track            -> plugin (shadows broken built-in)
# OK:  yandexmusic:album            -> plugin (shadows broken built-in)
# OK:  yandexmusic:artist:tracks    -> plugin (shadows broken built-in)
# OK:  yandexmusic:playlist         -> plugin (shadows broken built-in (users/<login>/playlists URLs))
# OK:  yandexmusic:artist:albums    -> plugin (shadows broken built-in (artist/<id>/albums URLs))
# OK:  yandexmusicv2:playlist       -> plugin (shared playlists + charts)
# OK:  yandexmusicv2:liked          -> plugin (liked/favorites playlists)
# OK:  yandexmusicv2:artist         -> plugin (artist pages (all tracks))

Note: yt-dlp --list-extractors won't show the plugin — yt-dlp handles that flag before loading plugins.

Session (cookies)

The plugin talks to the unofficial web API with your Yandex session. Two ways to provide it:

From your browser directly (no export):

yt-dlp --cookies-from-browser <browser>[:<profile-dir>] ...
# e.g. for the Helium browser (KDE):
yt-dlp --cookies-from-browser chromium:~/.config/net.imput.helium/Default ...

The browser name must match where the browser stores its cookie- encryption key: Helium registers it as Chromium Safe Storage, so use chromium, not chrome. Needs the keychain/KWallet to be reachable (i.e. a running desktop session — for headless/cron use the exported file instead).

Exported cookie file:

yt-dlp --cookies /path/to/cookies.txt ...

Netscape format, tab-separated (export with a browser extension like "Get cookies.txt LOCALLY"; hand-pasted space-separated lines are silently dropped by the parser). Must include the .yandex.ru Session_id cookie — it covers api.music.yandex.ru automatically.

The silent failure mode: with a stale/missing session the API returns smart_preview streams for every quality level — no error, just ~13–30 s files. The plugin detects this and prints a warning per track (the response's quality field says smart_preview, and as a fallback it HEADs the stream URL and compares the estimated duration against the track's metadata duration). Still, verify results with ffprobe -v error -show_entries format=duration file.

The guard can be disabled entirely for very large playlists (note: this also disables the zero-cost served-quality check, so a stale session becomes fully silent):

yt-dlp --extractor-args "yandexmusicv2:preview_check=off" ...

Usage

yt-dlp --cookies ~/Music/NFSMW/.cookies.txt \
  -o '%(playlist_index)02d - %(artist)s - %(title)s.%(ext)s' \
  --embed-metadata --embed-thumbnail \
  'https://music.yandex.ru/playlists/<uuid>'

# liked/favorites playlist (playlists/lk.<uuid>)
yt-dlp --cookies cookies.txt 'https://music.yandex.ru/playlists/lk.<uuid>'

# all tracks of an artist (paginated automatically)
yt-dlp --cookies cookies.txt 'https://music.yandex.ru/artist/<id>'

# all tracks of an album (incl. multi-disc box sets)
yt-dlp --cookies cookies.txt 'https://music.yandex.ru/album/<id>'

# user-playlist URL (uuid or numeric kind, e.g. 3 = liked)
yt-dlp --cookies cookies.txt 'https://music.yandex.ru/users/<login>/playlists/<id>'

# chart (top-100)
yt-dlp --cookies cookies.txt 'https://music.yandex.ru/playlists/ch.<uuid>'

# single track
yt-dlp --cookies cookies.txt \
  'https://music.yandex.ru/album/39688866/track/143540328'

# pin the request-signing key (normally not needed — the plugin
# refreshes it automatically when Yandex rotates it)
yt-dlp --cookies cookies.txt \
  --extractor-args "yandexmusicv2:hmac_key=7tvSmFbyf5hJnIHhCimDDD" \
  'https://music.yandex.ru/album/39688866/track/143540328'

Filenames containing non-ASCII (e.g. Cyrillic artist names) are not transliterated by yt-dlp — post-process if you need ASCII-only names (tools/standalone_download.py does it for you).

Metadata

Tagging is opt-in via yt-dlp's own flags (--embed-metadata, --embed-thumbnail — both off by default). With them, files get: title, artist, album, album artist, track/disc numbers, release year, source URL, and the 1000×1000 cover art. Notes:

  • Featured artists — the API has no structured feat. field; credits live in the track title (e.g. "… (feat. …)"), so they end up in the title tag.
  • Genre — not tagged: the API only exposes machine codes (ruspop, …), no display names.

Standalone downloader (no yt-dlp)

python3 tools/standalone_download.py \
  --cookies cookies.txt \
  --playlist 'https://music.yandex.ru/playlists/<uuid>' \
  --out ~/Music/NFSMW \
  --m3u /path/to/Playlist.m3u \
  --wine-prefix 'Z:\home\lw\Music'

Pure stdlib; writes NN - Artist - Title.ext files (ASCII-sanitized) and optionally an M3U (plain paths or Wine Z:\-style paths).

If signatures start failing (403 not-allowed)

The HMAC key is hardcoded in the web frontend bundle and only changes when Yandex ships a new frontend. The plugin handles a rotation automatically: on a rejected signature it re-downloads the frontend, extracts the new key, caches it in the yt-dlp cache dir, and retries.

If the automatic refresh cannot find the key (frontend layout changed again), extract it manually and pin it with an extractor-arg:

python3 tools/extract_secret_key.py            # prints the current key
yt-dlp --extractor-args "yandexmusicv2:hmac_key=<key>" ...

The hmac_key extractor-arg also works for testing/overrides and takes priority over the auto-refresh. Accepted names (top-level or per-IE, e.g. yandexmusicv2:hmac_key=… or yandexmusic:track:hmac_key=…): yandexmusicv2, yandexmusic, yandexmusic:track, yandexmusic:album, yandexmusic:artist:tracks, yandexmusic:playlist, yandexmusicv2:playlist, yandexmusicv2:liked, yandexmusicv2:artist.

Versioning

CalVer, in the style of yt-dlp itself: YYYY.MM.DD (e.g. 2026.09.16), with optional suffixes:

  • YYYY.MM.DD.N — same-day re-release (e.g. 2026.09.16.1)
  • YYYY.MM.DDrcN — pre-release (e.g. 2026.09.16rc1)

The version is the git tag — releases are tagged and published by CI (.github/workflows/publish.yml), so there is no version field to bump by hand. PyPI versions are immutable: one tag = one release, and a broken release gets a new date, not a re-upload. Release notes live in GitHub Releases.

CI/CD & releases

Pipeline

Workflow Trigger What it does
.github/workflows/tests.yml every push / PR to master test job: Python 3.10–3.14 matrix — installs the latest yt-dlp and the plugin, runs all test files in tests/ (as plain scripts and under pytest), plus tools/check_install.py. test-min job: installs the declared yt-dlp floor. build job: builds sdist + wheel (packaging sanity check), uploads a dist artifact.
.github/workflows/publish.yml GitHub Release published, or manual dispatch (Actions → Publish to PyPI → Run workflow; the tag input is required and must be an existing tag) test job: runs the full suite — a red commit cannot be published. build job: validates the tag (CalVer format, real calendar date, exists in the repo), injects it into pyproject.toml (asserted), builds sdist + wheel, uploads the artifact. publish job: uploads to PyPI (see below).

How the PyPI upload is authenticated — Trusted Publishing (OIDC)

No API token is stored anywhere. PyPI is configured to trust this repo's publish.yml workflow running in the pypi environment; at publish time GitHub presents a short-lived OIDC token, PyPI verifies it and mints a 15-minute API token that is used for the upload. The workflow declares environment: pypi + permissions: id-token: write, and skip-existing: true makes re-runs idempotent (PyPI versions are immutable, so re-uploading the same version would otherwise fail).

One-time setup (done 2026-09-16):

  • GitHub → repo Settings → Environments → environment pypi
  • PyPI → account → Publishing → pending GitHub publisher: owner fgsfds1, repo yt-dlp-yandex-music-plugin, workflow publish.yml, environment pypi, project name yt-dlp-yandex-music (the project was created automatically on first publish)

If the repo is ever moved/renamed, or the workflow file is renamed, re-register the publisher at PyPI → account → Publishing.

Release process

  1. Commit the changes to master (wait for Tests to go green).

  2. Tag the commit with the CalVer version (no v prefix):

    git tag 2026.09.16 && git push origin 2026.09.16
    
  3. Create and publish a GitHub Release for that tag (the published event is the trigger):

    gh release create 2026.09.16 --title "2026.09.16" --notes "..."
    

    or GitHub UI: Releases → Create a new release → pick tag → notes → Publish release.

  4. Watch Actions → Publish to PyPI.

  5. Verify: https://pypi.org/project/yt-dlp-yandex-music/ shows the new version, and in a fresh venv:

    python3 -m venv /tmp/ymtest && /tmp/ymtest/bin/pip install yt-dlp-yandex-music
    /tmp/ymtest/bin/python tools/check_install.py   # all lines OK
    

    Note: PyPI displays PEP 440-normalized versions — tag 2026.09.23 appears on PyPI as 2026.9.23 (zero-padding stripped). That is correct behavior, not a bug.

Version edge cases

  • Same-day fix: tag 2026.09.16.1 — a new release, not a re-upload.
  • Pre-release: tag 2026.09.16rc1 and tick Set as pre-release on the GitHub Release. Note that pip install skips pre-releases unless given --pre.
  • Broken release: PyPI versions are immutable — cut a new version (.1 suffix or a new date). You can delete a version as the project owner (PyPI → project → release → delete), but a new version is cleaner.
  • Re-run / re-publish: Actions → Publish to PyPI → Run workflow (optionally with a tag input), or re-run the release run — skip-existing makes this idempotent.
  • What CI does not test: live downloads need Yandex session cookies, which are not a CI secret. tests/test_sign.py pins the signing algorithm against captured live vectors, and the key-rotation path is smoke-tested manually (see QUICKSTART troubleshooting).

Tests

python3 tests/test_sign.py              # signing algorithm vs. captured vectors
python3 tests/test_url_matching.py      # extractor URL matching (per-regex + full resolver)
python3 tests/test_preview_warning.py   # silent smart_preview guard
python3 tests/test_rsc_payload.py       # RSC payload parsing (playlist/album preloads)
python3 tests/test_key_refresh.py       # hmac_key extractor-args, 403 handling, key auto-refresh
python3 tests/test_artist_pagination.py # artist track-list pagination loop
python3 tests/test_track_extract.py     # quality fallback + metadata mapping
python3 tests/test_playlist_extract.py  # playlist/album/artist-albums extractors

tests/test_sign.py verifies the signing algorithm against signatures captured from live web app traffic (2026-08-17), including the codecs-without-commas gotcha and the plugin's own codec/transport parameter combination. tests/test_url_matching.py verifies that each extractor matches exactly its own URL space (all TLDs, query strings, malformed URLs) and that with the plugin loaded yt-dlp resolves each URL to the intended extractor (incl. the shadowed built-ins). tests/test_preview_warning.py verifies the stale-session (smart_preview) guard: it must warn on a preview-quality response or a stream far shorter than the metadata duration, and never break the extraction on network errors. tests/test_rsc_payload.py pins the Next.js RSC payload parsing that the playlist/album extractors rely on (escaped strings, unicode, braces inside values, truncated payloads). tests/test_key_refresh.py covers the hmac_key extractor-arg lookup (all CLI/SDK forms), every 403 response shape, the key-rejection / auto-refresh flow (pinned key, successful refresh, failed refresh with its negative cache, a failed fetch staying retryable, the same-key /clock-skew case), and the frontend key scan itself (all three a.u chunk-name styles, found / no-match / fetch-fail, the disk-cache round-trip). tests/test_artist_pagination.py pins the artist pagination loop (pager total, a pager that ignores ?page=, empty pages, the safety cap). tests/test_track_extract.py covers the lossless→nq quality fallback, the metadata mapping (incl. cover normalization), the real POST /tracks multipart request, and the not-found / unavailable error paths. tests/test_playlist_extract.py covers the playlist/album/artist-albums extractors end to end (full / short / missing preloads, the API fallbacks with the uuid guards, entry URL construction, multi-disc albums). tools/check_install.py verifies an installed plugin. All run in CI on every push/PR — see CI/CD & releases.

Layout

QUICKSTART.md                             3-step how-to (start here)
yt_dlp_plugins/extractor/yandex_music_v2.py   the plugin
.github/workflows/tests.yml                 CI: tests + packaging build
.github/workflows/publish.yml               CI: CalVer tag → PyPI (OIDC)
tools/check_install.py                      verify the plugin is installed
tools/extract_secret_key.py                   re-extract the HMAC key
tools/standalone_download.py                  yt-dlp-free downloader + M3U
tests/test_sign.py                            sign-algorithm regression tests
tests/test_url_matching.py                    extractor URL-matching tests
tests/test_preview_warning.py                 silent smart_preview guard tests
tests/test_rsc_payload.py                     RSC payload parsing tests
tests/conftest.py                             shared pytest fixtures
tests/test_key_refresh.py                     key rotation / 403 handling tests
tests/test_artist_pagination.py               artist pagination loop tests
tests/test_track_extract.py                   quality fallback / metadata tests
tests/test_playlist_extract.py                playlist/album/artist-albums tests
research/api-notes.md                         full API + RE documentation
research/cdp/                                 CDP capture scripts (Node ≥ 22)

The one-paragraph summary of the RE

The web player signs GET api.music.yandex.ru/get-file-info requests with sign = base64(HMAC-SHA256(key, ts + trackId + quality + codecs.join("") + transport)).rstrip("="). The key is a static app secret hardcoded in the frontend bundle (7tvSmFbyf5hJnIHhCimDDD as of v4.1603.1, where it lives in a per-platform player.secretKey config object). The gotcha: codecs are joined without commas for signing (commas in the URL). With quality=lossless&codecs=flac,mp3&transports=raw the server returns unencrypted strm.yandex.net URLs (MP3 320 / FLAC) that download without cookies. Full details: research/api-notes.md.

Disclaimer

  • Vibecoded: this plugin was written with heavy AI assistance ("vibecoded"). It works for its author, but the code is not audited, not reviewed, and not tested against every edge case. Use with appropriate skepticism.
  • Use at your own risk — no ban guarantee: this plugin talks to Yandex Music's unofficial web API with your personal session cookies. Nothing here is endorsed by or affiliated with Yandex. The author cannot guarantee that using it will not lead to rate limits, CAPTCHAs, or (in the worst case) restrictions on your Yandex Music account. Keep request volumes reasonable, and if you value the account highly, think twice before hammering it.
  • Personal use: this is for downloading content you are entitled to access (your own subscriptions, e.g. personal playlist archiving). Respect Yandex Music's Terms of Service and applicable law; the built-in extractor's own documentation already assumes cookie-based personal use.

License

MIT — see LICENSE.

Metadata

Release files for yt-dlp-yandex-music 2026.9.24

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for yt-dlp-yandex-music 2026.9.24
File Size Uploaded
yt_dlp_yandex_music-2026.9.24.tar.gz 66.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for yt-dlp-yandex-music 2026.9.24
File Interpreter ABI Platform
yt_dlp_yandex_music-2026.9.24-py3-none-any.whl Python 3 none any Details

Total release size: 89.5 kB

Release files / yt_dlp_yandex_music-2026.9.24.tar.gz

Download URL yt_dlp_yandex_music-2026.9.24.tar.gz
Size 66.7 kB
Tags Source
SHA-256 checksum
How to use checksums
61c2a8ea81be0653280cf13ee02b3f87e48a5aa5684301679a1160ce8345f665
BLAKE2b-256 checksum
How to use checksums
6809113efb1de5e22482cfd0754e1b9a26c9f42495c5b357154302df9588930d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 23, 2026.

Transparency log

Release files / yt_dlp_yandex_music-2026.9.24-py3-none-any.whl

Download URL yt_dlp_yandex_music-2026.9.24-py3-none-any.whl
Size 22.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
339eb1867d8104d213f3653cf46584d1b7c5295178cd7ec82184ec5778cc840d
BLAKE2b-256 checksum
How to use checksums
9eaf1edff75471add8103d32a6634eeebe8ec3e3028b88960ab77444d9e43583
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 23, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

2026.9.24 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page