NekoBox and v2rayNG: What They Are and When to Choose Them

NekoBox and v2rayNG show up in every Android proxy discussion, usually in the same breath as Clash clients — but neither of them is one. They are built on different cores, speak different configuration formats, and belong to ecosystems that grew up in parallel with the Clash world rather than inside it.

That makes them the wrong first pick for some people and exactly the right tool for others. This article explains what each client is, how the two differ from mihomo-based apps like Clash Meta for Android, and the concrete situations where reaching for them is the sensible move.

Two clients from outside the Clash family

A proxy client is a shell around a core, and the core defines the ecosystem. Clash-family apps embed mihomo and consume Clash-format YAML: node lists, proxy groups, rule-based routing in one document. NekoBox embeds sing-box; v2rayNG builds on the v2ray/Xray lineage. Different cores, different native config formats, different conventions for how servers are shared and organized. Keeping that frame in mind, the individual clients are easy to place.

NekoBox for Android: the sing-box option

NekoBox, developed by MatsuriDayo, is an open-source Android client built on the sing-box core. sing-box is a newer universal proxy platform with notably broad protocol coverage, and NekoBox packages it in an approachable app: profiles, groups, per-app proxying, routing options. People typically arrive at NekoBox for one of two reasons — a provider offering protocols best served by sing-box, or a deliberate preference for that ecosystem's tooling. The project lives at github.com/MatsuriDayo/NekoBoxForAndroid.

v2rayNG: the long-standing choice

v2rayNG, developed by 2dust, is one of the oldest continuously maintained Android proxy clients, built on the v2ray/Xray core family. Its model is server-centric: you import individual servers via share links (the vmess:// and vless:// style strings passed around in this ecosystem) or via its own subscription mechanism that delivers lists of such links, then pick one to connect through. It is simple to operate and enormously widespread — when a provider hands you a share link and nothing else, v2rayNG reads it natively. Source and releases are at github.com/2dust/v2rayNG.

How they differ from Clash clients

• Configuration format. Clash/mihomo clients consume one YAML document describing everything. NekoBox and v2rayNG revolve around per-server entries and their own profile formats — a Clash-format subscription is not their native food, and a share-link list is not mihomo's.
• Routing philosophy. In the Clash world, rules and proxy groups arrive inside the subscription, so routing is provider-defined and rich out of the box. In v2rayNG, routing is configured in the app; sing-box sits somewhere between, with powerful but differently-shaped rule configuration.
• Subscription compatibility. Ask your provider which formats they publish. Many offer several — a Clash YAML link for mihomo clients and a share-link list for the others. The format must match the client, or the import simply fails.

When they are the right choice

• Your provider distributes only share links or a non-Clash subscription — v2rayNG consumes them directly.
• You specifically want the sing-box ecosystem or a protocol best supported there — NekoBox.
• You already run sing-box or Xray configs elsewhere and want your phone to match.

If none of these apply and you hold a standard Clash-format subscription, a mihomo client remains the smoother road on Android — Clash Meta for Android or FlClash will import it directly with routing intact.

Getting them and first steps

Our download center mirrors one arm64-v8a build of each; for any other architecture or an older release, use the official GitHub releases linked above. Either way, pick the right architecture (arm64-v8a suits most modern phones; the architecture guide decodes the options). First run follows the same arc in both: install, import a server via share link or subscription, select it, and start the VPN service when Android asks for permission. For the mihomo-based alternatives and how all five clients stack up feature by feature, our download center and the comparison article linked above are the natural next stops.