Package index Platform and architecture

V2Ray client downloads

Choose your operating system first, then match your device’s architecture. Use v2rayN on desktop; on Android, choose v2rayNG or v2flyNG based on the core your nodes require.

Windows packages

v2rayN

Recommended7.24.1

Desktop uses a new cross-platform interface and is a good fit for fresh installs or switching between desktop operating systems. WPF is the classic, stable version with the familiar Windows interface. Both downloads are ZIP archives: extract the entire archive before running the installer inside.

Before switching versions, export your current settings and quit the old client from the system tray. Don’t let both versions manage the system proxy at the same time; this can cause port conflicts or prevent your browser from connecting, even if both installed correctly.

Windows system requirements
CheckBefore you download
OS and architectureUse a supported 64-bit version of Windows. Check Settings → System → About and confirm the system type is x64.
Runtime requirementsCheck the release notes for the runtime requirements of your chosen version. If startup reports a missing component, note its name and version before addressing that dependency.

Install, update, and migrate

An installer determines whether the client can run on your device. Subscription updates and individual node connections depend on your configuration and network, and fail in different ways. Confirm the app starts before importing a configuration to avoid mistaking an installation issue for a node problem.

Check the file type after downloading

Windows downloads are archives containing an installer; don’t run files from the archive preview. macOS downloads are disk images; you can eject the image after copying the app. Open Android APKs with the system installer. On Linux, use the package manager or tool for your distribution to install DEB and RPM files. Avoid converting one format to another just to install it.

If your browser says the download is incomplete, check available storage, your network, and download history. Don’t rename an unfinished temporary file with an installer extension. If the system installer opens but can’t continue, check whether the error mentions architecture, OS version, dependencies, or permissions. Record the full message; it’s more useful for troubleshooting than simply saying “it won’t install.”

Keep a recoverable backup before updating

First, distinguish an in-place update from switching to a different version. For an in-place update, use the same download source and app identity where possible. When changing package, client, or device, don’t assume the data directory can be shared. If the client supports exporting settings, save a configuration it can import again, then separately note custom rules, proxy mode, and app exceptions you need to restore.

After saving a backup, make sure you can open it on your device and note which client and device it came from. Subscription URLs may contain credentials, and configuration backups may include node details. Don’t upload the entire file to an online converter or post it publicly. When asking for help, share your OS version, client name, and an error message with sensitive details removed.

On first launch, test one connection path

Once the app starts normally, follow the subscription import guide to add a configuration you’re authorized to use. Select one node and test it with an app that follows the proxy settings. If you change routing, DNS resolution, and proxy mode all at once, it’s hard to tell which setting fixed the issue.

Before quitting a desktop client, check whether it left a local proxy address configured. If the client has exited but the system still points to a local port, your browser may not load pages. On Android, check which VPN service is active. Installing two clients on your phone doesn’t mean you need to run both at once.

Check permissions on managed devices

Company computers, school devices, and phones with work profiles may restrict app sources, installation permissions, or system proxy changes. Ask your device administrator which apps and distribution channels are approved; don’t assume a policy restriction means the package is corrupted. If only apps in the work profile can’t connect, compare with the same app in your personal profile to help distinguish a device policy issue from a node configuration problem.

Download FAQs

Do I need to install both the Windows Desktop and WPF versions?

No. For a fresh install, start with Desktop, which uses a cross-platform interface. Choose WPF if you prefer the classic Windows interface or want to keep your existing workflow.

Which DMG should I download for my Mac?

Open About This Mac from the Apple menu. Choose Apple Silicon if it shows an Apple chip, or Intel if it lists an Intel processor.

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

The arm64 build is for systems that support arm64-v8a and is usually smaller. The universal build includes components for more architectures. It does not lower the app’s minimum system requirements.

Are amd64 and x86_64 the same architecture on Linux?

Yes, in this context. DEB packages are typically labeled amd64, while RPM packages commonly use x86_64; both refer to the 64-bit x86 platform. Choose the package format for your distribution.

What should I back up before updating?

Back up your nodes, subscriptions, and custom routing using the client’s built-in options, and note your system proxy settings. Backups may contain credentials, so store them somewhere you control.