V2Ray Client Downloads

Choose your operating system, then select a package by CPU architecture and format. Use v2rayN on desktop; on Android, choose v2rayNG or v2flyNG based on the core your configuration requires.

Windows downloads

Recommended7.24.1

v2rayN

Desktop features a modern cross-platform interface and is a good fit for first-time installations or users who switch between desktop operating systems. WPF is the stable classic version; stick with it if you're familiar with its menus and workflow. The interface version doesn't determine node compatibility. Check which core the client actually uses and whether it supports your node's parameters.

The download is a ZIP file. Extract it to a directory you can write to, then run the installer inside. Before switching interface versions, exit the running client and back up your configuration and custom rules. Don't overwrite your only working directory with the new version. After installation, open the main window and confirm your configuration works before turning system proxy or TUN back on.

Windows system requirements
CheckRequirement and how to verify
OS and architectureThis download is for 64-bit Windows 10 or 11 on x64. Check your system type and processor under Settings → System → About. ARM devices are not the same as x64 devices.
RuntimeIf startup reports a missing .NET component, check which major version and architecture it requires. WPF needs the Desktop Runtime, not just the base runtime.
Directory permissionsMake sure you can write to the extraction directory. Follow Windows permission prompts when installing to a managed directory or enabling a virtual network adapter.

Before you install or upgrade

Check the client, core, and configuration separately

The client displays nodes, manages subscriptions, and controls the system proxy. The core establishes connections using protocol parameters. Switching clients doesn't change the protocol used by the server. A configuration may appear in the list but include security-layer or flow-control fields that the current core doesn't support. For a new installation, confirm the protocol with your configuration provider, then choose a package for your device. When migrating from another client, also note the transport protocol and security layer used by a working configuration. For field details, see the protocol handbook.

Back up outside the client directory

If you have a configuration in use, note the client name, current version, and proxy mode, then back up your nodes, subscriptions, and custom routing rules. Subscriptions can usually be fetched again from the server, but manually added nodes, node labels, and rule order may not be restored. Store backups outside the app data directory; on Android, uninstalling may also delete local data. Subscription URLs and node configurations may contain access credentials. Keep backups somewhere you control, and don't post full links or configuration screenshots in public forums.

Know whether you're installing, upgrading, or switching clients

For a new installation, choose a package from the platform table. Before an in-place upgrade, exit the old client and note where it came from. Don't remove the old version just to dismiss an installation prompt. When switching clients, don't assume they use the same database format or rule syntax. Migrate using a format supported by the app, then check that transport-layer fields and routing rules were preserved. If you keep both clients temporarily for comparison, run only one at a time during testing to avoid conflicts over local listening ports or the system proxy.

Troubleshoot by where the failure occurs

If you get a format error before opening the file, first check that you've selected the right platform tab. If the installer won't run, check the OS version, CPU architecture, and installation permissions; on Linux, also check the specific dependency reported by the package manager. If installation finishes but the app won't start, look at the first runtime error instead of switching nodes. If the interface opens but the configuration doesn't work, check the node parameters, selected core, system proxy, or VPN status. Separating installation issues from connection issues makes it easier to compare results between attempts.

Verify one connection path first

After launching the client, import one configuration with clearly specified parameters. Confirm the selected node and local listening status, then choose a connection method supported by the app. On desktop, if you're using the system proxy, test with an app that follows system proxy settings. On Android, check whether the system accepted the VPN connection request. Once the basic connection works, add routing rules, adjust DNS, or enable TUN one change at a time. If you change several settings at once, it's hard to tell which one caused a connection problem.

See how to import a subscription, set up a proxy, and test your connection →

Download FAQs

Which should you choose: the Windows Desktop or classic WPF version?

For a new installation, start with Desktop for its modern cross-platform interface. Choose WPF if you prefer the classic interface or maintain an existing WPF setup. Both packages are for Windows x64. Back up your configuration before switching.

Can Apple Silicon and Intel packages be used interchangeably?

Check About This Mac: choose arm64 for an Apple chip and x64 for an Intel processor. Even if macOS can run some Intel apps through translation, use the package that matches your Mac's chip whenever possible.

Can the Android universal package fix an update installation failure?

The universal package mainly helps when choosing a CPU architecture. It won't fix a signature mismatch, an attempt to install an older version over a newer one, or an unsupported Android version. If you need to uninstall the app, export your configuration first.

Why do Linux dependency errors persist even when the package architecture is correct?

A matching architecture only means the binary targets your CPU type. Check the distribution, its version, and the dependencies available from its repositories too. For example, the RPM file on this page is marked el10; that doesn't mean it works on every RPM-based system.

Why might the version shown on a card differ from the installer filename?

The card shows the app version, while the download link points to a specific file. They may differ because their release listings are updated at different times. To confirm the installed version, check the client's About page after installation. Back up existing configuration before upgrading.

Download clients