Client Downloads · Configuration Reference

V2Ray Release Hub
v2rayN Client Downloads

Download v2rayN View Setup Guide

Choose an open-source client for your device, then follow the settings for subscription import and proxy routing.

Understand Clients and Configuration Separately

v2rayN and v2rayNG provide graphical interfaces; Xray and V2Fly cores handle connections. Choose a client for your device first, then check subscription settings, proxy mode, and routing rules. This helps keep interface options distinct from core configuration fields.

04 Platforms 03 GUI Clients Xray / V2Fly Core Families JSON Configuration Reference

Common v2rayN Settings

Follow five groups of settings in the order you’ll use them, from traffic entry to routing. The snippets below explain individual fields; they are not complete configurations for connecting to a remote server.

v2rayN · System Proxy Settings

Route Apps Through the Local Proxy First

The system proxy determines whether apps that follow system settings send requests to the client. After importing a subscription and selecting a server, enable the system proxy from the tray menu, then test access in a browser. This is separate from routing mode: the system proxy determines whether traffic reaches the local listener, while routing decides where that traffic goes next. Some apps use their own proxy settings, so you may need to enter the listener address and port manually. When troubleshooting, first confirm that the core is running and the port matches. Clear the system proxy before closing the client so apps don’t keep pointing to a stopped listener.

Check These Settings
Local mixed-inbound port: 10808
Local app proxy address: 127.0.0.1
System proxy: Set system proxy automatically
Before closing the client: Clear the system proxy

Note: Use the port set in the actual configuration.

Configure Settings in the Right Order

First, separate two questions: whether an app sends its traffic to the client, and how the core handles that traffic. A browser connection failure doesn’t necessarily mean the server configuration is wrong. The browser may ignore the system proxy, another program may be using the listener port, or the core may exit immediately after startup. Change one setting at a time and retest the same destination; this is usually more effective than toggling everything at once.

Read logs by stage: during startup, look for configuration parsing and port listening; during connection, check DNS resolution, handshakes, and timeouts. Raise the log level temporarily when needed, then restore your usual level when troubleshooting is done. Remove subscription URLs, credentials, and server identifiers before sharing logs. For the full configuration structure, see Configuration Fields and follow how inbounds, outbounds, and routing reference each other.

Client Downloads for Four Platforms

For desktop, start with v2rayN; on Android, choose v2rayNG or v2flyNG based on the core you need. Find the installers for each platform here; release details and download links are collected on the downloads page.

Windows · v2rayN

Best for desktop users who manage the system proxy, subscription groups, and routing mode from the tray menu. The downloads page lists both the cross-platform UI edition and the classic WPF edition. Check your operating system and processor architecture before choosing; don’t rely on the file extension alone.

For your first setup, run the client without elevated permissions and import a subscription. Once the local listener is working, configure the system proxy. Before enabling traffic capture that requires extra permissions, make sure you understand the permission prompt. If you already use another network tool, turn off its proxy capture first to prevent two clients from repeatedly changing system settings.

Go to Downloads

macOS · v2rayN

Choose an Apple Silicon or Intel installer to match your chip. Check the chip details under About This Mac before downloading to avoid installing a build that won’t launch on your architecture. The basics of subscriptions and routing are the same as on desktop; menu locations vary by version.

If macOS shows a developer verification or network permission prompt on first launch, read it in System Settings and handle it for that app only. Don’t disable system-wide protections just to run the client. After installation, check that the system proxy points to the client’s listening address. If the network still doesn’t work after closing the client, check for leftover proxy settings.

Go to Downloads

Android · v2rayNG / v2flyNG

For Xray configuration support, start with v2rayNG; consider v2flyNG if you need an existing V2Fly configuration. Most recent devices use arm64. If you’re unsure about your architecture, check the universal package details. Manage configurations separately in each client; similar names don’t guarantee full compatibility.

After importing a subscription, select a server and approve the system VPN request the first time you connect. The per-app proxy list determines which apps are captured, so test with an app that’s explicitly included. If the connection drops in the background, check battery management and background restrictions before reinstalling the client.

Go to Downloads

Linux · v2rayN

Choose deb or rpm based on your distribution’s package manager, then check whether you need x64 or arm64. A GUI client is useful for managing subscriptions and viewing logs on a desktop, but installing it won’t automatically route every app through the local proxy.

System proxy behavior varies across desktop environments. Browsers, terminal programs, and background services may each have their own proxy settings, so check them individually rather than assuming all traffic is captured because one app works. Before enabling a virtual network interface, check how permissions, system routes, and existing network management tools interact.

Go to Downloads

View All Clients →Compare the Three Clients →

Import a Subscription and Connect in Three Steps

This guide focuses on v2rayN for desktop and v2rayNG for Android. Work through installation, configuration, and traffic capture in stages so you know where to look if something goes wrong.

  1. Install the Client and Import a Subscription

    Choose an installer for your operating system and architecture, then open the client and find the subscription group settings. Add a descriptive name, enter a URL from a trusted source, and save it. Then update the group. Copy the full URL, including any parameters at the end; when pasting from a messaging app, watch for extra spaces or line breaks.

    After the update, check that server entries appear in the list. If you see a group name but no entries, review the update message to tell a network error from a parsing error. The client doesn’t include remote servers; after installation, you still need a configuration you’re authorized to use. Don’t show the full subscription URL in screenshots if it contains sensitive parameters.

  2. Select a Server and Set the Proxy Mode

    Choose an active entry from the server list and check that its protocol is supported by the selected core. On desktop, enable the system proxy; on Android, select VPN mode and approve the system request. For your first connection, keep the client’s default routing. Add custom domain rules or per-app selections after you’ve confirmed a basic connection works.

    A server-list test only reflects the result of that particular test; it doesn’t guarantee access to every website or app. If an entry fails, check the connection log, then verify the server address, port, credentials, and device time. Repeatedly changing transport and security settings can break the match between the client and the server configuration.

  3. Test Access and Keep a Troubleshooting Baseline

    Use an app you actually need to access a specific destination, then check whether the client log shows the connection. If there’s no log entry, first check whether the app is using the proxy. If an entry appears but the connection fails, inspect DNS, handshake, and timeout details. Change one factor at a time and note the results before and after.

    Once the connection works, configure routing exceptions, background operation, and startup behavior as needed. You can use the same subscription source on a computer and phone, but system proxy settings, VPN permissions, and per-app lists must still be configured on each device. Before closing the desktop client, clear the system proxy. If the network stops working, restore normal networking first, then re-enable traffic capture one setting at a time.

Read the Full Setup Guide →

Project V, V2Fly, and Xray

Knowing the difference between a project ecosystem, proxy core, and GUI client helps you work out where to import a configuration and which component will run it.

Project V Ecosystem
Xrayv2rayNG · Android Client
V2Flyv2flyNG · Android Client
v2rayNDesktop GUI · Choose a core for your configuration

From V2Ray to Different Core Families

Project V is a useful starting point for understanding the V2Ray ecosystem, with a modular approach to proxies, inbounds, outbounds, and routing. V2Fly continues community development of the V2Ray core. Xray grew from a related codebase and has followed its own path in protocol and transport support. The projects share some history, but that doesn’t mean every field, default, or protocol combination is interchangeable. When following a guide, first check which core it covers.

The Client Provides the Interface; the Core Handles Connections

v2rayN brings subscriptions, server selection, logs, and system proxy settings together in a desktop GUI. v2rayNG is for Android and organizes configuration around the Xray core; v2flyNG provides an Android GUI for the V2Fly core. These are open-source clients, and their UI projects don’t necessarily follow the same development schedule as their core projects. To determine whether a feature works, check both whether the client can generate the required configuration and whether the core that actually runs supports it.

Open-Source Licenses and Usage

Open source means the source code is available under a license that sets conditions for use, modification, and distribution; it doesn’t mean every component uses the same license. For example, v2rayN and v2rayNG use GPL-3.0, while the V2Fly core uses the MIT License. Review the requirements for each component before redistributing a combined product. For everyday use, check that the client comes from a trusted source, that you’re authorized to use the configuration, and that you understand the proxy and traffic-capture features you enable.

Releases and Configuration Compatibility

Client updates may change the interface, configuration generation, or bundled core. Core updates can also affect compatibility with configuration fields. The downloads page lists current release links; the home page doesn’t pin a specific release number. Before updating, keep your subscription groups and any essential settings. Test the existing setup after updating before trying new features. If something breaks, compare logs and configuration changes instead of blaming a core family without evidence.

V2Ray Release Hub provides client downloads and Chinese configuration guides; its name does not imply affiliation with upstream projects. The guides focus on procedures and configuration fields, and do not provide server accounts or subscription services. For protocol support, check the client, core, and server configuration you actually use. See About This Site for our scope and editorial principles.

Client Guides and Technical Notes

Explore configuration structure, desktop interfaces, and syncing across devices, with guidance for practical use cases. Check each menu and field against the client version you’re using.

View All Articles →