Is it safe to paste my Suno cookie into SunoDown?

The cookie is kept in server memory only and is never written to a database or log file. It is discarded immediately when you click Disconnect, when the session expires, or when the server restarts. The cookie does not contain your Suno password — it is a session token that Suno itself issued to your browser.

Why can I not just enter my Suno email and password?

Suno uses Clerk for authentication, which protects login with CAPTCHA and bot detection that a third party cannot bypass. SunoDown asks for the cookie instead because it is the only way to act on behalf of your already-authenticated session without ever seeing your password.

How long does the cookie stay valid?

Suno's __client cookie is a long-lived refresh token; the short-lived JWT derived from it is refreshed by SunoDown roughly every 50 seconds, so long as the cookie itself remains valid on Suno's side. If you log out of suno.com or Suno rotates the cookie, you will need to copy a fresh value.

Do I need Pro just to download MP3?

No. MP3 downloads on SunoDown are free with no account at all. The Pro cookie is only needed to unlock the lossless WAV endpoint that Suno gates to paying subscribers.

I pasted the cookie but downloads still fail with 401. What now?

401 usually means the cookie is no longer valid. Open suno.com in the same browser, confirm you are still logged in, then repeat steps 2–4 with a fresh __client value. If the issue persists, your Pro plan may have lapsed — verify the billing status on suno.com first.

Will SunoDown be charged to my Suno account?

No. SunoDown can only access what your existing Pro subscription already entitles you to — it cannot purchase credits, upgrade your plan, or make any change to your billing. It only calls the WAV conversion endpoint on tracks you can already play.

Suno Pro Cookie Setup — Unlock Lossless WAV Downloads

A practical setup walkthrough for linking your Suno Pro session to SunoDown. No password is involved — just one session cookie. This page goes deeper than the in-app modal so you can decide whether to trust the flow.

Updated: 2026-05-26 · Reading time ~3 min · Required: an active Suno Pro or Premier subscription on the same browser

Before you start

You only need this guide if you want WAV. MP3 downloads, including bulk ZIP, are free and require no cookie at all — see the how-to guide for that path. If you are not sure which format you want, the MP3 vs WAV comparison answers it in one page.

The five steps

Step 1

Log in to suno.com

Open suno.com in your browser and sign in to the account that holds your Pro or Premier subscription. The __client cookie only exists once you are authenticated — if you are not logged in, step 3 will show no result.

Step 2

Open DevTools and navigate to Cookies

Press F12 (or Cmd+Option+I on macOS) to open DevTools. The cookies view lives under a different tab depending on the browser:

Chrome / Edge

Application tab → Storage → Cookies → https://suno.com

Firefox

Storage tab → Cookies → https://suno.com

Safari

Enable Developer menu (Settings → Advanced), then Storage tab → Cookies → https://suno.com

Brave / Arc / Opera

Same path as Chrome (Chromium-based browsers all share the same DevTools).

Step 3

Copy the `__client` value

Find the row whose name is exactly __client. Click it and copy the entire Value field — it is a long string that often starts with eyJ. Copy all of it. Do not copy the name, the domain, or any other field.

Step 4

Paste it into SunoDown

On suno-down.com, click the Pro badge in the header (it reads "Connect Pro for WAV"). Paste the value into the input field, then press Connect. SunoDown verifies the session against Suno and confirms your plan tier — you will see a green "Pro Connected" badge within a second or two.

Step 5

Switch the format toggle to WAV

Load any playlist, switch the format toggle from MP3 to WAV, and download. Each WAV is triggered as a Suno conversion job and then streamed back to your browser — a few seconds per track. The ZIP bulk download works exactly the same way for the whole playlist.

Ready to connect?

Open SunoDown →

What SunoDown actually does with the cookie

The security model, in plain terms

No password is involved. The __client cookie is the session token Suno’s own login flow placed in your browser. SunoDown never sees your email or password.
Stored in server memory only. The cookie is held in an in-process Map on the SunoDown server. It is never written to a database, never logged, never persisted to disk. A server restart deletes every connected session.
Discarded the moment you disconnect. Clicking "Disconnect" in the Pro modal evicts the entry immediately. So does Suno-side session expiry or any explicit logout.
Used for one thing. SunoDown calls Suno’s WAV conversion endpoint on your behalf and refreshes a short-lived JWT every ~50 seconds. It does not browse, post, or modify your Suno account.
Receives the same access you already have. The cookie cannot grant SunoDown anything beyond what your subscription already allows. It cannot purchase credits or change your plan.

The full data-handling policy is in the privacy policy.

Session expiry and reconnection

Suno’s authentication uses a long-lived refresh cookie (__client) and a short-lived JWT derived from it. SunoDown handles the JWT refresh automatically about every 50 seconds, so a single connection stays alive across a long download session. The cookie itself only stops working when one of these happens:

You log out of suno.com in the same browser.
Suno rotates your session (e.g., after a password change or device review).
Your Pro/Premier plan lapses — the cookie still exists but the WAV endpoint refuses it.

When that happens, SunoDown surfaces a "session expired" banner. Reconnecting is the same procedure: repeat steps 2–4 with a fresh __client value.

Troubleshooting

"Connection failed" right after pasting: Almost always a truncated or stray-character paste. Re-copy the entire Value field from DevTools — do not include the name or the surrounding quotes, but do include the full string. If the value is several hundred characters, that’s normal.
Connect succeeds but WAV downloads return 401: The cookie is valid but the JWT lost sync mid-session. Click Disconnect, then Connect again — that triggers a clean refresh. If it repeats, log back into suno.com and copy a fresh cookie value.
"WAV download requires Suno Pro or Premier plan" after a successful Connect: Your billing tier is not detected as Pro. Verify at suno.com that the subscription is active and that you are signed in to the right account before copying the cookie again.
Connection drops after a few minutes: JWT refresh failed and could not recover. Reconnect manually — the entire procedure takes under a minute. Connection drops repeatedly within the same browser may indicate that Suno has rotated your session; re-login to suno.com first.
I cannot find a __client row at all: You are probably not logged into suno.com in that browser. Open a tab to suno.com, sign in, and reload DevTools — the row appears as soon as Suno’s login completes.

Frequently asked questions

Is it safe to paste my Suno cookie into SunoDown?: The cookie is kept in server memory only and is never written to a database or log file. It is discarded immediately when you click Disconnect, when the session expires, or when the server restarts. The cookie does not contain your Suno password — it is a session token that Suno itself issued to your browser.
Why can I not just enter my Suno email and password?: Suno uses Clerk for authentication, which protects login with CAPTCHA and bot detection that a third party cannot bypass. SunoDown asks for the cookie instead because it is the only way to act on behalf of your already-authenticated session without ever seeing your password.
How long does the cookie stay valid?: Suno’s __client is a long-lived refresh token; the short-lived JWT derived from it is refreshed by SunoDown roughly every 50 seconds while the cookie remains valid on Suno’s side. If you log out of suno.com or Suno rotates the cookie, you will need to copy a fresh value.
Do I need Pro just to download MP3?: No. MP3 downloads on SunoDown are free with no account at all. The Pro cookie is only needed to unlock the lossless WAV endpoint that Suno gates to paying subscribers.
I pasted the cookie but downloads still fail with 401. What now?: 401 usually means the cookie is no longer valid. Open suno.com in the same browser, confirm you are still logged in, then repeat steps 2–4 with a fresh __client value. If it persists, verify your Pro billing status on suno.com first.
Will SunoDown be charged to my Suno account?: No. SunoDown can only access what your existing Pro subscription already entitles you to — it cannot purchase credits, upgrade your plan, or make any change to your billing. It only calls the WAV conversion endpoint on tracks you can already play.