Selection guide
Client, architecture, and package format
These three criteria are independent: the client determines the interface and core path, the processor architecture determines the binary type, and the package format determines how the system installs it. Confirm them in order for a clearer choice.
01
Choose the client for your device first
Use v2rayN on Windows, macOS, and Linux desktops; for regular Android use, choose v2rayNG, and choose v2flyNG when you need the V2Fly core. Do not identify the platform by similar names alone: clients in the same ecosystem target different operating systems and interaction models.
02
Then confirm the processor architecture
x64 is common on Intel and AMD desktop PCs; arm64 is common on Apple M-series Macs, recent Android devices, and some ARM Linux devices. With a mismatched architecture, the installer may refuse to run or the system may report that the app is incompatible with the device.
03
Finally confirm the package format
This page provides compressed installers for Windows, dmg for macOS, apk for Android, and deb or rpm for Linux depending on the distribution. The file format only describes installation; it does not indicate different client features. Core settings remain consistent for the same client.