Client downloads / platforms and architectures

V2Ray Client Downloads

Choose v2rayN for desktop and v2rayNG for Android. Confirm your operating system first, then choose the processor architecture and package format.

The client is free and open source. After installation, import a valid configuration and verify that the proxy is working.

Choose a package by platform

Downloads are listed on each client card. Switch platforms to see the relevant instructions. If you’re unsure about the architecture, check the system requirements below rather than trying multiple packages.

Windows client

v2rayN

x64 · 7.24.1

Recommended

Download Desktop · x64 Download classic WPF · x64

Desktop uses a newer cross-platform interface. It’s a good choice for a first install and offers a consistent experience across desktop systems. WPF is the classic, stable version, with a familiar Windows interface and layout. They’re not separate proxy services; choose based on your interface preference and what works best on your system.

Both downloads are ZIP archives. Extract the files fully before running the installer; don’t launch it from the archive preview. Before switching versions, back up your subscription groups and custom settings, then quit the existing client to avoid conflicts with local ports and system proxy settings.

System requirements and first run

Item	What to check
System architecture	Both packages on this page are x64. Check your system type under Settings > System > About first.
Runtime	Follow the startup prompt for your chosen version. Install any missing runtime components as indicated.
Installation folder	Extract to a writable location and keep the files together; don’t move only the main program.
Permissions	The standard system proxy and Tun have different permission requirements. Start by testing with the system proxy.

If no window appears after you double-click, check the notification area to see whether the client is already running. If a port is in use, quit other proxy apps and try again. A missing window, a missing runtime, and a server timeout are different issues—check them separately.

Continue to the first-time setup guide →

macOS client

v2rayN

Desktop client · 7.24.1

Download Apple Silicon · arm64 Download Intel · x64

Open the Apple menu and select About This Mac. Check the Chip or Processor entry: choose Apple Silicon for an Apple M-series chip, or x64 for Intel. Don’t infer the architecture from the device’s appearance or screen size; different generations in the same product line may use different processors.

Open the DMG and copy the app to Applications, then launch it from there. If a security alert appears on first launch, verify the download source and read the system prompt, then use the Privacy & Security settings to proceed. You don’t need to disable macOS security features entirely to run the client.

System requirements and installation location

Item	What to check
Apple Silicon	Choose the arm64 DMG for an M-series chip.
Intel	Choose the x64 DMG for an Intel processor.
macOS compatibility	Check the current package requirements and any system prompts for the minimum macOS version.
Where to run the app	Copy the app to Applications before launching it; don’t run it long-term from a mounted disk image.

Opening the app successfully only confirms that installation is complete. After importing a configuration, check that the system proxy is enabled. Some apps don’t use the system proxy and need separate configuration. If a connection fails, check which apps are covered by the proxy before considering Tun. Change one setting at a time.

Check permissions and troubleshoot proxy issues →

Android client

v2rayNG

Xray core · 2.2.6

Recommended

Download v2rayNG · arm64 Download v2rayNG · Universal

For a first Android install, v2rayNG is the recommended choice. Most mainstream phones released since 2015 support arm64, but a device’s system architecture may not match its processor’s capabilities. Check what your device supports. If you’re unsure, choose the universal build, which includes files for multiple architectures and is usually larger.

After installing the APK, import an existing configuration and select a server. The first time you connect, Android will ask to set up a VPN connection. Approve the request so the client can route traffic from your device. To proxy only selected apps, check the per-app proxy list rather than switching package versions to change which traffic is routed.

v2flyNG

V2Fly core · 1.10.31

Alternative

Download v2flyNG · arm64 Download v2flyNG · Universal

v2flyNG is an alternative for configurations that require the V2Fly core. Despite the similar names, it doesn’t have the same core features or configuration support as v2rayNG. Before installing, check that the protocols and transport settings in your subscription are supported. Differences between clients don’t necessarily mean the installation failed.

Choose an architecture using the same guidance above: use arm64 if your device supports it, or the universal build if you’re unsure. You can keep configurations in both clients, but enable only one client’s VPN service at a time while testing. Disconnect the first client before starting the other so you can tell which one is routing traffic.

System requirements and permissions

Item	What to check
Processor architecture	arm64 is for devices that support 64-bit apps. Choose the universal package if you’re unsure which architecture your device uses.
Android version	Check the APK’s minimum Android version and any installer prompts.
Installation permission	Allow the browser or file manager you use to open the APK to install unknown apps.
Connection permission	Approve the VPN request on first connection. If the connection drops, check background battery restrictions and other VPN apps.

The version shown on the card and the version in the filename come from separate manifest fields and may differ. Treat them as separate values; don’t change the download URL based on them. Updates are also subject to signature and version downgrade restrictions. If Android refuses an update, keep your settings and read the specific error message.

Linux client

v2rayN

Desktop client · 7.24.1

Download deb · x64 Download rpm · x64

arm64 · deb arm64 · rpm

First identify your distribution’s package system, then choose the processor architecture. Debian and Ubuntu typically use deb packages; distributions using RPM package management use rpm. A matching package format doesn’t guarantee compatibility with every release, so check the software installer’s dependency requirements.

Choose x64 for a standard 64-bit Intel or AMD computer, or arm64 for a 64-bit ARM device using the link below. In filenames, amd64 and x86_64 refer to x64; aarch64 refers to arm64. Use your system’s graphical software installer where possible, so dependency errors and conflicts are shown clearly.

System requirements and package formats

Item	What to check
Desktop environment	These downloads are graphical clients and require an available desktop session.
deb	For systems that use Debian packages and meet the package’s dependency requirements.
rpm	For systems that use RPM packages; check your distribution and dependency versions.
Architecture and permissions	Match the package architecture to your system. Installation and Tun may require separate permissions.

If the installer reports unmet dependencies, don’t force the installation by ignoring them. Check your distribution version and package format first. After installation, system proxy settings may work differently across desktop environments. Browser access alone doesn’t confirm that terminal apps are using the proxy.

Check whether the local proxy is working →

Linux penguin graphic: Font Awesome Tux, licensed under CC BY 4.0.

Test the connection after installation

Downloading, launching, and connecting are three separate steps. Check the current step before changing later settings to preserve useful clues when troubleshooting.

Import an existing configuration

The client doesn’t include a usable server. On desktop, add a subscription address to a subscription group and update it. On Android, import through the subscription settings or a share-link option. A subscription URL and an individual share link are different types of data; using the wrong import option may leave the server list empty.

After updating a subscription, confirm that servers appear in the list, then select one. If the update fails, check the request message and response before changing routing or DNS. Subscription URLs may contain access credentials, so hide the full address in screenshots and support requests.

Choose which traffic to proxy

On desktop, check the system proxy mode first, then make sure the apps you want to use can read system proxy settings. Tun changes which traffic is routed and requires additional permissions and routing configuration; it doesn’t need to be enabled right after installation. Start with a simple connection test and change as few settings as possible.

On Android, approve the VPN request and check that the target app is included in the per-app proxy list. If the connection drops only when the screen is locked, check battery optimization and background activity restrictions. Keep only one VPN service active to avoid confusion over which app is routing traffic.

Verify that apps can connect

Run a real connection speed test with the selected server, then test access in the app you want to use. TCPing only checks whether a port is reachable; it doesn’t test the full proxy connection. If a test fails, note the error in the logs and distinguish between a local listener failure, a remote timeout, and a DNS resolution issue.

If a browser works but other apps don’t, check those apps’ proxy settings first. If no apps work, check the selected server and your network. Change one setting at a time and record the results; this makes it easier to find the cause than changing several configurations at once.

Read the full Getting Started guide → Find troubleshooting steps by symptom → Look up protocol and architecture terms →

Download and installation FAQs

Check the package type and system prompts first. Installation issues usually occur on your device, so don’t treat them as server connection problems.

For a first Windows install, should you choose Desktop or WPF?

For a first install, consider Desktop, which uses a newer cross-platform interface. WPF is the classic, stable version for users who prefer its familiar Windows layout. Both are v2rayN, though menus may differ. Back up your settings before switching, and don’t enable system proxy in both clients at once.

How do you know whether to download arm64 or x64?

Check the processor architecture reported by your system rather than relying on the device’s age. On macOS, check About This Mac: choose arm64 for Apple Silicon and x64 for Intel. On Linux, match the package to your system architecture: amd64 or x86_64 for x64, and arm64 or aarch64 for ARM. Most Android phones support arm64; choose the universal build if you’re unsure about compatibility.

Why can’t you run a downloaded ZIP as an installer?

A ZIP is a compressed archive. Extract it fully to a writable folder, then open the extracted files and run the installer. Launching a program from the archive preview can prevent it from finding other files in the same folder. Quit the client before upgrading.

What should you do if Android says the app can’t be installed or wasn’t installed?

Check that the package matches your device’s architecture and that you have enough storage. Allow the browser or file manager you’re using to install unknown apps. An existing installation may not accept an update if the signatures differ or the new version is older. Back up your settings and follow the system’s error message; avoid repeated uninstall attempts.

Why can’t you connect after installing the client?

Installing the client doesn’t provide a server configuration. Import a valid subscription or share link, update the group, select a server, and choose a proxy mode. On desktop, check the system proxy; on Android, approve the VPN request. Then test the connection and verify access in your apps.

What should you keep before updating the client?

Note your subscription groups, custom routes, local listening ports, and proxy mode. Use the client’s backup or export feature. Settings may contain subscription URLs and authentication details, so store backups securely. After updating, confirm the settings loaded and test the connection; don’t overwrite your only backup.