Choose a client · Import subscriptions · Configure routing

V2Ray Wikiv2rayN Downloads & Guides

Choose an open-source client for your platform, start by importing a subscription, then configure proxy modes and routing.

V2Ray Client Downloads

Choose v2rayN for desktop or start with v2rayNG on Android. On the download page, select a package based on your processor architecture and package type.

Windows

v2rayN comes in a desktop edition and a classic WPF edition. The desktop edition uses a cross-platform interface, while the WPF edition retains its familiar classic layout. Both support subscription and routing management.

Before installing, check your processor type in system settings. If you see a runtime requirement, follow the relevant installation instructions. Repeatedly changing subscriptions won't fix a runtime issue: a launch failure and an unusable subscription are separate problems.

Go to downloads Windows client→

macOS

Choose v2rayN and check the chip listed under About This Mac to select the Apple Silicon or Intel package. Matching the package architecture to your processor is more reliable than guessing based on the device's appearance.

If a security warning appears on first launch, verify the software source and read the warning before following the options provided by macOS. After setup, check that the system proxy is working. Grant administrator permissions separately for features that require them.

Go to downloads macOS client→

Android

For an Xray-based client, choose v2rayNG. If you need the V2Fly core, consider v2flyNG. Most recent mainstream Android phones use arm64; if you can't confirm your architecture, check the universal build details.

Android uses a VPN interface to route connections, so you'll need to approve the system permission on first launch. If the connection drops when the app is in the background, check battery optimization and background activity restrictions rather than assuming the subscription format is at fault.

Go to downloads Android client→

Linux

v2rayN offers deb and rpm packages for x64 and arm64. Check your distribution's package format first, then select the matching architecture. Package format and processor architecture are separate choices.

Desktop environments may handle system proxy settings differently. If your browser connects but other apps don't, check whether those apps follow the desktop proxy settings. For broader traffic routing, see the TUN configuration guide.

Go to downloads Linux client→

A client reads configuration and establishes connections; the installer itself does not provide server details. Before importing, get a subscription URL or share link from a trusted source. When switching computers or phones, check protocol support and the import result again instead of assuming settings will carry over just because the client names look similar.

View all clients →

Subscriptions, Routing, and Proxy Modes

Think of the setup as four steps: confirm the configuration was imported, choose which apps should use the proxy, then decide how connections are routed through the core.

Importing and Updating Subscription Groups

A subscription URL is used to retrieve a set of configurations; it isn't a link for opening a regular webpage in your browser. In v2rayN, enter a name and URL under Subscription Group Settings, save the group, then update it. On Android, add it from the subscription group menu. Groups keep sources separate and make it easier to see what an update affects. Unlike a one-time share link, a subscription gives you a way to fetch the configurations again. If an update fails, first check that the URL is complete and still valid. Then determine whether the problem is fetching or parsing, rather than creating another group with the same name.

These examples illustrate settings and rule behavior; they are not a complete, importable configuration. For the full setup sequence, see the Getting Started guide →

The Project V, V2Fly, and Xray Ecosystem

Start by distinguishing the client, core, and protocol. They refer to different layers, and similar interfaces don't mean every configuration is interchangeable.

The client provides the interface; the core handles connections

Project V is a good starting point for understanding the V2Ray ecosystem. V2Ray separates features such as inbounds, outbounds, transport, routing, and DNS into configurable modules. Graphical clients build on these features with controls for subscriptions, mode selection, and logs. That's why installing a client and having a usable configuration are two different things. A client launching successfully only confirms that the program runs; a working connection still requires complete server details, a compatible protocol, and the right way to route traffic.

V2Fly continues community development of V2Ray-related projects, while Xray is a separate core line built from related code. They share a technical background but have evolved in different directions. When following a guide, check both the client name and the core actually in use. Seeing a protocol name doesn't guarantee support for every extension parameter. Match the server's configuration requirements against the capabilities of the core your client can use.

What These Three Open-Source Clients Offer

v2rayN is designed for desktop use, with subscription groups, system proxy, and routing managed through a graphical interface. Desktop users can build familiarity with one client, then choose the package for their operating system. Because it can use cores from ecosystems such as Xray and V2Fly, it's important to distinguish the interface from the core handling connections. Available cores and features depend on the specific release and its interface; don't assume a feature shown in a screenshot from another platform is available in yours.

v2rayNG is a popular open-source Android client that uses the Xray core. Android relies on VPN permission to route connections, so its launch flow differs from the system proxy menu on desktop. v2flyNG offers an Android option using the V2Fly core. The names are similar, but choose based on the core your configuration needs rather than treating one as a general-purpose fix for the other. Before switching clients, check that the configuration fields and protocol features are compatible.

What to Check: Client and Core
ClientTypical useWhat to check first
v2rayNDesktop graphical configuration and subscription managementPackage architecture, runtime requirements, and the core in use
v2rayNGAndroid configuration with XrayProtocol support, VPN permission, and background activity restrictions
v2flyNGAndroid configuration with V2FlyCore compatibility, imported fields, and system permissions

Evaluate open-source licensing and configuration sources separately

All three clients are open-source software. Public source code and license terms let users examine how the software works and under what conditions it can be used. Projects in the ecosystem may use different licenses; check each project's terms before modifying, redistributing, or reusing its code. Open source describes how software is developed and licensed. It doesn't mean every subscription or server from an arbitrary source is trustworthy, nor does it make the client project responsible for connection logs, service quality, or availability.

Subscription URLs often contain parameters that identify the user, so treat them as sensitive configuration. When asking for help, share the error type, client name, and relevant settings, but redact the full URL, identity fields, and authentication data. Before importing a configuration from an unknown source, check for additional routing or DNS settings. Understanding these boundaries is more useful than relying on an interface showing that the client is running to judge whether the connection is behaving as expected.

Software, Subscription, and Rule Updates

A software update changes the client and its related components. A subscription update retrieves connection settings from a remote source, while a rule update may change the sets of domains and IPs used for matching. These are different operations. Updating the software may not fix an expired address, and repeatedly refreshing a subscription may not help if the client can't parse new protocol parameters. Identify which layer has changed before deciding what to update; this helps avoid redundant steps and lost settings.

Before upgrading, note the proxy mode, routing setup, and any essential custom settings that currently work, and save your configuration using the client's built-in options. After upgrading, test with the same known-good configuration. Confirm that the client launches, subscriptions load, and basic access works before restoring extra features. Don't change the core, import unfamiliar rules, and enable TUN all at once. If you change several things together and something breaks, the logs won't make it easy to identify the cause.

From Subscription Import to Connection Testing

For a first-time setup, follow a clear sequence: install a client that launches successfully, add a subscription group and update it, select a configuration, then enable the traffic routing method suited to your system. On desktop, start with the system proxy; on Android, approve VPN access. Then open an app you actually need to use and check that requests succeed, using the client logs to confirm that connections are coming through. A running status in the system tray isn't a substitute for testing access in a real app.

If access fails, first check whether it affects every app or just one. Then determine whether the issue is DNS resolution, a connection timeout, or a server rejection. If a browser works but other programs don't, check the traffic capture scope. If the subscription list is empty, check fetching and parsing. If only certain domains fail, inspect rule order and DNS. Narrowing down the issue based on what you observe usually preserves more useful clues than reinstalling. To learn the process step by step, continue with the V2Ray System Guide.

Popular Questions

Do subscription URLs and individual share links use the same import method?

No. Add a subscription URL to a subscription group, then update it. An individual share link is usually imported through the clipboard or a similar option. Identify which type of link you have, then follow the Getting Started guide instead of importing a subscription URL as a single configuration.

Do I still need routing rules if I enable the system proxy automatically?

They serve different purposes. The system proxy tells apps that support it how to connect to the local proxy; routing rules decide which outbound handles connections after they reach the core. Enabling the system proxy doesn't replace routing rules. For setup details, continue with the guide.

Why can't I connect after a subscription update succeeds?

A successful update means the configuration was fetched and parsed; it doesn't guarantee the server is reachable. Check the selected configuration, traffic routing method, and error logs, then review the server details and network conditions. Follow the connection testing steps to pinpoint the layer where the problem occurs.

Should I turn on TUN during the initial setup?

On desktop, first confirm that a basic connection works in regular proxy mode, then decide whether you need TUN for your apps. This helps separate configuration issues from problems with virtual network adapters, permissions, or system routing. Start with the Getting Started guide.

Subscription and Configuration Guides

Recent articles tackle specific issues: find the right setting, understand the configuration structure, and troubleshoot startup problems by checking the runtime environment.

View all articles →