V2Ray Download
Client installers

System requirements and installation prep

After the first launch, make sure the interface opens normally before importing a subscription or share link. Importing adds configurations to the list; you still need to select one to use. Then set the system proxy and routing mode: the system proxy determines whether apps send requests to the client, while routing determines how those requests are handled. They’re separate settings, and a successful installation doesn’t mean the connection is working.

Before updating an existing installation, exit the old process from the system tray to prevent two instances from competing for the same local listening port. Save any custom routing, DNS, or configuration files separately before updating. Menu locations may differ between the desktop and WPF versions; search by feature name when switching instead of following an old screenshot step by step. If startup fails, note the exact error message and follow the relevant steps in Troubleshooting.

System requirements and first launch

Don’t keep running the app from the mounted disk image after installation. Move it to a permanent location to keep updates and permissions consistent. If macOS blocks the first launch, check the download source, selected architecture, and system alert, then look up the relevant guidance in System Settings. Don’t disable system security entirely just to launch the app. If macOS says the app isn’t compatible with your system, check the version requirements and chip architecture first.

Importing a configuration into the desktop client doesn’t mean every app is using the system proxy. Browsers usually follow system settings, but some terminal tools and apps have their own proxy options. After setup, test with an app that’s known to follow the system proxy before configuring others. If you need broader traffic routing, review TUN permissions and routing settings. Avoid combining multiple traffic-routing methods, which can make troubleshooting harder.

System requirements and Android permissions

If the installer says “App not installed,” check for an architecture mismatch, unsupported Android version, signature conflict, or blocked downgrade. If an app with the same name is already installed, don’t delete it right away. Export anything you want to keep, then decide whether you need to change installation sources. Uninstalling may erase local settings, and reinstalling won’t restore custom settings that weren’t backed up.

After installation, add a subscription URL you’re authorized to use in the subscription group settings and update it, or import a share link from the clipboard. Confirm the selected configuration before connecting. On the first connection, system VPN authorization and subscription import are separate steps. If you want to route only selected apps through the proxy, look into per-app proxy settings rather than repeatedly switching installer packages. If the connection drops in the background, check battery optimization and background activity restrictions.

Choose between v2rayNG and v2flyNG based on configuration compatibility, not name or installer size. For REALITY and other configurations, check protocol and core support; don’t assume the same subscription will work the same way in both apps. See the core selection guide for details, and the Android setup guide for importing and permissions.

System requirements and package compatibility

Before downloading, check your distribution and hardware in the system’s About settings. Install the package using your system’s software installer and review any dependency prompts. If it reports missing system libraries or requires newer system components, first confirm that the package matches your distribution; don’t force past dependency checks. Check the target listed in an rpm filename against your actual system—rpm format alone doesn’t guarantee compatibility.

After launching the client, import a subscription and select a configuration, then check whether your desktop environment uses the system proxy. Apps differ in how they support proxy settings; if one browser works but another app doesn’t, check the app’s own proxy options. Set up permissions and routing for TUN only if needed. Keep permission errors, configuration issues, and apps that aren’t using the proxy as separate troubleshooting questions.