v2rayN · v2rayNG · v2flyNG

V2Ray Download
Choose a Client and Installer

Use v2rayN on desktop; for Android, start with v2rayNG and consider v2flyNG as an alternative. Choose your operating system first, then check the processor architecture and package format.

Free to use Open source Graphical client

The installer contains the client only. Before connecting, prepare a subscription URL or configuration you’re authorized to use. If you already have an installation, back it up before updating.

Windows：v2rayN

Both Windows editions are available as x64 installers. For a new installation, start with the desktop edition; choose WPF if you prefer the classic layout.

v2rayN Recommended

Windows x64 · 7.24.1

Download Desktop · x64

The newer cross-platform UI is built with Avalonia. A good fit for new installations and anyone who wants a consistent workflow across desktop operating systems.

Download classic WPF · x64

The classic, stable interface for Windows. Choose it if you’re familiar with the original menu layout or prefer a traditional desktop design.

“Desktop” and “WPF” refer to different UI frameworks—not separate subscription services, and not a guarantee that one version will connect faster. Protocol support depends on the core actually in use, connection parameters, and server configuration.

Compare client editions →

Windows installation requirements

Check	Requirements and how to check
System and architecture	This page provides Windows x64 packages. Check Settings → System → About for your system type. See the selected release’s notes for the minimum supported Windows version.
Runtime dependencies	The desktop and WPF editions may have different dependencies. If a runtime error appears, address the specific message. Don’t copy dependency files from another version into the installation folder.
Folders and permissions	Extract the entire archive to a writable folder, then run the included installer. System proxy settings usually don’t require ongoing elevation; TUN mode may need additional permissions.

The download is a ZIP archive. Don’t run the program from the archive preview. Extract all files first, then install or launch the app as instructed by the package. This keeps settings, logs, and bundled files out of temporary folders. If an older version is still running in the background, exit it first to avoid a port conflict.

If the app opens normally but websites still won’t load, make sure you’ve imported a profile and selected a server, then check the system proxy settings. Installing the app and routing network traffic are separate steps. For a guided setup, follow the user guide, starting with subscription import.

macOS: Choose by chip

Open About This Mac from the Apple menu to check your chip or processor, then download the matching DMG for Apple Silicon or Intel.

v2rayN

macOS · Cross-platform desktop UI · 7.24.1

Download Apple Silicon · arm64

Choose this package if About This Mac shows an Apple M-series chip. Match the package to the chip name rather than guessing from the Mac model or purchase date.

Download Intel · x64

Choose this package if About This Mac shows an Intel processor. It uses the same client name as the Apple Silicon edition, but the executable is built for a different architecture.

Open the DMG and copy the app to Applications before launching it. Start with a standard profile import and system proxy setup. Once the connection works, consider configuring TUN mode or custom DNS.

Configure the client after installation →

macOS installation requirements

Check	Requirements and how to check
Chip architecture	Apple M-series chips use arm64; Intel processors use x64. Choose the native package that matches your chip.
macOS compatibility	Check the current release notes for the minimum supported macOS version. If the app won’t start on an older system, check compatibility before trying a different chip package.
System permissions	Traffic routing and helper components may require permission. Follow system prompts only for apps from a source you trust, and leave macOS security protections enabled.

If macOS says it can’t open the app, read the full message first. An architecture mismatch, outdated system, security warning, and damaged download are different issues. Don’t assume they all have the same cause, and avoid disabling system security checks globally to fix one app.

Before updating, quit the client and then replace the app. The Applications folder and your user data folder are separate; moving the app doesn’t move all your settings. When switching computers, use the client’s supported export method to save what you need, then check proxy and permission settings on the new system.

Android: Recommended and alternative clients

Check the core first, then the processor architecture. For most users, start with v2rayNG. Consider v2flyNG if you specifically need the V2Fly core.

v2rayNG Recommended

Android · Xray core · 2.2.6

Download v2rayNG · arm64

Most mainstream phones released after 2015 use arm64. Some devices may run a 32-bit system, so check which app architectures your system actually supports.

Download v2rayNG · Universal

Choose the universal version if you’re unsure of your device’s architecture. It supports multiple architectures, but that doesn’t mean it works with older Android versions.

A good fit for Android users with configurations built around the Xray ecosystem. After installation, import a subscription or connection details and grant VPN permission when prompted. This permission routes device traffic; it does not mean the installer includes a working server.

v2flyNG Alternative

Android · V2Fly core · 1.10.31

Download v2flyNG · arm64

For users who specifically need the V2Fly core and have an arm64 device. Choose based on configuration compatibility, not on how closely the client’s name resembles another app.

Download v2flyNG · Universal

Choose this version if you’re unsure of your device’s architecture. After importing a configuration from another client, check its protocols, transport, security settings, and routing fields.

Don’t assume Xray-specific extensions will work with V2Fly. Being able to import a subscription only means the client can read its data; it doesn’t guarantee that the active core supports every connection parameter.

Compare the Android clients →

Android installation requirements

Check	Requirements and how to check
System and architecture	First check that your device supports arm64 apps. The minimum Android version depends on the APK’s requirements; the universal version does not support every system.
Installation permission	Follow the system prompt to allow your browser or file manager to install apps. You can revoke this permission after installation.
VPN and background activity	The first connection requires VPN permission. If another VPN app is running, check for conflicts first. If the connection drops frequently in the background, review battery optimization settings.

“App not installed” can have causes beyond architecture, including an unsupported Android version, a signature mismatch with an existing app, insufficient storage, or a problem reading the installer. If you see an update conflict, back up your current settings and confirm the original app’s source. Don’t delete your only copy of configuration data just to complete an update.

Android VPN permission controls network traffic routing. When comparing clients, run only one at a time: stop the other client’s connection, then check browser access and client logs. If only some apps have problems, check per-app proxy settings before switching installers.

Linux: Choose a package format

Choose deb or rpm first, then check whether you need x64 or arm64. The desktop client requires a graphical session and is not intended for a terminal-only server.

v2rayN

Linux · Graphical desktop client · 7.24.1

Download deb · x64

For distributions using deb packages, such as Debian and Ubuntu. Here, amd64 is the x64 architecture label and is not tied to a specific processor brand.

Download rpm · x64

For systems using rpm packages, provided the dependencies are compatible. The same package extension does not guarantee support for every distribution; check the installer’s dependency messages.

Packages for arm64 devices

deb · arm64 rpm · arm64

After downloading, open the package with your system’s software installer. If dependencies can’t be met, check whether the package matches your distribution rather than forcing installation. In these package names, arm64 and aarch64 refer to the same processor architecture.

System proxy, inbound connections, and routing →

Linux installation requirements

Check	Requirements and how to check
Package format	Use the deb or rpm format supported by your distribution. Check the package metadata and installer messages for specific system library requirements.
Processor architecture	x86_64 and amd64 refer to x64; aarch64 and arm64 refer to arm64. Check your system information to confirm.
Desktop and permissions	Requires a graphical desktop and the corresponding runtime dependencies. Whether an app uses the system proxy depends on the app. TUN mode and network interface management may require additional permissions.

Linux desktop environments don’t all handle system proxies the same way. If the client’s system proxy is enabled but a program still connects directly, check whether that program reads the desktop proxy settings or has its own proxy options. Reinstalling the same package usually won’t fix an issue with which traffic is routed.

When upgrading, stick to the same package management method; avoid mixing manual file copies with system package installations. If you keep multiple client folders, confirm which instance is running and which data folder and port it uses before investigating missing settings or port conflicts.

Configuration steps after download

Installation, profile import, and traffic routing are separate steps. Check them in order to avoid mistaking a configuration issue for an installer problem.

Install and launch for the first time

Install the package that matches your system and architecture, then confirm that the app opens. If an error appears, note the full message and determine whether it relates to system compatibility, missing dependencies, or permissions. Don’t replace multiple components at once.

Import connection settings

Use a subscription or connection details you’re authorized to access, then select a specific profile after updating. Subscription URLs may contain credentials; don’t post them in public forums or share them in screenshots.

Configure traffic routing

On desktop, check the system proxy; on Android, grant VPN permission when prompted. Once the connection works, adjust routing rules, DNS, or TUN settings one at a time, keeping a way to revert each change.

Read the full user guide → Troubleshoot installation and connection issues →

Download and update FAQ

Five answers on choosing a version, architecture, configuration compatibility, and backups.

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

For a new installation, start with the desktop edition, which uses the cross-platform Avalonia UI. Choose WPF if you prefer the classic Windows interface and workflow. Both are v2rayN; a different UI framework does not mean one will always deliver better connection performance. Back up your subscriptions, routing rules, and custom settings before switching.

Should you download the arm64 or universal Android version?

Most mainstream phones released after 2015 use arm64, but make sure your system supports 64-bit apps. If you’re unsure which architecture your device uses, choose the universal version. If Android reports that the APK is incompatible, check the system version and supported app architecture instead of repeatedly installing the same file.

Can you use the same configuration in v2rayNG and v2flyNG?

Don’t assume every setting is interchangeable. v2rayNG is based on the Xray core, while v2flyNG is based on the V2Fly core. General connection details may import successfully, but support for specific protocols, transports, and extra fields depends on the core and client version. Review the settings after switching.

What else do you need after installing the client?

The client installer does not include a ready-to-use connection profile. You’ll need a subscription URL or connection details that you’re authorized to use. Import them, select a working profile, then configure the system proxy or another traffic-routing mode. For your first connection, keep the default DNS and routing settings; adjust them one at a time after confirming the connection works.

How can you keep your settings when updating the client?

Exit the client first, then use its export or backup feature to save subscriptions, routing rules, and custom settings. Confirm where the data is stored. Keep the original installer and your backup, then check the active profile, system proxy, and logs after updating. Before rolling back, confirm that the data format is compatible. Never overwrite your only backup.

V2Ray DownloadChoose a Client and Installer

Windows：v2rayN

v2rayN Recommended

Windows installation requirements

macOS: Choose by chip

v2rayN

macOS installation requirements

Android: Recommended and alternative clients

v2rayNG Recommended

v2flyNG Alternative

Android installation requirements

Linux: Choose a package format

v2rayN

Linux installation requirements

Configuration steps after download

Install and launch for the first time

Import connection settings

Configure traffic routing

Download and update FAQ

V2Ray Download
Choose a Client and Installer