Downloads / Platform Index

V2Ray Client Downloads

Choose your OS, then select a download by CPU architecture and package format. After installation, connect using an existing subscription URL or node configuration.

  • Four platforms, three graphical clients
  • Use v2rayN on desktop
  • Choose a mobile client that supports your subscription

Choose a package by platform

v2rayN

Recommended
x64 · ZIP7.24.1

Desktop uses a newer cross-platform interface, making it a good fit for first-time installs and users switching between desktop OSes. WPF is the classic, stable version for users who prefer traditional menus and system tray controls. You don’t need both, and settings may not carry over automatically when switching.

Extract the ZIP before running the installer

Extract the entire ZIP to a local folder, then run the installer from that folder. Don’t launch the installer from the archive preview: the preview tool may extract only that file to a temporary folder, leaving it unable to find other files in the package.

If the installer reports a missing runtime, note the component name, version, and architecture shown, then install what it requests. Switching repeatedly between Desktop and WPF won’t fix missing dependencies. On a managed device, check your organization’s software installation policy rather than using another account to bypass restrictions.

If you already have a configuration, note the subscription groups, local port, and proxy mode in the old client. Back up your configuration, then exit the client from the system tray. Before importing into the new client, make sure the port is free; enable the system proxy only after importing. This helps distinguish migration issues from local port conflicts.

Windows system requirements

CheckRequirements
System typeBoth packages on this page are x64. Check System type under Settings → System → About.
RuntimeFollow the installer requirements for the version you selected.

Seeing “64-bit” isn’t enough; check the processor type too. x64 and ARM64 are both 64-bit, but they’re different architectures.

Check before downloading
Verify after installation

  • Test with only one client active per device
  • Verify the connection before changing routing rules

Handle fresh installs and upgrades separately

For a fresh install, choose one package for your device. Before upgrading, note the client name, system architecture, and original installation source, then back up your subscription and manual settings separately. You can fetch nodes again from a subscription, but locally changed routing rules, ports, and proxy modes may not be restored.

If the system identifies the downloaded file as a webpage, check whether the download finished and whether the file type matches the selected link. Don’t try to install it by changing the extension. The distinction is clear: a failed download didn’t produce the expected file format; an installation failure is reported by the system installer.

When preparing an installer for another device, choose it based on the target device’s OS and architecture. Copying the package won’t transfer the client’s subscription settings. To share configuration, use a supported import method and keep subscription URLs with access permissions secure.

Compare clients

Check the network path step by step

After the first launch, make sure the app opens normally. Then import your subscription and update it manually. Confirm the expected entries appear in the list, then test a known working node. Fetching a subscription and connecting to a node are separate requests; success with one doesn’t prove the other is working.

Start with an app where you can verify proxy settings, and change only one option per test. System proxy mode relies on apps reading the system settings. TUN uses a virtual network interface and involves system permissions and routing scope. Don’t change the mode, DNS, and routing rules all at once while troubleshooting; it’ll be hard to tell which change affected the result.

Compare the same app and destination address with the proxy on and off. If it fails only when the proxy is on, check the client logs first. If it fails both ways, start with your local network. When reporting the issue, include the error and steps to reproduce it, but remove subscription URLs and other access credentials.

View the v2rayN configuration guide

Download and installation
FAQs

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

No. Choose Desktop for a first installation. If you’re used to the WPF interface or have an existing WPF setup, you can keep using WPF. Back up your configuration and exit the old client before switching to avoid both instances competing for the local proxy port.

Will the universal APK fix every installation failure?

No. The universal package supports more CPU architectures, but it won’t fix an outdated OS, restricted installation permissions, or a signature conflict. Check the installer’s error message first, then decide whether to try another package.

How do I choose between deb and rpm?

Debian- and Ubuntu-based distributions typically use deb; Fedora- and RHEL-based distributions typically use rpm. Even with the right package format, check the CPU architecture and distribution dependencies. A file opening successfully doesn’t mean it can be installed.

Why is the list empty after I download the client?

The client installer doesn’t include subscriptions or nodes. Get a compatible configuration from your service provider or network administrator, then import it using the guide. Don’t share subscription URLs containing access credentials publicly.

The client starts, but webpages won’t load. Should I reinstall it?

Not yet. Check that the client can update the subscription, that a node is selected, and that the app is using the intended proxy mode. Note the first relevant error. If the internet still doesn’t work with the proxy paused, check your system network first.