v2rayN · v2rayNG · v2flyNG clients

V2Ray Help CenterClient downloads andsetup

Choose a client for your platform, follow the setup guide to import your subscription, then check routing and connection status.

Client selection and platform downloads

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.

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 →

macOS

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 →

Android

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 →

Linux

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 →

Common settings and where to configure them

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.

Add a group, then update the subscription

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 →

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.

From subscription import to connection testing

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.

  1. Prepare and import your configuration

    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.

  2. Choose a server and proxy mode

    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.

  3. Test the connection and save a baseline

    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.

Project V · V2Fly · Xray

Open-source ecosystem and
what each client does

Understand the difference between the interface, core, and server configuration to see why the same subscription can behave differently across environments.

Open sourceGraphical managementCommunity maintained

Project V and its core families

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.

What each of the three clients does

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.

Open-source licenses and usage boundaries

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.

Update the client, core, and rules separately

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.

In-depth guides to specific issues

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.