Clients and Downloads

V2Ray Client Downloads

For desktop, choose v2rayN. For Android, choose v2rayNG or v2flyNG. Select the device you want to install on, then choose the file that matches its CPU architecture.

Download selection steps
  1. Choose an operating system
  2. Check the CPU architecture
  3. Download the matching package

Choose by operating system

v2rayN

7.24.1
RecommendedWindows x64

Desktop uses a newer cross-platform interface, making it a good choice for first-time installs or anyone who wants a consistent experience across desktop systems. Classic WPF keeps the familiar, well-established Windows interface for users who prefer its menus and system tray controls. Both versions support subscription imports, so choose the one that suits your preferences.

Both download options provide a ZIP archive. Extract it to a local folder, then run the installer from the extracted directory. Don't launch it from the archive preview. If the installer can't find files in the same directory, check that you didn't extract only the executable.

Windows system requirements
ItemRequirements
Operating systemWindows 10 or 11 on x64. These installation steps may not apply to older versions of Windows.
ArchitectureCheck under Settings → System → About. Don't rely on the processor brand alone.
File format.zip; extract the archive, then run the installer inside.

Before updating, quit the old version from the system tray; closing its window isn't enough. If startup reports a missing runtime component, note the full message and check the requirements for that version. Downloading the same archive again usually won't fix a runtime issue.

Package selection and installation

From download to first connection

Check package selection, startup, and import separately. If something goes wrong, identify which step failed first.

Confirm which device you're installing on

Choose a package for the device that will run the client, not the device you're using to view this page. For example, if you transfer an Android installer from your computer to your phone, check the phone's Android version and architecture. For a virtual machine, check its operating system. Even computers in the same home running the same OS may use different architectures, such as x64 and arm64, so don't assume one package fits them all.

Check the downloaded filename and extension. Different package types may use the same client name, so keep installers separate from configuration backups. If the browser says the download was interrupted or is still in progress, let it finish before opening the file with the system's default installer. If the installer has already shown an error, note the exact message; that's more useful than trying every download option.

Back up your settings before updating

If the old client still opens, use its export or backup feature to save your settings. Note your subscription groups, current routing mode, and any manually added nodes. A subscription URL can restore subscription-managed nodes, but not local notes, custom rules, or individually imported nodes. When switching devices or clients, import everything into the new setup and verify it before deleting the old configuration.

Subscription URLs, node links, and backup files may contain access credentials. Keep backups somewhere only you can access. When asking for help, share your operating system, package type, and error message, but redact subscription URLs, node addresses, and QR codes from screenshots. If you're using the system proxy, turn it off in the client before quitting the app to prevent the system from pointing to a local proxy that is no longer running.

Import subscriptions after confirming the client starts

Open the client first and make sure its main window loads. If you have a subscription URL, add it under Subscriptions and refresh the group. If you only have a link for a single node, import it from the clipboard. If the list is still empty after an update, check whether you copied a subscription URL or a single-node link, then review the update log. Reinstalling the client isn't necessary just to retry.

Once the list appears, select a known working node and test it using system proxy settings or the client's connection steps. For your first test, check one mode at a time. If a browser works but another app doesn't, see whether that app follows the system proxy. Once the basic connection works, adjust TUN or routing settings; changing them one at a time makes it easier to identify what caused a problem.

Quick start guide · Installation and connection troubleshooting

Download help

Frequently asked questions

Package types, in-place updates, and version labels.

Do I need to install both the Desktop and classic WPF versions of v2rayN?

Install either version. Choose Desktop for a fresh install. If you already use a WPF setup and prefer the classic interface, stick with WPF. Before switching, back up your settings in the old client and close it before installing the new version. When you first open the new version, check that your subscription groups, routing, and proxy settings are intact before removing the old one.

Will the universal Android version fix every installation problem?

The universal version is useful when you are unsure of your device's architecture, but it won't fix an outdated Android version, low storage, or a signature mismatch. If Android reports a conflict with an existing app, check whether the update comes from the same distribution channel. Before uninstalling and reinstalling, back up your subscriptions and local nodes, since uninstalling may erase app data.

The download page shows a different version from the package filename. Which should I trust?

The version label comes from the client's release manifest, while the filename identifies the package linked from the selected download option; they may temporarily differ. Before installing over an existing version, check the version and architecture in the filename. To confirm which version is actually running, open the client's About page after installation. Don't rely on the webpage label alone to confirm an update.

Do I need a subscription URL after installing the client?

The installer contains only the client, not a subscription or working nodes. If you have a subscription URL, add it and refresh the list. If you only have a link for a single node, import it directly rather than creating a subscription. After importing, select a node and enable the proxy mode you need for your device and apps.

The browser finished downloading the installer. Why won't my system open it?

Check the file extension and platform first: extract archives fully, mount disk images, open Android installers on your phone, and use the appropriate package manager for desktop Linux packages. If the system reports missing dependencies, an architecture mismatch, or a blocked source, troubleshoot the stated issue. Don't change the file extension or disable system protections to force the installation.