Windows
Start with the v2rayN desktop edition, or choose classic WPF for the familiar layout. Back up your settings before switching editions.
Go to downloads →Choose a client for your platform, follow the setup guide to import your subscription, then check routing and connection status.
Check your operating system and processor architecture before choosing an installer. The client reads your configuration; you’ll need to obtain the required subscription or server details separately.
Start with the v2rayN desktop edition, or choose classic WPF for the familiar layout. Back up your settings before switching editions.
Go to downloads →Check About This Mac to pick the Apple Silicon or Intel build of v2rayN. If macOS shows a warning, verify where you got the app before allowing it.
Go to downloads →Use v2rayNG for Xray or v2flyNG for V2Fly. Most devices use arm64; check the universal build if unsure. Approve the VPN prompt on first connection.
Go to downloads →Pick the v2rayN package for your distro (deb or rpm) and CPU (x64 or arm64). Test the connection in your browser and other apps.
Go to downloads →The installer determines whether the app can run on your system; protocol compatibility also depends on the core and server configuration. Before switching clients, check which protocols, transport methods, and required parameters your subscription uses so you don’t lose connection settings when migrating.
View all clients →Check subscriptions, routing, and DNS separately. Change one category at a time and keep a copy of the original settings so you can roll back.
A subscription URL retrieves server configuration; it isn’t something to enter in the server address field. In v2rayN, add the source under Subscription groups, enter a recognizable name, and save it. Then select Update subscription. If the list is empty, switch to All to check the filter, then review the update log. Create a separate group for each source to make future updates, disabling, and removal easier to manage. Subscriptions let you refresh server details in one place instead of entering each server manually, but their validity and contents are controlled by the provider. Treat subscription URLs like credentials and keep them private.
Explore the settings →Routing rules decide which outbound handles a request; they won’t fix a broken subscription or server. Start with the client’s preset routing to establish a working baseline, then add a few specific domain or IP exceptions. Rules are usually evaluated in order, so put more specific conditions before broader ones. When using GeoSite or GeoIP categories, make sure the databases are up to date and the category names exist. Clear exception rules are easier to understand than repeatedly switching global modes. After making a change, retest the same destination and check the logs to see which rule matched.
Explore the settings →Some apps don’t use the system proxy. If your basic connection works, try TUN mode to handle that traffic. On desktop, check that the client has the required permissions before enabling TUN mode, then make sure the virtual network adapter, routes, and DNS are set up correctly. TUN works at a different level from the system proxy; it isn’t necessarily faster and doesn’t replace sound routing rules. If other virtual networking tools are already running, avoid having them capture the same traffic. If enabling TUN cuts off your entire connection, turn it off to restore your baseline, then check permissions, the adapter, and the DNS path one at a time. Don’t layer on settings you haven’t verified.
Explore the settings →DNS settings determine how domain names are resolved; routing settings determine where connections go. Both need to work together. If a domain won’t load but its known IP address is reachable, check DNS logs first, then verify the route used to reach remote DNS. Your browser’s encrypted DNS may also create a separate resolution path, so the client’s DNS settings aren’t the whole picture. Rather than swapping in a public resolver straight away, identify whether resolution happens locally, through the proxy, or inside the app. Before enabling FakeDNS, confirm that your core and traffic-capture mode support it, and keep the original settings for rollback.
Explore the settings →The client manages configuration through its interface; the core handles the actual protocols. Before connecting, check the subscription’s protocol, transport, and security parameters, then confirm that the selected core supports them. Similar names don’t mean every extension parameter is interchangeable. v2rayN can use a compatible core based on its build and configuration, while v2rayNG and v2flyNG follow different core approaches. Instead of repeatedly changing installers, start by reading startup errors and field warnings. Back up your configuration before switching cores, then retest routing, DNS, and UDP behavior—don’t stop at confirming that the interface opens.
Explore the settings →Here, migration across four platforms means manually moving subscriptions and necessary settings; it doesn’t mean the client offers automatic cloud sync. On a new device, import your existing subscription again, then configure the system proxy, VPN permission, or TUN access for that platform. Avoid overwriting the entire desktop configuration folder: file paths, adapter names, and system settings may differ. Moving settings in stages is easier to troubleshoot than copying the whole environment: test one connection first, then move routing and DNS, and finally configure per-app rules. Exported configurations and QR codes may contain credentials, so delete temporary copies after sharing them.
Explore the settings →The interface illustrations show how settings relate; menu locations may vary between client builds. Routing snippets must be merged into a complete configuration. Before making changes, confirm which core and configuration format you’re using.
Start with the fewest settings needed for a working connection, then enable routing and traffic capture one step at a time. If something goes wrong, return to the previous step and check the result.
After installing the client, check whether you have a subscription URL, a share link, or a complete configuration file. Save subscription URLs under Subscription groups; import share links using the client’s clipboard option. Don’t mistake a web page address for a subscription URL, and never show a full link in a public screenshot.
In v2rayN, save the group and select Update subscription. Confirm that servers appear in the list. On Android, use v2rayNG’s add or import menu to load an existing configuration. If import fails, check the request error in the logs first. Determine whether the link has expired, the response format is wrong, or the network request failed before choosing what to try next.
Choose a server from the imported list and select Set as active server in v2rayN. On desktop, choose Set system proxy automatically if you want your browser to use the proxy. On Android, start the connection and approve the VPN request when prompted. Stick with the client’s default routing for now; don’t add custom rules yet.
The system proxy isn’t a universal setting that every app follows. If your browser works but another app can’t connect, check that app’s own proxy settings first. Read the TUN setup guide only if you need to capture traffic from apps that don’t use the system proxy. This helps keep permission issues separate from server problems.
After selecting Test real connection latency, open the websites or apps you actually use to verify the connection. A test result only reflects connectivity to its specific test target; it doesn’t prove that every domain, transport protocol, or app will work. Keep the target consistent between tests and note the proxy mode and routing settings you used.
Once the connection works, back up the configuration before adding routing exceptions, DNS, or TUN settings one at a time. Retest after every change; if something breaks, restore the last working setup. You can record error types and when they occurred, but remove subscription URLs, user IDs, and other credentials.
Understand the difference between the interface, core, and server configuration to see why the same subscription can behave differently across environments.
Project V is an open-source ecosystem built around network proxy technology, with V2Ray as one of its key components. The V2Fly community continues to maintain a related core, while Xray is another core project that grew from related technical foundations. They share some protocol concepts and configuration conventions, but their features, extensions, and support aren’t identical. So when you see “V2Ray configuration,” check which core it’s actually for instead of judging compatibility by the filename alone.
A protocol name is only one part of the connection requirements. The same VLESS or VMess configuration can use different transport methods, security layers, and routing settings. For features such as REALITY, check core support and server requirements; don’t guess at missing parameters. If the logs report an unrecognized field, check compatibility and where the configuration came from before resetting all your network settings.
v2rayN provides a graphical desktop interface for managing server lists, subscription groups, routing, and system proxy settings. It’s useful if you need to organize configurations from multiple subscription sources. The client turns interface settings into a configuration for the core, which handles the actual connection. Saving a setting in the interface doesn’t mean the server will accept it; check both the startup logs and an actual connection to confirm the result.
v2rayNG is designed for Android and uses the Xray core to handle proxy connections through the system VPN interface. It also offers subscription management and per-app settings. v2flyNG is also for Android, but uses the V2Fly core and can be an alternative for compatible configurations. Choose based on your subscription requirements and feature needs, then consider which interface you prefer. Similar names don’t mean their extensions, export formats, or behavior are identical.
All three clients have publicly available source code, and each client and integrated core has its own open-source license. A license explains the conditions for using, modifying, and distributing code; it doesn’t guarantee the quality of third-party subscriptions or network services. Consider the client project, core project, and subscription provider separately. Even identical interfaces can connect to entirely different services.
Subscription links, share links, and exported configuration files may contain account identifiers, access tokens, or key material. If you need help, the error message, steps to reproduce it, and mode name are usually enough; don’t post your full configuration. This site covers client settings and technical concepts. Check with the relevant provider about service validity, server access, and subscription contents.
Updating the client mainly affects its management interface and integrated features. Updating the core can change protocol support and runtime behavior. Updating GeoIP or GeoSite databases changes which rules match. Treat these as separate operations. If only a few domains are routed incorrectly, check the rule order and database first. If the core won’t start, check the configuration fields against the core’s capabilities.
Before updating, export a working configuration and note your current proxy mode and routing preset. Afterward, test the basic connection first, then check custom outbounds, DNS, and TUN. Don’t introduce several new settings at once. Subscription updates may also change the server list, so record important manual changes separately to avoid losing them on the next refresh. A clear test sequence makes configurations easier to understand than simply updating as often as possible.
Browse by symptom: first identify whether the issue involves the background, DNS resolution, or protocol differences, then open the relevant guide. Here are the three latest articles.
First distinguish ongoing network activity from frequent disconnects and reconnects, then check background activity restrictions. The article explains battery optimization exclusions and how per-app proxy settings can limit which apps are handled, so you don’t blame every battery issue on the core.
Read article →Start by checking whether DNS requests take the expected route, then review resolution settings in the client, operating system, and browser separately. Learn how remote DNS, domain rules, and TUN work together—and why test results may differ from what you expect.
Read article →Compare VMess’s built-in encryption and time validation with how VLESS is commonly paired with TLS or REALITY. Choose based on server support and the complete connection parameters—not the protocol name alone as a measure of speed or reliability.
Read article →If you haven’t made your first connection yet, follow the guide to establish a working baseline, then return to the in-depth articles to adjust one setting at a time. You’ll find the cause more easily with a specific error message and reproducible steps than by trying several configuration snippets at once.
View all articles →