V2Ray Client Download

Both the Desktop and classic WPF editions let you manage subscriptions, choose servers, and configure the proxy. The main differences are the UI technology and layout. Desktop uses a modern cross-platform interface, with menus arranged differently from the classic edition; WPF retains the familiar Windows workflow. The edition name says nothing about server quality and doesn't replace checking your protocol settings.

Extract the entire archive to a writable location, then run the installer included in the package. Don't launch the app from your archive utility's preview window, where associated files may not be extracted correctly. Keep the installation path stable to make upgrades and configuration files easier to manage. If you see a runtime warning, follow the installer or system instructions; don't look for replacement files on untrusted sites.

On first launch, add a subscription group and update it. Select a valid server, enable automatic system proxy configuration, and choose a routing mode. The system proxy only affects apps that follow that setting; it doesn't route traffic from every app. Before switching editions, back up your configuration and exit the old client. Running both at once can cause local port conflicts or competing proxy settings.

Open About This Mac and check the chip or processor listed. Apple silicon uses arm64; Intel uses x64. Don't guess based on the device's appearance, purchase year, or macOS version—different models in the same product line may use different processors. Choosing the native package for your architecture can reduce reliance on compatibility layers.

When the download finishes, open the disk image and follow the included instructions to move the app to your Applications folder. Launch it from there. Don't keep running it from a temporarily mounted disk image; eject the image after installation and closing any related windows. If macOS shows a security warning, check the file's source and the warning, then follow the system's authorization steps. Don't disable system protection just to launch an app.

After importing a subscription, select a server and routing mode, then check that the system proxy is set for the network service you're using. Wi-Fi and Ethernet may have separate proxy settings, so check again when you switch networks. TUN mode may require additional permissions and take over network traffic. Start with the system proxy to make installation, configuration, and app traffic issues easier to distinguish.

On Linux, check both your distribution's package system and your processor architecture. Choose DEB for distributions that use DEB packages and RPM for those that use RPM. x64 may appear in filenames as amd64 or x86_64; arm64 may appear as aarch64. The file extension alone doesn't guarantee compatibility—package dependencies and system component versions matter too.

After downloading, open the package with your distribution's software installer or package manager so it can handle dependencies and keep an installation record. If it reports missing dependencies, check which packages and versions are required. Don't force past dependency errors or casually add repositories for other distributions. This is a desktop client and requires a working desktop session; headless machines with only a remote command line aren't covered here.

After launch, import a subscription and check the client's local listener and your desktop environment's proxy settings. Different desktop environments, browsers, and terminal apps may handle system proxies differently, so a running client doesn't mean every app is connected. For your first test, use an app known to follow the system proxy. If you need TUN mode, consult the advanced documentation for permissions, routing, and DNS handling rather than changing several layers of network settings at once.