Client Downloads and Configuration

Xray Official · Client Downloadsv2rayN Setup Guide

Choose an open-source client for your operating system. Start by importing a subscription, then configure routing and DNS. Use v2rayN on desktop; on mobile, choose a client based on its supported core.

Choose a Platform
Core and GUI: Separate LayersThe client manages settings; the core handles connections

First, confirm that the protocol is supported by the core, then adjust routing, name resolution, and traffic capture.

XrayV2Fly
Desktop Setupv2rayN

Manage subscriptions, routing, and system proxy settings in one place.

Choose a Mobile Clientv2rayNG / v2flyNG

Choose based on the server settings and required core.

Recommended OrderInstall → Import → Route

Establish a basic connection first, then adjust settings one at a time.

CLIENT SETTINGS

Common v2rayN Features and Where to Find Them

Subscriptions determine where server entries come from, routing determines where connections go, and DNS resolves domain names. Understand these three layers before configuring system proxy settings or TUN capture. Keeping them separate makes troubleshooting easier and avoids conflicting changes.

Subscription Groups

Save subscription URLs by source and check each result separately after an update. Groups and server filters help narrow the list, but filters can also hide imported entries. If the list is empty after an update, check the selected group and filter expression before assuming the subscription has expired.

Routing Rules

Match connections by domain, IP, port, and protocol, then send them to the specified outbound. Rules are checked from top to bottom, so put specific conditions before broad ones. Outbound tags in the rules must match those in the configuration.

DNS

Choose DNS servers for different domains. Core DNS and system DNS are configured separately. The actual query path depends on whether the application passes a domain name, the routing policy, and how traffic is captured. The server address alone cannot confirm that a setting is working.

TUN Mode

A virtual network interface captures IP traffic that meets the configured conditions, making TUN useful for applications that don't use the system proxy. Before enabling it, check permissions and other network tools, then verify whether the default route, DNS, or LAN access changes.

Multiple Cores

The GUI generates the configuration; Xray and V2Fly handle the protocols and transport settings each supports. Switching cores is not a general-purpose fix. Check the server requirements first, then look for incompatible fields in the generated configuration.

System Proxy

Set the system proxy to the local listening address and port. Set, Clear, and Keep Current affect the system proxy settings; they do not control every application's network traffic. Check browser extensions and app-specific proxy settings separately.

Custom Outbound

Use outbounds and tag references to define where connections go. A tag links a rule to an outbound; it is not the server's display name. When editing, check references, authentication fields, and connection direction to avoid creating a loop.

SETTINGS REFERENCE

Routing, DNS, and Subscription Group Settings

The examples below illustrate how settings relate to one another; they are not editable forms. Labels may vary between client versions. Use the field meanings and generated configuration to verify your setup.

In Routing Settings, first choose the outbound for each connection, then add domain, IP, or port conditions. Put specific domain rules before broader ones so they are not matched by another rule first. IPIfNonMatch means the core tries to resolve the IP and check IP rules if no domain rule matches; it does not mean every request is resolved in advance. After saving, reload the configuration and retest the same destination, then check the outbound tag in the logs. System proxy settings pass requests to the client; routing decides where they go once inside the client.

Read the Routing Rules Guide
PLATFORM ENTRIES

V2Ray Clients by Platform

Check your operating system and processor architecture before choosing an installer. Clients provide local configuration and connection features, but installing one does not give you a working server. You will also need a subscription or complete connection details from a trusted source.

Windows

v2rayN is the recommended desktop client. The download center offers a desktop edition and the classic WPF edition. The desktop edition uses a cross-platform interface, while the WPF edition retains the classic interface. Choose the one that suits your workflow; there is no need to run both.

Keep the default listening settings on first launch. Import a subscription, select a server, then set up the system proxy. If the core fails to start, check the startup log and port usage before changing routing, DNS, and TUN settings.

Go to Downloads

macOS

Use v2rayN's desktop interface to manage subscriptions and routing. Before installing, check your chip type in About This Mac. Apple Silicon and Intel require different installers, so don't rely on the device's appearance to tell them apart.

After installation, test the system proxy first, then configure any traffic capture features that require extra permissions. If your browser connects but other apps don't, check their proxy settings and whether they use the system proxy.

Go to Downloads

Android

First, check which Xray core features v2rayNG supports. For a V2Fly core, consider v2flyNG. Most newer devices use arm64; if you aren't sure which architecture your device has, check the universal package details in the download center.

The first connection requires system VPN permission. If the connection drops when the app moves to the background, check battery optimization and background activity restrictions. If no apps can connect, check the server settings, network, and client logs.

Go to Downloads

Linux

v2rayN provides a desktop GUI. Linux packages are offered as deb or rpm files according to the distribution's package management system, with options for different architectures. Check your Linux distribution and processor type before choosing a download.

Desktop proxy settings and proxy environment variables for terminal applications are separate. If GUI apps work but command-line tools don't, first check which proxy source the tool uses instead of immediately changing servers.

Go to Downloads

View All Clients →

PROJECT V ECOSYSTEM

Project V, V2Fly, and Xray Explained

Keep ecosystem names, proxy cores, and GUI clients distinct to understand which parts of a guide apply to your setup. Similar names don't mean configurations are interchangeable. Check feature support against your selected core and client interface.

Project V: Background to the Configuration Model

Project V is the open-source ecosystem behind V2Ray-related tools and technical documentation. A common way to understand the configuration is through inbound, routing, and outbound: inbound receives application requests, routing checks conditions, and outbound makes the connection. This model is more reliable than memorizing a particular setting's location and remains useful as interfaces change.

When reading older guides, distinguish protocols, transports, and security layers. VMess, VLESS, and Trojan are different protocols; WebSocket and similar options are transport settings; TLS covers connection security. Treating these as a single “mode” can make it easy to miss required server settings.

V2Fly and Xray: Separate Core Development Branches

The V2Fly community continues V2Ray development and maintenance, while Xray-core has developed its own implementation and features from related code. The two share some configuration concepts, but protocol extensions, supported fields, and defaults can change independently. A configuration accepted by one core may not work with the other.

When choosing a core, check the complete server settings and core requirements first. Don't judge compatibility by the server name alone or treat switching cores as a speed boost. If you see unknown fields or an unsupported transport, confirm which core the configuration is for before deciding whether to update or switch cores.

Three Clients: Open-Source GUIs and Their Cores

v2rayN, v2rayNG, and v2flyNG are open-source GUI clients. v2rayN is for desktop systems and manages subscriptions, settings, and core execution. v2rayNG is for Android and uses the Xray core; v2flyNG offers a mobile option based on the V2Fly core. Check the client name and the core that handles connections separately.

Open-source licenses set the terms for using, modifying, and distributing code. Xray-core and the V2Fly core are licensed under MPL 2.0, while each GUI client has its own licensing requirements. A core's license does not replace the license for the entire client. For redistribution or modifications, review the notices for each project separately.

Update in Order: Back Up, Then Retest

The GUI client and core may update separately, as can their settings interfaces, configuration generation, and protocol support. Before upgrading, back up subscription groups, routing rules, and custom settings, and note the current proxy mode. After upgrading, test a known working connection first, then restore extra rules one at a time to identify any behavior changes.

The download center provides platform-specific options; the homepage does not pin a specific version. Subscription updates and program updates are also different: the former refreshes server entries, while the latter updates the client or core. If an entry stops working, check the subscription update results and connection logs before reinstalling the entire client.

FIELD NOTES

Client Tips and Configuration Notes

Each guide focuses on a specific setting or issue, explains what to check, then gives a troubleshooting sequence. New users can start with the beginner Q&A; once you have a working setup, explore server selection and router deployment.

View All Articles →