Desktop and Android Downloads

V2Ray Client Downloads

Choose a client for your operating system, then match the processor architecture and package format. If you already have settings, back up your subscription groups and custom rules first.

Windows Downloads

v2rayN

Recommended 7.24.1

The Desktop version uses a modern cross-platform interface, making it a good choice for first-time installations or for anyone who wants a consistent experience across desktop operating systems. The classic WPF version keeps the familiar Windows interface. Both downloads are x64 packages. Extract the archive fully before running the installer inside.

Windows System Requirements
CheckRequirement
System typeGo to Settings → System → About to confirm you're running 64-bit Windows and check whether your processor is x64.
RuntimeUse a Windows version that still receives security updates. If the installer reports a missing desktop runtime, check the required version and architecture in the prompt.
Before upgradingExit any old instance from the system tray and back up your settings. Closing the main window alone may leave the app running in the background.

Before installing: checks and migrating existing settings

When changing operating systems, interfaces, or clients, verify the package first, then migrate your data. Handling these steps separately makes it easier to tell whether a problem comes from installation or configuration.

Check system information, not the device model

A device name can help identify the hardware, but it can't tell you the architecture of the system currently running on it. Devices in the same product line may have different chips, and the same processor may run systems with different bitness. Check the system information on the device you're installing to, not the device you're using to view this download page. If you're transferring the installer from another computer, choose the package for the target device.

If the installer won't open, first check whether the system is blocking installation or doesn't recognize the file format. Fully extract archives, mount disk images, and open mobile installation packages with the system installer. If the system recognizes the format but reports that a requirement isn't met, check the architecture, minimum system version, and dependencies. Don't rename the file extension and try again.

Back up subscriptions, routing, and local settings

Subscription URLs, manually added servers, and local client settings are separate types of data. Refreshing a subscription can restore only the configurations provided by that subscription. It won't restore custom routing rules, DNS settings, proxy ports, or startup options you've set yourself. Before upgrading, use the client's backup or export feature if available. Otherwise, record your custom values and rule order.

Subscription URLs and exported files may contain credentials, so keep them somewhere you control. When asking for help, share only the client name, package variant, system architecture, and where the error occurs. Don't post a full subscription URL or attach an unredacted configuration backup.

Confirm the client launches before restoring connection settings

After installation, open the client and check that the interface loads without missing-component warnings. Don't enable startup launch, system proxy, and TUN all at once. Import a known-good subscription group manually, confirm it refreshes, and select the server you want before configuring the connection. If it still fails, check the subscription or connection logs instead of repeatedly switching packages.

When switching desktop interfaces, exit the old client's background process first; closing its window may leave a process holding a local port. When moving to another device, don't reuse the old device's interface names, directory paths, or local ports without checking them. Establish a basic connection with the new device's defaults, then migrate device-independent routing rules one at a time.

Troubleshoot by stage

A download interruption, installer exit, client startup failure, and subscription refresh failure are different problems at different stages. For an interrupted download, retry the same link. If the installer exits, check the system message. If the interface won't launch, check the desktop runtime. Investigate subscriptions and connection settings only after the client starts normally. The first error is usually more useful than working backward from a later follow-on message.

If the basic connection works but custom routing or DNS causes problems, undo the last change and test it separately. Clients and cores may support different setting names and rule formats. When migrating, review each setting in the new client's interface; matching menu names don't guarantee identical behavior.

See how to import a subscription and connect for the first time · Compare the three clients and their use cases

Download and installation FAQs

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

No. Choose the Desktop version for a first-time installation. Choose WPF if you prefer the classic interface. Back up your client settings and exit any running instance before switching.

Can't install the Android arm64 version. Should I try the universal version?

First check whether the issue is an architecture mismatch or an update conflict. If your system doesn't support arm64-v8a, try the universal version. If Android reports a conflict with an installed app, check that the old package came from the same source and has the matching signature. Back up your settings before uninstalling.

Can I choose a Linux package based only on processor architecture?

No. First check whether your distribution uses deb or rpm, then match the processor architecture. Even when the package format and architecture match, check your distribution version and system library dependencies.

Will installing the client automatically give me a subscription?

No. The installer provides the client only. After opening it, import an existing subscription URL into a group or manually add an existing server configuration.

Why does the version shown on the Android card differ from the download filename?

The displayed version and package URL come from different fields in the release manifest and may not be in sync. Check the specific download entry before installing, then confirm the installed version in your system's app details.