CLIENT PACKAGE / Choose a platform

V2Ray Client Downloads

For desktop, choose v2rayN; for Android, start with v2rayNG. Check your operating system and processor architecture before selecting a package.

Free, open-source clients Packages for different architectures Import subscriptions separately

How to choose

Check your operating system
Check your processor architecture
Download and import your configuration

New to setup? Read the configuration guide →

01 / Package guide

Choose a client by platform

Download links are grouped by operating system. Switching platforms keeps the matching page anchor in the address bar.

Windows packages

For x64 devices. Start with Desktop for a first install; choose WPF if you prefer the classic workflow.

v2rayN

Windows · x64 · 7.24.1

Recommended

Desktop

A next-generation cross-platform UI, ideal for first-time installs and a consistent desktop experience.

Download Desktop · x64 ZIP archive · Extract before running

WPF Classic

The classic Windows interface for users familiar with its menus and workflow.

Download WPF · x64 ZIP archive · Choose this or Desktop

The main difference between these versions is their UI technology and workflow—not connection speed. Node quality, remote server load, routing, and your local network all affect performance. Choose one version, import your settings, and test the connection before switching; this makes it easier to distinguish interface differences from configuration issues.

After saving the file, extract the entire archive to a directory you can write to, then run the installer or launcher inside it. Don’t launch the app from the archive preview. If you’re told a runtime is missing, install the specific component named in the prompt rather than choosing an older runtime based on the filename alone.

If you already have a configuration, export a backup and quit the old client from the system tray before installing or migrating. Don’t run Desktop and WPF at the same time: even with separate windows, they may compete for local listening ports or repeatedly change system proxy settings. After migrating, check your subscription groups and routing, then test an actual connection.

Windows system and installation requirements

What to check	Before installing
Processor architecture	Both downloads on this page are x64. Check Settings → System → About for your system type; these packages won’t run in a 32-bit environment.
Windows version and runtime	Use a supported version of Windows. Check the installer prompts for the specific minimum OS version and runtime requirements of the build you download.
Install location and permissions	Choose a writable directory with enough room to extract the files. Start with standard permissions; grant elevated access only when a feature explicitly requires it.
Before connecting	Keep your existing subscription or node configuration. For your first test, use the system proxy; test TUN and other features separately after the basic connection works.

macOS packages

Open Apple menu → About This Mac to check your chip or processor, then choose the matching DMG.

v2rayN

macOS · DMG · 7.24.1

Desktop client

Apple Silicon

If About This Mac shows an Apple M-series chip, choose the native arm64 package.

Download for Apple Silicon · arm64 DMG disk image

Intel

If your processor is listed as Intel, choose the x64 package. Don’t guess based on when the device was purchased.

Download for Intel · x64 DMG disk image

Open the DMG after downloading and follow its instructions to move the app to Applications. Launch it from there. Don’t keep running the app directly from the mounted image: it may stop working if you eject the image or clear your downloads, and it can be hard to tell which copy you’re using.

Processor architecture and macOS version are separate requirements. Choosing the right arm64 or x64 package doesn’t guarantee your OS meets the build’s requirements. If you see an error or compatibility warning, note the full message, macOS version, and chip model. For a security warning, verify the file’s source and read the prompt before using the system-provided option to proceed; don’t disable security features altogether.

On first launch, import a known-working node and check the system proxy status. If a browser connects but another app doesn’t, first check whether that app uses the system proxy; don’t immediately switch installers. Test TUN separately from the system proxy because it uses different permissions and network routing, which can otherwise make troubleshooting confusing.

macOS system and installation requirements

What to check	Before installing
Chip architecture	Apple M-series chips use arm64; Intel processors use x64. Choose the native build for your hardware.
macOS version	Check the full version in About This Mac. Minimum requirements vary by build; follow the compatibility message from the app or system.
Install location	Make sure you can write to the Applications folder. After installation, launch the app from Applications rather than running it from the DMG.
System permissions	Grant only the permissions required for the features you use. If network routing requests additional access, read the prompt before deciding whether to enable it.

Android packages

Start with v2rayNG. Consider v2flyNG if you need a configuration that uses the v2fly core. Each client manages its own settings.

v2rayNG

Android · Xray · 2.2.6

Recommended

arm64

For most mainstream phones released after 2015, arm64 is a good first choice. Check your device’s supported app ABIs before downloading.

Download v2rayNG · arm64 APK package

Universal

A fallback when you’re unsure of your device architecture. Includes multiple architectures and usually takes up more storage.

Download v2rayNG · Universal APK package

v2rayNG is suited to users who need to import subscriptions, switch nodes, and route traffic through Android’s VPN service. After installing, open subscription settings, add a group, enter the full subscription URL, and update it. Copying a link to the clipboard alone won’t create a subscription group, and a single-node share link isn’t the same as an automatically updated subscription URL.

The first time you tap Connect, Android asks to set up a VPN connection. This system prompt lets the client route network traffic; approve it only after confirming the action. If another VPN service is running, stop it before testing. Also check per-app proxy settings so the app you’re testing hasn’t been excluded.

The version shown on the card and the installer filename may temporarily differ while the manifest updates. Check the installed version on the About page. Don’t edit the version number in the download URL or assume a different filename means the package has the wrong architecture.

v2flyNG

Android · v2fly · 1.10.31

Alternative client

arm64

For devices that support arm64 apps; choose this when you need a compatible core configuration.

Download v2flyNG · arm64 APK package

Universal

For devices with an unknown architecture. Check system compatibility before installing.

Download v2flyNG · Universal APK package

v2flyNG uses the v2fly core and is an alternative when your configuration requires it. Its name is similar to v2rayNG, but it’s a separate app, not a different skin. Check protocol, transport, and parameter support for each client. Successful import in one client doesn’t guarantee the other will recognize every field.

To migrate from v2rayNG, add a subscription you’re authorized to use to the new client, check the node count and settings, then test the connection. A full backup from one app may not restore directly in another. Keep the original configuration until the new client works, and run only one VPN service while testing.

Android system and installation requirements

What to check	Before installing
App architecture	Choose arm64 first. A 64-bit processor doesn’t guarantee the OS supports 64-bit apps; if you’re unsure, try the universal version and check whether it installs.
macOS version	Check your Android version in system settings. The APK installer prompt shows the minimum requirement; the universal package won’t work around OS requirements.
Installation permissions	Android may ask you to allow app installs from the browser or file manager you’re using. Grant permission only to that source and revoke it afterward if you prefer.
Upgrade conflicts	If you encounter a signature or app conflict, back up your settings and check where the existing app came from. Don’t uninstall it before making a backup.
Background operation	If the connection drops when the screen locks, check battery optimization and background restrictions. Verify the connection with the app in the foreground before changing multiple system settings.

Linux packages

Check your distribution’s package manager, then confirm your processor architecture. deb and rpm are different package formats, not interchangeable file extensions.

v2rayN

Linux · deb / rpm · 7.24.1

Desktop client

deb · x64

For desktop distributions that use deb packages, such as Debian and Ubuntu.

Download deb · x64 For arm64 devices: Download deb →

rpm · x64

For desktop distributions that use rpm packages. Check dependency requirements before installing.

Download rpm · x64 For arm64 devices: Download rpm →

Check your architecture in the system About page or hardware information: amd64 and x86_64 usually correspond to x64 here, while aarch64 usually corresponds to arm64. Package managers also check distribution dependencies and package metadata, so matching the file extension and architecture doesn’t guarantee a build will install on every distribution.

Open the downloaded package with your distribution’s graphical installer. Review the dependencies and change summary before confirming installation. If dependencies are missing, note the specific packages and your OS version; don’t bypass the error by forcing installation without dependencies. The GUI client requires a desktop session and isn’t a direct replacement for software on a command-line-only server.

Whether the system proxy works after installation depends on your desktop environment and whether the target app supports proxies. If an app doesn’t follow the system proxy, check its own network settings. If you later enable TUN, follow the permission prompts for that feature. Don’t run the entire GUI client with elevated privileges just to troubleshoot one app.

Linux system and installation requirements

What to check	Before installing
Package format	Choose deb or rpm for your distribution. Don’t try to fix incompatibility by changing the file extension or converting formats at random.
Architecture	x64 corresponds to amd64 / x86_64; arm64 corresponds to aarch64. Both package formats are available for these architectures.
Desktop and dependencies	A graphical desktop environment is required. System libraries, desktop components, and minimum versions depend on the installer and build requirements.
Installation permissions	Approve installation when prompted by the system installer. After installation, run the app from a standard user desktop session.

02 / First launch and migration

After installation: validation steps

Verify the configuration before routing more traffic

Downloading a client and getting a subscription are separate steps. After installation, import an existing subscription URL or single-node configuration, choose a node as your current server, and connect. A successful subscription update only means the configuration was retrieved; it doesn’t prove every node can connect. Check actual requests and core logs, not just whether nodes appear in the list.

On desktop, check the system proxy first; on Android, confirm the VPN service is active. After the basic connection works, configure routing, per-app proxy, or TUN one at a time. Record what changes when you adjust each setting to help distinguish installation, configuration, and network path issues.

Keep a recoverable configuration before upgrading

Save a client-generated configuration backup and separately record custom routes, listening ports, and essential DNS settings. Backups may contain subscription credentials and node connection details, so keep them in a private folder instead of uploading them to a public sharing service. Remove subscription URLs, server identifiers, and identity parameters before sharing logs.

After upgrading, check your subscription groups, current node, and outbound rules, then test access to a specific destination. If something goes wrong, keep the first useful error and its timestamp, then follow the troubleshooting guide to identify the issue. For import steps and your first connection, see the configuration guide.

03 / Download FAQs

Installation and upgrade questions

Which Windows version should you choose: Desktop or WPF?

For a first install, consider Desktop, which uses a next-generation cross-platform UI. Choose the classic WPF version if you prefer its familiar interface and workflow. Install one version at a time, export your settings before switching, and don’t run both at once or let them compete for the same listening ports.

What’s the difference between the Android arm64 and universal versions?

Most mainstream phones released after 2015 can use arm64, but check which app ABIs your device supports. The universal version includes multiple architectures and is a safer choice when you’re unsure. If parsing or installation fails, check system requirements, signature conflicts, and available storage.

Does the client download include server nodes?

The installer contains the client app, not ready-to-use nodes or a subscription service. After installation, import a subscription or node configuration you’re authorized to use, then choose a server, configure routing, and test the connection. Treat subscription URLs as sensitive information and don’t share them publicly.

The downloaded filename doesn’t match the version shown on the card. How can I tell which version it is?

The displayed version and download URL come from different manifest fields, so they may briefly disagree during an update. Don’t edit the filename to try to download another version. Check the selected platform and architecture, then confirm the installed version on the client’s About page before deciding whether to migrate your existing configuration.

What should I back up before upgrading the client?

Use the client’s backup or export feature to save subscription groups, custom nodes, routing rules, and essential settings. Store the backup in a private folder. Close the client before upgrading, then test a single node on the first launch. Don’t overwrite your original backup right away.

The client installed successfully but won’t connect. Should I download it again?

First check whether the core starts, the node configuration is complete, local ports are free, and the system proxy or Android VPN service is enabled. A successful installation doesn’t mean your subscription or remote service is available. Keep the first error log with sensitive details removed and follow the troubleshooting guide; this is usually more effective than reinstalling repeatedly.