Q2B Quark2Baidu CLI
GitHub

Move cloud files with one calm command

Q2B turns Quark-to-Baidu migration into a small, careful terminal workflow: npm install, local credentials, clear checks, and no extra backend.

Install from npm Open GitHub
Windows macOS Linux Node 18+
q2b transfer session
Quark Cloud source folders
Baidu Netdisk target path 
$ npm install -g quark2baidu
$ q2b doctor --online
ok  node runtime
ok  quark session
ok  baidu session
$ q2b
Rapid upload check 72%
Folder structure preserved

Designed for real migration days

The interface stays tiny, while the transfer path handles the fussy parts: path safety, fallback behavior, login checks, and clear recovery.

Rapid upload first

Q2B tries Baidu rapid upload before falling back to standard upload when the server-side cache misses.

Keeps folders intact

Recursive selection preserves the source layout under the Baidu target path you choose.

Safer by default

Diagnostics redact cookies, paths are normalized before requests, and failures are summarized for retries.

Local credential model

Cookies stay in your user config directory or environment, and Q2B does not use a proxy service.

Install once, then run q2b anywhere

Install from npm, configure once, then use q2b on Windows, macOS, or Linux with the same workflow.

Recommended Global npm install
npm install -g quark2baidu
npm package Node 18+ local config
After install A three-step run path
  1. 1

    Run q2b setup and paste Quark/Baidu cookies.

  2. 2

    Run q2b doctor --online to verify login state.

  3. 3

    Run q2b, choose files, and start the transfer.

A small command surface

Enough structure for everyday use, without asking non-developers to learn a new toolchain.

q2b setupSave cookies and defaults to a user-level config file.
q2bOpen the interactive Quark file picker and transfer selected files.
q2b doctor --onlineCheck Node, config, and current Quark/Baidu login status.
q2b config showPrint redacted config for support and debugging.

Safety and privacy commitments

  • Config is stored in the operating system user config directory, not inside the repo.
  • Cookie values are redacted in diagnostic output and can also be provided through environment variables.
  • Remote paths are normalized and checked before requests are sent.
  • No telemetry, proxy service, or third-party backend is used by Q2B.

From one route to a migration engine

Q2B starts with Quark to Baidu, then grows toward provider adapters and two-way cloud migration workflows.

Now Quark to Baidu

Cross-platform npm CLI, rapid transfer, fallback upload, and recursive selection.

Next Reliability layer

Resume state, transfer reports, rate-limit handling, and richer retry policy.

Later Provider adapters

A provider interface for more netdisks and two-way migration workflows.