v2rayN: Desktop Subscriptions and Routing
Top pick
v2rayN is a good fit for managing subscriptions in one place on a desktop and for users who regularly work with routing rules. Keep subscriptions from different sources in separate groups under Subscription Group Settings. If an update fails, you can troubleshoot that group without deleting and reimporting your entire node list. On Windows, choose between the desktop edition and the classic WPF edition: if you're installing for the first time, start with the desktop edition; if you prefer the familiar interface and workflow, stick with WPF. On macOS, choose the package for your processor. On Linux, check which package format your distribution uses. To connect a browser that follows system settings, first try System Proxy → Automatically Configure System Proxy from the tray menu. For apps that ignore that setting, consider Enable Tun. This helps you verify that the node works before troubleshooting traffic handling.
v2rayNG: Everyday Connections on Android
Recommended
If your provider supplies an Xray configuration or supports common Android import methods, v2rayNG is the first client to try. Add the subscription URL in Subscription Group Settings, then choose Update Subscription to fetch the nodes. Saving the URL and updating the list are separate steps, so an empty list doesn't necessarily mean the import failed. Start a node and approve the VPN permission prompt the first time you connect. On Android, the VPN service routes traffic through the client; you don't need to look for the desktop-only Automatically Configure System Proxy setting. When migrating from another setup, start with the default routing scope to confirm the connection, then adjust per-app settings. If the connection works but specific apps don't behave as expected, check whether they're included in the traffic scope before reimporting the entire subscription.
v2flyNG: Keep Using a v2fly Configuration
Alternative Core
Choose v2flyNG because you need its core, not because its interface looks simpler. If your provider specifies v2fly or an existing configuration works reliably with that core, test one confirmed-compatible node before importing the full subscription. This helps you tell whether an issue is with an individual configuration or with subscription updates, groups, or routing. When switching from v2rayNG, don't rely on familiar node names appearing in the list: a successful import only means the client read the entry, not that its core supports the protocols, transport, and security settings it contains. If the configuration requires an Xray-specific feature such as REALITY, stick with v2rayNG. If it specifically requires v2fly, choose a suitable policy in v2flyNG's Routing Settings rather than copying every setting from another client.