Nine cloud drives inside one browser helper
LinkSwift is built for a very specific frustration: a file is visible in a Chinese cloud-drive website, but getting a usable download URL or handing the job to a preferred downloader is awkward. The userscript injects its own controls into Baidu Netdisk, Aliyun Drive, China Mobile Cloud, Tianyi Cloud, Thunder, Guangya, Quark, UC, and 123pan. It can expose links, copy commands, adjust parts of the page, and send downloads to supported desktop or RPC tools.
That scope is its main appeal. Someone who encounters links from several Chinese sharing services does not need a different browser add-on for each one. LinkSwift also supports Windows, macOS, Linux, and Android through compatible browsers and userscript managers. The README lists Chrome 76 or newer and Edge 88 or newer, while the script metadata also names Firefox, Safari, and Opera.
This is not a cloud-drive speed hack. The maintainer is unusually direct about that point: links come from public provider APIs, and faster transfers may reflect account status, local networking, or a provider's current bandwidth policy. If your only goal is to defeat a service's limits, the project explicitly says it does not do that.
Installation is easy, operation is conditional
The happy path is short. Install Tampermonkey, ScriptCat, or another suitable manager, choose the stable source, and approve the userscript. A canary source tracks newer fixes for people willing to trade stability for quicker compatibility work. GitHub, ScriptCat, and OpenUserJS are the documented distribution channels, although the README warns that OpenUserJS updates can lag.
There is no build process for ordinary users. The repository's main artifact is a single userscript, and its package configuration mainly supplies ESLint for development. Once installed, LinkSwift runs at the start of matching cloud-drive pages and loads its controls there. That is far easier than deploying a server.
The setup becomes less tidy when downloads leave the browser. Aria2, BitComet, AB Download Manager, and IDM each bring their own client, RPC, or association settings. Version 1.1.3 added IDM client settings, while earlier releases added BitComet and AB Download Manager paths. LinkSwift can bridge the page and the downloader, but it cannot configure or secure those applications for you.
English readers face a more basic obstacle. The README, changelog, release notes, issue forms, and most user-facing explanations are Chinese. Browser translation can make installation understandable, but it is a weak substitute when diagnosing an API error or interpreting a provider-specific option.
Broad coverage creates a permanent maintenance bill
Every supported drive is an external dependency that LinkSwift does not control. The changelog is essentially a record of that reality: releases repeatedly adapt to new 123pan pages, Quark and UC sharing pages, Baidu authorization changes, Aliyun domains, and China Mobile or Thunder behavior. This history shows attentive maintenance, but it also tells buyers what will break next.
Current issue activity makes the cost concrete. Reports filed in August 2026 say the download controls are absent or links cannot be obtained on Thunder, Quark, China Mobile Cloud, and a redesigned 123pan sharing page. Another open Quark report describes cookie handling that can make pushed downloads fail. These are user reports rather than confirmed failures on every account and browser, but several providers appearing together is enough to rule out unattended reliability.
The stable release is another tradeoff. Version 1.1.3 arrived in February 2026 with IDM settings, better link caching and floating notices, and a Baidu share-page adaptation. Its own notes list a large Thunder dialog and misleading AB Download Manager failure feedback as known problems. The repository has continued receiving code since then, and the README identifies a 1.1.3.1 preview, so the release tag alone does not signal neglect. It does mean users may need the canary build to get work newer than the stable package.
Useful power features, with browser-level trust
LinkSwift does more than place a download button. It can copy links and cURL or Aria2 commands, push tasks to external downloaders, cache links, handle multiple service configurations, change some cloud-drive styling, and offer batch-oriented flows. These touches matter when moving many files or sending jobs to another machine.
The convenience requires meaningful trust. The script operates inside authenticated cloud-drive pages and requests cross-origin access so it can call provider APIs and downloader endpoints. That is normal for this type of tool, but it places a large, remotely installed script close to account data and download credentials. Use one of the project's stated sources, review update prompts, and avoid copies from unofficial mirrors. The AGPL-3.0 license makes the code inspectable, not automatically safe.
Health and the decision
The repository was last pushed on August 5, 2026. Issues were still being filed and discussed later that month, and GitHub showed 29 open issues plus three open pull requests. More than 19,000 stars indicate a substantial audience, while the long changelog shows four years of adaptation rather than a short experiment. The maintainer also asks users to report bugs only through GitHub, which keeps the public tracker central.
Documentation is adequate for Chinese-speaking existing users, not polished onboarding. It clearly names supported services, install sources, stable and canary channels, limitations, versions, and years of changes. It does not provide a structured tour of each provider, downloader configuration examples, or an English route through troubleshooting.
LinkSwift is worth installing if those nine services are part of daily life and copying links into download tools wastes time. It is broad, popular, and actively adjusted. Just treat it as a convenience layer over websites that can change without notice. For a critical archive job, verify the generated links, keep the official client nearby, and expect occasional provider-specific downtime.