Choose an installer

V2Ray Client Downloads

Choose your operating system, then check the processor architecture. Use v2rayN on desktop. For Android, v2rayNG is the recommended choice; choose v2flyNG if you need the V2Fly core.

Choose a package for your platform

Windows packages and system requirements

v2rayN

Recommended
Download Desktop · x64

v2rayN-Desktop-Setup-x64-7.24.1.zip

Download WPF · x64

v2rayN-Setup-x64-7.24.1.zip

The Desktop edition features a modern cross-platform interface and is a good choice for first-time installs. WPF is the classic Windows edition for users who prefer its familiar interface and workflow. Install either edition, not both.

CheckRequirements and how to check
Operating systemUse a supported version of Windows 11. For older systems, first check that the build and its runtime requirements are supported.
ArchitectureThese are x64 packages. Go to Settings → System → About to check your system type and processor.
InstallationExtract the ZIP file, then run the installer inside. If a runtime is reported missing, check that its version and architecture match the requirements.

System bitness and processor architecture are different things. A system marked “64-bit” does not necessarily have an x64 processor. If your device uses ARM, first confirm that your version of Windows can emulate this x64 build. Neither download here is a native ARM package.

Exit the old edition before installing. Close its window, then check the notification area by the taskbar. If its icon is still there, exit from the tray menu. Running both apps at once can cause port conflicts or have each app change the same system proxy settings. On first launch, check that the interface works before importing settings; don't enable both the system proxy and TUN while troubleshooting.

If the installer fails as soon as you launch it, keep the exact error message and identify which stage failed: the installer won't run, the client window won't open, or the client opens but can't connect. For the first two, check your system, runtime requirements, and installation-folder permissions. If the interface works but the connection fails, troubleshoot the profile and network instead of switching interface editions.

How to check downloads, installation, and connectivity

Make sure you downloaded the package you selected

After choosing a platform, check the filename below the button to confirm the format and architecture. If your browser still shows the download in progress, wait until it finishes before opening the file. If the saved file is a web page rather than an installer, try the download again and note whether the browser reports a network error, restricted access, or a broken link. Changing the file extension won't turn a web page into an installer.

If the manifest version on the card doesn't match the filename, distinguish the app-level version from the specific download entry. Use that entry's filename to identify the package, then compare it with your installed version before upgrading. A more recent download time doesn't mean the file is a newer version, and a package filename alone doesn't prove the running app was successfully replaced.

Preserve your existing setup when migrating

Before switching versions, note your current client, subscription groups, selected default node, and custom routes. Saving a subscription URL alone isn't a full backup: manually added nodes, local listening ports, and routing rules may need to be exported separately. Subscription URLs may contain access credentials, so keep backups on a trusted device and don't post them in public support tickets or group chats.

After installing, first check that the app launches, then confirm whether it has loaded your existing settings. If you need to restore them manually, import only what's needed and check the list before replacing the entire new directory. Keep the old version or backup until the new one launches, loads your settings, and passes a connection test; then decide whether to remove it.

Verify traffic routing after installation

An empty list is normal for a fresh client install. Import an existing subscription into the appropriate group and update it, or add a known server profile. Once nodes appear, select one and check the client logs for startup errors. A failed subscription update happens while fetching profiles; it's different from an imported node failing to connect, so troubleshoot them separately.

On desktop, distinguish a running client from an app actually using the proxy. Test with a site you know is reachable, then check whether the target app follows the system proxy settings. Before enabling TUN or changing routes, keep a verified working baseline and change one setting at a time. See the subscription import and connection guide. If the logs point to a port conflict, see how to troubleshoot local listening port conflicts.

Download FAQs

Why does the version shown in the download list differ from the package filename?

The version on the card comes from the app manifest, while the filename identifies a specific download. They may not be in sync. Check the filename for your chosen download before installing. To confirm the installed version, check the client's About page or your system's app info.

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

No. For a fresh install, start with the Desktop edition, which uses a cross-platform interface. Choose WPF if you prefer the classic interface or want to keep your existing workflow. Before switching, back up your settings and fully exit the old edition to prevent both apps from controlling the system proxy or competing for the same local listening port.

Android says the app wasn't installed. Will the universal package help?

A universal package may help only if the issue is an architecture mismatch. Also check your Android version, available storage, and whether an app with a different signature or newer version is already installed. If Android reports a signature conflict, back up your settings before deciding whether to uninstall the existing app.

How can I keep my subscriptions and routing settings when upgrading?

Exit the client before upgrading. Export your settings using the client's built-in feature, or back up its data directory as directed for your current version. Note your subscription groups, custom routes, local ports, and proxy mode. Once the new version has loaded your settings, you can remove the old directory or app.

Why is the node list empty after installation?

The installer provides only the client. First import an existing subscription or server profile. If you're using a subscription, update it and check that nodes appear in the list. Once the profile has loaded, select a node, enable the required proxy mode, and test the connection.

Download clients