v2rayN · Windows / macOS / Linux

V2Ray for Windowsv2rayN Guide

Start by choosing an installer. Add servers with subscription import, then configure system proxy or TUN for your needs.

  • Open source
  • Graphical interface
  • Split routing

Feature overview

Client featuresDesktop and Android compared

Node protocols and transport settings

When importing a node, check the protocol first, then its transport and handshake settings. The desktop v2rayN and Android v2rayNG clients can both handle common VMess, VLESS, and Trojan configurations with compatible cores, but matching protocol names don't mean transport settings are interchangeable. When copying a node, keep the transport and security options provided by its source. If it connects on desktop but not Android, compare the fields parsed by each client and check whether the core supports that combination. Change one setting at a time.

  • VMess: Check that the protocol, transport, and security options match the details from the source.
  • VLESS: Check that the flow control setting is supported by the core and transport used by the node.
  • TLS and REALITY: Keep the handshake settings from the original node configuration.
Itemv2rayN desktopv2rayNG for Android
VMessSupportedSupported
VLESSSupportedSupported
TrojanSupportedSupported

Choose an installer

Four platformsDownload by OS and architecture

Check your device's CPU architecture first, then choose a package for your operating system, distribution, or interface. The installer contains the client only; you'll need to obtain a node or subscription URL separately. If you already use a client, back up its settings first, then test the new installation with the same node.

Windows

v2rayN · Desktop / WPF

Check System Type on your system's About page. Both download options are for x64: the desktop edition uses a cross-platform interface, while the classic WPF edition keeps the original interface layout. Choose either one for your first installation; there's no need to install both just to follow a guide.

If the download is a compressed package, extract all files to a writable folder before running the program. Don't launch it directly from the archive window. If Windows reports a missing runtime, follow the instructions for your chosen build. Quit any older client first to prevent two instances from competing for the same local port.

Go to downloads

macOS

v2rayN · Apple Silicon / Intel

Open About This Mac and check the chip or processor. Choose arm64 for Apple silicon or x64 for an Intel processor. Don't guess based on the purchase year; models released around the same time may use different architectures. Open the disk image and follow its installation instructions.

After installation, launch the client from Applications rather than running it from the mounted disk image. For your first connection, check that your browser uses the system proxy as expected, then configure proxy settings for individual apps if needed. When macOS asks for permission, check whether it's for launching the app or enabling a network feature.

Go to downloads

Android

v2rayNG · v2flyNG

The usual choice is v2rayNG, which uses the Xray core. Consider v2flyNG if an existing configuration specifically requires V2Fly. Most recent devices can use arm64. If your device information doesn't list supported app architectures, try a universal package rather than transferring a desktop installer to your phone.

After installation, import a subscription, update the list, and select a node before tapping Start. Follow the system prompt to establish a local VPN session. If only certain apps can't connect, check the per-app proxy list. If the connection drops after the app has been in the background, check whether the system restricts its background activity.

Go to downloads

Linux

v2rayN · deb / rpm

Choose a package format for your distribution, then select the architecture for your device. Debian and Ubuntu typically use deb; Fedora and openSUSE typically use rpm. The download page lists x64 and arm64 builds. During installation, check dependency prompts in your distribution's package manager.

On first launch, make sure the client starts and the core loads the node before configuring proxy settings in your desktop environment. Even if the graphical interface's system proxy works, terminal apps may not use the same settings. Test apps individually, then decide whether TUN is necessary. This helps keep traffic coverage issues separate from node problems.

Go to downloads

Quick start

Import a subscriptionTest your connection in three steps

  1. Add a URL and update the subscription group

    Open subscription group settings, create a group, add a recognizable note, and paste the full subscription URL. Saving records the URL but usually doesn't populate the node list. Return to the main screen and update the subscription, then open the new group and check that it contains selectable nodes. If you only have a link for one node, use the client's clipboard import option instead of entering it as a subscription URL.

    If the list is still empty, first make sure you updated the group you just added, then check the update message. Extra spaces in the URL, an expired subscription, and a client receiving a login page instead of node data all require different fixes. Get the list to update before moving on.

  2. Select a node and choose a proxy mode

    Choose a node from the group and set it as the current server. For your first desktop test, leave TUN off. In the system proxy menu, choose “Set up system proxy automatically” and test with a browser that uses the system proxy. On Android, select a node and start the connection, then approve the system VPN prompt the first time.

    If the browser works but the target app doesn't, check whether the app has its own proxy settings. Try TUN only if you need to cover an app that ignores the system proxy. Note the original system proxy status before switching, so you can identify which change caused any issue.

  3. Test access and note where it fails

    Check the client log to confirm the core started successfully, then open the page or app you want to test. A latency test only reports the result of that probe; it doesn't replace testing actual access. If an app can't connect, note the approximate time, current node, proxy mode, and first useful error message.

    For the next test, change just one variable: try a known working node in the same app, then compare different apps using the same node. The first test can help identify a node or transport issue; the second can show whether an app is covered by the proxy. When you're done, turn off TUN or clear any temporary system proxy settings, then check that your usual network access is restored.

Open-source ecosystem

Project VHow clients and cores work together

The graphical client is for entering and managing settings; the core establishes connections, handles protocols, and applies routing. Understanding the difference helps you decide whether to switch installers, fix node settings, or change the proxy entry point.

Project V and V2Fly

Project V organizes inbound connections, outbound connections, and routing into a composable network configuration. Inbounds determine how traffic enters the program, outbounds determine how it's sent, and routing directs traffic to the appropriate outbound. V2Fly is a community project that continues V2Ray development and maintains the V2Ray core and related documentation.

This division also explains common configuration issues: importing a node successfully only means the client can read the list. Whether a connection works depends on whether the core supports its settings. Whether a browser uses that connection depends on whether the app sends requests through the client. Check these three stages separately when troubleshooting; it's more effective than repeatedly updating the subscription.

Xray and protocol support

After splitting from the V2Ray codebase, Xray has developed independently. It shares some configuration concepts with V2Fly, but the two projects maintain their own features and settings. REALITY, for example, is a connection security layer setting, not a node protocol that replaces VMess or VLESS. Separating connection settings into protocol, transport, and security layers helps pinpoint which field is incompatible.

Before switching cores on desktop, check that the new core supports the node's transport, flow control, and security settings. Once the configuration loads, review the connection log. If startup fails, check the configuration and core combination first rather than changing the system proxy or repeatedly switching DNS.

Open-source clients and licenses

v2rayN, v2rayNG, and v2flyNG are open-source graphical clients. v2rayN manages desktop nodes and routing and can use supported cores. v2rayNG is for Android and uses the Xray core; v2flyNG is for Android configurations that require the V2Fly core. Similar interfaces or names don't mean advanced settings and configuration files are interchangeable.

Open-source licenses govern the use, modification, and redistribution of code; check each project's license and the licenses of bundled components for specific terms. Open-source client code is separate from who provides a subscription or how long its nodes remain available. Choose a client based on platform and core requirements, and check the subscription source and update status separately when troubleshooting.

Updating the client, core, and subscription

Client updates can change the interface, defaults, or runtime environment. Core updates can change supported protocol features, configuration parsing, or connection behavior. Subscription updates fetch the node list again. These updates aren't interchangeable. If the node list hasn't refreshed, reinstalling the program isn't the first step. If the core can't recognize a field, repeatedly refreshing the list may not help.

Before making changes, note the current node, system proxy mode, custom routes, and listening port. Update one layer at a time, then retest with the same node and app before moving on. If the connection fails, compare the old and new settings one by one. If you have questions about protocol names or configuration fields, start with the glossary.

Setup and troubleshooting

Latest guides

Complete v2rayN Windows setup guide: Desktop or WPF edition?

Compare the interface and runtime differences between the two v2rayN Windows editions, then follow the full setup process: extraction, first launch, subscription import, and system proxy configuration. Includes common issues such as antivirus false positives and port conflicts.