Download V2Ray clients

Installing and switching between Desktop and WPF

For your first install, try Desktop. Fully extract the downloaded archive to a writable folder, then run the installer from there. Don’t launch it from an archive preview window; files in a temporary folder may not be available. If prompted to install a runtime, follow the installer’s instructions, then restart the client.

If you already use the WPF edition and your settings are stable, you can keep using its familiar interface. Both editions manage subscriptions, nodes, and routing, but menus, settings, and configuration storage may change between versions. Before switching, use the client’s backup or export feature. Don’t copy every file from the old folder over the new one, and don’t let both clients manage the system proxy at the same time.

After the first launch, import a subscription and select an active node before enabling the system proxy. Look into TUN only if you need to route apps that ignore system proxy settings. If the window opens but the core won’t start, check the client logs for port conflicts, configuration errors, or permission issues. Reinstalling the interface repeatedly usually won’t fix a configuration error.

Identify your chip and launch the client

Open About This Mac. If the Chip field shows an Apple M-series name, choose the Apple Silicon installer. If the Processor field shows an Intel processor, choose the Intel installer. Don’t rely on the device’s appearance or purchase year. A native installer for your processor makes compatibility issues easier to troubleshoot and helps avoid confusing an architecture mismatch with a subscription problem.

Open the downloaded disk image and copy the app to Applications, then launch it from there. If macOS displays a security alert, read the reason and follow the steps provided in Privacy & Security in System Settings. Don’t disable system security globally just to launch one app. If your device is managed by an organization, check whether installing apps and changing network settings are allowed.

After installation, check the client’s menu bar status, import a subscription, and select an active configuration. System proxy settings affect only apps that follow them, so test with a browser before checking other apps. Restore proxy settings before quitting or switching clients. When multiple tools manage the same system proxy, they can overwrite each other’s settings and cause seemingly random connection problems.

Choosing an architecture, granting install permissions, and understanding cores

Most newer phones can use an arm64 package, but a 64-bit processor doesn’t necessarily mean the operating system can install every 64-bit app. If you can’t confirm your device’s architecture, try the universal version; the installer will select suitable components. If you see “App not installed,” also check available storage, Android compatibility, whether an existing app has a different signing key, and whether you’re trying to install an older version.

Grant only the permissions needed by the download or file manager you’re using, and revoke them after installation if you prefer. Once you launch the client and import a configuration, Android will ask for VPN permission the first time you connect. This sets up a local virtual network interface; it doesn’t mean you’re connected to a remote service. Check the active node and logs, then test app connectivity.

Choose between v2rayNG and v2flyNG based on core capabilities and configuration compatibility, not because they’re interchangeable shells. For REALITY, specific flow control, or newer transport fields, confirm that the selected client core supports the configuration syntax. A successful import only means the client read the configuration; it doesn’t guarantee every feature will work.

If the connection drops only after the app moves to the background, check battery optimization and background activity restrictions. Allow the client to run in the background if needed. Don’t run another app that also needs the VPN interface. Before switching clients, stop the existing connection and save your subscription groups and routing rules. Restore them one at a time in the new client to help pinpoint issues.

Package formats and desktop proxy settings

Check your distribution and processor architecture in system information before choosing an installer. deb and rpm are package formats, not feature tiers. x64 and arm64 are processor architectures, not newer and older versions. Check these requirements separately to avoid downloading a package with the right format but the wrong architecture.

Open the downloaded package with your distribution’s software installer. Review the dependency resolution before installing. If the installer reports that a required runtime is unavailable, don’t force the installation or replace system libraries from an unknown source. Check your distribution version, desktop environment, and the package requirements; being part of the same distribution family isn’t enough to ensure compatibility.

After launching v2rayN, import a configuration and check the local listening port. Desktop environments vary in their support for system proxy settings, and some apps have their own proxy options. Browser access doesn’t mean every app is using the proxy. Check whether each target app follows the desktop proxy before deciding whether to configure TUN. Before enabling a virtual interface, note your existing routes to avoid conflicts with other network tools.