Generate a local --cookies-from-browser command without pasting cookie values into this site. Learn when authentication is needed, how browser and profile selectors work, and how to diagnose expired, locked, or incomplete sessions.
No cookie uploadBrowser profile syntaxSecurity-first guidance
LOCAL AUTH COMMAND
Generate a browser-cookie command
This helper outputs a local command only. It never asks for a cookie value, username, password, token, or browser profile upload.
Keep authentication on your deviceUse a browser profile you control and review the target URL.
Local command
DoClose a browser if its cookie database is locked, test with --simulate, and refresh expired sessions by signing in normally.
Do notPaste raw cookie values into websites, public issues, chat messages, screenshots, or shared configuration files.
Preferred approach
When a supported extractor needs login, use --cookies-from-browser with a browser profile you control. The command points gallery-dl at local browser storage; never paste raw cookie values into a website, issue report, or shared script.
AUTHENTICATE LOCALLY
Use gallery-dl cookies from Chrome, Firefox, or Edge
Sign in through the site's normal browser flow first. Confirm that the exact page is visible in that browser profile, then close private windows and consider closing the browser fully if its cookie database is locked. Run gallery-dl with --cookies-from-browser and the browser name. Add the supported domain or profile portion only when the default profile is not the one you tested.
The selector tells gallery-dl where to read cookies on your own device. It does not send cookie contents to gallery-dl.wiki. Browser storage formats and encryption can change, so keep gallery-dl current and use the official option documentation for the selector grammar supported by your installed release.
The official option accepts a browser selector with optional domain, keyring, profile, and container portions. Most people should begin with only the browser name. A domain restriction can reduce which cookies are read. A profile selector helps when the signed-in session is not stored in the default profile. Firefox containers are an advanced case and should be added only when you intentionally use them.
Profile names and paths can expose personal information. Treat the generated command as local data, especially when it includes a full filesystem path. If you request help, replace private paths, usernames, post URLs, and account identifiers with neutral placeholders while preserving the error type and gallery-dl version.
Selector part
Example
When to use it
Browser
firefox
Start here for the default profile
Domain
firefox/example.com
Limit cookie extraction to one domain
Profile
firefox:Profile Name
Use a known non-default profile
Cookie file
--cookies cookies.txt
Use an exported local Netscape-format file
Username/password
Extractor-dependent
Use only when official extractor docs explicitly require it
ALTERNATIVE INPUT
Use a local cookies.txt file with gallery-dl
The --cookies option can read a local cookies file, commonly in Netscape/Mozilla format. Export only from an account and browser profile you control, store the file with restrictive permissions, and delete it securely when it is no longer required. Do not upload it to this tool or attach it to a public support request.
A cookie file is a snapshot and may expire sooner than a browser session. It can also omit required cookies if an exporter filters domains or session values. When browser extraction works, it is generally easier to refresh by signing in normally. When a cookie file is necessary for a controlled environment, document its source and renewal process without recording the secret values.
Anyone who obtains valid session cookies may be able to act as the signed-in account. Never share them, and revoke sessions through the site when exposure is suspected.
DIAGNOSE IN ORDER
Fix gallery-dl cookie and login errors
First confirm the content is visible in the same browser profile while signed in. Next confirm the browser selector and profile, update gallery-dl through its original installation channel, and retry a small public or authenticated URL with --simulate. If browser storage is locked, close the browser completely. If decryption fails, verify that gallery-dl is running under the same operating-system user who owns the browser profile.
A 401 or login redirect often means cookies are missing or expired. A 403 can also come from site policy, rate limits, extractor changes, regional behavior, or a challenge that cookies alone do not solve. Do not repeatedly hammer the endpoint. Compare a clean --config-ignore request, wait when appropriate, and consult the current supported-sites notes or upstream issues without publishing sensitive logs.
Verify the page in the exact signed-in browser profile.
Start with only the browser name before adding profile syntax.
Close the browser if its cookie database is locked.
Run as the same operating-system user who owns the profile.
Update gallery-dl and test with --config-ignore --simulate.
Redact cookie values, private URLs, paths, and account identifiers from logs.
KEEP THE SESSION LOCAL
Keep gallery-dl cookies on your own device
Keep gallery-dl cookies on your own device throughout setup, testing, and troubleshooting. This helper only creates selector syntax; it has no reason to receive a cookie database, cookies.txt file, exported value, password, or private URL. Review the generated command locally and store scripts with the same care as any file that identifies a browser profile.
Keep gallery-dl cookies on your own device when requesting support too. Reproduce the problem with a public URL when possible, state the browser name and gallery-dl version, and redact account details and paths. If exposure is suspected, sign out other sessions or use the platform's session controls before testing again.
A simple security rule
Keep gallery-dl cookies on your own device; share the error category and a sanitized command, never the authentication material.
Is it safe to give gallery-dl my username and password?
Prefer browser cookies or the extractor's documented OAuth flow. Only use credentials when official documentation explicitly requires them, and never enter them on this site.
Does this helper upload my browser cookies?
No. It builds command text locally in your browser and never asks for raw cookie values.
How do I use Chrome cookies with gallery-dl?
Sign in with Chrome, then use --cookies-from-browser chrome with a supported URL. Add a profile selector only when the default is wrong.
Why does gallery-dl say the cookie database is locked?
The browser may have the database open. Close all browser processes and retry, or use another supported profile you control.
Why do valid cookies still return 403?
A 403 can reflect site policy, rate limits, challenges, regional behavior, or an extractor change. Stop repeated requests and isolate the cause with a clean simulated test.
Can I share gallery-dl cookies or cookies.txt to get help?
No. Keep gallery-dl cookies on your own device because cookie files can grant account access. Share only redacted errors, version information, and a public reproducible URL when permitted.
