CLIENT PACKAGES / PLATFORMS & ARCHITECTURES

V2Ray Client Downloads

Choose v2rayN for desktop, v2rayNG for Android, or v2flyNG if you need the V2Fly core. Select your operating system first, then check the CPU architecture and package format.

Open source
Free to use
Xray · V2Fly

Download v2rayN for Windows

x64 packages · Desktop / WPF

v2rayN

Recommended 7.24.1

Desktop edition

Download Desktop · x64

A newer cross-platform UI. A good place to start for a first install, with one desktop interface for managing subscriptions, servers and routing.

ZIP / x64 / Windows

Classic WPF edition

Download classic WPF · x64

The stable classic edition with the Windows WPF interface. Suited to users who know the original menu layout and want to keep their established desktop workflow.

ZIP / x64 / Windows

These downloads offer different interfaces, not different connection quality tiers. Connection results depend on server settings, core support and network routing. Back up your configuration before switching, then quit the old process to avoid conflicts over local listening ports.

Windows requirements and setup

Check	What to look for
Operating system	Use a Windows desktop edition that is still supported. Check the selected package's installation prompts for its minimum system requirements.
CPU architecture	Both downloads on this page are x64. Check your system type under Settings → System → About.
Package and runtime	The download is a ZIP file. Extract it before running the installer. If a required runtime is missing, follow the installer prompts; don't install components for a different architecture.
Permissions	Follow the client's prompts for normal startup and system proxy settings. TUN may require administrator privileges.

Extract the archive to a separate writable folder; don't launch the app from the archive preview. After installation, import a valid configuration and test it before enabling startup at sign-in. If another proxy app is running, first check which one controls the system proxy.

Download v2rayN for macOS

Choose a DMG based on the chip listed in About This Mac

v2rayN

7.24.1

Apple Silicon

Download for Apple Silicon · arm64

For devices showing an Apple M-series chip under “Chip.” Use the package built for your processor architecture; a different filename alone is no reason to choose the Intel package.

DMG / arm64 / macOS

Intel

Download for Intel · x64

For devices showing Intel under “Processor.” Don't rely on the device's appearance or purchase year; check the hardware details in the system before downloading.

DMG / x64 / macOS

Open the DMG and follow the installer window to move the app to Applications, then launch it from there. If macOS shows a security warning on first launch, verify the file source and app name, then follow the system's steps to allow that app.

macOS requirements and setup

Check	What to look for
Chip	Open About This Mac from the Apple menu to check whether your device uses Apple Silicon or Intel; these correspond to arm64 and x64.
System version	The package must support your macOS version. Check the compatibility prompt during installation for the minimum requirement.
Install location	Move the app to Applications before launching it. Avoid running it long-term from a mounted disk image.
Network permissions	System proxy or TUN may trigger a permission request. Confirm it comes from the client you're using, then grant only the required access.

Installing the app doesn't automatically route traffic through it. Check your server configuration first, then choose the system proxy or another routing method suited to your needs. If you use other network tools, note their proxy and DNS settings so you don't change several apps at once while troubleshooting.

Download Android clients

Recommended: v2rayNG · v2flyNG as an alternative with the V2Fly core

v2rayNG

Recommended Xray core 2.2.6

arm64

Download v2rayNG · arm64

For most mainstream phones released after 2015, arm64 is a good first choice. Confirm that the operating system supports 64-bit apps; the processor name alone isn't enough.

APK / arm64-v8a

Universal

Download v2rayNG · universal

Choose this if you're unsure of the app architecture. The universal package includes components for multiple architectures and is usually larger; it still has minimum system requirements.

APK / universal

v2rayNG uses the Xray core. After importing a connection, check the server address, port, protocol and transport options. The first time you connect, Android will ask for permission to establish a VPN connection. This allows the app to route traffic on your device; it does not provide server connection details.

v2flyNG

Alternative · V2Fly core 1.10.31

arm64

Download v2flyNG · arm64

For devices that support arm64 apps and need a V2Fly core configuration. Before installing, check that the required protocol and transport are supported by this client.

APK / arm64-v8a

Universal

Download v2flyNG · universal

For installations where the device architecture is unknown. This is the same client as the arm64 package; choose based on device compatibility, not server speed.

APK / universal

v2flyNG and v2rayNG aren't two themes for the same core. If you already use a V2Fly configuration, check protocol and field support before switching. After importing connection details, review DNS, routing and traffic interception settings. Don't overwrite the other client's entire configuration folder.

Android requirements and setup

Check	What to look for
System compatibility	Check the APK installer for the minimum Android version and supported app architectures.
Architecture	Choose arm64 for mainstream devices that support 64-bit apps; if unsure, try the universal package.
Install permissions	Grant install permission only to the browser or file manager opening this package. You can revoke it after installation.
Traffic routing	Confirm the VPN permission on first connection. Usually, only one VPN service should route traffic at a time.
Background operation	If the connection drops when the screen locks, check battery optimization and background restrictions, then adjust the relevant device settings.

If you see “App not installed,” read the full error first. An architecture mismatch, an outdated system, insufficient storage or a signing conflict with an existing installation can all cause failure. Don't uninstall an existing app right away; export your configuration and make sure the backup works before resolving an installation conflict.

Download v2rayN for Linux

Choose a package format for your distribution, then select x64 or arm64

v2rayN

7.24.1

Debian / Ubuntu

Download DEB · x64 For ARM devices: download DEB · arm64

Choose this format for desktop distributions that use DEB packages. In the filename, amd64 indicates the x64 architecture and also applies to compatible Intel processors.

Fedora and other RPM distributions

Download RPM · x64 For ARM devices: download RPM · arm64

Choose this format for desktop distributions that use RPM packages. Check dependencies and distribution compatibility with your package manager; the file extension alone doesn't guarantee it will work.

Open the package with your distribution's graphical software installer. Review the dependencies and proposed changes before confirming. Once v2rayN appears in the software menu, launch it from the desktop. If it won't start, check the package manager's compatibility details first instead of trying packages for unrelated architectures.

Linux requirements and setup

Check	What to look for
Desktop session	Requires a desktop environment that can run graphical apps. This is a desktop client, not a deployment package for headless servers.
Package format	Debian- and Ubuntu-based systems usually use DEB; Fedora and other RPM-based systems use RPM. Check the dependencies for the specific package.
CPU architecture	x64 corresponds to amd64 or x86_64; arm64 corresponds to arm64 or aarch64. Check your system's hardware information.
Permissions and dependencies	Install through the graphical package manager. TUN and system network settings may require additional permissions.

After installation, check that the GUI, configuration import and local listening work before adding the app to desktop startup. Whether apps use the system proxy depends on the desktop environment and each app. TUN requires separate checks for permissions, routing and conflicts with other network tools.

Install and configure in order

The package installs the client; connection settings, proxy mode and testing are separate steps.

install → import → select → verify

Check your target system. Confirm the operating system and CPU architecture in system settings, then choose the matching package. x64 and arm64 are architectures, not performance tiers; DEB and RPM are package formats, not connection modes. The wrong choice usually prevents installation or startup and can't be fixed by changing server settings.
Keep your existing settings. If you already use a client, export your servers, subscriptions, custom routes and DNS settings first. Note the local ports and traffic-routing mode. Backups may contain connection credentials, so store them somewhere you control. Don't post an entire configuration folder in a public discussion as a troubleshooting attachment.
Import a working connection. After installation, import a connection in the client using a subscription URL, a link from your clipboard or a supported configuration file. A subscription name is just a label; it doesn't replace the server address, port, authentication or transport settings. Check that the fields imported correctly.
Choose a mode and test it. Select a server, then enable the proxy method that fits your needs. The system proxy mainly affects apps that respect system proxy settings; TUN routes more traffic and requires additional permissions and routing checks. Verify the basic connection first, then add split tunneling, DNS and startup settings.

Once you've completed these steps, test the connection with the app you actually need and check the client's logs for error categories. Timeouts, authentication failures and DNS resolution errors require different troubleshooting. Don't reinstall after a single failed test or change the protocol, DNS, routing and proxy mode all at once; keep a baseline you can compare against.

Read the getting started guide View config.json fields

Client updates and core selection

Check client updates, connection settings and core compatibility separately; they are different issues.

Record a working configuration before updating

Updating the client usually doesn't require changing servers, but the interface, default options and configuration conversion may differ. Note your working servers, listening ports, routing mode and DNS settings. Quit the client before installing the update. Afterward, check that your subscriptions are still there, the right server is selected and the system proxy behaves as expected.

If you need to roll back, start with the backup exported before the update. Older versions may not recognize every setting written by newer ones; being able to open a configuration file doesn't guarantee full compatibility. Follow the same principle when moving between Desktop and WPF.

Choosing between Xray and V2Fly

The Project V ecosystem includes several core implementations. v2rayNG is based on Xray, while v2flyNG uses V2Fly. For desktop v2rayN, check the client interface and connection configuration to see which core is in use. The same protocol name doesn't guarantee identical support for extended transport options, TLS parameters or routing fields across all cores.

Choose a client based on the server configuration requirements, then check protocol and transport support. Don't copy all settings from one Android client over another. See the configuration field reference for field details, or the glossary for terminology.

Protocol and core terminology →

Download and installation FAQs

Check the package format, architecture and system prompts first; troubleshoot client settings afterward.

Desktop or classic WPF for Windows: which should you choose?

For a first install, start with Desktop, which uses a newer cross-platform interface. Choose the classic WPF edition if you prefer the familiar Windows interface or want to keep your existing workflow. Both require a valid connection configuration. Back up subscriptions, routing rules and settings before switching, and don't run both clients at once because they may compete for the same ports.

Android: arm64 or universal?

Most mainstream phones released after 2015 can start with arm64, but check which app architectures the device's operating system supports. Some devices have 64-bit processors but support only 32-bit apps. If you can't confirm the architecture, or the arm64 package reports an incompatibility, try the universal package. It does not guarantee compatibility with every older system.

Can you connect right after installing the client?

The client package does not include server connection details. You'll need a subscription URL you’re authorized to use or an individual connection configuration. Import it, select a server, choose a proxy mode and test connectivity. Subscription URLs may contain credentials, so don't share them in screenshots or public discussions.

How do you keep your settings when updating?

Use the current client’s export or backup feature to save subscriptions, servers and custom rules. Note your system proxy and TUN settings, then quit the client before updating. Don't assume configuration folders are interchangeable across interfaces, clients or cores. After updating, check the configuration and listening ports before restoring traffic routing.

What should you check if the package won't open?

Check the operating system, CPU architecture and package format, and make sure the download is complete. Windows downloads are ZIP files that must be extracted first; on macOS, choose the DMG for your chip; on Android, check app-install permissions and architecture compatibility; on Linux, review dependencies in the graphical package manager. Don't disable system-wide security just to open a package.

Can you use the same configuration with v2rayNG and v2flyNG?

They use different cores, Xray and V2Fly, so support for protocols, transports and extension fields may vary. You can re-import common connection details using each client's supported method, but don't assume every setting or raw JSON will transfer unchanged. Back up first, then check server parameters, TLS, transport, DNS and routing rules one by one.