v2rayN
Desktop uses a newer cross-platform UI, while WPF keeps the classic Windows interface. Both support subscription imports, so choose the one that suits your workflow.
For desktop, choose v2rayN. For Android, start with v2rayNG, or choose v2flyNG if it better fits your configuration. Select your operating system below, then check the device architecture and package format.
Each option includes its system requirements and installation steps.
Desktop uses a newer cross-platform UI, while WPF keeps the classic Windows interface. Both support subscription imports, so choose the one that suits your workflow.
| Check | Requirement and where to find it |
|---|---|
| System type | Go to Settings → System → About and confirm that you have a 64-bit system with an x64 processor. |
| Installation folder | Extract the ZIP archive fully, keeping the installer and bundled files in their original folder structure. |
| Runtime requirements | If startup reports a missing runtime, check the component name, version, and architecture shown in the message. |
In File Explorer, select Extract all, then run the installer from the extracted folder. Don't double-click it in the archive preview. Keep the extracted folder somewhere easy to find, rather than running it repeatedly from a temporary folder or synced drive. After installation, launch the app from its new shortcut and check that both the main window and notification area icon open correctly.
When switching from WPF to Desktop, don't copy the old installation folder over the new one. Back up your subscriptions, custom routing rules, and local port settings in the old version, then fully exit it, including the tray instance. If your lists or rules don't appear after switching, check where the new version stores its settings and import what you need. If your browser still uses the old proxy port, check which port is actually listening instead of repeatedly updating your subscription.
In About This Mac, choose arm64 if you see an Apple M-series chip, or x64 if you see an Intel processor. Both downloads are DMG files. Choose based on the chip, not the model year.
| Check | Requirement and where to find it |
|---|---|
| Chip | Check the chip or processor in About This Mac from the Apple menu. |
| Operating system version | You can also check the macOS version in that window. If macOS is too old, switching to a different architecture package won't help. |
| Installation permissions | Make sure your account can copy apps to the target Applications folder. |
Open the DMG and drag the app to Applications, then launch it from that folder. Once the copy is complete, you can eject the disk image. Opening the app directly from the disk image isn't the same as launching it from Applications. When updating, make sure you replace the copy in your usual folder so you don't accidentally launch an old shortcut.
If macOS blocks the first launch, check the message to identify the issue. For an OS version mismatch, check the system requirements; for an architecture mismatch, choose the right package. If the device is managed by an organization, follow its installation policy. Don't weaken system-wide security settings just to install the client. If the app opens but its traffic isn't routed through the proxy, that's a configuration issue: check the proxy settings for your current network service instead of downloading another DMG.
Most mainstream phones released since 2015 can start with the arm64 package, but check that the device supports arm64-v8a. If you're unsure, choose the universal package.
Choose this client if your existing configuration is specifically set up for V2Fly. Before switching clients, make sure the target client supports your nodes' protocols and transport settings.
| Check | Requirement and where to find it |
|---|---|
| App architecture | Before choosing the arm64 package, confirm that Android supports arm64-v8a; a 64-bit processor alone isn't enough. |
| Installation requirements | Your Android version and device management policy must allow installation. If permission is required, check which installation source the system identifies. |
| Connection requirements | On first connection, approve the system VPN permission. Pause any other VPN apps while testing. |
If Android says “App not installed,” check whether an app with the same name is already installed. Updates require a compatible app ID and signing key; switching to the universal package won't change that requirement. Before uninstalling, make sure you can retrieve your subscription URL and note any manually added nodes or per-app settings. The badge on each card comes from the client listing. To check the exact version of an APK, see the downloaded filename and the app's version information.
If the app opens but stops when you tap Connect, check whether Android displayed a VPN permission prompt. If another VPN is running, disconnect it normally before testing the new client. If the connection starts but a particular app still isn't using the proxy, check whether it's excluded in the per-app settings. Installation, permission, and traffic routing are separate steps; troubleshoot the one where the failure occurs.
For Debian- or Ubuntu-based distributions, start with the deb package. For RPM-based distributions, start with rpm and check your distribution version and dependencies.
| Check | Requirement and where to find it |
|---|---|
| CPU architecture | In system information, x86_64 corresponds to x64, and aarch64 corresponds to arm64. |
| Distribution | Your package manager must support the relevant format. In an RPM filename, el10 indicates the build target; it doesn't mean the package is compatible with every RPM-based system. |
| Desktop environment | A working desktop session is required. Use your package manager to check for missing system libraries. |
Open the appropriate deb or rpm file with your system's package manager. If it reports an architecture mismatch, choose a different architecture above. If dependencies are missing, note their names and required versions, then check your distribution's package repositories. Don't change the file extension to convert formats or force the installation past missing dependencies. After installation, launch the client from your regular desktop account so you can find the same user configuration later.
Proxy settings for a desktop session and terminal processes may be configured separately. If your browser works but terminal commands connect directly, check whether the terminal tool reads proxy settings and which local port it uses. If your browser fails to connect after you close the client, check whether the desktop proxy still points to a local port that's no longer listening.
First make sure the client opens, then check your configuration and traffic separately. There's no need to troubleshoot everything at once.
You only need one. If you're new to v2rayN, start with Desktop. Choose WPF if you're familiar with its classic Windows interface or following an existing WPF guide. Back up your settings before switching versions, and run only one instance during initial testing to avoid conflicts over the same local port.
Open About This Mac from the Apple menu. If it lists an Apple M-series chip, choose Apple Silicon (arm64); if it lists an Intel processor, choose Intel (x64). The Mac's name and screen size don't indicate its architecture, and models in the same lineup may use different chips.
The arm64 package is for devices that support arm64-v8a and is usually smaller. The universal package supports multiple architectures included in that release. If you're unsure which architecture your device uses, start with the universal package. It won't lower the minimum Android version or resolve app-signature conflicts.
Back up your settings first, then check that the app, installation source, and package format match. On desktop, quit the old process before upgrading as directed by the installer. Android updates require a compatible app ID and signing key. If you see a signature conflict, keep the old version and export your settings before considering an uninstall.
The client installer and a subscription are separate. Launch the GUI client, then add your subscription URL or a single share link. Follow the client's prompts to confirm any required components. If the client opens but the list is empty, check that you used the right import option and that the subscription updated successfully; there's no need to download the installer again.