CLIENTS / ROUTING / DNS

v2rayNG Official Site Client Downloads

Choose your platform and learn how to configure v2rayN / v2rayNG / v2flyNG, from subscription imports to routing and DNS, with a clear explanation of what each setting affects.

Open sourceXray / V2FlyConfiguration guides

CONFIGURATION / SETUP PATHS

Subscriptions, routing & operating modes

Graphical clients manage servers and generate configurations; cores handle the actual traffic forwarding. First identify the client and core in use, then adjust the relevant settings. The five sections below are organized by task, with examples showing each setting in context. Desktop and Android options are kept separate rather than presented as one shared interface.

Keep subscriptions from different sources in separate groups to make updates, filtering and troubleshooting easier. In v2rayN, enter the subscription URL in the group settings, then update the subscription. If the list is empty, check the update result and filters before reinstalling. Group names are for local organization only and do not change the server protocol. Subscriptions are useful for managing many servers, but updates may overwrite older entries from the source; save personal changes separately. Treat subscription URLs like credentials and never share them publicly.

↗

Routing determines whether connections reaching the core go direct, through a proxy or are blocked. In v2rayNG, you can select a preset such as bypassing mainland China, then add custom rules for more complex needs. Rules are generally matched in order, so put more specific domain or address conditions first and make sure the outbound tag exists. Unlike a global proxy, rule-based routing can preserve direct access to your LAN and selected services. System proxy settings and routing are separate layers: changing rules will not capture traffic that never reaches the client.

↗

DNS resolution affects connection destinations and routing decisions based on addresses. First distinguish system DNS, core DNS and encrypted DNS built into the browser, then decide which layer to change. Understand v2rayNG's local DNS and FakeDNS settings in the context of its operating mode; enabling a toggle does not mean every app is covered. Rather than replacing a single resolver, assigning DNS servers by domain is better suited to fine-grained routing. After making changes, reconnect and check the logs to confirm the resolution path—cached results may not reflect the new configuration.

↗

If desktop apps ignore the system proxy, consider TUN mode in v2rayN. It captures traffic through a virtual network interface and may require administrator privileges; system routes, firewalls and other virtual adapters can also affect it. Compared with the system proxy, TUN captures more traffic and can take longer to troubleshoot. First confirm the server works with the system proxy, then enable TUN separately and check LAN access and DNS. Android clients use the system VPN interface instead, with different permissions and lifecycle behavior, so desktop adapter troubleshooting steps do not apply.

↗

Protocol support depends on the core actually running, not just on whether the client can display an imported profile. In v2rayN, choose a runtime component based on the configuration type and installed cores. Before switching, check that the protocol, transport and security settings are compatible. v2rayNG uses Xray, while v2flyNG is built for V2Fly; these are separate Android apps, not options within one app. Checking fields against the core is more reliable than copying a configuration blindly. In particular, do not assume every core supports features such as REALITY.

↗
v2rayN · Subscription group settings example

GROUP MANAGEMENT / SUBSCRIPTIONS

NotesName by source
Optional URLSubscription URL
AliasSet as needed
Update subscriptionUpdate this group

Workflow: save the group → update the subscription → check the server list. This illustrates the settings layout; it is not a running client.

DOWNLOAD / PLATFORMS

Choose a client for your platform

For desktop, start with v2rayN; for Android, start with v2rayNG. Consider v2flyNG if you need a V2Fly core. Package format and processor architecture are separate factors: identify your operating system first, then your hardware. The download page lists specific downloads, installation instructions and platform notes; this homepage focuses on choosing a client.

Windows

v2rayN · Desktop pick

A good fit for managing browsers and desktop apps through the system proxy. The download page distinguishes the cross-platform Desktop edition from the classic WPF edition; choose the one that suits your workflow rather than running both.

On first launch, confirm that the core runs before importing a subscription. Address runtime warnings or local port conflicts based on the specific error. Restore the system proxy before closing the app so you can tell a client shutdown issue from leftover system proxy settings.

Go to downloads →

macOS

v2rayN

Check About This Mac to identify your processor: Apple Silicon and Intel have different download options. Do not infer the architecture from the device's appearance or purchase year, especially on a device migrated from another Mac.

The first launch may require you to approve the app in System Settings. Check system proxy and network permissions separately; opening the app does not mean the proxy is working. If you plan to use TUN, verify its permissions separately. Changing the operating mode and server settings at the same time makes problems harder to diagnose.

Go to downloads →

Android

v2rayNG · Recommended

v2rayNG uses the Xray core; v2flyNG is an alternative with the V2Fly core. Most recent devices use arm64. If you are unsure of your device architecture, check the universal package notes.

After importing a configuration, approve the system VPN connection request. Background battery restrictions may interrupt a persistent connection; check battery management after confirming the connection is stable. If another VPN app is running, first check whether it is already using the VPN interface. Before switching clients, verify that the new app supports the protocol and transport settings you use.

Go to downloads →

Linux

v2rayN

Choose deb or rpm based on your distribution's package system, then confirm whether your system uses x64 or arm64. Include the desktop environment, permissions and system components required for the graphical interface in your installation checks.

System proxy handling varies between desktop environments, and some apps may need a proxy address configured separately. First test with an app that follows the proxy settings, then consider TUN permissions and route capture. If terminal apps behave differently from the browser, check their proxy settings separately rather than assuming the server is down.

Go to downloads →

QUICK START / WORKFLOW

Import, connect and test

The client does not provide server access. Before you begin, get a working subscription URL or single-server share link and make sure you are authorized to use it. For your first setup, aim for the simplest working connection: keep the defaults you understand, verify the server, then add routing, DNS and traffic capture settings one at a time.

STEP 01

Import a subscription or single server

On desktop, save the source URL in a subscription group and update it. On Android, import clipboard contents from the menu or add a subscription and update it. Subscription links and single-server links use different import options. A link may look like a URL but still fail to create a server entry if it is imported in the wrong place.

After importing, check that the server type, address, port and transport are all present. If only one entry is missing, check that entry's format first. If the whole group is empty, check the subscription request and filters. Never include a full subscription URL in a public screenshot; error messages and field names are usually enough for troubleshooting.

STEP 02

Choose a server and operating mode

Select the server you want to use, then start the connection. On desktop, v2rayN usually needs the system proxy enabled for apps that follow it to use the local proxy port. On Android, v2rayNG receives traffic through system VPN authorization. The interfaces differ, but in both cases distinguish a selected configuration from a running service.

For your first setup, choose an easy-to-understand routing preset. Avoid adding custom DNS, complex rules and TUN all at once. Change only one of the server, capture method or routing settings at a time so you can return to the last working setup if something goes wrong. If another proxy app is running, stop one of them to avoid conflicts over ports and system settings.

STEP 03

Verify with a real request

Open the target app, make a real request and check the client logs. A test result only reflects the specific test path; it does not replace testing access from the app itself. Browsers may also use their own proxy extensions or DNS settings, so check those separately.

If the connection fails, troubleshoot in this order: can the subscription update, can the core start, is the app's traffic reaching the proxy, and can it connect to the remote server? Recording the error type is more useful than repeatedly changing every setting. Once the basic connection works, use the guides to configure finer rules for LAN access, DNS resolution and app compatibility.

PROJECT V / V2FLY / XRAY

Clients and open-source cores

Similar names do not mean the tools do the same job. Understanding how graphical clients, proxy cores and server configurations fit together helps distinguish installation issues from protocol problems and DNS issues from server problems.

Project V's modular foundation

V2Ray is part of the Project V proxy ecosystem, with configurations organized into modules such as inbounds, outbounds, routing and DNS. Traffic from local apps first enters through an inbound, then routing rules direct it to an outbound. DNS resolution and traffic identification provide information for those decisions. This modular design lets graphical clients turn common actions into configuration without requiring every user to write a complete JSON file from scratch.

A “server” in the interface usually means a set of remote connection parameters; it does not mean a connection has already been established locally. “System proxy” is an operating-system entry point, not a core routing mode. Keep these layers separate when following a guide to understand why a successful import still requires selecting an active configuration, starting the core and confirming how app traffic reaches it.

V2Fly and Xray: different capabilities

The V2Fly community maintains V2Ray-related implementations, while Xray follows another core development path within the same technical ecosystem. They share some protocol and configuration concepts, but their newer features, field syntax and compatibility are not always the same. Check Xray support for specific features such as REALITY; a client saving a field does not mean every core can run it.

VMess, VLESS, Trojan and Shadowsocks are protocol choices; TCP, WebSocket and gRPC are transport options; TLS and REALITY relate to connection security. Check each layer against the server configuration when troubleshooting. Changing only the protocol name while keeping incompatible transport and security settings usually will not produce a working connection.

What each of the three clients does

v2rayN is for desktop, with graphical tools for server management, subscription updates, system proxy settings and routing, and can run configurations with available cores. v2rayNG is for Android, uses the Xray core and receives device traffic through the system VPN interface. v2flyNG is also for Android, but uses the V2Fly core and suits setups with corresponding compatibility requirements.

All three clients are open-source software. The client projects, integrated cores and other components may use different open-source licenses; refer to each project's accompanying license for the applicable rights and obligations. Choose based on platform, configuration compatibility and workflow, not just similar names. An alternative Android app does not automatically inherit another app's settings.

Update and migration sequence

Updating the client, the core and a subscription are three separate tasks. Client updates mainly affect the interface and configuration generation; core updates may change protocol support and runtime behavior; subscription updates only sync the server entries provided by the source. If a subscription update fails, check the request error, source status and group settings first rather than blaming the client installation.

Keep your current working setup before changing configuration. After an update, check the active server, proxy entry point and basic connectivity before restoring custom rules. Logs can reveal unsupported fields, missing permissions or port conflicts, but may also contain server addresses and connection history. Remove personal configuration details before sharing error reports. This site provides software links and technical documentation; confirm server access and permission yourself, and follow applicable local laws.

TECHNICAL NOTES / CONFIGURATION

Configuration structure and platform settings

The quick start gets a basic connection working; these technical notes explain how the configuration fits together. The three latest posts are listed by publication date, newest first, covering JSON modules, first-install checks and DNS-based routing. Start with the topic closest to your question.