Client Downloads / Platforms and Architectures

V2Ray Downloads
v2rayN and Android Clients

Choose v2rayN for desktop. For Android, v2rayNG is the usual choice; choose v2flyNG if you specifically need the V2Fly core. Select your operating system first, then your processor architecture.

01 · Operating system 02 · Processor architecture 03 · Install and import

Windows Installer

v2rayN comes in Desktop and classic WPF editions. Both downloads on this page are x64 installers.

v2rayN

Recommended

Windows · x64 · 7.24.1

Download Desktop · x64 Download classic WPF · x64

Desktop is the newer cross-platform UI. It’s a good fit for first-time installs and for users who want a similar interface across desktop operating systems. You’ll still need to check your server list, subscription groups, and settings after the first launch. Changing the interface doesn’t connect you automatically.

WPF is the established classic edition. Choose it if you’re already comfortable with the traditional Windows layout. Base your choice on the interface and workflow, not the server protocol. Protocol support depends on whether the selected core and server configuration are compatible.

Both downloads are ZIP archives. Once the download finishes, extract the archive to a separate folder before opening the installer. Don’t run it from the archive preview. Keep the folder path short and avoid temporary folders that may be automatically cleared.

Windows Installation Tips

Check your system type under Settings → System → About. An x64 package is for a 64-bit Intel or AMD system; your computer’s brand alone doesn’t tell you which package to choose.

Close the previous version of v2rayN before updating, including the app in the system tray.
On first launch, import a subscription or configuration, select an active server, then set up the system proxy.
Use standard permissions for system proxy mode. If you need TUN, handle the virtual network adapter and permission requirements separately.

The system proxy mainly affects apps that follow your system proxy settings; it doesn’t route every program through the client. If a browser behaves differently from other apps, check its own proxy settings first.

See the v2rayN first-time setup guide →

Windows System Requirements

Check	Packages on this page	Recommendation
Processor	x64 for 64-bit Intel / AMD systems	Confirm your architecture in System Information. Don’t use the x64 packages on other architectures.
Operating system	Use a Windows 10 or 11 version that still receives security updates	Check the installer for the exact minimum build requirement. Older Windows versions may need additional compatibility checks.
Runtime components	Desktop and WPF may have different dependencies	If a runtime component is missing, install the component named by the installer. Don’t copy DLLs at random.
Permissions	System proxy and TUN have different permission requirements	Set up standard proxy mode first. Grant additional permissions only if you enable TUN or another feature that requires them.

macOS Installer

Download the v2rayN DMG. Native builds are available for Apple Silicon and Intel.

v2rayN

Desktop client

macOS · DMG · 7.24.1

Download Apple Silicon · arm64 Download Intel · x64

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. The year you bought the Mac is only a guide—the chip name determines the right package.

Open the DMG and drag v2rayN into the Applications folder. Launch it from Applications rather than running it from the mounted disk image, which can make the app’s location unclear when you eject or update it.

If macOS says it can’t verify the developer on first launch, check the app’s name and source, then review the alert under Privacy & Security in System Settings. Don’t disable system-wide security just to open one app.

Launch and Network Permissions

macOS app approval and proxy permissions are separate. Allowing the app to open only clears the launch restriction; to route app traffic, you still need to choose a proxy mode in the client.

Launch the app from Applications, then import an existing subscription or share configuration.
Select an active server and check the client’s listening port and current routing mode.
When enabling the system proxy, follow the system prompts to grant permission. Allow local network access only if your use case requires it.

Quit the old process before updating. If macOS reports that the app is in use, don’t keep dragging the new version over it. Quit the menu bar client first, then install the update.

Read about app approval and network permissions →

macOS System Requirements

Check	Compatible hardware	Recommendation
Apple Silicon	Apple M-series chip · arm64 package	Use the native package for your chip. You don’t need to use translation just to install the client.
Intel	Intel processor · x64 package	Check the processor name in About This Mac. Don’t install the arm64 package on an Intel Mac.
Operating system	Must meet the minimum macOS version specified by the app in the DMG	Check compatibility before installing on an older macOS version. A matching architecture doesn’t guarantee that the OS version is supported.
App location	Install in the Applications folder	Eject the disk image after installation. Launch and update the app from its installed location.

Android APKs

For most users, v2rayNG with the Xray core is the right choice. Choose v2flyNG only if you specifically need the V2Fly core.

v2rayNG

Recommended

Android · Xray core · 2.2.6

Download v2rayNG · arm64 Download v2rayNG · Universal

v2rayNG is for Android users who want to import subscriptions, manage servers, and control which apps use the proxy. For configurations using VLESS, REALITY, or other features, check that both the share parameters and the client’s bundled core support them. A server name alone doesn’t confirm compatibility.

Most phones released since 2015 can use arm64, but some devices may support only other app architectures. If you’re unsure, choose the universal build. It includes multiple architectures and is usually larger; check the file details for its actual size.

The version shown on the card and the installer filename come from separate release fields. To identify a specific build, check the downloaded filename and the client’s About page. Don’t infer the build number for an architecture-specific package from the version shown above.

v2flyNG

Alternative

Android · V2Fly core · 1.10.31

Download v2flyNG · arm64 Download v2flyNG · Universal

v2flyNG uses the V2Fly core and is suited to configurations specifically designed for it. It’s a separate client, not a v2rayNG skin or an installer you can swap in based on the name alone. Manage data directories and some settings separately for each app.

Choose the architecture the same way as for v2rayNG: check your device’s supported app architectures, then choose arm64 or universal. If your configuration uses Xray features such as REALITY, don’t import it just because the interfaces look similar. Check the required protocols and security layer first.

When switching from another Android client, re-import your subscription or a compatible share link. Check per-app proxy, routing, and DNS settings separately; importing servers doesn’t necessarily carry over those options.

Android System Requirements

Check	Compatible hardware	Recommendation
arm64	Android system that supports arm64-v8a apps	Most phones released since 2015 are good candidates, but check the architectures your system actually supports.
Universal build	Includes multiple app architectures	Choose this if you’re unsure of your device’s architecture. The universal build doesn’t bypass the app’s minimum Android version requirement.
Operating system	Must meet the minimum Android version specified by the selected APK	If Android can’t parse the APK, check the OS version, architecture, and whether the file finished downloading.
Connection permissions	VPN mode requires Android VPN approval	Verify the app before granting permission. In proxy-only mode, apps must connect to the local proxy port themselves.
Background operation	Battery and background limits vary by device	Adjust background permissions for this client only if it disconnects when the screen is locked.

Not sure which Android core to choose? See how the three clients compare before deciding whether you need v2flyNG.

Linux Packages

v2rayN is available as deb and rpm packages. Choose the package format used by your distribution, then select x64 or arm64.

v2rayN

Desktop GUI client

Linux · deb / rpm · 7.24.1

Download deb · x64 Download rpm · x64

arm64 devices Download deb · arm64 Download rpm · arm64

Debian, Ubuntu, and related distributions typically use deb; Fedora, RHEL, and related distributions typically use rpm. A matching package format means the package managers are similar, not that the system libraries are guaranteed to be compatible with this package.

In filenames, amd64 and x86_64 identify the x64 architecture; arm64 and aarch64 refer to 64-bit ARM. Don’t install across architectures just because both devices are 64-bit.

This page provides a desktop GUI client. After installation, launch it from your app menu and configure the proxy in your desktop session. This isn’t a graphical install guide for command-line-only servers. For configuration fields, see the documentation; there’s no separate core package to download here.

Package Management and Desktop Setup

Open the package with your distribution’s software installer when possible. If it reports missing dependencies, review the missing packages and OS version first. Don’t force installation by ignoring dependency errors.

Check your distribution, processor architecture, and desktop environment in System Information.
Install the matching package with your system package manager, then launch the client from the app menu.
After importing your configuration, check the system proxy. How proxy settings are applied varies by desktop environment.

TUN requires a virtual network adapter, routing, and additional permissions. First confirm that the server connects in standard proxy mode, then enable the features you need one at a time. This makes it easier to distinguish installation issues from routing problems.

See inbound, routing, and DNS fields →

Linux System Requirements

Check	Compatible hardware	Recommendation
Package format	deb or rpm	Choose the format used by your distribution’s package manager. Don’t rename one format to make it look like another.
Processor	Packages available for x64 and arm64	Use the architecture reported by your system. Appearance and processor bitness alone aren’t enough to identify it.
Desktop environment	Requires a desktop session that can run graphical apps	Whether apps use the proxy also depends on the desktop environment and their own settings.
Dependencies and system libraries	Must meet the dependencies declared by the package	Let the package manager check dependencies. If installation fails, note the specific missing package instead of forcing the install.

Before You Install: Preparation and Configuration Migration

The installer provides the client; server settings, subscriptions, and proxy coverage must be configured separately.

First Install: Get Your Configuration Ready

Before installing, prepare a subscription link, share link, or configuration file you’re authorized to use. A subscription usually provides updates for a group of servers; it isn’t a single server address. After importing, check that the group appears and the configuration fields are complete, then select an active server. Seeing servers in the list doesn’t mean the system proxy is enabled.

On desktop, start with system proxy mode. On Android, approve the VPN connection when prompted by the client. If an app requires manual proxy settings, use the local listening address and port shown by the client—not the remote server’s port. Follow the steps in the quick-start guide.

Existing Configuration: Back Up Before Switching

Before updating the same client, save your subscription URL, manually added settings, custom routing, and DNS settings. If the client offers export or backup, use it. When switching between Desktop and WPF, or between Android clients, don’t assume all settings will carry over automatically.

After installation, check the active server, routing mode, and local listening port before restoring per-app proxy or TUN settings. If something goes wrong, change one setting at a time and check the specific error in the logs. Subscription URLs and exported configurations may contain access credentials; don’t share them in public screenshots, documents, or discussions.

Download and Installation FAQ

First rule out package format and architecture issues, then check your configuration and proxy mode.

Which should you choose for Windows: Desktop or WPF?

For a first install, start with Desktop, which uses a newer cross-platform interface. If you're familiar with the classic Windows layout, choose the established WPF edition. With either edition, check your active server, routing, and system proxy settings separately. Back up your subscription and configuration before switching.

What’s the difference between Android arm64 and universal builds?

Most phones released since 2015 can start with arm64, but check which app architectures your system supports. The universal build includes multiple architectures and is a good option if you’re unsure or need compatibility with other devices. If Android reports that the package is incompatible, check the architecture and OS version instead of repeatedly reinstalling it.

Does installing the client automatically provide server settings?

The installer provides a GUI client, not ready-to-use server settings. You’ll need a subscription link, share link, or configuration file that you’re authorized to use. Import it, select an active server, then configure system proxy or VPN mode as needed.

What should you save before updating or switching clients?

Save your subscription URL, manually added server settings, custom routing, and DNS settings. Use the client’s export or backup feature, and note the current proxy mode. When switching clients, prefer a compatible subscription or share link; don’t overwrite another client’s data directory.

The version shown on the download button doesn’t match the filename. Which should I check?

The version shown on the card and the filenames for each architecture come from separate release fields and may update at different times. Confirm the client, OS, and architecture first. To identify a specific build, check the downloaded filename and the client’s About page—not just the version shown on the card.

V2Ray Downloadsv2rayN and Android Clients

Windows Installer

v2rayN

Windows System Requirements

macOS Installer

v2rayN

macOS System Requirements

Android APKs

v2rayNG

v2flyNG

Android System Requirements

Linux Packages

v2rayN

Linux System Requirements

Before You Install: Preparation and Configuration Migration

First Install: Get Your Configuration Ready

Existing Configuration: Back Up Before Switching

Download and Installation FAQ

V2Ray Downloads
v2rayN and Android Clients