Package index

V2Ray Client Downloads

Choose your operating system, then check the architecture and package format. Use v2rayN on desktop; on Android, choose v2rayNG or v2flyNG.

Windows client

Two x64 packages. Choose Desktop or classic WPF based on the interface you prefer.

v2rayN

Recommended7.24.1

Desktop uses the newer cross-platform interface, making it a good fit for first-time installs or switching between desktop operating systems. WPF is the classic Windows option for users who prefer familiar menus and system tray layout. These are interface choices, not different protocol versions.

Windows system requirements

CheckRequirement
System typeGo to Settings → System → About and confirm that your system is 64-bit and uses an x64-based processor.
Package formatExtract the ZIP completely before running the installer from the extracted folder.
RuntimeIf a runtime error appears at startup, install the component and architecture specified for that interface version.

Close the old client, then check that its process has exited from the system tray. Running both interfaces at once may make them compete for the same local port and overwrite each other's system proxy settings.

Choosing and upgrading packages

Architecture, package format, and interface

Architecture determines whether a program can run on your system. x64, amd64, and x86_64 are different names for the same architecture class and aren't tied to a specific processor brand. arm64, aarch64, and arm64-v8a are common names for 64-bit ARM builds across different operating systems. These labels help identify architecture, but don't make packages interchangeable across systems: Android APKs and macOS DMGs for arm64 are installed by different operating systems.

Package format determines how to open a file. ZIP is an archive, DMG is a disk image, APK is handled by the Android installer, and DEB and RPM are handled by the package manager for the corresponding distribution. The interface is a separate choice. Both Windows Desktop and WPF are x64 options; switching interfaces won't fix an architecture mismatch. Some devices have 64-bit processors but run systems that can't support the corresponding 64-bit apps. Choose a package for the environment you're actually running.

Back up your configuration before upgrading

Open the old client and note its name, current version, configuration, and proxy mode. Export and save any connection profiles and custom rules you can; if the client has a backup feature, use it to save the remaining settings. Subscription URLs may contain access credentials, and exported files may include connection details. Keep backups on your own device. Don't post the original files in public forums or share screenshots that show complete addresses.

After downloading the new package, turn off the system proxy enabled by the old client or disconnect its current session, then exit the old process. When upgrading, use the same interface and release channel as the existing installation when possible. If you're also changing devices or clients, first test importing a known-working configuration in the new environment, then migrate the rest. After installation, check the active profile, routing, and local listener settings. Keep the original backup until you've verified the configuration.

Troubleshoot by stage

Downloads, installation, startup, and connection are four separate stages. If clicking the link doesn't download a file, check whether the browser download is paused or blocked by an organization policy. If the file is on your device but the installer fails, note the system message and check the platform, architecture, and dependencies. If the client won't open, start with any startup error. If the interface opens but apps can't connect, check the active profile and proxy settings. Don't assume a connection problem is caused by the downloaded ZIP, DMG, or APK.

If the log says a local port is already in use, check whether the old client is still running in the system tray. Close its process and try again. If another app is using the port, identify it before deciding whether to change the client's listening port. If you changed the port manually, update the proxy address in your browser and other apps too; otherwise, the client may start successfully while apps continue connecting to the old port.

First connection and configuration migration

After installation, import your subscription or a single connection profile from the client menu, then select the profile you want to use. Importing and enabling are separate steps: seeing a profile in the list doesn't mean the app has connected through it. For an initial test, use an app that clearly follows the current proxy settings. Adjust routing scope after testing; changing proxy mode, rules, and DNS settings all at once makes problems harder to diagnose.

Different clients may apply different defaults to the same configuration. If only some apps behave unexpectedly after migration, first check whether they follow the system proxy, then check the routing rule selected in the client. If a configuration field is unsupported, note its name and the exact error message. Before reporting it, remove addresses, credentials, and subscription parameters. See the client comparison guide to compare clients, or the quick start guide for import, connection, and verification steps.

Download and installation FAQ

Find answers about interfaces, processors, installation messages, and connection status.

Which should I choose: Windows Desktop or classic WPF?

For a first install, choose Desktop, which uses the newer cross-platform interface. If you prefer the classic Windows menus and system tray layout, choose WPF. Both options are x64; the difference is the interface framework, not the connection protocol.

Which DMG should I download for my Mac?

Open About This Mac from the Apple menu. If Chip shows an Apple M-series processor, choose Apple Silicon; if Processor shows Intel, choose Intel. Follow the system report rather than the Mac's appearance or purchase date.

Android says “App not installed.” What should I check first?

First, make sure the APK downloaded completely, then check the system message. If the architecture doesn't match, try the universal package. If the message indicates a conflict with an existing app, check where the old version came from and back up its configuration before taking any action—don't uninstall it right away. On managed devices, follow your organization's installation requirements.

Can I use a different package format to fix Linux dependency errors?

Changing package formats is not recommended as a way to fix dependency errors. First check your distribution version and system architecture, then review the missing dependencies reported by the package installer. The RPM package is built for el10; compatibility with other distributions or versions depends on the package's dependencies and system support.

Does the client connect automatically after installation?

The installer provides only the client. On first launch, import your own connection configuration, select an entry, and choose how apps should use the proxy. After starting the client, test the connection with an app that follows that setting before expanding its scope.

See all FAQs →