v2rayN
Windows · x64
Listed version7.24.1
Both downloads are ZIP archives. Extract each to its own folder, then follow the included instructions to run the installer. Don't launch it from the archive preview window.
Client downloads / Platforms and architectures
V2Ray Download
v2rayN for desktop, v2rayNG for Android.
Choose your operating system first, then the package that matches your device.
v2rayN, v2rayNG, and v2flyNG are free, open-source clients. Downloading and installing one does not configure a connection; you'll also need a valid server configuration or subscription.
- VMess
- VLESS
- Trojan
- Shadowsocks
- REALITY
Download options
Choose your operating system
For desktop, choose v2rayN. On Android, start with v2rayNG; consider v2flyNG if you need the V2Fly core. Download buttons are at the top of each client card, with installation and architecture notes below.
Windows client
Both are v2rayN builds. Choose Desktop or the classic WPF interface based on how you prefer to work.
System and installation requirements
| Check | How to choose |
|---|---|
| System architecture | Both installers on this page are x64. Check your system type under Settings → System → About. |
| Windows version | Use a supported version of Windows. Check the current release notes and installer prompts for the exact minimum version and runtime requirements. |
| File location | Choose a local folder you can write to, with enough space for extraction, installation, and configuration files. |
| Permissions | Start with standard user permissions. Grant additional permissions for TUN or network components only when prompted for those features. |
Desktop and WPF mainly differ in UI technology and how workflows are presented. The interface alone doesn't determine whether a particular protocol is supported; that also depends on the included core and configuration fields. If you're new to the client, start by importing a subscription, selecting a server, and setting the system proxy before customizing routes.
Before upgrading from an older version, export your configuration and quit the old process. If you're switching interface editions, keep the original folder and install into a new one. Migrate using an import method supported by the client; don't mix program files from different versions.
If the window opens after installation but browser traffic is unchanged, check the system proxy status before reinstalling. The system proxy affects only apps that follow the system proxy settings. For other traffic-routing options, see the mode descriptions in the setup guide.
macOS client
Check About This Mac for your chip, then choose the matching package for Apple Silicon or Intel.
v2rayN
macOS · Choose by chip
Listed version7.24.1
Open the downloaded DMG, follow its instructions to install the app in your Applications folder, then launch it from there.
System and installation requirements
| Check | How to choose |
|---|---|
| Chip type | Apple Silicon uses arm64; Intel uses x64. |
| Windows version | Check the current release notes and launch prompts. Confirm compatibility before updating on an older system. |
| Install location | Install the app in your Applications folder instead of running it from a temporarily mounted DMG. |
| Network permissions | Read system permission prompts and verify what you're approving when setting the system proxy or enabling network traffic interception. |
Chip architecture and macOS version are separate requirements. A package with the right architecture won't necessarily run on every older system. If you see a message that your system version is too old, check the release requirements first; downloading a package for another architecture usually won't fix an incompatible system API.
If a security warning appears on first launch, read the details and confirm the download source and app origin. If you're unsure about a file's source, signature, or permissions, stop and investigate. Don't force it to launch by disabling system security controls across the board.
If another proxy tool is running, check whether it's still changing your system proxy settings. Multiple programs managing the same setting can leave your network in an unexpected state when one client exits. Before switching, note the old tool's proxy and DNS settings, then enable the new client's features one at a time.
Android clients
Start with v2rayNG. Choose v2flyNG only if your configuration requires the V2Fly core.
v2rayNG
Android · Xray core
Listed version2.2.6
The version shown is the listing's version label; installer filenames may follow a different release schedule. Check the installed version in your system's app info.
v2flyNG
Android · V2Fly core
Listed version1.10.31
Before switching from v2rayNG, check your subscription and configuration formats. A similar interface doesn't mean every setting can be copied directly.
System and installation requirements
| Check | How to choose | Installation notes |
|---|---|---|
| Processor architecture | For mainstream 64-bit systems, start with arm64; choose Universal if you're unsure. | A 64-bit-capable processor doesn't guarantee the device runs a 64-bit system. |
| Windows version | Check the minimum Android version required by the current installer. | If you see a parsing error, check both the system version and whether the package finished downloading. |
| Installation permissions | Install the APK through the system installer. | Grant installation permission only to the file manager or browser you're using, and revoke it afterward if you like. |
| Connection permissions | The first time you start a connection, Android may show a VPN connection request. | Confirm the request comes from the client you just installed. Other VPN apps may be using the same connection capability. |
After installation, import a known-good configuration before accepting the system connection request. If the app works in the foreground but disconnects when the screen is locked, check battery optimization, background activity permissions, and power-saving settings. Don't change Mux, DNS, routing, and per-app proxy settings all at once, or it will be harder to identify the cause.
v2rayNG uses the Xray core, while v2flyNG uses the V2Fly core. They may differ in protocol extensions, security layers, and configuration formats. For VLESS, REALITY, or custom transport parameters, check the server requirements and the current client's actual support. Importing a link successfully doesn't guarantee the connection will work.
If an update reports that the app isn't installed, note the full error and check the old app's signature, version compatibility, device architecture, and available storage. Don't uninstall the old app right away; that could also delete local settings. Export or otherwise back up your configuration first.
Linux client
Choose deb or rpm for your distribution, then check whether your system is x64 or arm64.
v2rayN
Linux · Desktop environment
Listed version7.24.1
For arm64 devices
For a 64-bit ARM system, choose the matching package below, not one of the x64 packages above.
System and installation requirements
| Check | How to choose |
|---|---|
| Desktop environment | v2rayN is a GUI client and requires a working graphical desktop session. |
| Processor architecture | amd64 and x86_64 correspond to x64; aarch64 corresponds to arm64. |
| Package system | Use deb or rpm as required by your distribution. Renaming a file extension doesn't convert a package format. |
| System dependencies | Check the dependencies reported by your package manager. The same package format can still require different system library versions. |
Open the downloaded package with your distribution's software installer, review the app information and dependency prompts, then confirm installation. If dependencies are missing, check your distribution version and the package's build target; don't force installation by ignoring dependencies. Older distributions may need an update to a supported system environment.
Architecture aliases can be confusing: typical 64-bit Intel and AMD desktops use amd64 or x86_64; 64-bit ARM devices commonly show aarch64. amd64 is an architecture name, not a reference to a specific processor manufacturer. Check your desktop's system information for the processor and OS architecture.
After installation, start the GUI as a regular user. System proxy settings vary by desktop environment, and some apps don't automatically use them. If you need TUN, follow the client instructions for the required network permissions instead of running your entire desktop session with elevated privileges.
After installation
Configuration, updates, and permissions
Get a basic connection working first, then adjust routing and DNS one setting at a time. When something goes wrong, keeping the error message is more useful than repeatedly reinstalling.
First install: import a valid configuration
The client manages configuration and runs the core; it doesn't include a ready-to-use server. Get a valid subscription URL, share link, or compatible configuration file, then use the relevant import option in the client. After importing, check the server type, transport, security layer, and required fields. Don't mistake a webpage URL for a subscription URL.
After selecting a server, check the system proxy mode on desktop or approve the system connection request on Android. Test with a regular webpage request and check the client logs; a single latency test doesn't prove that all apps are using the proxy.
Upgrade or migrate: keep your existing settings
Before updating, preserve subscription groups, custom routes, DNS, listening ports, and other manual changes. Prefer the client's built-in export feature. Configuration files may contain credentials, so store exports somewhere secure and don't upload them to public pages.
Quit the old version before installing so its files aren't in use. After updating, check that your configuration is still present and the proxy mode is correct before restoring launch-at-startup or automatic updates. When switching clients, test one configuration first; migrate the full list only after confirming the fields are compatible.
How clients, cores, and subscriptions fit together
GUI clients in the Project V ecosystem provide server lists, subscription management, and access to system network settings. The core handles proxy protocols and connections. V2Fly and Xray are related core projects that have evolved separately, so check compatibility against specific versions. If a security layer or transport option is missing after installation, check whether the core supports it rather than choosing a similarly named protocol at random.
A subscription distributes configuration; it isn't a client installer. A failed subscription update and a failed installation are different problems: for the former, check the URL, request errors, and response format; for the latter, check OS compatibility, architecture, and installation permissions. For background on VMess, VLESS, Trojan, Shadowsocks, and REALITY, read the protocol and core reference, then choose a client that supports your configuration.
Download questions
Common installer questions
Narrow down the issue by interface, device architecture, and when the error occurs.
Windows: Should you choose Desktop or WPF?
If this is your first time, start with Desktop, which uses a newer cross-platform interface. Choose the classic, stable WPF interface if you prefer the traditional Windows experience. Both are v2rayN builds for x64. Export your settings before switching, and don't mix the two versions' program folders.
Android: What's the difference between arm64 and Universal?
Most mainstream phones released after 2015 can start with arm64, but the device's supported ABI is the deciding factor. The Universal build includes multiple architectures and can help if you can't identify your device's architecture or the arm64 package is incompatible. Universal does not mean support for every older Android version.
Can I connect right after installing the client?
The client does not provide a server. After installation, import a valid subscription link, share link, or compatible configuration, then select a server and set the proxy mode. Subscription URLs may contain credentials; don't share them publicly or paste them into an unfamiliar conversion service.
What should I save before updating the client?
Export your configuration using the client, and note your subscription groups, custom routes, DNS, and local listening settings. Quit the running client before updating. When switching interfaces or cores, don't assume every configuration field will carry over unchanged.
What if the download won't open or installation fails?
First, determine whether the problem is downloading or installing. For download failures, note the browser's message and try again later. For installation failures, check the OS version, processor architecture, available storage, and whether older processes have exited. Read any security warning carefully; don't disable system protections to bypass an unknown risk.
Can I switch directly between v2rayNG and v2flyNG?
Both are Android GUI clients, but v2rayNG uses the Xray core and v2flyNG uses the V2Fly core. Both may import common share links, but protocol, security-layer, and configuration support depends on each version. Before using configurations such as REALITY, confirm support in the target client and core.