Client downloads · Choose a platform

V2Ray client downloads
v2rayN and Android clients

Choose an operating system, then a processor architecture. Use v2rayN on desktop; v2rayNG is the recommended Android client, with v2flyNG as an alternative.

New to V2Ray? Learn how to import a subscription and connect →

Windows client

Both interface editions are x64 packages. Choose one based on your preference; there's no need to install both.

v2rayN

Recommended Manifest version 7.24.1

DesktopNext-generation cross-platform UI · x64

Download v2rayN Desktop

Classic WPF editionClassic, stable interface · x64

Download v2rayN WPF

Desktop uses a next-generation cross-platform UI, making it a good fit for first-time users or anyone who wants a similar experience across desktop operating systems. The WPF edition keeps the classic window layout for users familiar with its server list, menus, and settings. A different interface doesn't replace the need for a subscription: both editions require a valid server configuration.

This download is a ZIP archive. Extract all its contents to a writable folder before running the installer; don't launch it from the archive preview. Before upgrading, quit the old client from the system tray. If a file is in use, make sure the related process has stopped before continuing.

Windows setup requirements

Check	Requirement and where to check
System and architecture	This page provides x64 packages. Check Settings → System → About for your system type; these downloads aren't suitable for 32-bit systems.
Runtime environment	Your OS version and desktop runtime must meet the requirements of the selected release. If a runtime is missing, follow the version and architecture specified in the startup error.
Folder permissions	Make sure the extraction and data folders have enough free space and are writable. Don't launch the app from a temporary archive folder or overwrite program files while the client is running.
Network permissions	System proxy and TUN are separate traffic entry points. Verify a standard connection first; if you need TUN, follow the system prompts to grant the required permissions.

If the app quits on launch, note the message in the dialog first, then check the runtime and folder permissions. Repeatedly switching interface editions isn't a troubleshooting step. See how to fix v2rayN crashes on startup.

macOS client

Check About This Mac to identify your chip. DMG installers are available for Apple Silicon and Intel.

v2rayN

Manifest version 7.24.1

Apple SiliconApple M-series chips · arm64

Download v2rayN · Apple Silicon

IntelIntel processor · x64

Download v2rayN · Intel

Open About This Mac from the Apple menu. If it lists a Chip with an Apple M-series name, choose Apple Silicon. If it lists an Intel processor, choose Intel. Don't infer the architecture from the case model, purchase year, or screen size; different generations of the same product line may use different processors.

Open the DMG and follow its instructions to move the app to Applications, then launch it from there. If a security prompt appears the first time you open it, verify the file's source and the prompt, then check the relevant options in System Settings → Privacy & Security. Don't disable system-wide security protections just to launch one app.

macOS setup requirements

Check	Requirement and where to check
Chip type	Apple Silicon uses arm64; Intel uses x64. Check About This Mac rather than guessing from the filename.
Operating system version	Your OS must meet the current app build requirements. If you see an incompatibility warning, check your macOS version first instead of trying a different architecture.
Install location	Make sure you have enough free space and permission to install in Applications. Quit any running instance before replacing the app.
Connection permissions	You may be prompted to grant permission the first time you change proxy settings or use TUN. Check what the feature does before approving the requested access.

If the app launches but your browser can't reach the target site, check that a server is selected and confirm the system proxy status. Package architecture affects whether the app can install and run; it doesn't replace checking your connection configuration.

Android clients

Start with v2rayNG, then consider v2flyNG if it suits your configuration. Most mainstream phones released since 2015 can use arm64, but check which architectures your device supports.

v2rayNG

Recommended Xray Manifest version 2.2.6

arm64Most mainstream 64-bit Android devices

Download v2rayNG · arm64

UniversalAn alternative if you're unsure of your architecture

Download v2rayNG · Universal

v2rayNG uses the Xray core and supports importing subscriptions, share links, and QR code configurations on Android. It's a good starting point for a first installation. Then check the protocols, transport, and security parameters used by your configuration. Support for a protocol name doesn't guarantee that every server-side parameter combination will work.

Once the APK has downloaded, open it from your browser's downloads list or a file manager. If Android asks you to allow app installations from this source, grant permission only to the browser or file manager you're using. You can revoke it after installation. The first time you connect, Android will ask for VPN permission; confirm the app name before continuing.

v2flyNG

Alternative v2fly Manifest version 1.10.31

arm64Most mainstream 64-bit Android devices

Download v2flyNG · arm64

UniversalIncludes multiple processor architectures

Download v2flyNG · Universal

v2flyNG uses the v2fly core and is an alternative for users with existing V2Fly configurations. Like v2rayNG, it's an Android client with a graphical interface, but core capabilities and supported parameters differ. Don't treat the two apps as identical packages with different names; check configuration compatibility before switching.

When switching between the two clients, stop the connection in the current app before starting the other one. Reimport what you need using a valid subscription or individual server share link rather than assuming a full app backup will work in both. After updating a subscription, check the selected server, routing, and DNS again; don't rely on the other client's status to judge the connection.

Android setup requirements

Check	Requirement and where to check
Processor architecture	The arm64 package requires OS support for that architecture. 64-bit hardware doesn't necessarily mean the OS provides a compatible runtime; try the universal version if you're unsure.
System compatibility	Check the minimum OS requirement shown by the installer. The universal version helps with architecture selection; it doesn't lower the app's system requirements.
Installation permissions	Allow app installs from the current source and make sure there's enough storage. Enterprise management policies or device restrictions may block installation.
Background operation	Connections require Android's VPN permission. If the connection drops when the screen turns off, check battery optimization and background activity settings; there's no need to grant every permission in advance.

If the installer reports a signature conflict, check where the existing app came from and how it was backed up. Don't uninstall it immediately; that may remove local configurations. Keep the error details and decide whether you need to migrate data.

Linux client

Choose deb or rpm based on your distribution, then check x64 or arm64. The extension indicates the package management system; renaming the file won't convert it.

v2rayN

Manifest version 7.24.1

deb · x64For distributions that use deb packages

Download v2rayN · deb

rpm · x64For distributions that use rpm packages

Download v2rayN · rpm

arm64 devices: arm64 · deb arm64 · rpm

Choose deb for desktop distributions that use the deb package system, and rpm for those using rpm. Matching the package format is only the first step; your system must also meet the build's dependency and environment requirements. For rpm packages in particular, being able to open an rpm file doesn't mean all dependencies are satisfied.

Open the downloaded file with your system's graphical package installer to review its architecture, dependencies, and installation prompts. After installation, launch v2rayN from the applications menu. Desktop environments handle system proxy settings differently; if your browser works but other apps don't, check whether those apps read the desktop proxy settings before reinstalling the client.

Linux setup requirements

Check	Requirement and where to check
Desktop environment	This page provides a graphical client. You need an environment that can run desktop apps; it's not installed as a background server service.
Architecture names	amd64 and x86_64 correspond to x64 on this page; aarch64 usually corresponds to arm64. Check your system information before choosing.
Dependencies and permissions	Check for missing dependencies in your graphical package manager and use the authorization method required by your system during installation. Don't run a graphical client as an administrator long-term.
Proxy routing	Not every app uses the desktop system proxy. If you need to route other traffic, check the TUN permissions and routing guidance first.

If the package installer reports unmet dependencies, note the missing component and distribution version, then check which environments are supported. Renaming the file extension, ignoring dependencies, or mixing package management systems aren't appropriate fixes.

Configuration after installation

Import a subscription, then verify the connection

The installer contains only the client, not a server you can connect to. Get a subscription URL or share link you're authorized to use, then follow these three steps. Test with one app first; don't change multiple clients and routing setups at the same time.

Read the full user guide

Import and update a subscription
On desktop, add the URL under Subscription Groups and update it. You can also copy a valid share link and press Ctrl+V in the main window. On Android, add the configuration from the client's import menu. After updating, check that servers appear in the list. If it's empty, first check the subscription URL and access.
Choose a server and traffic entry point
Select a server configuration, then set the system proxy or start the connection as needed. The system proxy determines whether app traffic enters the client; routing presets determine the outbound route after it does. They aren't interchangeable. For your first setup, keep the settings easy to understand and skip custom DNS and TUN for now.
Check websites and logs
Open the target website, then check the client logs for connection or DNS errors. A successful latency test only shows that the test route is reachable; it doesn't confirm that the site itself works. If the page fails, note the time, selected mode, and exact log message. Hide subscription URLs, server credentials, and personal information before sharing screenshots.

Back up your configuration before updating

A first-time installation and an in-place update are different. If you have a working configuration, use the client's backup or export feature before updating to save subscription groups, custom routing, and any settings you need. Backup files may contain connection details, so store them somewhere you control. A server alias alone usually isn't enough to restore a configuration in a new environment.

Quit the main window and tray process before updating, then wait for the connection to stop before running the new installer. Afterward, check that subscriptions are still present, the default server is correct, and local ports haven't changed; then test a real connection. If you use multiple devices, don't copy the entire desktop data directory over an Android app. For cross-client migration, use a compatible subscription or share link where possible.

To compare the three clients, see our client comparison. Routing rules, DNS, and TUN setup are covered in the advanced guide. Make these changes one at a time, after your basic connection is working.

Download and installation FAQs

Which should you choose: v2rayN Desktop or the classic WPF edition?

For a first installation, try Desktop, which uses a next-generation cross-platform interface. If you prefer the classic window and familiar workflows, choose the stable WPF edition. Both require a valid configuration. Back up your existing settings before switching editions, quit the running client, and then launch the new version.

Should you download the arm64 or universal Android version?

Most mainstream phones released since 2015 can start with arm64, but check which architectures your device's operating system actually supports. If the installer reports that the package is incompatible, try the universal version. It includes multiple architectures and is usually larger; it won't fix an outdated OS, a signature conflict, or insufficient storage.

Do I need a subscription or server configuration after installing the client?

Yes. The client reads configurations, manages servers, and directs traffic, but the installer does not include a server you can connect to. Import a subscription URL, share link, or configuration file that you are authorized to use. Subscription URLs may contain access credentials, so don't share them publicly or include them in screenshots of support requests.

Will updating the client keep my subscriptions and routing rules?

Whether they are retained depends on the installation method, data directory, and version migration behavior; the package name alone doesn't tell you. Before updating, use the client's backup or export feature and note the current data directory. Quit the old version before updating. Once subscriptions, routing, and local ports are working as expected, you can remove the old files.

What should I check if installation fails or the app quits on launch?

First check your operating system, processor architecture, and whether the downloaded file was saved correctly. Extract Windows archives before running them; follow the error message if a runtime is missing. On macOS, check the chip type and security prompts. On Android, review the installer’s compatibility or signature details. On Linux, check dependency notices in the graphical package manager. Keep the exact error message and avoid repeatedly reinstalling over the existing copy.

The download button opened, but the file hasn't started downloading. What should I do?

Open your browser's downloads list first and check whether the task is paused, blocked, or waiting for you to choose a save location. The page tries to read a same-origin version manifest to refresh download links; if that fails, it keeps the package links already on the page. Refresh and try again. If it still fails, note the selected platform, package type, and browser error. Don't edit the file path or extension.

See more frequently asked questions →

V2Ray client downloadsv2rayN and Android clients

Windows client

Windows setup requirements

macOS client

macOS setup requirements

Android clients

Android setup requirements

Linux client

Linux setup requirements

Import a subscription, then verify the connection

Back up your configuration before updating

Download and installation FAQs

V2Ray client downloads
v2rayN and Android clients