Free, open-source GUI clients

Download V2Ray clients

Choose your operating system first, then your CPU architecture. Use v2rayN on desktop and v2rayNG on Android. If you already have a V2Fly configuration, consider v2flyNG.

First-time setup and subscription import guide

Windows downloads

Both downloads are x64 packages. For your first install, start with Desktop.

v2rayN

Recommended

7.24.1 · Windows x64

Desktop features a newer cross-platform UI. Classic WPF keeps the familiar Windows interface and is a stable choice for users who prefer the traditional experience.

Download Desktop · x64 Download classic WPF · x64

After downloading the ZIP file, extract it completely to a separate folder, then run the installer from there. Don’t launch it from the archive preview, where it may not be able to access files in the same folder.

Choose either version for your first install. Menus and settings may be in different places, so use feature names in the guide to find what you need rather than expecting an exact match.

System and installation requirements

Check	Selection and details
Processor	x64; check System type under Settings > About.
Operating system	Use a supported version of Windows. Follow the installer’s prompts for specific minimum versions and runtime requirements.
File permissions	The extraction and configuration folders must be writable.
Network permissions	Standard system proxy and TUN mode have different permission requirements. TUN may require administrator approval.

If the installer reports a missing runtime, install the required component as prompted, then restart the client. If no window appears, don’t keep launching the app; first check the taskbar notification area and background processes.

Switching between Desktop and WPF

If you’re used to the classic interface, you can keep using WPF. Choose Desktop if you want a similar workflow across desktop operating systems. The versions differ mainly in interface and runtime; installing either one does not provide a working server. You’ll still need to configure a subscription, select a server, and choose a routing mode.

Before switching versions, export your servers, subscription groups, and custom routing rules, then exit the old app before launching the new one. Running both clients at once can cause local port conflicts or interfere with system proxy settings. If a port is already in use, first check whether the old instance is still running in the notification area instead of changing every port.

macOS downloads

Check your chip under About This Mac and choose the matching DMG installer.

v2rayN

Desktop client

7.24.1 · macOS

If Chip shows an Apple M-series processor, choose Apple Silicon. If it shows an Intel processor, choose Intel. The downloads target different architectures; you don’t need both.

Download Apple Silicon · arm64 Download Intel · x64

Open the DMG and copy the app to the Applications folder, then launch it from there. Once the copy is complete, eject the disk image rather than running the app from the temporary mounted volume.

Choose the native package that matches your chip. Don’t rely on compatibility translation as the default installation method. If you see an architecture mismatch warning, check your chip information and try the other download.

System and installation requirements

Check	Selection and details
Apple silicon	Choose the arm64 package for Apple M-series chips.
Intel chip	Choose the x64 package for Intel processors.
Operating system version	Use a supported macOS version; check the app’s current prompts for minimum requirements.
Permissions	System proxy setup may request authorization. TUN mode may also require permission to create a virtual network interface.

If macOS displays a security warning, first verify the download source and app details. Then use the per-app authorization option in System Settings. Disabling system-wide security protections is not recommended.

First launch and system proxy

After opening the app for the first time, import a subscription and make sure servers appear in the list. Select a server, then enable the system proxy. Opening the app alone does not activate the proxy. Some apps ignore system proxy settings; configure a proxy in those apps directly, or consider TUN mode once you understand its impact.

Before quitting the client, turn off the system proxy. If the client is closed while your browser is still trying to connect to a local proxy port, regular websites may stop loading. Check the proxy settings in your system network settings before assuming the server is down. If you’ve made several configuration changes, switch back to standard system proxy mode and test each setting one at a time.

Android downloads

v2rayNG is the recommended choice. Choose v2flyNG if you need the V2Fly core.

v2rayNG

Recommended

2.2.6 · Xray core

A good choice for everyday Android use, with subscription management and rule-based routing. Most phones released since 2015 should use arm64; choose universal if you’re unsure of the system architecture.

Download v2rayNG · arm64 Download v2rayNG · universal

The universal package includes multiple processor architectures and is usually larger. Some older devices or phones with specialized systems may run a 32-bit OS even if the processor supports 64-bit. Check actual system compatibility before choosing.

v2flyNG

Alternative

1.10.31 · V2Fly core

For users with existing V2Fly configurations or who need the behavior of its core. Before installing, make sure the server protocol and transport settings are compatible. Don’t rely on the client name alone to determine what it supports.

Download v2flyNG · arm64 Download v2flyNG · universal

v2flyNG uses a different core from v2rayNG, so configuration fields and protocol support aren’t identical. Before switching, save your existing subscription and custom rules. Import them, test a single server, then restore more complex routing settings.

System and installation requirements

Check	Selection and details	Troubleshooting
Processor architecture	Choose arm64 for most modern phones; if you’re unsure, choose universal.	If installation reports incompatibility, check the system architecture first.
Operating system version	The minimum Android version depends on the current APK. Follow the installer’s prompt.	Older systems may need an upgrade; the universal package won’t fix an outdated Android version.
Install permissions	Allow installs for the browser or file manager you use to open the APK.	After installation, you can turn off install permission for that source.
Connection permissions	Approve the system VPN prompt when starting a connection.	Check whether another VPN app is already using the VPN connection.

Installing the APK and background operation

Once the download is complete, open the APK from your browser’s downloads or a file manager. Android manages permission to install apps from unknown sources separately for each app; authorizing your browser doesn’t authorize your file manager. If the installer reports a signature conflict, save your existing configuration and check where the installed app came from. Don’t uninstall it without a backup.

The first time you connect, Android will request VPN permission. This system interface lets the client route traffic; it doesn’t mean the imported server is working. After connecting, test with an app you actually use. If the connection often drops when the screen locks, check battery optimization, background activity, and power-saving settings. Change one setting at a time and see whether it helps, rather than changing your subscription, routing, and background settings all at once.

Linux downloads

Choose deb or rpm for your distribution, then check whether your processor is x64 or arm64.

v2rayN

Desktop client

7.24.1 · Linux

Most Intel and AMD desktop computers use x64. Debian- and Ubuntu-based distributions usually use deb; Fedora- and RHEL-based distributions usually use rpm. Check package dependencies with your distribution’s package manager.

Download deb · x64 Download rpm · x64

For arm64 devices

Download deb · arm64 Download rpm · arm64

Open the package in your system’s software installer. Review the dependencies and installation prompts before continuing. A matching package format doesn’t guarantee compatibility with every distribution. If the installer reports missing components, first check whether the package supports your distribution version.

System and installation requirements

Check	Selection and details
Desktop environment	A desktop session that can run graphical applications is required.
x64 architecture	System information often reports x86_64 or amd64.
arm64 architecture	System information often reports aarch64 or arm64.
Software dependencies	Check dependencies with your package manager; don’t force the installation past missing dependencies.
Network permissions	TUN may require additional permissions and system network support.

The specific build target for an rpm file doesn’t make it compatible with every rpm-based distribution. Check the system installer’s compatibility information before installing rather than relying on the file extension alone.

Desktop proxy and app settings

Linux desktop environments handle system proxies differently. Even when the client is running and listening on a local port, some apps may need the proxy address and port entered manually. Test with an app that supports proxy settings before deciding whether you need TUN. A desktop proxy toggle alone doesn’t mean every program is using the proxy.

For regular desktop use, run the client as a standard user to avoid configuration folder ownership problems. If you need TUN, grant the permissions requested by the client. Before updating, exit the old instance and confirm the package architecture matches the installed version. After installation, check that your subscription groups, routing rules, and local port are still set as expected.

Install and configure after downloading

The package installs the client; server configuration, proxy mode, and network testing come next. Follow these steps to identify whether an issue is with installation or connectivity.

Match the package to your device

Check the operating system first, then the architecture and file type. Extract Windows ZIP files before running them; macOS uses DMG, Android uses APK, and Linux uses a package for your distribution. Renaming a file extension won’t make it compatible with another system. Don’t open a temporary file while the browser still shows the download in progress.
Import a subscription and select a server

The client does not include a working server. Paste your existing subscription URL into subscription management, save the group, and update it. To add an individual server using a share link, import it from the clipboard. Once servers appear in the list, select one as the current server. A successful subscription update only means the configuration was retrieved; it doesn’t guarantee that every server can connect.
Choose a proxy mode and test it

For your first desktop setup, start with the system proxy. On Android, start the VPN connection when prompted. Keep the default routing rules initially, test with a real website or app, then consider changing TUN, DNS, or custom routing. Check the logs as you test: a local listening error and a remote connection timeout happen at different stages and need different fixes.
Save a restorable configuration

Once you’ve confirmed the connection works, export your server and custom settings, and note the proxy mode and local port. Subscription URLs, share links, and exported files may contain credentials; don’t include them in public screenshots or support messages. When asking for help, share only the error and necessary system details, removing server addresses, user identifiers, and subscription parameters first.

Export your settings and exit the old instance before updating

Before installing an update, use the client’s export feature to save your configuration. Don’t assume the program folder and configuration folder are always the same, or that an in-place update will migrate settings automatically. System installers, portable setups, and different interface versions may store settings in different locations. Only clean up the old folder once you’ve confirmed the configuration can be restored.

After updating, check the current server, subscription groups, and local listening port before enabling the proxy. If the new version won’t start, keep the system error message and logs; don’t repeatedly uninstall and reinstall. Version information on this page identifies a client release, but the download button links to the package to install. Check the client’s About page for the version actually installed.

Download and installation FAQs

These questions focus on choosing a package. If the client is installed but won’t connect, visit the Help Center.

Which should you choose: v2rayN, v2rayNG, or v2flyNG?

Use v2rayN on Windows, macOS, and Linux desktops. For Android, v2rayNG with the Xray core is the recommended choice. Android users with existing V2Fly configurations or a need for its core behavior can choose v2flyNG. All three clients require you to import a working server configuration or subscription.

What’s the difference between v2rayN Desktop and classic WPF for Windows?

Desktop uses a newer cross-platform interface, making it a good choice for first-time installs and users who want a consistent experience across desktop platforms. Classic WPF is the established Windows version for users who prefer the familiar interface. Both downloads are x64 packages; choose one to start, and export your configuration before switching.

Should you download the Android arm64 or universal version?

Most phones released since 2015 are best served by arm64, but make sure the system supports 64-bit apps. If you’re unsure of the device architecture or installation reports incompatibility, choose the universal version. It includes multiple architectures and is usually larger. You don’t need both packages for the same client.

Why can’t I connect after installing the client?

The client does not include a working server. After installation, import a valid subscription or server configuration, update the subscription, select a server, and enable the system proxy or Android VPN connection. If it still fails, check the local port, server settings, system clock, and logs in that order.

What should you save before updating the client?

Export your server configurations, subscription groups, and custom routing rules. Note the local listening port and proxy mode, then exit the old client. Configuration locations vary by platform and version, so use the client’s export feature. Backups may contain subscription URLs and credentials; store them securely, verify the update, then remove old configuration files if appropriate.

What should you do if a download or installation fails?

If a download fails, check your browser’s download history, available disk space, and network connection, then reload the page and try again. If installation fails, confirm the download is complete, the file extension matches the platform, and the architecture, permissions, and system prompts are all correct. Renaming a file extension won’t fix compatibility. After opening the client, check its About page to confirm the installed version.

Download V2Ray clients

Windows downloads

v2rayN

Switching between Desktop and WPF

macOS downloads

v2rayN

First launch and system proxy

Android downloads

v2rayNG

v2flyNG

System and installation requirements

Installing the APK and background operation

Linux downloads

v2rayN

Desktop proxy and app settings

Install and configure after downloading

Match the package to your device

Import a subscription and select a server

Choose a proxy mode and test it

Save a restorable configuration

Export your settings and exit the old instance before updating

Download and installation FAQs