Choose your platform

V2Ray Client Downloads

Start by identifying your operating system and processor architecture. The installer determines whether the app can run; node settings determine whether the connection is compatible. Check both separately. The links below open download options for each platform.

Windows

v2rayN · Desktop pick

For a graphical interface to manage subscriptions, switch nodes, and configure routing, start with v2rayN. The download page offers a cross-platform edition and the classic WPF edition. Choose based on your system requirements and workflow; there’s no need to install both just because their interfaces differ.

After installation, add a subscription and confirm that the node list updates. Then enable the system proxy. Consider TUN only if an app doesn’t follow the system proxy settings; you don’t need to turn on every option at the outset.

Download

macOS

v2rayN · Choose by processor

Open “About This Mac” in the system menu to check whether your device has an Apple Silicon or Intel processor, then choose the matching installer. Each package is built for different hardware, so file size alone isn’t a reliable guide. You don’t need to switch cores just because a tutorial screenshot shows a different interface.

If you see a security alert on first launch, confirm the download source, then check “System Settings → Privacy & Security” for details. The system proxy affects apps that follow system settings; TUN requires separate permissions. Set it up after confirming a basic connection works.

Download

Android

v2rayNG recommended · v2flyNG alternative

Start with v2rayNG, which uses the Xray core. Choose v2flyNG if your existing configuration specifically requires V2Fly. Most newer devices use arm64; if you’re unsure, check your device information or choose a universal package. A universal package supports more architectures, but doesn’t improve connection capabilities.

After saving a subscription URL under “Subscription Group Settings,” run Update Subscription as well. On the first connection, Android asks for permission to establish a VPN connection. Other tools using the same VPN slot may conflict, so stop one of them first.

Download

Linux

v2rayN · Linux desktop

Choose deb or rpm to match your distribution’s package system, then check whether your device is x64 or arm64. The file extension determines how to install the package; the processor architecture determines where it can run. Both must match. This graphical client is designed for managing subscriptions and rules in a desktop environment.

After installation, make sure the app launches and the core runs, then check your desktop environment’s proxy settings. Apps vary in their support for system proxies. If a terminal program isn’t using the proxy, check that program’s proxy configuration instead of importing the same subscription again.

Download

You’ll need to obtain a subscription URL separately. The client reads configuration and forwards requests; installing it doesn’t provide a working server automatically.

View all clients →

Settings → Plain-language guide

V2Ray Terms and Settings, Explained

Similar setting names don’t mean the settings do the same thing. A system proxy tells apps where to send requests; routing decides where those requests go; DNS looks up addresses for domain names. Understand how these fit together to know which menu to check when troubleshooting.

TUN Mode: Capture More Traffic

Think of TUN as a virtual network interface that lets the client handle traffic from more apps, including those that don’t read system proxy settings. It addresses whether requests reach the client—not whether a node can connect. First, use the system proxy to confirm the subscription and node work. Then enable TUN and grant any requested permissions. Other virtual network adapters or VPN tools can interfere with routing. Permissions vary by desktop platform. After enabling TUN, check DNS and routing results too; an enabled switch alone doesn’t confirm everything is working as expected.

v2rayN main window → Enable TUN
Confirm the node works, then check permissions and routing.

Setup Order: Get One Connection Working, Then Add Rules

For your first setup, follow the shortest path: “Import subscription → Update nodes → Select a node → Start connection → Test access.” Change one setting at a time and note the result before and after. If you change nodes, enable TUN, replace DNS, and edit routing all at once, even a successful fix won’t tell you which change worked. You’ll be left guessing the next time something breaks.

Check both the client and the apps you use when testing a connection. A running status only means the program has started; a successful test doesn’t prove every domain matched the intended rule. First check that a regular website loads, then test a destination that should use a specific route, and finally review routing results in the logs. See the full walkthrough in the Getting Started guide. For platform-specific installation and permissions help, see Troubleshooting.

FAQs: Clients, Subscriptions, and Connection Modes

What do I need after downloading a client?You’ll also need valid node settings or a subscription URL. Think of the client as a control panel: it stores settings, starts the core, and displays status. The server address, port, and authentication details come from the service you use. A client without configuration can’t establish the corresponding proxy connection.

Are global mode and TUN the same thing?No. Global mode generally describes how the client selects an exit for requests it receives; TUN describes how requests are captured. Even with TUN enabled, routing rules may send some requests directly. And global mode can’t capture requests from apps whose traffic never reaches the client.

Will updating a subscription overwrite manual changes?Subscribed nodes may be recreated or replaced during an update, so temporary edits aren’t a reliable way to keep long-term changes. Back up any settings you need to retain, and check whether they belong to a subscription group. Compare terms in the Glossary; you don’t need to memorize every acronym on your first day.

Clients / Cores / Protocols

The Project V, V2Fly, and Xray Ecosystem

These names refer to different layers. A client provides the interface, a core handles network connections, and a protocol defines how they communicate. Understanding how the three fit together is more useful than memorizing a download name.

Graphical clientsv2rayN · v2rayNG · v2flyNG
Connection and routing coresXray · V2Fly
Communication protocols in the configurationVLESS · VMess · Transport and security settings

Project V: From Network Tools to a Client Ecosystem

Project V is a useful starting point for understanding V2Ray’s background. Its core idea is to organize proxy connections, routing, and transport capabilities into configurable modules. In everyday discussions, “V2Ray” may refer to a specific core or to a broader set of tools using related protocols. That’s why a search for the same name can lead to very different downloads. This site clearly separates graphical clients from background programs that don’t offer a click-to-use interface.

V2Fly continues development and community maintenance of implementations related to V2Ray. Xray builds on related technology but has developed its own implementation and features. They share technical roots, but configuration fields, feature support, and protocol extensions don’t always match. When following a guide, check which client and core it covers. Similar menus only mean the interfaces look alike; they don’t prove that the underlying behavior is identical.

Three Open-Source Clients: Choose an Interface and a Core

v2rayN is an open-source graphical client for desktop, handling subscription management, node selection, parameter generation, and core startup. It can work with different cores; exact support depends on how the client integrates them and which core you choose. The desktop and classic WPF editions differ first in interface technology and platform coverage. A newer interface doesn’t mean the same node will connect faster.

v2rayNG is an open-source Android client using the Xray core; v2flyNG is an open-source alternative using the V2Fly core. Their workflows have similarities, but your choice should depend on node requirements and feature compatibility. If your configuration includes specific extension parameters, first confirm the core supports them, then choose a client. For a side-by-side look, see Client Comparison. There’s no need to keep migrating subscriptions just because the names look alike.

Open-Source Licenses: Code Rights and Service Terms

Open source means the source code is available under a license that allows people to read, use, modify, or distribute it within the license terms. Clients, cores, and their dependencies may each use different licenses; refer to the license included with each project for specific conditions. Readable code supports technical review and community collaboration, but users should still consider download sources, system permissions, configuration contents, and how the service handles requests.

Client software and subscription services are separate. Open-source clients may be free to use, while subscription fees, validity periods, and node availability depend on the service provider. This site provides download links and configuration guides; it doesn’t sell nodes or manage service accounts. If a subscription stops working, check the URL and service status first. Reinstalling the client repeatedly usually won’t fix a server-side problem.

Updates: Apps, Cores, and Rules Are Separate

“Update” can mean at least three things: upgrading the client app, updating the core that establishes connections, or refreshing the node list in a subscription. Routing may also rely on rule data such as GeoIP and GeoSite, which has its own update process. Updating a subscription won’t upgrade the app, and upgrading the app won’t fix an expired subscription URL. Identify what needs updating before choosing a menu.

Before changing your setup, back up subscription groups, routing rules, and manually added nodes, and save a configuration that still works. After an update, check your subscription, default node, and proxy mode one by one. If something goes wrong, review the specific error in the logs to determine whether it’s a compatibility issue or a permission change. Don’t overwrite every setting while troubleshooting. The menu paths on this page help you find features; if the interface changes, use the current client’s feature names and descriptions.

Subscription links may contain access credentials, and logs may reveal server addresses. Before asking for help, hide this information and share only the error type, relevant settings, and steps to reproduce the issue. Follow the laws where you live and the rules governing your network.

Explore protocol and core terminology →

Setup Guides

v2rayN and v2rayNG Guides

Once your basic connection works, dig into the issues that matter to you: which route DNS queries take, which desktop edition to choose, or why a subscription won’t update. Each guide focuses on a specific setting so you can follow along in the client.

Browse all articles →