Subscription Setup / Desktop and Android

V2Ray Subscription Guide

Import subscriptions in v2rayN and download clients.

Start with subscription groups, then configure routing and the system proxy in order.

Setup guides in English Xray · V2Fly Open-source clients

CLIENTS / DOWNLOADS

Choose a client for your operating system

Use v2rayN on desktop and start with v2rayNG on Android. Check your operating system and processor architecture before importing an existing subscription. Installing a client does not provide server settings.

Windows

v2rayN offers desktop and classic WPF versions. The desktop version uses a cross-platform interface, while WPF retains the classic window layout. Both require a compatible subscription and runtime environment; a newer-looking interface does not guarantee a better connection.

For a first-time setup, start with a basic import, select a configuration, and enable the system proxy. If you have another proxy app running, disable its proxy controls first and check for local port conflicts before trying TUN mode. Before switching clients, note your subscription groups, routing rules, and local ports so old settings do not cause problems with the new installation.

Go to downloads →

macOS

v2rayN packages are available for Apple Silicon and Intel. Check the chip or processor information under “About This Mac” and choose the matching build. Don’t guess based on the computer’s appearance or purchase date.

After installation, follow the system prompts to allow the app to open, then import your subscription. The system proxy affects only apps that use that setting; command-line tools may need a proxy address configured separately. When troubleshooting, first confirm that the client is listening on a local port, then check browser settings and terminal environment variables separately. There’s no need to change every network option at once.

Go to downloads →

Android

v2rayNG is primarily based on the Xray core and is a good first choice for Android. v2flyNG, based on the V2Fly core, is an alternative. Compare subscription protocol support and core capabilities, not just the names.

Most recent devices use arm64; if you’re unsure of your architecture, try the universal build. On first connection, approve the system VPN request. Usually, only one app at a time can use this VPN connection. If the connection drops in the background, check power-saving settings, background permissions, and logs before assuming the subscription has stopped working.

Go to downloads →

Linux

v2rayN packages for Linux are available in deb and rpm formats for x64 and arm64. Choose the package that matches your distribution and device architecture. The graphical client also requires a working desktop session and its runtime dependencies.

A desktop environment’s system proxy does not automatically apply to every process. Check command-line tools, containers, and background services separately. Before enabling TUN, review your network setup and any existing virtual adapters, and keep a copy of the original configuration. If routing breaks, switch back to the basic proxy setup, then check permissions, DNS, and the routes being captured one at a time.

Go to downloads →

The same subscription may not work identically across different cores. Before importing, check that the target client supports the protocol, transport, and security options. Seeing a node name is no substitute for checking compatibility.

View all clients →

SETTINGS / SETTINGS GALLERY

Common v2rayN settings

Understand settings in this order: configuration source → traffic destination → capture scope. These screens are static illustrations; option names and locations may change between client versions. The example switches do not change your device’s network settings.

Check the entry point, then the exit

A successful import only means the client read the configuration; it does not guarantee that the destination server is reachable. Enabling the system proxy also does not mean every program is using it. Change one type of setting at a time: update the subscription and select a configuration, set the browser to use the local proxy, then check routing and DNS. Once the basic connection works, add TUN, LAN sharing, or app-specific exceptions as needed.

When testing, distinguish connection establishment, DNS resolution, and the destination service’s response. A site may fail to load because of the resolved address, a routing rule, or the service itself. A single node speed test cannot represent every use case. Note when the error occurred and check the client logs; this is more useful than repeatedly toggling settings.

ECOSYSTEM / PROJECTS AND CORES

Project V, V2Fly, and Xray

Clients, cores, protocols, and subscriptions are four distinct layers. Understand what each one does before deciding whether a setting applies to your device and configuration.

Configuration source

Subscription / share link

Graphical interface · Import, groups, settings

v2rayN · v2rayNG · v2flyNG

Connection handling · Protocols, transport, routing

Xray / V2Fly

The exact combination depends on the client implementation and included core. The diagram shows each layer’s role; it does not mean every client lets you switch cores freely.

Project origins and forks

Project V provides useful context for understanding the V2Ray ecosystem. Its modular approach separates inbound connections, outbound connections, routing, and transport. In everyday usage, “V2Ray client” usually means a graphical management app, not a single protocol. A client can display configurations for multiple protocols and call different connection cores, so similar product names do not guarantee identical capabilities.

V2Fly continues community maintenance of the V2Ray core project, while Xray developed from related code into an independent technical branch. They share some history and configuration concepts, but their features no longer evolve in lockstep. When following a guide, check both the client and the core. Don’t apply parameters from one branch to another without checking, and don’t assume that recognizing a configuration means every field is active.

What the three graphical clients are for

v2rayN is for desktop systems and manages subscription groups, server configurations, routing, and local listeners in one place. v2rayNG is for Android and primarily uses the Xray core. v2flyNG is an alternative for Android users who prefer the V2Fly core. All three are open-source graphical clients; their interface settings must ultimately be translated into configurations the core can run.

Choose based on your operating system, the protocol capabilities your subscription needs, your preferred traffic capture method, and the project’s maintenance status—in that order. There’s no need to force the same core across devices just to keep the names consistent. Clear subscription records and settings you can roll back make cross-device troubleshooting easier. If a group works on your computer but not your phone, compare protocol parameters and permissions before assuming the server is at fault.

Open-source licenses and service boundaries

v2rayN is licensed under GPL-3.0. An open-source license sets the terms for using, modifying, and redistributing software; it does not guarantee network service quality. A free client does not mean remote servers, subscriptions, or bandwidth are free. The software project, configuration provider, and this site’s documentation each serve different roles. For account status or subscription limits, check the information from your configuration provider.

Open-source code can be reviewed, but actual results still depend on the installation source, permissions, core configuration, and remote service. This site explains graphical client workflows and technical concepts; it does not provide subscriptions or server accounts. Addresses shown in example windows illustrate field formats only and are not real connection details.

Update order and compatibility

Updating the client, the core, and the subscription are three different things. A client update changes the interface and configuration generation; a core update changes protocol handling; a subscription update retrieves the latest configuration from its source. If import fails, check the format and URL first. If a connection parameter is unsupported, check the core’s capabilities. Treating all three updates as the same can hide the real issue.

Before upgrading, note the working traffic capture method, local ports, and custom routes. Back up your configuration using the client’s features and protect any sensitive fields it contains. After upgrading, test one configuration first, then try subscription updates and everyday apps. If the protocol combination includes VLESS, TLS, or REALITY, understand the separate roles of authentication, transport, and the security layer. Changing only the protocol label can leave required parameters missing.

NOTES / SETUP AND TROUBLESHOOTING

Recent tutorials

Once the basic connection works, look up settings based on what you’re seeing. These articles cover app traffic, port listeners, and virtual adapter capture separately, so you can avoid applying the same fix to problems at different layers.

Troubleshooting

System proxy enabled but not working: troubleshoot browsers and terminals step by step

For browsers, check whether extensions, PAC, or an exception list are taking over. For terminals, learn why they may ignore the system proxy by default and how to set a local HTTP proxy with environment variables.

First check whether the app is using the local proxy, then confirm the proxy backend can connect. Separating “the app is bypassing the proxy” from “the proxy connection is failing” can prevent unnecessary routing changes.

Read the guide →
Troubleshooting

V2Ray local port already in use: find the conflicting process and change SOCKS and HTTP listening ports

If the client won’t start or reports that a port is in use, use a system command to find the process occupying it. Then choose an unused port in the settings and update any apps that depend on the old port.

Clients may use different listening port configurations. First check whether yours uses a mixed port or separate ports. Changing the client without updating the proxy address in your app will still leave the connection broken.

Read the guide →
Advanced Setup

How v2rayN TUN mode works: how a virtual network adapter captures system-wide traffic

Learn how TUN’s virtual adapter differs from the system proxy, which apps need virtual adapter capture, and what permissions, setup steps, and common conflicts to expect.

Understand the difference between how traffic enters the core and where it exits. TUN still needs suitable routing and DNS settings; capturing more traffic does not mean all traffic uses the same outbound route.

Read the guide →

If you’re not sure which layer is causing the problem, check the FAQ for subscription validity, permissions, and proxy modes. Then open the relevant guide and note what changes before and after each adjustment.