Android · Windows · macOS · Linux clients

V2Ray Android Client

Download and set up v2rayNG for Android or v2rayN for desktop. Start by importing a subscription, then configure routing as needed.

  • Open source
  • Graphical interface
  • Guides in Chinese

Choosing an installer

Download a client for your platform

Check your operating system and processor architecture before choosing an installer. Back up existing configurations before updating.

Windows

The standard v2rayN desktop edition is the recommended choice. If you prefer the classic interface, choose the WPF edition. Menus differ between the two, so identify your interface before following a guide.

Open Settings → System → About and check System type. An older PC may support a 64-bit OS without currently running one. Before updating, note your current edition and data directory to avoid mixing old and new files.

macOS

Open About This Mac from the Apple menu. If the Chip field shows Apple silicon, choose the Apple Silicon installer; if Processor shows Intel, choose the Intel installer.

Open the disk image, drag v2rayN to Applications, then launch it. Don’t open both the copy in the disk image and the one in Applications. If the old interface appears after an update, check where the app is launching from.

Android

v2rayNG is the usual choice. Consider v2flyNG only if you know you need V2Fly compatibility. If your system supports arm64, choose the matching package; if you’re unsure, check the universal build and system requirements on the download page.

If the system says the app can’t be installed over the existing version, first check that the package is for the same client and note the specific reason. Don’t uninstall the old app straight away: manually added configurations and group notes may only be stored there.

Linux

Choose a package format for your distribution, then match the architecture. Debian and Ubuntu usually use deb; Fedora usually uses rpm. The right package format doesn’t guarantee an architecture match.

Check your device architecture on the system’s About page. If the installer reports missing dependencies, note the library names in the error. If it reports an architecture mismatch, return to the download page and choose another build. Whether system proxy settings are respected can also vary by desktop environment and app.

Browse all clients

From import to routing

Client settings and routing rules

First get one configuration connecting successfully. Then decide which apps and addresses should use the proxy. Check these four areas in order.

View configuration guides

Import subscriptions and organize groups

A single share link and a subscription URL are different kinds of input. If you have one link, copy it and choose “Import from clipboard” to test a configuration. For a subscription URL, create a group with a recognizable name, save it, then update it. Groups make it easier to switch sources or troubleshoot without searching the full list. After updating, check which group received the new entries, then select the configuration you want to use. If the list hasn’t changed, check that the URL is complete and that you updated the right group instead of repeatedly tapping Connect.

Import a single configurationTop-right + → Import from clipboard
Save the subscription, then refreshSubscription group settings → Update subscription

Routing rules

Routing determines which outbound handles traffic that has already reached the core. To keep access to LAN printers and router admin pages, start with a preset rule that bypasses LAN addresses. Custom rules are usually matched in order, so put specific exceptions before broader rules. The snippet on the right shows only direct routing for private addresses; your actual configuration also needs an outbound with a tag matching the rule. After editing, test both a local service and a destination expected to use the proxy. If only one fails, check its rule rather than rewriting the entire routing setup.

Direct routing for private addresses · single rule
{
  "type": "field",
  "ip": ["geoip:private"],
  "outboundTag": "direct"
}
Domain strategy example

domainStrategy: AsIs does not resolve domains solely for routing matches.

Choosing between Xray and V2Fly cores

The term “dual core” refers to two options in this ecosystem; it doesn’t mean every client lets you switch cores in the app. On Android, v2rayNG uses Xray and v2flyNG uses V2Fly. On desktop, v2rayN manages multiple core options, depending on the installer. Match the client to the protocols, transport, and security settings provided by your server. Successful import only means the client read the configuration fields; it doesn’t guarantee that the core supports that combination. If a configuration fails in just one client, note its original settings and compare both clients using the same configuration.

Android

v2rayNG → Xray
v2flyNG → V2Fly

Compare configuration fields on desktop

outbounds[].protocol is the protocol; streamSettings.network is the transport.

TUN and system proxy modes

On desktop, start with the system proxy and test it in a browser. It usually affects only apps that honor system proxy settings. If the target app doesn’t use them, consider TUN after checking system permissions and possible conflicts with existing virtual network adapters. On Android, VPN mode requires system authorization. If you enable per-app proxy, also check the app list and whether apps are included or excluded. When troubleshooting, change only one connection method at a time and test with the same app. A lit Connect button only means the service has started; verify that the target app’s actual requests are going through the proxy.

v2rayN desktop menuSystem proxy → Set system proxy automatically
v2rayNG Android menuSettings → Per-app proxy

Open-source projects and maintenance

Project V and the core ecosystem

The interface manages configurations; the core establishes connections and applies routing. When troubleshooting, first identify which layer is involved.

About the project Read the advanced guide

From Project V to V2Fly and Xray

Project V is an open-source proxy ecosystem built around V2Ray. It breaks protocols, transports, routing, and other components into configurable parts, providing cores that graphical clients can use. The V2Fly community continues V2Ray’s maintenance, while Xray developed from a fork of V2Ray code and follows its own maintenance path. Similar-looking configuration fields don’t mean the two implementations are identical. When following a guide, check which core its examples use and whether the fields shown are actually generated or read by your client.

What each client does

v2rayN is an open-source desktop GUI client for managing subscriptions, cores, and local proxy settings. v2rayNG is an open-source Android GUI client that uses Xray and routes traffic through the system VPN service. v2flyNG is another open-source Android GUI client; it uses V2Fly and is suited to configurations known to require that core. A client’s name tells you about its interface and installation, but not whether a configuration will work: the protocol, transport parameters, and server requirements still need to match. When comparing screenshots in a guide, distinguish the main screen from subscription editing and runtime settings.

What open-source licenses mean

The V2Fly V2Ray core is licensed under MIT, while the Xray core uses MPL 2.0. The former permits code reuse subject to conditions such as retaining relevant notices; the latter requires source availability for covered files when distributing modified software. Cores, clients, and their dependencies may each use different licenses, so a core’s license doesn’t automatically apply to the whole installer. For everyday use, this distinction helps separate using software from redistributing code. If you plan to modify or distribute software, read the relevant project’s license.

Check the client, core, and rules separately when updating

A client update may change menus or how configurations are saved; a core update may change protocol support or parameter validation; and a routing data update may change how certain destinations are matched. They don’t necessarily update together. Before updating, note your commonly used groups and proxy mode, and save custom local rules. Afterward, test a configuration that used to work before enabling per-app settings or custom routing. If something breaks only after an update, identify what changed most recently. Changing the core, rules, and proxy mode all at once makes the results difficult to compare.

Identify the problem layer from the symptoms

If a subscription update fails, first check whether the client can fetch it. If an imported entry won’t start, check the core’s error. If the core starts but only one app can’t connect, check whether that app is using the proxy. You can also test another app that honors system proxy settings to avoid mistaking an app-level network setting for a server problem. When reporting an issue, include the steps taken, where it failed, and the exact error text. Before sharing logs, remove subscription URLs, credentials, and identifying account details.

Common configuration questions

Not sure what a menu item means? Check the V2Ray glossary.

Will updating a subscription switch the configuration in use automatically?

Treat refreshing the list and selecting a configuration as two separate steps. After refreshing, return to the main screen and check the current entry. If it was removed or renamed, select it again and test. New entries appearing in the list doesn’t mean the active session has switched.

Should I check per-app proxy or routing first?

First check whether the app is using the proxy, then see which routing rule matches the destination. If the app is excluded from the per-app list, changing domain or address rules won’t change where its traffic goes.

The connection test passes, so why can’t my app open anything?

A successful test only shows that the client could reach the test destination through the selected configuration under the conditions at that time. Test again in the app that’s actually failing. Check whether it honors system proxy settings, matches a different routing rule, and can resolve the domain that fails.

Will manually added configurations migrate with my subscription?

No. A subscription only provides the entries returned by that source. Manually added configurations must be exported or imported separately. During migration, also check group notes, custom routing, and system permissions.

Client troubleshooting notes

Recent guides

Choose a guide based on what you’re seeing: slow loading, no access after connecting, and disconnects after locking the screen each call for a different starting point.

Why Is V2Ray Slow? Diagnose Server Load, Network Quality, and Local Settings

Slow speeds don’t always mean the server is at fault. This guide breaks troubleshooting into server, network, and local layers, showing how to narrow down the cause with real connection tests and comparisons before adjusting transport settings and routing rules.

For cases where pages open but load or download noticeably slowly. Compare results on the same device and test destination to tell whether one route is slow or local apps are broadly affected.

V2Ray Says Connected but Websites Won’t Load: Check System Proxy, Routing, and DNS

The client says it’s connected, but the browser keeps spinning. Check the local proxy port, system proxy status, routing rules, DNS resolution, and time sync in order to find where the connection breaks.

For cases where the connection button is active but requests won’t complete. Start by checking the device; don’t rush to delete the subscription. Note the first step that fails before deciding whether to switch configurations.

v2rayNG Battery Drain and Background Kills: Battery Optimization and Keep-Alive Settings

v2rayNG runs in the background as a VPN service. Battery use depends on system power policies and client settings. This guide covers battery optimization and autostart settings across device makers, plus ways to reduce wake-ups.

If it works with the screen on but disconnects after being locked, check background restrictions first. If the connection stays stable but battery use rises, check system battery usage and how often the client wakes. Don’t troubleshoot both symptoms as if they were the same issue.

View all articles