Choose a download for your platform
V2Ray Client Downloads
Choose v2rayN for desktop, or v2rayNG or v2flyNG for Android. Select your platform first, then check your device architecture and package format.
Install the download and migrate your settings
A fresh install and replacing an existing version are different tasks. For a first install, check the downloaded file and confirm the app starts. If you already use a client on the device, back up its settings before replacing the package. That way, if the new version opens but your old settings aren’t carried over, you can restore them from the backup.
Make sure the installer downloaded completely
Check your browser’s downloads list to confirm the download is complete, then open its saved location. Temporary files left by a paused or canceled download can’t be installed. If the file opens as a webpage or its type doesn’t match the platform card, delete it and choose the download again for that platform. Don’t try to install it by changing the file extension.
If the system reports insufficient installation space, free up room on your local drive first. Desktop downloads may need space for the original file, extracted folder and app folder at the same time. Having room for the archive alone doesn’t mean there’s enough space to install it.
Record your working settings before switching versions
Along with your subscriptions, note the routing setup, local listening port and system proxy mode you currently use. An export may not include every preference, especially when switching versions or clients. Seeing nodes in the client only confirms they were imported; it doesn’t mean your previous routing rules were restored.
Some options are saved in the app, while others are controlled by the operating system. For example, the client sets the local listening port, but the OS controls whether the system proxy is enabled. After migrating, check both settings to spot differences more easily than by reinstalling.
Test the connection after the first launch
Import a known-working configuration, then test with just one way of routing traffic enabled. On desktop, start with an app that follows the system proxy. On mobile, check whether the system has granted the connection permission. Confirm the client is still running, then open a site you can usually reach and compare the results with the client enabled and disabled.
If only one app can’t connect, check whether it uses its own proxy or DNS settings before assuming the entire client is broken. If no apps can connect, check the node status, selected mode and first error in the logs, one at a time.
Tell installation errors from configuration issues
If the installer won’t open, check the OS version, architecture or runtime first. If the app opens but subscriptions won’t refresh, check that the subscription URL is still valid and that your network can reach the subscription service. If nodes appear but won’t connect, check the selected node, protocol settings and client logs. Troubleshoot each stage differently; there’s no need to reinstall everything.
When reporting an error, include what you were doing, the platform and the exact error message. Before sharing logs or screenshots, hide subscription URLs, connection credentials and internal network details.
Download and installation FAQs
Do I need to install both the Desktop and WPF editions on Windows?
Usually, install just one. For a first install, try the Desktop edition with its cross-platform interface. If you prefer the classic Windows interface and want to keep your familiar workflow, choose WPF. Before switching editions, quit the existing client and back up your settings to prevent two instances from listening on the same port.
Should I download the arm64 or universal Android version?
If your system supports arm64-v8a, choose the arm64 package. Most mainstream phones released after 2015 are a good place to start with this option. If you’re unsure which architectures your system supports, choose the universal package. It includes components for multiple architectures, so it’s usually larger, and it still requires a compatible Android version.
Why doesn’t the client version match the number in the installer filename?
The version shown on each card comes from the app version in the release manifest, while the download link points to a specific file for that platform and architecture. They may not update at the same time. Don’t edit the file URL based on this difference. After installing or updating, check the About page in the client to confirm the version that’s running.
How can I keep my subscriptions and routing rules when updating?
Disconnect and quit the client first, then use its export or backup feature. If it has neither, locate the saved configuration and back it up separately. After updating, check your subscription groups, active routes and local port. Backups may contain subscription URLs or connection credentials, so don’t share them with others.
There are no nodes after installation. What should I do?
The client app and node configuration are separate. If you have a subscription URL, add it in subscription management and refresh it. If you only have a single share link, use the client’s link import feature. After importing, check that the entry appears in the list, then select a node and test the connection.