Direct answer. After this site finishes a Baidu transfer, download links.txt — one HTTPS URL per file on branded object storage (dl.baidudownloaderfree.com), not a hotlink to pan.baidu.com. In Internet Download Manager open Tasks → Import → From file list (or the equivalent menu on your build), pick that file, and start the queue. Multi-thread works because IDM talks to R2, not Baidu’s edges. URLs expire in 48 hours; objects are deleted after 7 days.
If you already have a completed job, skip to import below. If you are still stuck on Baidu’s page — no mainland phone, crawl speeds, or a share that refuses foreign logins — start with how we download Baidu Netdisk without a Baidu account, then return here for the download manager step. This article is the handoff from “job completed” to files on your disk.
Why links.txt instead of Baidu’s own download button?
Baidu’s browser download is built for logged-in users on Chinese routes. Free accounts are throttled; outside China the same edge often crawls. Scripts that scrape a “direct link” from pan.baidu.com still leave your laptop talking to Baidu. When the cookie dies mid-file, multi-connection managers thrash or fail.
Our pipeline reverses that. A server SVIP verifies the public share, lists the tree, transfers into a temp folder, then streams every byte to Cloudflare R2. Only after that export mints links.txt: one HTTPS GET per file. IDM, Aria2, and Motrix all accept one URL per line. Multi-thread works because the bytes already left Baidu on the server — your manager hits object storage with normal range requests, never a Baidu session. That is why the hostname is dl.baidudownloaderfree.com, not pan.baidu.com.
What is inside links.txt?
Plain text. One completed file produces one line. Nested shares encode the relative path in the object key (and often the URL path) so same basenames in different folders do not collide on storage. Empty folders produce no line. Export is available only when the job is Completed or still serving as Cleaned — partial jobs do not mint a full list.
Two clocks matter. Each URL is valid for 48 hours from mint. Objects are deleted after 7 days. Pause a queue carefully: finish inside 48 hours or re-export while objects still exist. We do not keep a permanent public mirror of other people’s shares.
How do I import links.txt into IDM?
- Wait until the job shows completed, then download
links.txt. - In Internet Download Manager open Tasks → Import → From file list (some builds say “Import URL list from text file”).
- Select the file. Confirm one queue row per URL and set the destination folder before starting all.
- Start downloads with multi-connection enabled. Do not paste the lines into a browser tab expecting Baidu cookies — they do not apply.
- If a file 403s after a long pause, the 48-hour signature expired. Re-download
links.txtwhile objects remain inside 7 days and import only the missing lines.
Aria2 and Motrix use the same file. Aria2: --input-file=links.txt. Motrix accepts paste or file import depending on build. Contract: HTTPS, one URL per line, no auth header from you.
What happens to nested Baidu folders in IDM?
URLs encode the relative path, but IDM’s default import often flattens everything into one destination folder. Two files named readme.txt in different remote directories can overwrite each other on disk. Set a careful destination, enable path-preserving options if your IDM build has them, or use Aria2 with a controlled directory option for deep trees. A single pre-zipped archive is fine to flatten. Multi-file project packs need a plan before Start all. Large trees may also hit the guest gate — see share folder size limits.
IDM + links.txt vs browser vs official client
| Method | Where bytes come from | Multi-thread | Account you need | Main failure mode |
|---|---|---|---|---|
| This site + IDM / Aria2 | R2 via dl.baidudownloaderfree.com | Yes, normal HTTPS ranges | None on Baidu; site account only if share >100 files or >5 GiB | 48h URL expiry / 7-day object delete |
| Browser on pan.baidu.com | Baidu edges from your IP | Weak / single stream | Baidu login, often +86 SMS | Throttle, geo path, login wall |
| Official Baidu client | Baidu app protocol | App-limited for free users | Baidu account + client install | Signup and SVIP upsell outside China |
| Hotlink / userscript | Still Baidu from your laptop | Fragile | Cookie or UA tricks | Breaks when Baidu rotates checks |
This is not generic “10 IDM tips”. The load-bearing detail is the host after transfer. If the URL still points at Baidu, multi-thread will not fix international routing. If it points at our object storage after a completed SVIP pull, IDM is the right tool.
What should I check before I submit a share?
Only public https://pan.baidu.com/s/… links work. Group shares and friend-only or enterprise packs that Baidu will not transfer fail on purpose. Wrong or missing 提取码 fails at inspect — see the extraction code (提取码) guide.
Guests can finish jobs without registering here (reCAPTCHA when enabled). The gate is whole-share: more than 100 files or more than 5 GiB needs a free account on this site — not a Baidu account. The rule is enforced in the API, not only in WordPress. Baidu Pan only; Quark, 123Pan, Alipan, and Weiyun will not produce a job. If the official site is the slow part, read why Baidu Netdisk is slow outside China — after our pull, speed is between your ISP and R2.
End-to-end steps from share URL to IDM queue
- Copy the full
pan.baidu.com/s/URL from the address bar. - Paste it on the homepage. Add the 提取码 if it is not already in
?pwd=. - Wait for Checking…. Confirm file count and size. Sign in on this site if the guest gate blocks you.
- Open the job page until status is completed (queued → transferring → pulling → completed).
- Download
links.txt, import with Tasks → Import → From file list, set destination, finish within 48 hours.
Troubleshooting IDM after a successful job
All URLs 403 immediately: old file or 48-hour window closed — re-export while objects remain. Some files fail: re-import only those lines. “Invalid URL” on every row: open the text file and confirm real https:// lines, not an HTML error page. Low speed: check local congestion and antivirus HTTPS scanning; multi-connection usually saturates a home line once the server pull is done. Job still “pulling”: wait — IDM cannot help until completed. Job failed before export (group share, cancelled link, rotated code): fix the share; another SVIP will not change Baidu’s refusal.
Frequently asked questions
Does IDM download from pan.baidu.com when I use this site?
No. After the job completes, each line in links.txt points at branded object storage on dl.baidudownloaderfree.com. The server SVIP already copied the bytes off Baidu. IDM never needs a Baidu cookie and should not open the original share page.
How long do the download links last?
Presigned download URLs last 48 hours. Objects are deleted after 7 days. Export again only while objects still exist; after retention you must resubmit the share if you still have access.
Can Aria2 or Motrix use the same links.txt?
Yes. One HTTPS URL per line. Aria2 accepts it as an input file list; Motrix and similar managers import plain URL lists the same way. No Baidu plugin is required after the job completes here.
Why does a large folder ask me to sign in on this site?
Guests are limited to at most 100 files and at most 5 GiB per share. Larger public Baidu shares need a free account on this site so we can schedule more SVIP capacity. That login is not a Baidu Netdisk account and never replaces the 提取码.
Start a job and open IDM when it finishes
Paste a public Baidu share, wait for completed, download links.txt, import with Tasks → Import → From file list, and pull from object storage while the 48-hour URLs are live.