A field-by-field comparison of the 10 proxy clients people actually ask about — so you can pick by requirement instead of by screenshot.
Scope note: every cell below is a checkable fact (platform, core, license, price model), verified against the official project pages in November 2026. Anything that changes per-region — App Store price, subscription tiers — is explicitly marked as "check the store", not stated as a number. If a cell says open source, the source is on GitHub; this repo does not claim a specific license type for any client without checking it first.
| Client | Platforms | Core | TUN | Rule system | Source | Price |
|---|---|---|---|---|---|---|
| Clash Verge Rev | Windows, macOS, Linux | Mihomo (Clash Meta) | Yes | Clash rule providers | Open source | Free |
| FlClash | Windows, macOS, Linux, Android | Mihomo | Yes | Clash rules + overrides | Open source | Free |
| v2rayN | Windows (x64/x86/arm64), Linux, macOS 11+ | Xray, sing-box, Mihomo | Yes | Xray routing | Open source | Free |
| v2rayNG | Android | Xray | Yes (VpnService) | Xray routing + per-app | Open source | Free |
| Shadowrocket | iOS, macOS | Proprietary | Yes | Rule-based | Closed source | Paid (store price varies by region) |
| Surge | iOS, macOS | Proprietary | Yes (Enhanced Mode) | Rule + script | Closed source | Paid (tiered) |
| Stash | iOS, macOS | Proprietary, Clash-compatible config | Yes | Clash-style rules | Closed source | Paid |
| sing-box | Windows, macOS, Linux, Android, iOS | sing-box | Yes | Route rules + rule-sets | Open source | Free |
| Hiddify | Windows, macOS, Linux, Android, iOS | sing-box | Yes | Routing rules | Open source | Free |
| Karing | Windows, macOS, Linux, Android, iOS, tvOS | sing-box | Yes | Routing rules | Open source | Free |
Minimum OS observed (from official download pages, Nov 2026): v2rayN → Windows 10+ / macOS 11+ / Debian 9+ · Karing → iOS 15+, tvOS 17+, Android 8+ · verify your own platform before downloading, these move.
Pick in this order. Most people start at step 3 and end up reinstalling twice.
- iOS / iPadOS → Shadowrocket, Surge, Stash, sing-box, Hiddify, Karing. The first three are paid and closed; the last three are free.
- Android → v2rayNG, FlClash, Hiddify, Karing, sing-box.
- Windows → Clash Verge Rev, FlClash, v2rayN, Hiddify, Karing, sing-box. (v2rayN is the most mature on Windows; Clash Verge Rev has the better GUI.)
- Linux desktop → Clash Verge Rev, FlClash, v2rayN, Hiddify, Karing, sing-box. Only some have a GUI; sing-box is CLI-first.
- Apple TV → Karing (tvOS 17+).
System proxy only covers apps that respect the system proxy setting. Browsers usually do; games, terminals, Docker, and many native apps do not.
TUN captures at the network layer, so everything is covered — but it needs a privileged service (Windows: admin + service install; macOS: network extension; Linux: root/CAP_NET_ADMIN). TUN is also where most "no internet after enabling" reports come from.
If you only need browser traffic, system proxy is enough and has far fewer failure modes. If you need SSH, Docker pulls, or a game client to go through the proxy, you need TUN.
Three families, and they are not interchangeable:
- Clash / Mihomo YAML → Clash Verge Rev, FlClash, Stash (compatible), Mihomo-based setups
- Xray JSON / share links → v2rayN, v2rayNG
- sing-box JSON → sing-box, Hiddify, Karing
Most subscription providers give you a URL that returns one of these based on a parameter or a separate path per format. Feeding a base64 node list to a YAML parser is the single most common import failure — see the error reference below.
Rule syntax differs meaningfully:
- Clash family — rule providers, proxy groups,
RULE-SETremote lists - Xray family — routing rules with domain/IP/port matchers, geoip/geosite databases
- sing-box — route rules with typed rule-sets, and newer versions moved several fields around (which is why "unknown field" errors appear after upgrades)
If you switch clients across families, expect to rewrite your rules, not import them.
| What people do | Why it fails |
|---|---|
| Install a client, then import a subscription without checking the returned format | Parser mismatch. The subscription "works" in the browser because you're looking at base64 text, not a config. |
| Enable TUN as the first step | TUN has the most prerequisites (service, privilege, routing). Get system proxy working first, then escalate. |
| Compare clients by node speed | The client is a transport shell. Speed comes from the node and the route, not the GUI. |
| Judge a client by "it supports the most protocols" | You use one protocol per subscription. Protocol count is not a differentiator in practice. |
| Use a paid client expecting better nodes | Paid clients sell the app, not the nodes. Nodes come from your subscription. |
| Switch clients to fix a "connected but no internet" problem | That fault is almost always DNS, rules, or a second network-takeover tool. Changing clients usually reproduces it. |
Machine-readable version of this reference (field mapping and the full error table, no JavaScript): https://overnice2025.github.io/
If this comparison saved you from installing three clients to find out, star the repo.
- Error code reference — exact error strings from Clash Verge Rev, v2rayN, v2rayNG, Hiddify, sing-box, FlClash, and what each one means
- Subscription format notes — base64 vs YAML vs JSON,
subscription-userinfo, conversion pitfalls - Client setup guides (ZH) — full walkthroughs with download verification steps
- Troubleshooting index (ZH)
Corrections welcome — open an issue with the official source URL and the date you checked it. Cells that can't be verified against an official page will be removed rather than guessed.
MIT — see LICENSE.