Choose an Installer

Download V2Ray Clients

Choose your operating system, then check the CPU architecture. Use v2rayN for desktop and v2rayNG for Android.

Choose an Installer by Platform

v2rayN

7.24.1
Recommendedx64 · ZIP

Desktop uses a modern cross-platform interface and is the best choice for a first install. WPF is the classic, stable version for users familiar with the older interface and menus. These are two alternative versions, not a main app and a patch—choose one.

Before Installing on Windows

Windows System Requirements
ItemHow to check
System typeGo to Settings → System → About and confirm that you have a 64-bit system with an x64 processor.
RuntimeIf startup reports a missing .NET desktop runtime, check the required version and architecture in the prompt.
Unzip locationExtract all files to a separate folder your account can write to, then launch the app.

Check the full entry under “System type.” Seeing “64-bit operating system” alone isn’t enough; it doesn’t tell you whether the processor is x64 or ARM. Both builds here are x64. If your device uses a different architecture, don’t choose based on “64-bit” alone.

When switching interfaces, test the new version in a separate folder. Don’t extract both builds to the same location. Keeping the old folder helps you tell whether the new version failed to launch or an old setting caused migration trouble. After the first launch, make sure the main window and system tray work before importing a subscription. There’s no need to enable the system proxy or launch at startup yet.

If no window appears after you double-click the app, check whether it’s already running in the system tray, then look for a runtime warning from Windows. If the error says the app can’t write to its folder, move it to your Documents folder or another writable location. Don’t make running as administrator part of your routine.

From Installation to Your First Connection

Check the download before setting up your configuration

After clicking Download, check your browser’s download history to confirm the file is complete. Don’t open a temporary file that’s still being written. Filenames may include the client, architecture, package format, and release version; check the client and architecture first. The version shown on the card comes from the app listing and may not match a number in the filename. When recording the installed version, use the one shown after launching the client.

If a button opens the wrong page, return to the platform section and make sure you clicked the installer, not a platform tab. Then check whether the download hasn’t started, was interrupted, or completed. The first two are download issues; if it completed but won’t open, check the system requirements, package format, chip, and OS version. Troubleshoot each stage separately instead of downloading several builds in a row.

Keep a recoverable copy of your settings before updating

Before updating, note your current subscription groups, routing mode, and custom settings. If the client has an export or backup feature, save a copy somewhere you can access. A server’s display name alone isn’t enough: names can be duplicated and can’t be used to reimport a configuration. Don’t share backups containing subscription URLs or connection details in public comments, screenshots, or support tickets.

After updating, check that your groups are still there, then test a configuration that worked before. If neither the old nor new version connects, check your local network and subscription status first. If only the new version has issues, compare its mode, permissions, and routing options. To roll back, restore your backed-up settings; don’t mix app files and data folders from different versions at random.

Test connections and routing in order

After installation, open the setup guide and follow the steps in order: import a subscription, select a configuration, enable the appropriate mode, and test access. The client’s connection status and an app’s actual ability to access a site are different signals. The latter also depends on the app, routing rules, and DNS resolution.

For your first test, keep the default settings and use just one app and one configuration. Once the basic connection works, see the advanced guide for groups, routing, and DNS settings. When making changes, note what you changed, which apps you expect it to affect, and how to undo it. If something goes wrong, revert the most recent change and test the same app again; there’s no need to reinstall the client and change every variable at once.

Download and Installation FAQs

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

No. Choose Desktop for a first install; choose WPF if you prefer the classic interface or want to keep your familiar workflow. Back up your settings and exit the old client before switching.

How do I check which chip my Mac has?

Open the Apple menu and choose About This Mac. If it says Apple chip, choose the Apple Silicon build; if it says Intel processor, choose the Intel build.

Will the Android universal APK fix every installation issue?

No. A universal APK is worth trying when you’re unsure of your device’s architecture, but installation can still fail if Android is too old, the signature doesn’t match, or device policies block it. Check the system message before switching builds.

Does amd64 on Linux work only with AMD processors?

No. amd64 and x86_64 both refer to the same 64-bit x86 architecture, supported by compatible Intel and AMD devices. For ARM devices, choose the arm64 or aarch64 build.

Why is the server list empty after installation?

The installer includes only the client. Add a subscription URL or configuration that you’re authorized to use, follow the setup guide to import it, then select a profile and test the connection.