Client downloads · Subscription & routing setup

V2Ray Config Guidev2rayN Download & Advanced Setup

Start with subscription import, then configure routing and DNS.

VMessVLESSTrojanShadowsocks

Common v2rayN Settings

First identify the subscription source, traffic entry point, and outbound rules; then adjust DNS resolution. The settings below are illustrative. Names and available options vary by client and core.

Subscription Group Settings

AliasDaily use
Auto-update intervalSet as needed
Update subscriptionCurrent group

Subscription groups keep server configurations from different sources separate, making it easier to maintain everyday and backup connections. Open the subscription group settings, enter a recognizable alias and a valid subscription URL, then update only the current group. If you need to filter servers, check the filter conditions first to avoid mistaking an empty list after refresh for a missing subscription. Compared with repeatedly pasting individual links, groups make it easier to track sources and diagnose update failures. Subscription contents are determined by the provider, however; client-side groups cannot change the remote service or fill in missing protocol parameters.

Read the subscription group guide →

Think of a connection as three layers: an app sends requests through the system proxy or TUN entry point, the core uses rules to choose a direct or proxy outbound, and DNS resolves domain names where needed. These layers are related but cannot replace one another. A website working in your browser does not mean every app uses the same entry point, and enabling proxy outbound does not mean every DNS query follows the same route.

Save a working baseline configuration before adding routing rules, remote DNS, or a virtual network interface. Change one thing at a time and note what happens before and after. If something breaks, reproduce the issue with the baseline and check the logs rather than enabling several options at once. To compare client interfaces, cores, and use cases, read the client comparison before deciding whether to migrate your configuration.

Choose a V2Ray Client for Your Platform

Use v2rayN on desktop. For Android, start with v2rayNG; consider v2flyNG if you need the V2Fly core. The download page explains package architecture, system format, and interface options.

Windows

v2rayN offers desktop and classic WPF editions. The desktop edition uses a cross-platform interface, while WPF retains the familiar classic window-based workflow. Check your operating system and processor compatibility first, then choose based on interface preference. After the first launch, import a subscription and confirm that a server is available. Avoid overwriting an existing configuration directory.

Go to downloads

macOS

v2rayN packages are available for Apple Silicon and Intel Macs. Check your chip in About This Mac and choose the matching architecture. After installation, confirm that the app runs before configuring the system proxy. If another networking tool is already managing your proxy or routes, disable overlapping features before testing.

Go to downloads

Android

v2rayNG uses the Xray core, while v2flyNG is an alternative built on the V2Fly core. arm64 is the usual choice for modern devices; if you are unsure of your processor architecture, check the universal package details. On first connection, grant the system VPN permission. If the connection drops in the background, check battery optimization and background activity restrictions.

Go to downloads

Linux

v2rayN packages for Linux distributions use deb or rpm formats and are available for different processor architectures. Check your distribution and hardware architecture first, then use the system package manager to handle dependencies. Whether desktop apps honor the system proxy depends on each app. Consider TUN if you need to capture more traffic.

Go to downloads

Installing a client and configuring proxy service access are separate steps. The client provides tools for managing and connecting, but you still need valid server parameters or a subscription URL. Subscriptions often contain credentials; don't post them in public discussions or submit them to unfamiliar online converters. If importing into another client fails, check the original format and core support before deciding whether conversion is actually needed.

Before switching platforms, note your subscription group names, routing policies, and DNS settings instead of copying the entire runtime directory. Configuration paths, permission models, and network entry points vary by system, so migrating settings one at a time makes it easier to pinpoint problems. If your current connection works, keep the original client and configuration until the new setup has been verified.

View all clients →

Quick Start: Subscription, Mode & Testing

Start with a reproducible baseline connection, then configure routing and DNS. These three steps illustrate the recommended sequence; see the full guide for specific menus and permission prompts.

View the full guide →
STEP 01Start here

Import a Subscription and Update the Group

In subscription group settings, add a source, enter an alias and the full subscription URL, save it, then update the current group. A successful import only confirms that the URL was saved; check that recognizable server configurations appear in the group. If the list is empty, check the filters, subscription validity, and update logs first.

A single share link and a subscription URL are different types of input. Importing a single link usually adds just one configuration, and later parameter changes won't be picked up by subscription refreshes. Don't enter a subscription URL in a server address field. If you get a format error, check the original source to confirm what type of link it is.

STEP 02Entry Point & Outbound

Choose a Server and Proxy Mode

Set a configuration as the active server, connect, and enable the system proxy if needed. On desktop, test with a browser that follows the system proxy; on Android, confirm that VPN permission is granted. The entry point sends requests to the client, while routing determines how they leave it.

“Global proxy” can refer either to the system proxy entry point or to a routing policy that sends all traffic through the proxy. Check which menu a guide means. For your first setup, keep the default routing and avoid changing TUN, FakeDNS, and custom outbounds at the same time; otherwise, it can be hard to identify the cause of a failure.

STEP 03Test & Record

Check Access and Runtime Logs

Test sites that should use the proxy, sites that should connect directly, and local network resources. Check whether each behaves as expected. If you see timeouts, handshake failures, or DNS errors, note the relevant log entries and timestamps. Importing a subscription does not guarantee a server connection, and opening one webpage successfully does not verify every routing rule.

Once the baseline connection works, add DNS and routing changes one at a time. After testing, check that network access returns to normal when you exit the client. If only one app has issues, first check whether it follows the system proxy, then decide whether to configure its own proxy or use a different traffic entry point.

Project V, V2Fly & Xray

Client names, core families, and proxy protocols refer to different layers. Understanding what each one controls is more useful for migration and troubleshooting than memorizing a software name.

The Project V Ecosystem and Graphical Clients

Project V is the open-source ecosystem behind a set of proxy tools and related capabilities, with V2Ray among its widely used projects. Graphical clients build on this kind of core functionality to provide interfaces for subscription management, server selection, and configuration. The interface stores settings; the running core establishes connections, applies routing, and handles DNS resolution. So seeing a protocol listed in a client does not guarantee every transport combination is supported by the selected core.

v2rayN, v2rayNG, and v2flyNG are all open-source client projects, but they are not just different skins for the same program. Desktop and Android differ in permissions, network access, and background operation, so their settings won't always match. When following configuration instructions, check the client name, core, and specific feature. Don't assume a configuration file can be imported unchanged into another client.

V2Fly and Xray: What Each Core Supports

The V2Fly community continues to maintain V2Ray-related implementations, while Xray is another core project that grew out of V2Ray. They share some protocol and configuration concepts, but each has features and fields that evolve independently. Choose based on the server's requirements: check whether the core supports the protocol, transport, security layer, domain parameters, and other options you need. Similar names don't guarantee full compatibility.

Desktop v2rayN provides options for configuring multiple cores. On Android, v2rayNG uses the Xray core and v2flyNG uses the V2Fly core; choose according to your existing configuration. If you need a specific protocol extension, check core support before choosing a client. For basic subscriptions and everyday connections, starting with a compatible default combination is usually easier to maintain than switching cores frequently.

Open-Source Licenses and Subscription Privacy

Open source means a project's code is published under a license; use, modification, and distribution must still comply with its terms. V2Fly's V2Ray and Xray-core use MPL-2.0. Client projects have their own license terms, so a core's license does not automatically cover every graphical client or bundled component. Before redistributing or modifying software, review the licenses for the projects you use and their third-party components.

Open-source code and the trustworthiness of a remote service are separate issues. A client does not determine how a subscription provider handles accounts, connections, or service logs, nor does it guarantee that servers will be available. Treat subscription links like account credentials. Before sharing screenshots, exporting configurations, or submitting logs, remove authentication fields, subscription URLs, and account-identifying information. The configuration examples on this site explain how settings relate to one another; they do not include usable server details.

Update Order and Configuration Maintenance

Client updates, core updates, rule data updates, and subscription refreshes address different things. Client updates affect the interface and configuration generation; core updates may change protocol support or behavior; rule data updates affect classification and matching; subscription refreshes sync remote server parameters. One update succeeding does not mean the others are complete. When troubleshooting, identify exactly what changed most recently.

Before updating, record your working configuration and custom rules. Afterward, check that the core starts, then test existing connections and key services. If an issue appears only after adding a rule, roll that rule back first. If the core won't start, check the error log for the fields and file paths it mentions. Don't assume every problem is a subscription issue. For a systematic approach to subscriptions, routing, DNS, and custom outbounds, read the advanced configuration manual. For specific how-to questions, browse the FAQ by category.

Recent Configuration Guides

Each article focuses on one setting: when to use it, how to change it, and how to verify the result. Apply the steps in context of your client interface, core support, and network environment.

View all articles →