CLIENT PACKAGES / CHOOSE A PACKAGE

Download V2Ray Clients

Choose a client by operating system, processor, and package format.

Use v2rayN on desktop, v2rayNG on Android, or v2flyNG as an alternative with the V2Fly core. Check your device architecture before downloading. See the user guide for importing configurations and setting up a connection.

Free to use Open source Xray · V2Fly

WINDOWS / x64

v2rayN

Recommended

Desktop GUI client 7.24.1 ZIP archive

Download Desktop · x64 Download classic WPF · x64

Desktop: the newer cross-platform UI. WPF: the classic, stable version.

Desktop is a good fit for first-time installs and users who want a consistent cross-platform experience. WPF keeps the classic Windows interface for those familiar with its settings and layout. These are interface choices, not separate packages for different protocols. Connection support also depends on the core and configuration you use.

Both downloads on this page are x64. After downloading, extract the ZIP contents to a separate folder, then run the installer or application included in the package. Don't launch it from the archive preview, where required files may not be extracted correctly. If prompted to install a runtime, follow the app's instructions and system requirements.

System and installation requirements

Windows requirements
Check	What to look for
Operating system	Windows; check the current client requirements for the minimum version
Processor	x64; check System type in Windows settings
Package format	ZIP; extract all files before running the included program
Runtime requirements	The folder must be writable; install any required runtime components when prompted

Check System type under Settings → System → About or System information. If your device uses a different architecture, don't install the x64 package just because the operating system has the same name.

For your first run, import a configuration and confirm it starts before setting the system proxy. Standard proxy settings and TUN mode have different permission requirements. You don't need to change all network permissions just to import a subscription.

See the desktop setup guide →

MACOS / CHIP TYPE

v2rayN

Desktop client

Apple Silicon / Intel 7.24.1 DMG disk image

Download Apple Silicon · arm64 Download Intel · x64

Open Apple menu → About This Mac, then check the Chip or Processor entry.

Choose Apple Silicon for an Apple M-series chip, or Intel for an Intel processor. A Mac's model name and purchase year aren't reliable indicators; the same product line may use different processors. Prefer the package that matches your Mac's architecture rather than relying on compatibility translation by default.

Open the DMG and follow its instructions to move the app into Applications, then launch it from there. If macOS shows a warning on first launch, read the reason and check the relevant entry under System Settings → Privacy & Security. Don't disable system protections entirely just to launch an app.

After importing a configuration, check the selected node and local listening port. The system proxy affects apps that follow system proxy settings; it doesn't automatically route every network request. If you need another routing mode, read its setup instructions before handling permission requests.

System and installation requirements

macOS requirements
Check	What to look for
Operating system	macOS; minimum version depends on the current build
Apple silicon	Choose arm64 for M-series chips
Intel processor	Choose x64 for Intel processors
Package format	DMG; move the app to Applications

Quit the app before updating so no running process holds files open during replacement. If the previous version enabled the system proxy, check its status and port again after updating.

When moving to a new device, back up nodes, routing rules, and client settings separately. A subscription URL only retrieves the content provided by that subscription; it may not include custom local rules.

Learn about local listening settings →

ANDROID / XRAY

v2rayNG

Recommended

Xray core 2.2.6 APK

Download v2rayNG · arm64 Download v2rayNG · universal

Most mainstream phones released after 2015 support arm64. If you're unsure of your device's architecture, choose the universal version.

Use v2rayNG to import nodes, update subscriptions, and configure routing on Android. For configurations using VLESS or REALITY, check that the included core supports the required features and that the transport and security parameters match the server. Sharing a protocol name doesn't mean every optional field is interchangeable.

After downloading the APK, open it from your system's downloads list. If Android asks you to allow app installs from your browser or file manager, grant permission only to the source you're using. When you connect for the first time, confirm the app name in the VPN permission prompt before proceeding. Notification permissions and background restrictions may also affect the status shown by the app.

ANDROID / V2FLY

v2flyNG

Alternative

V2Fly core 1.10.31 APK

Download v2flyNG · arm64 Download v2flyNG · universal

A good choice for users with existing V2Fly configurations who need to preserve the behavior of that core.

v2flyNG and v2rayNG serve similar purposes, but use different core families. Before importing a configuration, check whether it relies on extensions specific to one core; the apps aren't interchangeable just because their names are similar. When switching clients, keep a copy of the original subscription URL or configuration, and check DNS, routing, and transport settings in each app.

You can install both apps and manage their configurations separately, but run only the one you plan to use when troubleshooting. Multiple connection services taking over network traffic can make test results confusing. Stop the old connection before starting the new one, then check the active app's logs.

System and installation requirements

Android requirements
Check	What to look for
Operating system	Android; minimum version depends on the package
Recommended architecture	Choose arm64 on devices that support 64-bit apps
Alternative architecture	The universal package includes multiple architectures and is usually larger
Installation and connection	Allow installs from the current source; approve VPN access when connecting

A 64-bit processor doesn't necessarily mean the system can run 64-bit apps. If the arm64 package is reported as incompatible, check the system architecture rather than relying only on the phone's release year.

Installation can also fail because the Android version is too old, storage is low, or an existing app has a different signing key. Read the system message first. Don't uninstall an existing app right away, or you could lose nodes and rules that haven't been exported.

The displayed version and filename come from separate manifest fields and may not match. This page preserves the listed values; check the app's About page to confirm the installed version.

See how to import a subscription →

LINUX / DEB · RPM

v2rayN

Desktop client

x64 / arm64 7.24.1 Choose a package format for your distribution

Download deb · x64 Download rpm · x64

arm64: download deb arm64: download rpm

Debian / Ubuntu generally use deb; Fedora / RHEL-based distributions generally use rpm.

Choose the package format for your distribution and the processor architecture for your device and system; both must match. x64 may appear as amd64 or x86_64 in package names, while arm64 may appear as aarch64. Different labels don't mean it's a different client.

Open the downloaded file with your system's software installer. Review dependency and compatibility messages before confirming installation. Using the same package format doesn't guarantee that every version of a distribution meets the dependencies. If a library is missing or versions conflict, note the exact component rather than forcing the installation past dependency checks.

After launching the GUI, import a configuration and check the local listening address and port before setting up a proxy in your apps. Desktop environments may handle system proxy settings differently, and browsers or other apps may have their own proxy options. Test the connection in the app you actually plan to use.

System and installation requirements

Linux requirements
Check	What to look for
Desktop environment	Must support the current GUI client and its dependencies
deb package	Debian, Ubuntu, and compatible distributions
rpm package	Fedora, RHEL-based, and compatible distributions; check dependencies
Processor	Choose x64 or arm64 to match your system

Check your processor architecture in About or Hardware information, and confirm your distribution version in its system information. If the installer reports an architecture mismatch, choose the correct package instead of renaming the file.

The system proxy and TUN mode are different settings. Configure network features that need extra permissions separately, following the client documentation; don't assume every startup problem is caused by insufficient permissions.

See the routing field guide →

AFTER INSTALL / FIRST RUN

Client installation and connection setup

Installing the client only prepares the graphical app. Subscriptions, outbound settings, and traffic routing still need to be configured separately.

01 / IMPORT

Import an existing configuration

Have a subscription URL, share link, or configuration file you're authorized to use ready. Subscription URLs may contain access credentials, so don't include them in public screenshots or feedback. After importing, check that the nodes appear and have clear names, then update the subscription.

Updating a subscription may replace entries in its group. Save any locally edited nodes first. Keep custom routing and DNS settings separately too; don't assume they're included in the subscription.

02 / SELECT

Select a configuration and routing mode

Select the node you want to use, then start the connection. On desktop, check the address and port used by the system proxy. On Android, confirm VPN permission and app-level routing settings. A node appearing in the configuration list doesn't mean it's active.

Stop the existing connection before switching clients to avoid port conflicts or overlapping traffic routing. When troubleshooting, change one clearly documented setting at a time to make the cause easier to identify.

03 / CHECK

Test traffic from the app you use

Use the target app to access the service you're testing and check the client logs. If the logs show no related requests, check the system proxy, app-specific proxy, and routing rules. If requests appear but the connection fails, check the server address, port, and security parameters.

Download speed, node names, or a successful configuration import don't prove that a connection is working. Keep the exact error message and note the steps that led to it; this is usually more useful than repeatedly reinstalling the client.

Read the full user guide → For field definitions, see the glossary and configuration reference.

PACKAGE NOTES / COMMON QUESTIONS

Download and installation help

First identify whether the issue is package selection, installation, or connection setup, then follow the relevant prompt.

Desktop or WPF: which Windows version should you choose?

Desktop is the newer cross-platform interface; WPF is the classic, stable version. For a first install, start with Desktop. Choose WPF if you prefer its familiar layout. Both downloads are x64 packages. Export any configurations you want to keep before updating.

Android: arm64 or universal APK?

Most mainstream phones released after 2015 support arm64, but check which app architectures your device supports. If you're unsure or Android reports that the package is incompatible, try the universal version. It supports more architectures and is usually larger.

How to choose between Apple Silicon and Intel for macOS

Open About This Mac from the Apple menu. Choose Apple Silicon if Chip shows an Apple M-series processor; choose Intel if Processor shows Intel. Don't rely on the computer's appearance or purchase year.

Linux: should you choose deb or rpm?

Debian, Ubuntu, and compatible distributions generally use deb packages; Fedora, RHEL-based, and compatible distributions generally use rpm. Check whether your system is x64 or arm64 as well. A matching package format doesn't guarantee dependencies are met, so follow your system installer's prompts.

Why won't the client connect after installation?

The client manages configurations and connections; its installer doesn't include server connection details. Import a subscription URL or node configuration you're authorized to use, select it, and start the connection. Then check whether app traffic reaches the client through the system proxy or VPN mode.

What if the version shown doesn't match the package filename?

The displayed version and package path are separate fields in the download manifest and may not match. This page shows each value as listed rather than inferring a version from the filename. Check the client's About page after installation to confirm its version. Before installing a specific release, verify the package details.