TLS Fingerprint
Why some sites can only be downloaded using GD, and how to switch.
Why other downloaders are blocked
Some sites inspect the network fingerprint of download tools. The fingerprint of ordinary downloaders differs significantly from a real browser, so they are directly rejected (403) or shown a verification page.
GD can emulate a real browser's network fingerprint, making the server think it is a normal browser request.
Global Settings
Settings → General Download Settings → Emulate Identity
| Option | Effect |
|---|---|
| Automatic | Default. Tasks from the extension automatically match the source browser; manually added ones use the latest Chrome. |
| No emulation | Disables fingerprint emulation. Use only when you need to fully customize request headers. |
| Specific browser | Locks to Chrome / Edge / Firefox / Safari, etc. (specific version selectable). |
Per-Domain Switching
When a specific site requires a different fingerprint, create an identity preset:
Settings → Identity Presets → Add
Fill in the matched domain (supports *.example.com wildcards), select a fingerprint, and save. Tasks that match a preset automatically use the preset fingerprint.
Presets are matched in list order; drag to adjust priority.
When to Adjust
Keep it on "Automatic" for daily use. Switch manually in the following cases:
- A Task is rejected with 403 → Right-click the Task → Edit → switch to a different browser fingerprint
- The same site is repeatedly blocked → create an identity preset for that domain
- Speed is unusually slow → try changing the fingerprint and reducing the subworker count