The Desktop edition uses a modern cross-platform interface, making it a good fit for new installations and users who want a consistent experience across desktop operating systems. The WPF edition retains the classic Windows interface and familiar menu layout. Both are full clients; choose one rather than installing both.
System requirements and pre-install checks
Check
Details
System type
Go to Settings → System → About and confirm that Windows is 64-bit and the processor architecture is x64. Both packages on this page are for x64.
Installer format
Extract the ZIP file completely before opening the installer inside. Don’t launch it from the archive preview.
Runtime dependencies
If a runtime error appears at launch, note the version and architecture mentioned in the message, install the required runtime, and try again.
When migrating from an older version, save your configuration first and exit the old process from the system tray. Closing the window doesn’t always quit the app. If the new interface reports that a local port is in use, check whether an older instance or another proxy client is still running in the background. Start one version and verify your configuration before deciding whether to remove the old one.
Open About This Mac from the Apple menu. If it lists a Chip with Apple silicon, choose the Apple silicon build. If it lists a Processor with Intel, choose the Intel build. Use the chip information shown by macOS rather than guessing from the model’s appearance or purchase year.
System requirements and pre-install checks
Check
Details
Chip
Apple silicon uses arm64; Intel uses x64.
macOS version
Note your macOS version in About This Mac. If the system says the app requires a newer version, check the requirements for that installer.
Installer format
Open the DMG and follow the prompts to copy the app to your Applications folder. Launch it from there.
Quit v2rayN before updating, then replace the app. It’s easy to confuse the copy in the disk image with the one in your Applications folder. After replacing it, reopen the app from Applications and check its version in the client. On a work-managed device, ask your administrator about installation policies if you run into permission restrictions.
Powered by Xray. Most mainstream phones released after 2015 can use the arm64 build. If your device doesn’t support 64-bit apps or you’re unsure of its architecture, check the device specifications and consider the universal build.
Powered by V2Fly. Choose this client if you specifically need V2Fly configuration support. Before switching clients, check that your protocol and transport settings are supported. Being able to import a subscription doesn’t guarantee that every configuration in it will work.
System requirements and pre-install checks
Check
Details
CPU architecture
Choose the arm64-v8a package if your system supports it. The universal package supports more architectures, but still requires a compatible minimum Android version.
Installation
Open the downloaded APK in your system’s installer. If prompted to allow installs from this source, confirm that the source is your browser or file manager.
Connection permissions
The system usually requests VPN permission when you connect for the first time. Other VPN services on the device may conflict.
If an update fails because of a signature conflict, check where the old app and new package came from. Don’t uninstall by default: this may delete subscriptions and local settings. Keep a copy of any configuration you can re-import, then decide whether to switch installation sources.
Check which package format your distribution uses, then confirm your CPU architecture. Debian- and Ubuntu-based systems generally use DEB. For RPM-based distributions, also check the distribution release and dependencies; the file extension alone doesn’t confirm compatibility. In the RPM filename here, el10 indicates the build target.
System requirements and pre-install checks
Check
Details
CPU architecture
amd64 and x86_64 refer to x64 here; aarch64 refers to arm64.
Runtime dependencies
v2rayN is a graphical client and requires a desktop session.
System dependencies
Open the local package with your distribution’s package manager and review the dependency resolution. Don’t force installation by skipping dependency checks if conflicts appear.
After installation, launch the client from your desktop’s app menu. Before using it, check how your desktop environment handles proxy settings: some apps use the system proxy, while others have their own network settings. If a particular app doesn’t use the proxy, the installation may still be fine; first check which settings that app uses.
Install, update, and connect for the first time
Understand architecture, package format, and interface edition
Choosing an installer involves three separate decisions. Architecture determines whether the program can run on your system; package format determines which installer to use; interface edition determines the client’s layout. Confusing these can lead to questions like, “My system is 64-bit, so why can’t I install this?” Check the architecture in your system’s About page, then verify the architecture and file extension in the package name. Consider the interface edition last. When moving to another device, choose a package for that device instead of copying the executable from your old one.
Keep a restorable copy of your configuration before updating
Note which client and interface edition you use, along with the location of its configuration. If the client supports exporting, save the items you need somewhere secure and confirm that the exported file can be opened. Subscription URLs may contain access credentials, so handle backups and troubleshooting screenshots separately; don’t post a full URL in a public forum. After reinstalling, check that your subscription groups and selected connection are back before changing routing or proxy settings. This makes it easier to tell whether an issue is due to a configuration that wasn’t migrated or a setting that needs adjustment in the new version.
Verify in order: launch, import, connect
A successful installer exit only means the installation process is complete. First open the client and confirm it stays running. Then import your existing configuration and check that the expected entries appear. Finally, start a connection and test it in the app you actually use. When troubleshooting for the first time, don’t change the subscription URL, routing rules, and traffic interception mode all at once. Otherwise, even if the connection works again, it’s hard to tell which change fixed it. For detailed steps, see the configuration import guide.
Choosing an installer and troubleshooting
Download FAQs
Why might the version shown here differ from the version in the filename?
The version shown on the card comes from the app release manifest, while the filename identifies the specific installer. They may be updated at different times. To confirm the installed version, check the version shown in the client’s About page.
Do I need to uninstall the old version before updating?
For the same client and interface branch, back up your configuration first, then update as prompted by your system. Before switching interface versions, installation sources, or configuration folders, check how to migrate your data to avoid deleting local files during uninstall.
Why can’t I connect after installing the client?
Installation only prepares the client. You still need to import a valid configuration, select a connection, and grant any required permissions or enable the appropriate proxy mode. Check the client logs first to determine whether the issue is with the configuration, permissions, or connection.
Why is the installer incompatible even though my device is 64-bit?
x64 and arm64 are both 64-bit architectures, but they use different instruction sets. Check the architecture reported by your operating system, then verify that the OS version and installer format are compatible.
Where should I look if a download is interrupted or the system blocks installation?
First confirm that the browser finished downloading the file, then check the exact system error. Architecture mismatches, missing dependencies, and device management policies require different fixes. Don’t disable system protections just to install the client.