Client downloads

V2Ray Downloads
Choose a client for your system

Use v2rayN on desktop systems and v2rayNG on Android. Check your processor architecture before downloading the matching installer.

Already have a subscription? After installation, follow the subscription import steps. If you're new, first establish a basic proxy connection, then configure routing and TUN.

Windows：v2rayN

One client, two interfaces. All installers below are for x64 systems.

View installation guide →

v2rayN

Recommended 7.24.1

Desktop edition

Next-generation cross-platform UI · x64

Download v2rayN Desktop

Desktop is a good place to start if you're installing for the first time. Its newer cross-platform interface offers a similar experience across desktop systems. The download is a ZIP archive: extract it completely before running the installer. Don't launch it from the archive preview.

Classic WPF edition

Classic, stable interface · x64

Download v2rayN WPF

Choose the WPF edition if you're used to the traditional Windows interface. It retains the classic layout, which differs from Desktop. Switching editions doesn't change your subscription service. Back up your settings before migrating, verify the import, and only then remove the original installation.

Windows installation requirements

Check	Requirements and steps
Processor architecture	Both installers on this page are x64. Check System type under System Information in Windows Settings; don't assume x64 in the filename means the package works on every architecture.
OS and runtime	Use a Windows version supported by the current client. Follow the installer prompts for minimum version and runtime requirements, and install any missing dependencies as instructed.
Files and permissions	Extract the archive completely to a writable folder. Standard system proxy configuration usually doesn't require running as administrator. TUN may require elevated permissions.

Check the system proxy after installation

After launching v2rayN, import your subscription, update the server list, and select an active server. Then choose “Set system proxy automatically.” This mainly affects apps that follow the system proxy; it doesn't route all network traffic. If your browser connects but other apps don't, check their individual proxy settings before downloading a different installer.

To upgrade, exit the old client before installing the new version. Avoid running Desktop and WPF as active clients at the same time, as they may overwrite each other's system proxy settings. If the app fails to start, save the error message, check the runtime and extraction folder, and then decide whether to reinstall. Repeatedly replacing program files rarely fixes configuration or permission issues.

macOS：v2rayN

Open About This Mac and choose the DMG installer that matches your chip.

View installation guide →

v2rayN

Desktop client 7.24.1

Apple Silicon

Apple M-series chip · arm64

Download v2rayN · Apple Silicon

Choose this option if About This Mac shows an Apple M-series chip. The arm64 package matches that architecture; you don't need to choose the Intel package just to reuse a file from another device. Check the chip again when you switch computers rather than relying on appearance or model name.

Intel

Intel processor · x64

Download v2rayN · Intel

Choose this option if About This Mac shows an Intel processor. After downloading, open the DMG and follow the prompts to move the app into your Applications folder. Copy it before launching for the first time; running it from the mounted disk image can complicate updates and file management.

macOS installation requirements

Check	Requirements and steps
Chip type	Choose arm64 for Apple M-series chips and x64 for Intel processors. Check About This Mac in the Apple menu.
OS version	Use a macOS version supported by the current client. If a startup prompt says your system version isn't supported, check its requirements; switching architectures is not a substitute for upgrading macOS.
Installation and permissions	Copy the app before launching it. System proxy, network extension, or TUN features may request permissions; grant only those required for the features you use.

Tell installation blocks from connection issues

If a system alert mentions compatibility, source, or permissions, read the full message and check the relevant setting in System Settings. Don't disable system protections as a general installation step, and don't run terminal commands from untrusted sources. If the app opens but can't connect, troubleshoot the subscription, server, and proxy settings instead of reinstalling it.

Before enabling the system proxy, make sure no other client is changing the network proxy settings. Consider clearing the system proxy before exiting v2rayN, especially before uninstalling or migrating settings. If your browser still has connection problems after exit, check for leftover proxy settings in Network Settings and restore normal connectivity. This helps separate installation and permission issues from connection problems.

Android: v2rayNG recommended

Install the recommended client first. Consider the alternative only if you have a specific need for its core.

View subscription import steps →

v2rayNG

Recommended Xray core 2.2.6

arm64 package

Recommended for most devices

Download v2rayNG · arm64

Most phones released since 2015 will use arm64, but check which app architectures the device's OS supports. Processor support and OS support don't always match. If the installer reports an architecture mismatch, check your device details and then try the universal version.

Universal package

For unknown architectures

Download v2rayNG · Universal

The universal version supports a wider range of app architectures; it doesn't add proxy features. Like the arm64 package, it must meet the Android system requirements. Switching to universal may not help if your Android version, installation signature, or available storage doesn't meet the requirements.

v2flyNG

Alternative V2Fly core 1.10.31

arm64 package

For configurations that specifically require V2Fly

Download v2flyNG · arm64

Choose this client when your configuration or documentation specifically requires the V2Fly core. Different cores support different protocols and extensions, so you can't determine compatibility from the appearance of a shared link alone. Check the configuration requirements before switching clients.

Universal package

Alternative architecture

Download v2flyNG · Universal

If you need v2flyNG but can't confirm your device's architecture, use the universal package. Keep your existing subscription and custom settings before switching clients. Don't assume settings transfer one-to-one, and don't let two VPN connections compete for the system network interface.

Android installation requirements

Check	Requirements and steps
App architecture	Check for arm64 support first; choose universal if you're unsure. The universal package is still limited by the Android version and client compatibility.
Installation permission	Your system may ask you to allow the current browser or file manager to install apps. After installation, you can revoke permission for that source if you no longer need it.
Connection permission	Read and approve the system VPN prompt when you first start a proxy connection. Other VPN apps may use the same connection slot, so disconnect them before testing.

Keep your settings before resolving installation conflicts

If you see “App not installed,” check available storage, Android version, and app architecture first. Then check whether an existing app with the same name has a different signing key. Don't uninstall the current app as your first step; doing so may delete subscription groups and local rules. If you need to change the installation source, export essential settings first and store any files containing subscription credentials securely.

The version label and installer filename come from separate release-list fields and may be updated at different times. Don't infer the page label from the filename or assume a mismatch means installation failed. After installing, check the actual build version on the client's About page. To verify connectivity, test a real connection and make sure the apps that need a proxy are included in the client's app routing rules.

Linux：v2rayN

Check your distribution's package manager first, then confirm the processor architecture.

View client and core details →

v2rayN

Desktop GUI client 7.24.1

deb package

Debian / Ubuntu family · x64

Download v2rayN · deb

For arm64 devices: Download arm64 deb

Start here if your desktop distribution uses the deb package format. The amd64 filename corresponds to x64 and isn't limited to a specific processor brand. Open the package with a graphical software installer, review dependency and compatibility prompts, and then confirm the installation.

rpm package

RPM-based distributions · x64

Download v2rayN · rpm

For arm64 devices: Download arm64 rpm

Choose this package if your system uses RPM. The same package format doesn't guarantee compatibility with every distribution release, so check your environment and dependencies. In filenames, x86_64 corresponds to x64 and aarch64 to arm64. Don't try to convert a package by changing its extension.

Linux installation requirements

Check	Requirements and steps
Desktop environment	This page provides a graphical client. You'll need a graphical desktop and the required runtime dependencies. These packages aren't instructions for deploying a background service.
Package format and dependencies	Choose deb or rpm for your distribution and use a software installer to check dependencies. Resolve missing dependencies or environment incompatibilities before proceeding.
Processor architecture	Choose the main button for a standard x64 PC; arm64 users should use the smaller link in the card. The architecture must match the system's user space.
Network permissions	Whether apps follow the system proxy depends on the desktop environment and each app. TUN may need additional permissions; verify a standard proxy connection first.

Verify the desktop proxy first

After installation, launch v2rayN from the app menu, import your subscription, and select an active server. Browsers, command-line tools, and other apps on a Linux desktop may not share the same proxy settings. A running client doesn't mean every app is using the proxy. First test with an app that follows the system proxy, then check other apps one by one.

If the software installer reports unsatisfied dependencies, note the package names and required versions; don't force installation while ignoring dependencies. Before upgrading, record where the app stores its settings and back up custom routes and DNS settings. Grant only the permissions needed for the feature rather than running your everyday graphical session with elevated privileges.

Install and upgradeBack up settings, then test the connection

The installer deploys the client only. Configure your subscription, active server, and proxy mode in the app.

First-time setup: follow these steps

First, check that the download's architecture matches your device, then extract or install it. Launch the client, add a subscription group, enter a subscription URL you're authorized to use, and save it. Update the subscription, choose a fully configured server as the active server, and enable the appropriate system proxy or VPN connection.

Updating a subscription retrieves server configurations; it doesn't select an active server for you. For your first test, use the default or basic routing settings and leave advanced DNS and TUN options unchanged. Establish a working connection first, then change one setting at a time to pinpoint any issues.

Continue to subscription import →

Upgrade in place: back up and exit first

Back up subscription groups, custom routes, DNS settings, and manually added server details. Backups may contain credentials, so don't upload them publicly or include them in unredacted support screenshots. Exit the running client before updating; don't copy the entire settings folder while the app is still writing to it.

After upgrading, check that your subscriptions are intact, the correct server is active, and the proxy mode is as expected. Remove the old folder only after confirming that your browser and commonly used apps connect normally. When migrating between interfaces or clients, don't overwrite settings files in an unknown format; use an import method supported by the client.

View the complete maintenance guide →

Choosing an installerDownload FAQs

Check the architecture and package format before troubleshooting installation or connection issues.

Which Windows edition should I choose: Desktop or WPF?

If you're new to v2rayN, start with Desktop, which uses a newer cross-platform interface. If you prefer the classic interface, choose the stable WPF edition. Both are v2rayN. Back up your settings before switching, and don't let both clients modify the system proxy at the same time.

Should I download the arm64 or universal Android version?

Most phones released since 2015 will use arm64, but check which app architectures your system supports. If you can't confirm the architecture or the arm64 package won't install, try the universal version. It doesn't add features and must still meet the client's system requirements.

Does the client download include a subscription?

The installer contains the client, not a ready-to-use subscription. You'll need a subscription URL or server configuration that you're authorized to use. Import it, update the subscription, select an active server, and set the proxy mode.

What should I back up before updating the installer?

Exit the client first. Back up subscription groups, custom routing, DNS, and any other settings you've changed manually. Backups may contain subscription credentials, so store them securely. Keep a copy of the original settings and remove old files only after confirming the new version connects successfully.

Why might the Android version label differ from the installer filename?

The release list's version label and installer path are separate fields and may be updated at different times. The page uses the label and download path as listed rather than deriving a version from the filename. After installation, check the actual build version in the client's About page.

Why can't I connect after installing successfully?

First check that the subscription updated and an active server is selected. Then confirm that the system proxy or Android VPN permission is enabled. Check the logs for connection errors, then troubleshoot the server settings, system time, DNS, and routing in that order. Avoid changing several settings at once.

Follow the guide to verify your proxy →

V2Ray DownloadsChoose a client for your system

Windows：v2rayN

v2rayN

Desktop edition

Classic WPF edition

Windows installation requirements

Check the system proxy after installation

macOS：v2rayN

v2rayN

Apple Silicon

Intel

macOS installation requirements

Tell installation blocks from connection issues

Android: v2rayNG recommended

v2rayNG

arm64 package

Universal package

v2flyNG

arm64 package

Universal package

Android installation requirements

Keep your settings before resolving installation conflicts

Linux：v2rayN

v2rayN

deb package

rpm package

Linux installation requirements

Verify the desktop proxy first

Install and upgradeBack up settings, then test the connection

First-time setup: follow these steps

Upgrade in place: back up and exit first

Choosing an installerDownload FAQs

V2Ray Downloads
Choose a client for your system