01 / DESKTOP
Windows
Use v2rayN to manage subscriptions, servers, the system proxy, and routing rules. Check your system architecture before downloading, then keep the configuration folder in a stable location.
Go to downloads// INSTALLER INDEX · English Docs
Download V2Ray clients
Enter v2ray5.com to find the right client for Windows, macOS, Android, or Linux, then continue with English guides to import subscriptions, configure proxy modes, and manage routing.
Free forever
Open source
English docs
Xray · V2Fly
PLATFORMS / 04
CLIENTS / v2rayN · v2rayNG · v2flyNG
CORES / Xray · V2Fly
MODEL / OPEN SOURCE
// CLIENT CAPABILITIES
Core client settings
From importing a subscription to system proxy settings, routing, and runtime logs, these four panels cover the operations most users perform every day. Rather than presenting isolated terms, the guide explains what each setting does, when to change it, and what to check afterward.
select feature → read field note
Choose the exit based on the destination type
Routing sends different domains, IP ranges, or rule sets through different exits. A practical approach is to keep the client’s built-in rules, add only the custom rules you need, and place specific rules before broader ones. v2rayN can combine domain, ip, and geosite matching. Change one rule group at a time, then use the runtime log to confirm that traffic reaches the intended exit. Compared with global forwarding, split routing is better suited to long-term use because local services, LAN addresses, and selected sites can keep their normal connection paths.
routing.rules[].domain · routing.rules[].ip
Maintain server lists with groups
Subscription management handles bulk configuration imports and later updates. When adding a link, make sure the copied content is complete, then give the subscription an identifiable group name; only after an update will its servers appear in that group. When several subscriptions coexist, avoid deleting and recreating them repeatedly. Keep a stable group structure and sync changes through updates. If the list is empty afterward, check the link boundaries, network connectivity, whether the group is enabled, and the response shown in the log. v2rayN and v2rayNG place these controls differently, but the workflow is largely the same.
subscription.updateInterval · subscription.group
Separate system proxy coverage from TUN coverage
The system proxy affects programs that follow the operating system’s proxy settings, making it a good default starting point on desktop. Apps that ignore those settings need their own configuration or TUN. Before enabling either mode, select a working server and confirm that the core is running. After switching modes, do not rely only on a button color; check the client status, system proxy indicator, and actual requests. Start with the fewest variables: establish a basic connection through the system proxy, then learn bypass rules and TUN. This makes it easier to tell whether a problem comes from the server, rules, or traffic interception scope.
systemProxy · tunMode · inbound.socks
Trace problems through startup, connection, and routing logs
The runtime log is not an auxiliary window; it is the first source of evidence that the configuration is working. Start with the latest core startup entry, then follow configuration loading, DNS resolution, connection establishment, and route matching. If the interface says the client is running but requests fail, record which stage fails instead of switching several settings at once. Common clues include an occupied port, unreadable subscription data, an incorrect system clock, abnormal DNS responses, and unmatched rules. Keeping one complete reproduction is more useful than capturing only the final error line.
logLevel: warning · routing decision · core startup
// PLATFORM ENTRY
Choose an installer by operating system
Start with v2rayN on desktop platforms, and choose v2rayNG or v2flyNG on Android based on your preferred core. A platform link opens the download page and switches to the matching section, where file formats, architecture options, and system requirements are explained.
02 / DESKTOP
macOS
Use v2rayN and choose the installer for Apple Silicon or Intel. Grant network permissions when prompted, and approve the first launch in the system security settings if needed.
Go to downloads03 / MOBILE
Android
Choose v2rayNG for Xray or v2flyNG for V2Fly. Most recent devices use arm64; choose the universal build if unsure, then import your subscription and allow the network connection.
Go to downloads04 / DESKTOP
Linux
Use v2rayN and choose deb or rpm for your distribution, with arm64 builds for ARM devices. If the core does not start, check permissions, port usage, and the log path.
Go to downloads// QUICK START
Three steps from installation to activation
For first-time setup, install the client, import the subscription, and enable the proxy separately. Confirm the result after each step before continuing. This avoids changing several settings at once and makes problems easier to locate.
-
01
Choose a client and install it
Start with v2rayN on desktop platforms and v2rayNG on Android. Before downloading, check the operating system, processor architecture, and installer format rather than judging by a single part of the filename. Launch the client once after installation to confirm that the main window, settings, and log area open correctly. On desktop, keep the configuration directory somewhere permanent; on mobile, allow the required network connection permission so the local interception interface can be created later.
If the program does not start normally, no subscription has been imported yet, so the likely causes are system compatibility, file permissions, or the runtime environment. Fix startup first, then configure the client; this produces clearer results than changing routing, DNS, and TUN immediately.
-
02
Add a subscription and update the server list
Create a group in the subscription manager, paste the complete link, save it, and run a manual update. Adding a subscription and updating it are separate actions: saving the link alone does not add servers to the list. After the update, check the group name, entry count, and update time, then select a server as the active entry.
If the list is empty, copy the link again and check for spaces at either end, then look for read or parse errors in the log. Name subscriptions separately so you can identify each server’s source later. Regular updates sync changes from the service, but there is no need to delete and recreate groups every time the client starts.
-
03
Enable the proxy and verify the actual route
On desktop, start by enabling the system proxy; on Android, select a server and start the connection. Do not equate a running status with every app using the connection. Whether an app follows the system proxy, whether routing rules match, and whether DNS behaves as expected all affect the result. Begin verification with an ordinary network request, then test domains and apps that require split routing.
Once the basic connection is stable, adjust LAN bypass rules, rule mode, or TUN as needed. Change one item at a time and keep the working configuration from before the change. If the connection breaks, inspect the latest startup and routing entries in the log instead of switching multiple servers and modes.
// OPEN SOURCE ECOSYSTEM
How Project V, V2Fly, and Xray relate
V2Ray is commonly used to describe an open network proxy technology ecosystem, not just one graphical program. Project V established early configuration structures, protocol implementations, and modular processing patterns. The community later developed different maintenance paths, including the V2Fly and Xray core families. Graphical clients organize subscriptions, server lists, system proxy settings, routing rules, and logs into usable interfaces; the selected core performs the actual connection, transport, routing, and DNS work.
Understanding the boundary between the client interface and the core helps isolate problems. If the interface will not start, check operating system compatibility and permissions first. If the interface works but the core fails to start, inspect ports, generated configuration, and runtime logs. If the core runs but a particular request takes the wrong path, continue with DNS, routing rules, and interception scope. Treating every symptom as a client failure can hide the layer where the error actually occurs.
ECOSYSTEM
Project V technology ecosystem
An open implementation ecosystem for protocols, transports, routing, and configuration models.
V2Fly core family
A community-maintained path descended from the V2Ray ecosystem, callable by graphical clients such as v2flyNG.
Xray core family
Develops independent capabilities while retaining compatibility with common configuration concepts; v2rayN and v2rayNG commonly use this core path.
01 / CLIENT
v2rayN: desktop graphical management layer
v2rayN targets Windows, macOS, and Linux, bringing subscription groups, server entries, the system proxy, routing rules, DNS, TUN, and core status into one place. Its main value is turning structured configuration into repeatable interface workflows while preserving access to logs and advanced parameters. For most desktop users, mastering subscription updates, active server selection, and the system proxy is enough to establish a stable baseline; move to routing and advanced settings when you need finer control.
02 / CLIENT
v2rayNG: Android and Xray path
v2rayNG is a common graphical client for Android and typically runs with the Xray core. Its mobile interface supports subscriptions, share links, individual configurations, routing rules, and local connection controls. Mobile operating systems impose extra controls on background activity, battery usage, and network permissions. As a result, the same server configuration may work differently on desktop and mobile without any protocol parameter changing; also check whether the system is limiting background processes or network interception.
03 / CLIENT
v2flyNG: V2Fly core alternative
v2flyNG also serves Android users but follows the V2Fly core path. It suits users who want to retain V2Fly configuration practices or compare different core behaviors on the same platform. Choose based on the core family, supported configuration scope, and compatibility with existing subscriptions—not just similar names. Most users can start with v2rayNG; choose v2flyNG when you have a clear V2Fly requirement, rather than migrating configurations repeatedly without understanding the difference.
Open-source licensing and reviewable implementations
All three clients and their related cores belong to an open-source ecosystem. Open implementations allow the community to discuss and review configuration generation, protocol handling, and feature changes, while enabling different clients to build their own interfaces around shared concepts. For users, more practical criteria are maintenance activity, documentation quality, system compatibility, and update history—not merely interface style or naming.
Update mechanisms and configuration migration
Client updates may change the interface, core, rule data, or default settings. Before updating, note the client type and configuration directory; afterward, confirm that subscription groups, the active server, and proxy mode still exist before checking new options. When moving between clients, the subscription link is often safer than manually copying an entire configuration directory. Custom routing and DNS rules should be recorded separately because fields do not always correspond exactly between clients.
Core changes and routine maintenance
Core capabilities evolve along different maintenance paths, and clients may adjust which settings are visible. Daily use does not require chasing every new parameter. A stable setup should be judged by whether it starts, subscriptions update, requests follow the rules, and logs remain free of persistent errors. After an upgrade changes behavior, read the client’s change notes and compare routing, DNS, and TUN settings before and after the upgrade; this is usually more effective than reinstalling immediately.
// COMMON QUESTIONS
Selected frequently asked questions
These four topics cover the most common decisions after a first installation. More complete guidance on subscriptions, proxy modes, server testing, and troubleshooting is collected on the troubleshooting page.
How should I choose between v2rayN, v2rayNG, and v2flyNG?
Choose v2rayN first on Windows, macOS, and Linux desktop platforms. Android users generally start with v2rayNG using the Xray core, and choose v2flyNG when they specifically need the V2Fly core. Base the decision on the operating system, core family, and source of the existing configuration—not on treating the three names as different installers for one program.
Why is the server list still empty after adding a subscription?
You must update the subscription after adding its link. If the list remains empty, check that the link is complete, the group is enabled, and the network request succeeded, then look for read or parse errors in the log. Do not create multiple duplicate groups before checking the log, or later cleanup and diagnosis will become harder.
What is the difference between the system proxy and TUN?
The system proxy mainly affects apps that actively read the operating system’s proxy settings. It is simple to configure and a good desktop starting point. TUN covers more traffic but adds routing, DNS, permission, and virtual interface variables. Get the system proxy working reliably first, then decide whether to enable TUN based on which apps bypass the proxy.
Why are actual requests not following the rules when the client says it is running?
A running status only means that the client or core process has started. You must also confirm the active server, system proxy status, app coverage, DNS, and routing rules. Use the log to determine whether the request entered the core, then see which rule and exit matched it. If the request does not appear in the log, the problem is usually in the app’s proxy settings or the system interception layer.
// LATEST NOTES
Client and routing notes
Recent articles focus on client comparison, routing-rule priority, and the v2rayN interface structure. Each article addresses one specific question, making it easy to move from installation into subscription management and advanced configuration.
v2rayN, v2rayNG, or v2flyNG? A platform and feature comparison
Compare the three clients across platform support, core family, subscription management, and routing features. Includes default choices for desktop and Android, plus guidance on when v2flyNG is the better fit.
Read the full article →Writing custom V2Ray routing rules: domain, ip, geosite matching, and priority
Organizes domain, ip, and geosite matching syntax, explains top-to-bottom rule evaluation, and shows how to order specific rules before broad ones.
Read the full article →A quick tour of the v2rayN interface: server lists, subscription groups, logs, and settings
Walks through the server list, subscription groups, log panel, and common settings from the main window, giving first-time v2rayN users a complete map of the interface.
Read the full article →