v2rayN is a cross-platform V2Ray graphical client that supports mainstream protocols like VMess / VLESS / Trojan, with built-in subscription management, routing, and multi-platform support, covering Windows, macOS, Android, and Linux.
The client wraps V2Ray's underlying configuration into a visual interface, so even regular users can quickly import subscriptions, switch nodes, and set up routing. The following covers core capabilities across three dimensions: subscription management, routing, and kernel compatibility. Each dimension corresponds to a set of real, actionable settings.
v2rayN lets you create separate groups for multiple subscription links, each with its own auto-update interval. When auto-update is enabled, the client fetches the latest node list in the background, eliminating the need to manually copy and paste subscription URLs. Different groups can have different update frequencies—for example, frequently used nodes update daily while backup nodes update weekly, reducing resource usage.
Multiple subscription sources can coexist in the same client without interfering with each other. v2rayN manages nodes from different sources using groups and tags—switching groups switches the node pool. Nodes support drag-and-drop sorting, or can be automatically arranged by latency or name, making it easy to find a working line. Groups can also have independent auto-update policies to match different nodes' update rhythms.
The built-in latency test tool sends real connection requests to each node and judges availability based on response time. Results are color-coded green, yellow, and red—nodes with high latency or timeouts are automatically flagged. After testing, you can sort by latency to pin the fastest nodes to the top, reducing repeated switching. The test interval is customizable to avoid burdening nodes with frequent requests.
Routing rules are based on two data tables: geosite (domains) and geoip (IP addresses). v2rayN includes common rules, such as directing geosite:cn traffic directly and sending geolocation-!cn through the proxy. Rules are matched from top to bottom—once a rule matches, it executes and stops further matching. Rule order affects the final split result, so new custom rules should be placed in the appropriate position.
This is the most common split scenario: mainland China websites and traffic go direct locally, while overseas traffic goes through proxy nodes. v2rayN's default routing rules already include this configuration, and users can adjust it themselves. This split ensures fast access within mainland China while reducing proxy bandwidth consumption, letting proxy nodes handle only necessary traffic. Rule priority settings affect the actual split result—after adjusting, restart the client to verify.
Advanced users can write their own rule groups in routing settings, assigning specific domains, IP ranges, or ports to designated nodes. Rules support wildcards and regular expressions for precise traffic control. Custom rules must follow V2Ray's routing syntax and take effect in real time after configuration—no client restart needed. If a rule is written incorrectly, the client will prompt you; just follow the prompt to fix it.
v2rayN supports switching between V2Fly and Xray cores. The Xray core has more complete implementations of newer protocols like VLESS, XTLS, and REALITY, with better performance. Users can choose a default core in settings, and different groups can bind different core versions to meet various needs. After switching cores, you need to reconnect nodes for the change to take effect.
The client supports multiple proxy protocols including VMess, VLESS, Trojan, and Shadowsocks, and nodes in a subscription can be mixed. The client automatically identifies node types and selects the corresponding protocol implementation—no manual configuration needed. Protocol selection only affects the transport method, not the higher-level subscription management logic. Different protocols differ in performance and security, so consider protocol type and latency when choosing nodes.
v2rayN covers Windows, macOS, and Linux desktop, while v2rayNG and v2flyNG cover Android mobile. All four platforms use the same subscription links, so node lists stay consistent after import. Desktop and mobile differ slightly in advanced options like routing rules and DNS settings, but basic usage is the same. Users can choose the appropriate client based on device type and share the same subscription configuration.
Three clients cover four platforms—v2rayN is the top choice for desktop, v2rayNG for mobile. Each platform has corresponding installation packages and system requirements, and the download page offers version selection and access to historical versions.
v2rayN desktop uses a new-generation cross-platform UI, while the classic WPF version remains stable. Suitable for Windows 10 and above.
Go to Download →Available for both Apple Silicon and Intel—choose the package that matches your chip. macOS 13 and above.
Go to Download →v2rayNG uses the Xray core and supports arm64 and universal builds; v2flyNG is available as a v2fly core alternative.
Go to Download →Offers deb and rpm packages supporting mainstream distributions, plus an arm64 architecture entry.
Go to Download →Project V is a collection of open-source tools for proxy scenarios, consisting of the V2Ray core, routing rule databases, and surrounding components. It defines transport protocols like VMess and VLESS, as well as routing matching based on geosite and geoip. The entire project is released under open-source licenses—code is inspectable, versions are traceable, and community maintenance has continued for years. The client wraps the underlying configuration into a graphical interface, so regular users don't need to edit JSON files directly.
V2Fly is a community-maintained fork of V2Ray that continues the original core's functionality and stability. Xray builds on V2Fly with extensive performance optimizations and introduces newer protocols like VLESS, XTLS, and REALITY. v2rayN, v2rayNG, and v2flyNG are based on these two cores, wrapping the underlying configuration in a graphical interface so users can manage nodes, set up routing, and switch protocols without editing config files directly.
Both clients and cores are released under open-source licenses—anyone can view the source code, contribute translations, or submit fixes. New versions are released periodically, fixing known issues and adding protocol support. Subscription management means users don't need to manually update config files—the client automatically fetches the latest node list in the background. Multi-platform clients share the same subscription format, so importing once lets you use it on multiple devices.
Open-source proxy toolset defining VMess / VLESS protocols and routing mechanisms.
Community-maintained V2Ray fork keeping the core stable and continuously updated.
Optimized from V2Fly, supporting newer VLESS / XTLS / REALITY protocols.
The latest articles on client usage and troubleshooting, covering routing configuration, connection checks, and port conflicts.
Using v2rayN as an example, this explains how to write geosite and geoip rules and their priority, providing a complete rule set that directs mainland China websites directly and sends all other traffic through the proxy.
Read More →When the proxy shows connected but pages won't load, check five areas step by step: node availability, time sync, DNS resolution, system proxy settings, and routing rules.
Read More →When the client reports a port conflict, use the netstat command to find the process using 10808/10809, then decide whether to end the process or switch to another local port in settings.
Read More →Here are the questions users ask most often—click to jump to the full answer page.