Client Settings · Review

V2Ray Reviewv2rayN Download Guide

Download v2rayN View the Guide

Start with subscription import, routing rules, and log troubleshooting. Choose a client for your platform, then check each connection setting.

  • PROTOCOL NOTES
  • VMess
  • VLESS
  • Trojan
  • REALITY
04 Platforms 03 GUI Clients Xray · V2Fly Core Families Open-source projects Free to use
CLIENT NOTES / SETTINGS

V2Ray Client Settings

Separate nodes, routing, and traffic capture before changing settings. A client starting successfully does not mean app traffic is reaching the proxy core.

For desktop use, start with v2rayN; for Android, check v2rayNG first. Consider v2flyNG when you specifically need V2Fly compatibility. All three clients provide a graphical interface, but their menus, core capabilities, and system permissions differ. Choose based on your platform, node protocol, and use case—not the number of toggles in the interface.

Keep one node with verified, complete settings while you configure the client. Test a single-node connection before enabling subscription updates or complex routing. Change one setting at a time and compare logs before and after. The five guides below follow a typical workflow. Menu names can change between versions; if you cannot find a setting, first confirm which client you are using.

v2rayN / v2rayNG / v2flyNG

Subscription Groups and Single-Node Imports

Subscriptions are useful for managing node lists that change over time; single-node share links work well for quick tests or moving a node to another device. In v2rayN, save the subscription URL in a subscription group, then update it. On Android, add it in subscription settings. After importing, check the group, node count, and protocol fields before selecting a node. The clients may parse some share-link formats differently, so the URL prefix alone does not guarantee compatibility. If an update fails, check that the URL is complete and whether the request is going direct or through the proxy. Avoid repeatedly deleting your existing settings.

Where to find this settingv2rayN → Subscription Groups → Subscription Group Settings
PLATFORM / DOWNLOADS

Choose a Client for Your Platform

Check your operating system and processor architecture first, then compare installation options. The download page lists available builds and their requirements.

Client installers and node subscriptions are separate. Installing a client sets up the local tool; you still need valid node settings to connect. The subscription provider controls node availability, update frequency, and service status. When moving to a new device, you can import the same subscription on both, but routing rules, app proxy coverage, and local ports still need to be checked separately. Syncing nodes does not sync every setting.

Windows

Recommended: v2rayN

A good fit if you need subscription groups, rule editing, and desktop log views. The download page offers Desktop and Classic WPF editions: Desktop uses a newer cross-platform interface, while Classic WPF retains the traditional workflow. Choose based on the menus you know and your existing settings; interface differences do not indicate node speed.

On first launch, check the local listening port, import a node, and choose a system proxy mode. If a browser works but a standalone app does not, check that app's own proxy settings. Test TUN separately if you need broader traffic capture. Work device restrictions and existing network software can also prevent a virtual network interface from being created.

Go to Downloads

macOS

v2rayN

A good fit if you want a similar subscription-management workflow across desktop systems. Open About This Mac before installing to identify whether your processor is Apple Silicon or Intel, then choose the matching build. The installers target different processors, so do not choose based only on file size or download order.

If macOS shows a security alert when you first open the app, confirm the download source and read the alert before following the system's authorization steps. After enabling the proxy, test both your browser and the target app. Whether an app honors the system proxy or has its own network settings affects the result. Back up your old settings before moving them, and do not carry over local file paths from another operating system unchanged.

Go to Downloads

Android

Recommended: v2rayNG

For typical setups, start with v2rayNG, which uses the Xray core. Choose v2flyNG when you specifically need V2Fly compatibility. The download page offers arm64 and universal builds. Most newer phones use arm64; if you are unsure, check your device's architecture.

After importing a subscription, select a node, start the connection, and approve the system VPN prompt. A running notification only confirms that the local service is active; test with an actual request. If the connection drops when the screen locks, check battery optimization, background permissions, and network changes. If only one app fails, check app-level proxy coverage to make sure it is included.

Go to Downloads

Linux

v2rayN

A good fit if you want GUI-based subscription management and are comfortable checking how your desktop environment handles network traffic. Choose deb or rpm for your distribution, then confirm whether your processor is x64 or arm64. Package format and processor architecture are separate requirements; matching one does not guarantee the other.

Desktop environments and apps can handle the system proxy differently. Check that the client is listening, then test the request path in the target app. Terminal programs may not use the desktop proxy settings. Before enabling TUN, understand the permission and routing changes. After stopping the client, check that network access has returned; a leftover system proxy setting can look like a node failure.

Go to Downloads

Browse all clients →

Common Download and Connection Questions

What else do I need after installing the client?
You need valid node settings or a subscription URL. The client reads and applies configuration; it does not create a working remote service. First learn the difference between a single-node share link and a subscription URL, then follow the guide to import the right one.

Read the subscription import guide →

The node test passed. Why can't my app connect?
The test and the app may use different network paths. Check the system proxy, TUN, or per-app settings, then look for the app's requests in the logs. A successful test does not replace checking the app itself.

Find causes by symptom →

Will switching clients fix every timeout?
Not necessarily. Node service status, your network, and configuration compatibility can all affect the connection. Compare clients using the same node and network conditions to distinguish client-specific issues from problems with the route.

Browse common questions →

Can I share my subscription URL for troubleshooting?
A subscription URL may contain access credentials. Share a redacted error message, client name, and steps to reproduce instead. Check screenshots and backup files too, so you do not accidentally expose node passwords.

Learn about configuration and subscription management →
PROJECT V / OPEN-SOURCE ECOSYSTEM

How Cores, Clients, and Subscriptions Differ

Project V is a good starting point for understanding the V2Ray ecosystem. V2Fly and Xray are related core families, while GUI clients provide interfaces for managing nodes and system settings.

Project History and Differences in Capabilities

V2Ray uses a configuration model built around inbounds, outbounds, and routing, separating traffic reception, protocol handling, and path selection. V2Fly continues the maintenance and development of the V2Ray project, while Xray evolved from related code into its own implementation and extensions. They share some technical concepts, but their features do not evolve in lockstep. Similar-looking configurations do not mean every field is interchangeable.

When following a guide, check both the client and the core. Features such as REALITY require support in the relevant implementation. Importing a node, generating a valid configuration, and establishing a connection are three separate checks. If an error mentions an unknown field or unsupported transport parameter, check the core's capabilities before changing routing.

Graphical Clients and Runtime Cores

v2rayN, v2rayNG, and v2flyNG are open-source GUI clients for managing subscriptions, editing settings, and controlling services. v2rayN targets desktop systems and centralizes configuration and core selection. v2rayNG is primarily for Android and Xray; v2flyNG offers another way to use V2Fly on Android. They share some workflows, but their interfaces and configuration backup formats are not identical.

When moving from a computer to a phone, share links and QR codes are usually easier to verify than copying an entire configuration directory. After importing, check that the node is selected, the app is included in proxy coverage, and DNS and routing suit the new device. Do not reuse desktop listening addresses, file paths, or permissions on Android unchanged.

Open-Source Licenses and Free Use

Open source means the code is available under its applicable license, which permits viewing, using, and modifying it within the license terms. The V2Fly core uses the MIT License, and Xray-core uses the MPL-2.0 License. GUI clients and their dependencies have their own applicable licenses; a core's license does not automatically apply to every component in an installer.

These clients are free to use, but the client and remote service are independent. Subscription charges, data limits, and node expiration are set by the service provider. Separating “can the tool start?” from “is the remote service available?” helps avoid mistaking an unavailable service for a reason to buy another client.

Updates, Compatibility, and Rollbacks

Client updates can change the interface, configuration generation, and bundled core dependencies; core updates can change protocol support or behavior. Before updating, save subscription groups and custom rules, and note which traffic-capture method currently works. After updating, test your existing node first, then restore extra settings one at a time. Avoid changing the client, node, and DNS all at once.

If something goes wrong, reproduce the issue and check startup logs before deciding whether the error points to a configuration compatibility problem. Updating a subscription refreshes the node list from the provider; it does not update the client or core. The download page and quickstart cover installation and setup, while the troubleshooting guide links log, port, DNS, and system proxy checks to specific symptoms.

Configuration → Inbound → Routing → Outbound Read the Troubleshooting Guide
FIELD NOTES / PRACTICAL GUIDES

Subscriptions, Logs, and Device Migration

Start with a specific question: find the setting, identify where the failure occurs, then decide what to change.

Browse all articles →