Client Releases / Platform Selection
V2Ray Client Downloads
For desktop, choose v2rayN. For Android, v2rayNG is the recommended choice; v2flyNG is another option if it better fits your configuration. Select your OS first, then check the processor architecture and package type.
Installation Order / Configuration Migration
Three things to check before installing
Check OS version and architecture separately
If installation fails, first determine whether you chose the wrong package or the device doesn't meet the runtime requirements. The OS version determines which APIs and runtime libraries are available; the architecture determines whether the included program can run in your environment. Neither tells you the other. Two 64-bit computers may use different architectures—one x64, the other ARM64. Even with the same processor, different OS versions can support different client releases. When helping someone remotely, ask them to check the target device's details instead of guessing from your own device model.
Match the package format to the installation method
The file extension determines which program handles a download. Extract ZIP files, open DMG disk images, install APK files through Android's installer, and use the relevant package manager for deb and rpm files. Seeing a download in your browser's history doesn't mean installation is complete. If the system says it can't open a file, check that the download finished and that the format is supported by your OS. Don't rename an extension to try installing a package on another platform; changing the name doesn't convert the package or its executable.
Know whether you're installing, upgrading, or switching clients
A new installation requires the right package and runtime environment. An in-place upgrade also depends on the version, release channel, and existing data. When switching clients, check configuration compatibility separately; being able to import a subscription doesn't mean every entry will work. If the old client had multiple groups, note the selected group, frequently used servers, proxy mode, and custom routing rules. Store backups containing subscription URLs or authentication details somewhere secure; don't upload or forward them with troubleshooting screenshots.
Verify after first launch and upgrades
After installation, make sure the interface opens normally, then test with one configuration you're authorized to use. Don't change subscriptions, routing rules, and traffic interception mode all at once, or it will be hard to identify the cause if something fails. If you used the system proxy before, you can keep using it after upgrading to test apps that follow system proxy settings. Test TUN separately if needed. These modes route traffic differently: a successful browser test doesn't prove other apps use the same route.
During migration, check in this order: group is visible → entries are readable → one connection works → the target app can access the network. If entries don't appear after a subscription update, check the import or update logs first. If an entry appears but won't connect, check its protocol, transport, and security layer. If the client reports a connection but nothing changes in the target app, check the proxy mode and which routing rule applies. Troubleshooting these three layers makes it easier to keep existing settings and diagnostic clues than simply reinstalling.
If the problem started after an upgrade, note the step where it occurred and any system message, then compare the settings with your backup. On desktop, check whether the old process is still running in the system tray and whether the system proxy is restored as expected when you quit. On mobile, disconnect the previous client before switching. For step-by-step instructions, see the subscription import and connection guide. If an entry may be incompatible with the core, see the protocol and core reference.