Client downloads

V2Ray client downloads

For desktop, choose v2rayN. On Android, start with v2rayNG; if your existing configuration relies on the V2Fly core, consider v2flyNG. Select your operating system first, then match the download to your device architecture.

Systemdetermines compatible clients and installation methods
Architecturedistinguishes x64, arm64, and universal builds
Package formatchoose ZIP, DMG, APK, deb, or rpm for your device

Windows downloads

v2rayN

v2rayN

Recommended

Windows x64 · manifest version 7.24.1

The Desktop edition has a modern cross-platform interface, making it a good choice for first-time installs or for a consistent experience across desktop systems. Classic WPF provides the familiar Windows interface for users who prefer its menus and system tray controls. Choose one; you don't need to install Classic before Desktop.

After downloading, fully extract the ZIP to a local folder, then run the installer inside. If you're switching editions, quit the old client from the system tray first and save your settings. On first launch, leave startup launch disabled until subscriptions, nodes, and the system proxy are working as expected.

First-time setup and updates

Make sure the client starts on its own

On first launch, check three things: the main window opens, settings can be saved, and the app can be reopened after quitting. On desktop, closing the window may leave the app running in the system tray or menu bar; to restart it, choose Quit from there. If double-clicking doesn't open a window, first check whether a process is already running, then look for system prompts about dependencies, compatibility, or device policies. There's no need to change nodes or routing rules yet—the app hasn't reached the point where it handles traffic.

Tell subscription links apart from single-node links

A subscription URL fetches a list of nodes. Usually, you need to add a group first, then update it manually. A single-node link describes just one node; import it using the client's clipboard or QR code option. After importing, check that the node appears in the list, then select it as the active node. If an update reports success but the list is still empty, make sure you're viewing the group you just updated, then check that the URL was copied in full, the subscription hasn't expired, and its response format is supported by the client. Subscription URLs may contain access credentials; don't post them in public comments or screenshots.

Desktop and Android clients use different menu labels. Follow the subscription import steps for guidance. Still deciding which Android client to use? Compare their cores and use cases in the client comparison, then return here to download the right package.

Test the connection before changing proxy settings

Test with a known-working node before changing settings, and adjust one thing at a time. On desktop, after enabling the system proxy, test with a browser that respects system proxy settings. Other apps may use their own network settings, so browser access doesn't mean every app uses the same route. On Android, the first connection usually triggers a system VPN confirmation. If another app is already using the VPN, disconnect it before retrying.

If your local network stops working after you enable the proxy, restore the previous proxy state first, then check the client's startup and connection messages. Change one setting at a time and test again—for example, switch the active node and see whether the problem follows it before changing proxy mode. Changing several options at once makes troubleshooting harder. Once the connection is stable, add rules using the routing and split tunneling guide, then test requests that should connect directly and through the proxy.

Keep a restorable backup before updating

If the old client still opens, use its export or backup feature first. If it doesn't have one, note your subscription groups, active node, proxy mode, ports, and custom routing rules, and safely save any configuration data you need. When updating the same client, check the platform, architecture, and distribution channel. When switching clients, import a subscription or individual node first, then reconfigure local settings one by one. Don't overwrite the new app's configuration folder.

After upgrading, check the installed version on the About page. Then confirm that subscriptions update, nodes can be selected, and the proxy can be enabled and disabled. Finally, check startup launch, automatic subscription updates, and custom rules. If you need to roll back, first confirm whether the older version can read settings written by the newer one. If you're unsure, keep both backups and don't overwrite either with the other.

Download and installation FAQs

Installing on Windows for the first time: Desktop or Classic WPF?

Both are x64 versions of v2rayN. For a first install, start with the Desktop edition, which uses a modern cross-platform interface. If you rely on the classic Windows menus or have workflows built around the older interface, use the Classic WPF edition.

Will the Android universal build fix every installation problem?

The universal build supports multiple ABIs, so it can help with some architecture mismatches. If you see a signature conflict, a downgrade warning, or an unsupported Android version, follow the prompt; switching architectures won't fix these issues. Back up your settings before uninstalling an older version, as uninstalling may erase app data.

Why might the version on a download card differ from the package filename?

The card shows the app's manifest version, while the filename identifies a release package for a specific platform and architecture. They come from different fields and may not match. Use the actual file linked from your selected download option, and check the installed version on the old client's About page before upgrading.

Why is the node list empty after installing the client?

The installer includes the client app, not subscriptions or nodes. To use an existing subscription URL, add a subscription group in the client, then update it. For a single node share link, use the clipboard import or QR code option.

Can I copy the entire configuration folder when switching clients?

Configuration layouts can vary between clients, cores, and releases. Back up your current settings first, then import subscriptions or nodes using a method supported by the new client. Check proxy mode, bypass rules, and local ports individually; don't assume your old settings were migrated.

Download v2rayN