Clients powered by Xray / V2Fly

V2Ray for Windows v2rayN Setup

From subscription imports to routing rules, follow setup steps for v2rayN desktop and Android clients, then choose the right proxy mode and core for your needs.

  • Xray Core
  • V2Fly Core
  • GPL-3.0 licensed open-source client
  • VMess · VLESS · Trojan · Shadowsocks
CLIENT SETTINGS / CLIENT SETUP

v2rayN Key Features

Explore setup tasks step by step. Menu labels may vary by release, so check your client and core before following the instructions.

Subscriptions bring multiple server configurations together under one update source. In Subscription Group Settings, enter a name and URL, save the group, then update it and choose a server from the corresponding list. Groups are easier to manage than pasting links one by one, especially when you have multiple sources, and help narrow down update issues. If the list is empty, check the update log and response format first, then review your filters. Avoid creating duplicate groups. Subscription URLs often contain access credentials, so keep them on trusted devices and hide the full URL in screenshots.

Subscription Group SettingsUpdate SubscriptionServer Filters

Setup order matters more than the number of toggles: import a working config, select a server, confirm how app traffic reaches the client, then adjust routing. Subscriptions, traffic entry modes, and outbound rules are separate layers. Changing them all at once makes troubleshooting harder.

Explore protocol, subscription, and routing terminology →
QUICK START / THREE STEPS

Import a subscription and connect for the first time

These steps use v2rayN on desktop as an example. On Android with v2rayNG, the same basics apply: import a config, start the connection, and check that traffic works.

01 / IMPORT

Create a subscription group

After installing a client for your device, open Subscription Group Settings. Give the source a recognizable name, paste the full subscription URL, and save it. Then update the subscription. Get the URL from a trusted service provider or the administrator of your own service. The client manages connections; it does not generate working servers.

After the update, check that servers appear in the selected group. If you have just one share link, import it from the clipboard instead of putting it in the subscription URL field. Subscription URLs and single-server links serve different purposes; mixing them up can lead to import errors or an empty list.

Keep the default settings for your first setup. Start with one group and one server so it is easier to tell whether the issue is an unexpected response, an incompatible format, or connection settings that need another look.

02 / CONNECT

Choose a server and proxy mode

Select a server from the list and set it as active, then choose an entry mode that suits your apps. Apps such as browsers that follow system proxy settings can use the system proxy for an initial test. For apps with their own proxy settings, enter the address and port the client is actually listening on.

If an app does not use proxy settings, consider TUN. Before enabling it, read the permission prompts and check whether another virtual interface or network tunnel is already capturing traffic. System proxy and TUN are traffic entry methods; do not confuse them with routing outcomes such as proxy, direct, or block.

The first time you start a connection on Android, the system usually asks for permission to set up a VPN connection. After granting permission, check the app's background activity restrictions. A connection that drops after locking the screen needs a different diagnosis from one that never connects.

03 / VERIFY

Test access and check logs

Visit a known working destination, then check whether the corresponding connection appears in the client log. A latency test is only a quick indicator: a response from the server address does not prove that the protocol handshake, DNS resolution, or webpage access will work. Test the apps you actually need to use.

If the connection fails, check your local network, subscription validity, active server, entry mode, routing, and DNS—in that order. Note when the error occurred and save the complete error message, but do not share your subscription URL, user ID, or password. Change one variable at a time and retest the same destination.

Once the first connection works, add custom routing rules and server filters. When you finish, clear the system proxy or turn off TUN using the client’s controls so apps do not keep pointing to a local port that is no longer listening.

PLATFORMS / DOWNLOADS

Four platformsClient options

Start with your operating system, then check your processor architecture and package format. The download page lists the specific system requirements and release notes.

Windows

v2rayN / Desktop · Classic WPF edition

For everyday desktop use, start with v2rayN. The desktop edition uses a cross-platform interface, while the classic WPF edition follows the Windows UI approach. Both focus on server, subscription, and routing management, but layouts, dependencies, and some menu locations may differ. Match tutorial menu names to the version you have installed.

Before downloading, check your device architecture and system details in Settings. If a component prompt appears on first launch, install the dependencies listed for that release; missing runtime components do not mean your subscription is unusable. If you plan to test TUN, check its permissions and virtual interface requirements separately. You can test the system proxy first.

Go to downloads

macOS

v2rayN / Apple Silicon · Intel

For desktop use, choose v2rayN. Installers are available for Apple Silicon and Intel Macs. Check the chip or processor under About This Mac; that is more reliable than guessing from the year you bought the computer. Matching the installer to your device architecture helps avoid runtime differences.

After installation, make sure the client launches before importing a subscription. Whether the system proxy takes effect depends on whether an app uses the system network settings. If an app still uses its usual connection, check its own proxy options first. For network extensions, permissions, or TUN, follow the current release notes and system prompts rather than steps for another platform.

Go to downloads

Android

v2rayNG / Xray · v2flyNG / V2Fly

For Android, start with v2rayNG, which uses the Xray core. If you need the V2Fly core route, look at v2flyNG. Check each client’s capabilities separately: importing a node into one does not guarantee the other supports the same transport and security settings.

Most recent devices use the arm64 package. If you are unsure of your device architecture, check the universal package and device documentation. If the connection drops when the screen locks, the network changes, or the app stays in the background, start by checking battery management and background restrictions. Mobile battery use also depends on signal strength, the number of connections, and app activity—not just the protocol name.

Go to downloads

Linux

v2rayN / deb · rpm

For a Linux desktop, choose a v2rayN package that matches your distribution. Debian and Ubuntu typically use deb packages; Fedora and similar distributions typically use rpm packages. You also need to choose between x64 and arm64. Package format and processor architecture are separate requirements, and both must match.

Once the graphical interface launches, check the local listener and app proxy settings. Support for system proxy settings varies by desktop environment, and command-line tools may not read desktop settings automatically. Before enabling TUN, check permissions, routes, and existing network services to avoid running multiple traffic-capture methods at once. Follow the selected package’s documentation for dependencies and system requirements.

Go to downloads

If you use the same subscription on multiple devices, check the service’s device and connection limits. Switching clients changes how connections are managed and handled locally; it does not change the subscription’s expiration date, server settings, or account permissions. Verify everything on one device first, then configure the others.

View all clients →
CORE LINEAGE / PROJECTS AND CORES

Project V, V2Fly, and Xray

Understand the ecosystem, core, and graphical client separately before checking protocol compatibility. Similar names do not mean their configurations are interchangeable.

EcosystemProject V / V2Ray

Protocol, transport, and routing foundations

CoreV2Fly · Xray

Handles connections and parses configuration

Client interfacev2rayN · v2rayNG · v2flyNG

Manages subscriptions, servers, and user settings

Origins and development of the ecosystem

Project V is a useful starting point for understanding the V2Ray ecosystem. Its design separates inbounds, outbounds, transports, and routing so different connection methods can be combined. V2Fly continues the community development of V2Ray; Xray grew from related code and continues to evolve beyond shared capabilities. As a result, “V2Ray config” can mean a general concept in the ecosystem or a configuration that a specific core can read. Pay attention to the context in documentation.

This lineage explains why some basic settings look similar while support for newer features differs. A protocol name is only part of the picture; transport, security layer, and optional parameters matter too. For example, REALITY is a security-layer technology and should not be treated as a choice at the same level as VMess or VLESS. Check the full combination rather than importing a config just because you recognize an abbreviation.

How graphical clients and cores work together

v2rayN manages desktop server lists, subscriptions, and settings, then turns your selections into a configuration the core can run. v2rayNG is an Android client that uses the Xray core; v2flyNG offers an Android option based on V2Fly. All three are open-source projects. An option with the same name may still work differently depending on the core and platform implementation.

If the interface recognizes a share link, that only confirms the parsing step succeeded. Check the logs and test the connection to confirm that the core accepts the generated configuration and the remote server supports it. When troubleshooting, note the client and core versions separately; updating the client does not necessarily update every component. With multiple cores, confirm which executable is handling the active node.

Open-source licenses and usage

v2rayN, v2rayNG, and v2flyNG are licensed under GPL-3.0. The license sets the terms for using, modifying, and redistributing the code. Cores and other dependencies may have their own licenses, which should be reviewed separately. A free client and a paid remote service are different things; you still need server settings you are authorized to use.

Open-source projects improve through public code and community collaboration, but results still depend on the device, configuration source, and server status. Before use, check the rules that apply where you are, your network administrator’s requirements, and the service provider’s terms. This site collects download links and technical guides; it does not provide subscription accounts or guarantee any particular service quality based on protocol choice.

Updates and compatibility

Updates can change the interface, configuration fields, core behavior, or system dependencies. Read the release notes for your version and back up your current settings before upgrading. Afterward, test the connection and routing against the same destination. When moving between devices, use a share-link or subscription format supported by the target client. Copying a full config file may carry over platform-specific paths, listeners, or routing settings.

Subscription formats are not all interchangeable. Single-server share links, encoded link lists, and full configuration files serve different purposes. If a format is incompatible, ask the source for a suitable export first. Sending a subscription URL with access credentials to an unfamiliar online converter increases the risk of exposure. Before converting anything, identify the fields that must be retained and confirm the target core supports them.

If you are dealing with a failed subscription update, a browser that works while other apps do not, or local devices becoming unreachable after enabling TUN, troubleshoot the affected layer before reinstalling. The help center organizes answers by fundamentals, setup, usage tips, and troubleshooting, making it a quick reference while configuring the client.

Visit the help center →
FIELD NOTES / CONFIGURATION GUIDES

Subscriptions and routing in practice

Go beyond everyday tasks to understand how configuration works. Reproduce the issue first, then follow each check in the guide.

Manage Multiple Subscriptions in v2rayN: Filter Servers and Organize Nodes from Multiple Providers

Learn how to group multiple subscriptions in v2rayN, filter servers by keyword, remove duplicates, and sort the list to keep nodes from multiple providers easy to use.

Useful when you have many subscription sources, repeated server names, or trouble finding nodes after an update. Separate the original subscription contents from local filter results before changing how the list is organized, so hidden servers are not mistaken for missing ones.

Read article →

10 V2Ray Questions for Beginners: Choosing a Client, Importing a Subscription, and Troubleshooting Connections

Answers to ten common beginner questions about choosing a client, importing subscriptions, switching modes, and troubleshooting connection failures, with links to further guides.

For anyone unsure what to do after installing a client for the first time. Start with the difference between a client and a service, then learn how traffic entry modes, routing outcomes, and server settings fit together before moving on to specific options.

Read article →