GUI clients · Choose a package by OS

V2Ray Client Downloads

For desktop, choose v2rayN; for Android, start with v2rayNG. Check your OS and processor architecture before downloading the right package.

Free forever Open source Compare the three clients →

Windows downloads

This page offers x64 installers. Check your system type under “Settings → System → About.”

v2rayN

Recommended 7.24.1

Desktop uses a newer cross-platform UI. The classic WPF edition retains the familiar Windows interface and is a stable choice if you want to keep your current workflow. New users can start with Desktop; those familiar with WPF can stick with the classic edition.

Desktop · x64

Download Desktop

Newer cross-platform interface. Extract the ZIP archive in full, then run the installer inside.

Classic WPF · x64

Download WPF

Classic Windows interface. Keeps your existing workflow; quit any running instance before installing.

Extract, install, and launch

Extract the archive to a writable folder and keep its directory structure intact. Don’t run the app from the archive preview. If the installer reports a missing runtime, follow its instructions; required dependencies vary by package. Standard system proxy use usually doesn’t require administrator access. If you plan to enable TUN, follow the client’s prompts for the required permissions.

On first launch, import your subscription and refresh the server list. Select a working configuration, then set up routing and the system proxy. Avoid adding TUN or custom DNS settings for now. Test the basic connection first to help distinguish installation issues from configuration problems.

System requirements and installation checks

Check	Requirements for this download	How to check
Processor architecture	64-bit x64	Check “System type” in System Information; don’t infer it from your computer’s brand.
OS and runtime	Use a supported version of Windows. Check the installer for the exact minimum version and dependencies.	Install Windows updates first. If a dependency warning appears, note the full message.
Files and permissions	Writable install folder; TUN may require additional permissions.	Extract all files. Use the standard system proxy for your first test.

A successful installation doesn’t mean the server is ready to use. An expired subscription link, outdated configuration, or incorrect routing needs to be troubleshot separately during setup. Continue with the v2rayN installation and subscription import guide.

macOS downloads

Check your chip under “About This Mac” in the Apple menu, then choose Apple Silicon or Intel.

v2rayN

7.24.1

On macOS, v2rayN uses its cross-platform desktop interface. The two DMG files are for different processors, so you only need one. Choose arm64 for Apple M-series chips and x64 for an Intel processor.

Apple Silicon · arm64

Download for Apple Silicon

For Apple M-series chips. Choose the build that matches your processor architecture.

Intel · x64

Download for Intel

For Intel-based Macs. Don’t guess the architecture based on purchase date or appearance.

Install location and security prompts

Open the DMG and drag the app to Applications, then launch it from there. Don’t keep running it from the disk image; that can complicate updates, saved paths, and permissions. If macOS says the developer can’t be verified, first confirm the app’s source and download. Then check “System Settings → Privacy & Security” for the option to handle this specific block.

Don’t disable system-wide security just to launch the app once. If it reports a damaged file, incompatible architecture, or outdated OS, check the specific message rather than treating every launch failure as a permissions issue. Network and TUN permissions depend on what your system and client actually request; grant only the access needed for the feature you’re using.

System requirements and chip check

Check	How to choose	Installation notes
Apple Silicon	“About This Mac” shows an Apple M-series chip.	Download the arm64 DMG, move it to Applications, then launch it.
Intel	“About This Mac” shows an Intel processor.	Download the x64 DMG. Don’t use a build for another architecture.
OS and permissions	Check the app’s launch prompt and release requirements for the minimum macOS version.	Check for blocks under Privacy & Security and grant network access if needed.

When migrating from another desktop OS, export your subscriptions and routing settings first. Then check local paths, listening ports, and proxy mode; don’t copy OS-specific paths as-is. If macOS blocks the app at launch, see how to allow macOS permissions and grant network access.

Android downloads

Start with v2rayNG. Consider v2flyNG if you need the v2fly kernel ecosystem.

v2rayNG

Recommended 2.2.6

v2rayNG uses the Xray core and routes device traffic through Android’s VpnService. For VLESS, REALITY, or other configurations, check that the client supports the required fields; a protocol name alone doesn’t guarantee compatibility.

arm64 · Recommended

Download v2rayNG for arm64

Most mainstream phones released after 2015 can use this build. Confirm that your device supports 64-bit apps.

Universal · Alternative architecture

Download v2rayNG Universal

Choose this if you’re unsure which app architecture your device supports. The Universal package does not bypass minimum OS requirements.

The version shown on the page and platform file paths come from separate parts of the download manifest, so they may temporarily differ. Check the client’s About page after installation; don’t edit the file URL yourself.

v2flyNG

Alternative · v2fly core 1.10.31

v2flyNG is built for the v2fly kernel ecosystem. Consider it if your existing configuration specifically depends on this core. Features can differ between cores, so check the transport and any extra parameters before importing.

arm64 · Recommended architecture

Download v2flyNG for arm64

For devices that support arm64 apps. Back up your subscriptions and settings before switching clients.

Universal · Alternative architecture

Download v2flyNG Universal

For devices that need another supported architecture. Keep a copy of your current configuration before installing.

System requirements and installation permissions

Check	Requirement or selection guide	What to do
App architecture	Your device’s OS must support the arm64 app architecture.	If you’re unsure, choose Universal; don’t rely on the processor model alone.
System compatibility	Check the APK installer prompt and current app requirements for the minimum Android version.	If installation reports an incompatibility, check both the OS version and architecture.
Install source	Your browser or file manager may need separate permission to install apps.	Grant permission only to the app you’re using, then turn it off when you’re done.
Connection permission	Confirm Android’s VPN connection request the first time you connect.	Don’t run it alongside another app that’s using the VPN connection.

After downloading, open the APK from your system’s Downloads list. If you see a signature conflict with an installed app, stop and back up your old configuration; don’t clear app data just to overwrite it. Once installation is complete, import your subscription and select a configuration, then confirm Android’s VPN connection request.

Keep per-app rules simple for your first test. If connections drop frequently when the screen is locked, check battery optimization, background activity, and auto-start permissions instead of reinstalling repeatedly. See v2rayNG per-app proxy and battery optimization settings for details.

Linux downloads

Choose the package format for your distribution first, then select x64 or arm64. These are GUI client packages.

v2rayN

7.24.1

On Linux, v2rayN uses its cross-platform desktop interface. Debian- and Ubuntu-based distributions typically use deb; Fedora and RHEL-based distributions typically use rpm. The same file extension doesn’t guarantee compatibility or dependencies across every distribution, so check your distribution version and package manager’s prompts before installing.

deb · x64

Download x64 deb

For x64 desktop systems using deb packages; the package architecture is labeled amd64.

For arm64 devices: download deb →

rpm · x64

Download x64 rpm

For x64 desktop systems using rpm packages; check dependencies with your package manager.

For arm64 devices: download rpm →

Use your system’s software installer to handle dependencies

Open the package with your distribution’s software installer and check the architecture and dependencies. If the graphical installer reports missing dependencies, first confirm the package supports your distribution. Don’t force installation by ignoring dependency checks; distributions with similar names may use different system library versions.

Check the processor architecture in System About or hardware information: x86_64 generally matches this page’s x64 packages, while aarch64 generally matches arm64. amd64 is a common package label for x64, not a processor brand. If you chose the wrong architecture, download the correct package rather than renaming the file.

System requirements and package format

Check	Requirement or selection guide	Installation notes
Desktop environment	An active Linux desktop session that can run GUI apps.	This page is not for installing on a headless, command-line-only server.
Package format	Choose deb or rpm based on your distribution.	Your package manager still needs to check system libraries and other dependencies.
Processor architecture	Choose x64 for x86_64; arm64 for aarch64.	Confirm your system’s actual architecture to avoid using the wrong package.
Proxy and permissions	System proxy support depends on your desktop environment.	Test the app proxy first; configure TUN permissions only if needed.

Some apps don’t automatically use the desktop system proxy, so a client that launches successfully won’t necessarily proxy every app. First confirm the local listener and standard proxy work, then see the advanced configuration guide for routing, DNS, and TUN.

After installation: import a configuration and test the connection

The installer only provides the client. Subscriptions, routing, and the system proxy need to be configured separately. Follow these steps in order to troubleshoot more easily.

Configuration source

Get a valid subscription

Get a subscription link from a service you’re authorized to use or from your own server, then import it and refresh the list. Subscription links contain access credentials; don’t share them in screenshots, comments, or support requests. If no servers appear, first check that the link is valid, then make sure the subscription request completed.

See the subscription import guide →

Basic setup

Start with the standard proxy

After choosing a server, start with a common routing preset and the standard system proxy, leaving other settings close to their defaults. On Android, confirm the VPN request. Don’t change DNS, routing, and TUN all at once; if something fails, it’ll be harder to find the cause.

Read the routing and TUN guide →

Check the result

Tell download issues from connection issues

If the client installs but won’t connect, check your subscription details, server status, or proxy settings instead of downloading it again. Return to the installation steps first only if the installer won’t open, the architecture is incompatible, or a dependency is missing. Recording the full error message is more useful than repeatedly switching packages.

Browse frequently asked questions →

Updates and keeping your configuration

Before updating, note your current client, installation method, and configuration location. Export subscription groups, custom routing, and any essential settings, then quit the running app. Backups may contain server addresses and authentication details; store them somewhere you control and remove extra copies when migration is complete.

Before updating with a system installer or package manager, read its prompts. Switching from Desktop to WPF, or from v2rayNG to v2flyNG, is a configuration migration: confirm the new client supports the fields you need and check routing and DNS one by one. Don’t assume every setting has an equivalent switch.

After updating, check the client’s About page to confirm the installed version, then test subscription updates and your usual connection. The version on the card comes from the download manifest, while the package filename depends on the platform. If they temporarily differ, don’t edit the URL to construct another download link.

If your browser can’t connect after you quit the app, check whether the system proxy still points to a closed local port. Restore the system proxy before relaunching the client, and confirm no other app is using the port. Before uninstalling, disable the proxy and related connection modes to avoid mistaking leftover settings for a network problem.

Download and installation FAQs

Do I need a subscription link after downloading the client?

The client reads your configuration and connects to a server; the installer does not include a usable server configuration. You’ll need a subscription link or individual server details that you’re authorized to use. After installation, import your configuration, then choose a server and routing mode. Downloads on this page do not include subscription service.

Which should I choose: the Windows Desktop or classic WPF edition?

For a first install, start with Desktop, which uses the newer cross-platform interface. If you’re used to the classic Windows interface or want to keep your existing workflow, choose the stable WPF edition. Both are v2rayN. Back up your configuration before installing or migrating, and don’t let two instances manage the system proxy at the same time.

Should I download arm64 or Universal for Android?

Most phones released after 2015 will use arm64, but check which app architectures your device supports. If you’re unsure, or your device only runs another architecture, choose Universal. If installation reports an incompatibility, check the Android version too; Universal does not resolve every system compatibility issue.

The version shown on the page differs from the package filename. Which should I trust?

The version on each card comes from the download manifest’s latest field, while each button links to the actual file path for that platform. They may not update at the same time. To confirm the installed version, check the client’s About page. Don’t edit version numbers in download URLs; use the relevant link on this page to get an update.

Do I need to uninstall the old client before updating?

Quit the old client and back up your configuration before updating as directed by the installer. Whether you need to uninstall first depends on how it was installed and your package manager’s requirements. If you run into a signature or package conflict, or are switching clients, don’t delete app data right away. Make sure your backup can be restored before removing the old install, then check subscriptions, routing, and the system proxy after updating.

If you still have configuration questions after installing, see the FAQs. For the full setup sequence, read the client setup guide.