Start from the device and the configuration model
| Client | Main platform | Best fit | What this page verifies |
|---|---|---|---|
| Shadowrocket | iPhone, iPad and other Apple platforms | Users who need a rules-based client on Apple hardware and will check the config format | Client and line service are separate; store price and system requirements follow the actual listing |
| Surge | Apple platforms | Users who need detailed rules, policy groups, request inspection and network debugging | Configuration structure explained from the official manual; no provider-compatibility judgement |
| sing-box | Cross-platform core and official clients | Users who want one configuration model across platforms and understand inbound, outbound and route | Only concepts supported by official documentation; no promise that third-party subscriptions import cleanly |
| v2rayNG | Android | Android users who will check the config format against the current version | Based on the official repository and current release material; no assumption that every protocol works |
Shadowrocket: buying the client is not buying a line
Shadowrocket is a client. Subscriptions and nodes come from your own provider. When obtaining the app, check the App Store listing, the developer and the app identifier; do not treat a same-named app, a shared account or a third-party installer as an official build.
The listing confirms that the app can import rule files from a URL or from iCloud Drive. That is not the same as “any provider subscription imports directly”. After you have your own configuration, compare the format the provider states against what the app supports, then check inside the app whether nodes actually appear.
If the node list is empty, check in this order: whether the address is still valid, whether the response is a configuration rather than a login page, whether the provider requires a specific format, whether the client has network permission, and whether the device clock is correct. Never post a private subscription address in a public troubleshooting thread.
Surge: four sections, and one of them decides everything
Surge's quick-start documentation splits a configuration into [General], [Proxy], [Proxy Group] and [Rule]: global settings, proxy policies, policy groups, and rule matching. Rules are evaluated from top to bottom, and the matched rule decides whether traffic is proxied, rejected or sent direct.
A policy group is not a node. select takes a manual choice, url-test picks by test result, and fallback takes the first available by priority. After importing a provider configuration, check which policy group the final rule points at — otherwise you can end up with “the node connects but traffic actually goes DIRECT”.
sing-box: a file extension is not a compatibility check
sing-box organises configuration around inbound, outbound, route and DNS. A JSON file generated by a third-party tool can still contain deprecated fields, client-private fields, or protocol options the installed version does not implement, even when the filename looks right.
Before importing, confirm the target client explicitly supports the format, and check the fields against the documentation for that version. When parsing fails, keep the failing field name and the client version and consult the migration notes. Do not delete TLS, certificate or security fields to force an import through.
One distinction that saves time: “the subscription did not update” and “the rule set failed to download” look like network errors but read different objects. A normal subscription is served by your client or provider; a remote rule set is route.rule_set with type: remote; a local rule set reads a path on the device. Read the failing tag first, then decide which source to check.
v2rayNG: format and version, not protocol folklore
On Android, the practical questions are which formats the current release imports and whether the provider's configuration matches it. A share link, a Base64 subscription and a Clash YAML are three different inputs. Importing the wrong one produces an empty list or a parse error, not a network problem.
Keep the version visible in your notes. Reports about a specific field or protocol behaviour belong to a specific release, and “it worked on my old phone” is not a version statement.
The failure that all four share
Every one of these clients can show a populated node list while traffic still goes direct. The reason is the same in each: the node list and the routing decision are different objects, and the second one decides. Check, in order:
- Is a node selected as active?
- Is the capture method (system proxy, VPN/TUN) actually in effect?
- Does the matched rule point at the proxy, at DIRECT, or at a rejected policy?
- Does one real HTTPS request succeed end to end?
Latency indicators do not answer question four. They show that something answered on some path at some moment.
What this comparison does not claim
This page describes checking procedures, based on each project's official documentation. Menu names and supported formats follow the installed version, not this page. Nothing here judges whether a particular provider is compatible with a particular client, and no client on this list supplies lines by itself.