Open-source project
qjfoidnh/BaiduPCS-Go avatar
qjfoidnh/BaiduPCS-Go

BaiduPCS-Go puts a Linux style shell on Baidu netdisk, and keeps losing features when the provider moves

Based on the original iikira/BaiduPCS-Go, with added support for saving shared links and instant-upload (rapid-upload) links.

5,936 stars725 forksGoApache-2.0

At a glance

What is it?
BaiduPCS-Go is a Go command line client for Baidu netdisk with wildcard paths, shared link transfer, share management and offline downloads. Its release history is a running log of interface changes on the provider side, which tells you which parts of the client to trust.
Who is it for?
BaiduPCS-Go fits people who already live in a terminal and want Baidu netdisk reachable from scripts and from a remote shell. It does not fit anyone who needs transfer or share behaviour that survives the next provider side change.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 67 days ago.
What is it written in?
Mainly Go, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • qjfoidnh/BaiduPCS-Go5,936 ★ · +276
Star history
Repository2026-09-232026-11-15
qjfoidnh/BaiduPCS-Go5.7k5.9k

276 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Wildcards and Tab completion sit at the center of the shell layer

A BaiduPCS-Go binary started with no arguments drops the terminal into an interactive mode that behaves like a Linux shell. The cursor line reads `BaiduPCS-Go >` before any account is loaded, and switches to `BaiduPCS-Go:<working directory> <Baidu ID>$ ` once you are signed in, so the prompt tells you whether authentication took. Netdisk paths take wildcards, and Tab completes commands and paths. The shell is a real part of the tree rather than a wrapper: pcsliner/ sits beside the peterh/liner v1.2.2 dependency that drives line editing, pcstable/ renders table output through olekukonko/tablewriter v0.0.4, and pcsutil/ and pcsverbose/ sit alongside them. If characters come out as garbage, the fix named in the notes is to set the terminal encoding to `UTF-8`.

Installing means cross compiling, because prebuilt binaries sit behind one link

Compiled builds for the common platforms are linked from one Lanzou cloud page with the password `4pix`, and everything else starts from source. The module is `github.com/qjfoidnh/BaiduPCS-Go` and go.mod asks for go 1.23. Cross compiling is the documented route: set GOOS and GOARCH, list the supported pairs with `go tool dist list`, and build with CGO disabled. From Linux or macOS the Windows 64 bit binary is one line.

code
GOOS=windows GOARCH=amd64 CGO_ENABLED=0 go build

From a Windows shell, the same build targeting Linux 32 bit takes four lines.

code
set GOOS=linux
set GOARCH=386
set CGO_ENABLED=0
go build

The tree carries what a release needs: build.sh, versioninfo.json, Info.plist, entitlements.xml, BaiduPCS-Go.exe.manifest, resource_windows_386.syso and resource_windows_amd64.syso, plus a debian/ folder. On Windows the program expects Command Prompt or PowerShell, and mintty such as GitBash can render it badly. urfave/cli v1.22.5 provides the command layer.

v4.0.0 took resumable upload away and made rapid upload mandatory

Uploads are where the rules moved. In v4.0.0 the notes say an interface change means uploads no longer support resuming, and that downloads are unaffected. The same release brought `--norapid` back for skipping rapid upload, and extended `--policy` on the upload command to `skip`, `overwrite` and `rsync`, with a config key for the global default. Single file uploads reach 128G as of v3.9.9, the release that also stopped preallocating files on download and forced rapid upload calculation for uploaded files because the provider interface moved. Upload concurrency is configuration: since v3.7.1 both the number of parallel files and the chunk count per file can be set. v3.8.7 moved the file size check ahead of the real upload. The most honest entry is v3.8.5, whose own changelog says a known fault made uploads fail and produced empty files, and tells you to skip that version.

Rapid transfer has been switched off and restored four times

Rapid transfer saves a file into your drive by hash instead of copying bytes, and it is the least dependable thing here. v3.9.2 dropped short link support after an interface change. v3.9.3 cancelled the feature because the provider blocked it in principle. The v3.9.5 beta restored it for long and short links with a warning that it required developer authorization and that stability was unknown. v3.9.5 shipped it behind an accessToken set through `setastoken --help`, while rapid upload for local files needs no accessToken at all. v3.9.6 turned the whole thing off again and fixed ordinary transfer instead. Error code 9019 came out of transfer in v3.9.1, v3.7.8 added a `--fix` flag for blocked rapid links, and v4.0.2 fixed a false report that STOKEN was missing. Verify the instant transfer path against the release you actually run.

Transfer and share collect flags faster than they lose parameters

The transfer command accepts share links, including password protected ones. v4.0.2 added a `--fs_id` flag so you can pick individual objects out of a shared folder instead of taking the whole thing, and that release also made transfer accept share codes. v3.8.6 had already accepted links carrying their own extraction code, and v3.7.5 allowed a multi file share to be archived into a directory named after the first file, a path the notes flag as unsupported for rapid transfer. On the sharing side, `-f` prints a link that includes the password, custom share codes and validity days arrived in v3.7.3, and `share list` reports how many times each share was downloaded. v3.7.4 added support for pointing uploads at a custom upload server. Set, list and cancel all exist as separate share subcommands.

Download kept its resume path while thread count stays capped

Downloads kept what uploads lost. Several files or whole directories can be fetched in one call, transfers resume after an interruption, and a single file can be split for parallel download. The recommended ceiling on download threads is 12, a limit the v3.8.6 notes attach to issue #172. Both the concurrency and the maximum number of simultaneous downloads are config values, and v3.7.1 had to fix the latter not taking effect. v4.0.2 raised the ceiling on objects: directories holding more than 1000 entries can now be listed and downloaded. Two flags control local layout, `--fullpath` keeps the full structure from the drive root and `--mtime` preserves the modification time. Since v3.7.0 file verification after download is off by default and the config can switch it back on.

What this client will not do, and what it leaves undocumented

Three limits are stated outright. It gives you no download speed beyond what the official client gives you, and the notes send ordinary and SVIP users to the config section for their own account settings. Mobile is a poor target: Android and iOS are called troublesome, the prebuilt Linux arm64 build does not run on a phone, and you would need the source plus your own cross compile. Beyond that, every command leans on provider endpoints that move without notice, which is why unsupported parameters are deleted between releases and why v3.9.8 could remove features outright.

Editorial conclusion

BaiduPCS-Go fits people who already live in a terminal and want Baidu netdisk reachable from scripts and from a remote shell. It does not fit anyone who needs transfer or share behaviour that survives the next provider side change. Before committing, read the v4.0.2 notes for the transfer and upload commands, set your download thread count at or below 12, and confirm you can rebuild from source when a parameter disappears.

Frequently asked questions

Can I run BaiduPCS-Go on Android or iOS?

The project advises against it. Mobile operation is called troublesome, the prebuilt Linux arm64 build does not run on a phone, and mobile users have to download the source and cross compile for the device themselves.

Does BaiduPCS-Go download faster than the official Baidu client?

No. The README states the software provides no download speedup beyond the official client, and it points ordinary users and SVIP users to the program config section instead.

Why does the BaiduPCS-Go transfer command report a missing STOKEN?

That false report has been fixed more than once. v4.0.2 fixes transfer falsely reporting a missing STOKEN, and v3.7.7 fixed the same alarm. If you sign in with bduss, the notes say an stoken has to be supplied alongside it.

Official sources

  1. Issues
  2. License: Apache-2.0
  3. qjfoidnh/BaiduPCS-Go on GitHub
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/qjfoidnh-baidupcs-go.svg)](https://hysenlabs.com/projects/qjfoidnh-baidupcs-go)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/qjfoidnh-baidupcs-go.svg)](https://hysenlabs.com/projects/qjfoidnh-baidupcs-go)

Was this useful?