CLIENT PACKAGES / INSTALLATION
Choose your operating system, then check the processor architecture. Use v2rayN on desktop; for Android, v2rayNG is the recommended choice, though you can choose v2flyNG if it better fits your configuration.
After installation, import a subscription or share link. See the setup guide → for instructions.
Desktop uses a newer cross-platform UI and is a good choice for a first installation. WPF retains the classic interface and familiar workflow. Both links below are x64 installers; choose one.
The download is a ZIP file. Extract it fully, then run the installer inside. Do not launch it from the ZIP preview.
Open Settings → System → About and check that the system type is x64. The installer architecture must match your system; knowing the processor brand alone is not enough to choose a package. The Windows downloads listed here are for x64. Do not edit the download URL based on the filename.
| Check | Requirements and steps |
|---|---|
| Operating system | Use a Windows version that still receives security updates. Check the installer for the minimum supported version. |
| Processor architecture | Use an x64 system; confirm this in System Information. |
| Runtime | Install the runtime prompted for by your chosen version. Do not mix components built for different architectures. |
| Permissions and location | Choose an installation path you can read and write to. TUN may require administrator permissions. |
Extract the files to a permanent folder, not a temporary downloads cache. After installation, launch the app without elevated permissions first and confirm that the main window and settings open. If a runtime is missing, note the component name and architecture shown in the prompt, then install it. Downloading the same package again usually will not resolve a missing dependency.
On first launch, check the local listening port before importing a subscription. If switching from WPF to Desktop, export your existing configuration first and keep a recoverable backup. Menu locations may differ between interfaces; after restoring, check subscription groups, routes, and shortcuts one by one. Do not run both versions at once, as they may conflict over the local port.
Choose arm64 for Apple Silicon and x64 for Intel Macs. Open the Apple menu and select About This Mac, then check the Chip or Processor field before downloading.
Both links are DMG disk images. Choose based on your Mac's chip, not its appearance or purchase year.
When the download finishes, open the DMG and copy the app to Applications, then launch it from there. Running it directly from the mounted disk image can complicate troubleshooting updates and app permissions. Once the copy is complete, eject the disk image and use the installed app.
| Check | Requirements and steps |
|---|---|
| Operating system | Use a macOS version that still receives security updates. Check the app's compatibility notice for the minimum supported version. |
| Chip type | Apple Silicon uses arm64; Intel uses x64. |
| Installation location | Copy the app to Applications and make sure you have write access to the destination. |
| Network permissions | Follow system prompts to review and grant the permissions needed to change proxy settings or enable TUN. |
If macOS blocks the first launch, confirm the file source and selected architecture, then review the prompt under Privacy & Security in System Settings and follow Apple's instructions. Do not disable system-wide security just to launch an app. If your device is managed by an organization, check whether its policies allow network setting changes.
Start with a minimal setup: import one subscription, select a server, enable the system proxy, then test with a browser that follows system proxy settings. Keep the default local port for now so you can compare the steps with the guide. Configure TUN only if you need to route traffic from other apps; this keeps installation issues separate from routing issues.
Uses the Xray core. Most phones released since 2015 should start with arm64; consider the universal build if the device architecture is unclear or the system reports an incompatibility. Check your device's system for actual support.
The version shown on the card may not match the current package name due to release timing. Check the version shown by Android's installer before installation, then confirm the installed version in App info.
Uses the v2fly core and is suited to configurations specifically designed for it. Before choosing this client, confirm that your subscription's protocols and transport settings are supported. Similar client names do not guarantee identical features.
Each client manages its own configuration. v2rayNG is usually the right place to start; choose v2flyNG only if you specifically need the v2fly core. The universal build supports multiple architectures, but does not offer better connectivity or increase server bandwidth.
| Check | Requirements and steps |
|---|---|
| System compatibility | The Android installer checks the minimum system version required by the app. |
| App architecture | Start with arm64 on most devices. If unsure, check your device details or choose the universal build. |
| Installation permission | Allow app installation only for the browser or file manager you use to open the APK. |
| Connection permission | On first connection, approve Android's VPN request. Usually, only one VPN service can run at a time. |
Open the APK from your browser's download list or a file manager, check the app name, and continue with installation. If Android says the app wasn't installed, check storage, architecture, and system version, then look for an existing app with a different signature. Don't uninstall the old version right away: export its configuration first, or locally saved subscriptions and rules may be deleted along with it.
After installation, import a subscription, select a server, tap Connect, and approve the system permission request. If the connection drops frequently when you switch apps, check battery optimization and background activity restrictions. If the app launches but cannot connect, troubleshoot the configuration, server, and network instead of repeatedly changing the installer.
Choose deb or rpm according to your distribution's package system; the primary downloads are x64. Debian- and Ubuntu-based systems typically use deb. For distributions using RPM package management, choose rpm and check that your system dependencies meet the package requirements.
For arm64 devices, use the matching package:
Check the processor architecture in your system's About or hardware information, then confirm which package manager your distribution uses. x64 may appear as amd64 or x86_64; arm64 may appear as aarch64. These names identify processor architectures, not different client feature sets.
| Check | Requirements and steps |
|---|---|
| Desktop environment | Requires a Linux desktop session that can run graphical applications. |
| Package format | Choose deb or rpm as supported by your distribution. Changing a file extension does not convert its format. |
| Processor architecture | Use the package that matches your x64 or arm64 architecture. |
| Dependencies and permissions | Check dependencies with your graphical package manager. Follow system prompts for installation and TUN permissions. |
Open the package with your system's graphical installer and review the dependency and compatibility notices first. If the package manager reports unmet dependencies, check your distribution version and software sources; do not force installation while ignoring dependencies. A matching package format does not guarantee that a package will run on every distribution, so check its system library requirements.
After installation, launch the app from the applications menu. Import a configuration and test the local proxy first, then check whether your desktop environment uses system proxy settings. Support varies across desktops and apps; if one app does not use the proxy, that does not mean the client failed to install. If you need TUN, check permissions and routes, and avoid changing multiple network settings at once.
INSTALLATION NOTES
Test installation, configuration, and connectivity separately to avoid unnecessary reinstalls. First, make sure the app launches, then check your subscription and proxy settings.
When upgrading an existing client, use its backup or export feature to save your configuration first. Include subscription groups, manually added servers, custom routes, local listening ports, and app-specific routing settings. Exported files may contain access credentials; store them securely and do not post them publicly or put them in shared folders.
Next, disconnect and quit the client. Desktop apps may keep running in the system tray after the main window closes, so confirm all background instances have exited before updating. Keep the existing configuration and installation details for comparison, and do not delete the old backup until you have confirmed the new version works.
After opening the client, check the source and validity of the subscription URL or share link before importing and updating it. Select a server as the active one and make sure no other program is using the local listening port. A successful subscription update only means the configuration was fetched and parsed; it does not guarantee every server in it can connect.
On desktop, enable the system proxy and test with a browser that follows system proxy settings. On Android, approve the system VPN request when connecting. Keep routing simple until the basic connection works, then add custom rules. Do not run multiple proxy clients at the same time, as this can cause port or routing conflicts.
Separate these four symptoms: the app will not start, the subscription will not update, the server will not connect, or only some apps cannot access the network. For launch failures, check dependencies and permissions. For subscription issues, check the URL and expiration. For connection failures, check server settings and network access. For app-specific issues, check system proxy settings, DNS, and routing rules.
When reviewing client logs, note the error type, time, and action that triggered it. Remove subscription URLs and server credentials before sharing logs. Before switching clients, check that the new client supports the protocols and transport settings your configuration requires. Similar interfaces do not mean different cores support every configuration in the same way.
PACKAGE / UPDATE / SETUP
Quick answers about packages, architecture, and updates. For connection and routing issues, see the Help Center.
The installer contains the client, not a ready-to-use server configuration. On first launch, import a subscription URL or share link that you manage or are authorized to use, then select a server and set the proxy mode. Subscription URLs may contain access credentials, so do not share them publicly.
For a first installation, start with Desktop, which uses a newer cross-platform interface. WPF is the classic, stable edition for users who prefer its familiar interface and workflow. They are separate interface versions, so you do not need both. Back up subscription groups, routing rules, and custom settings before switching.
Most phones released since 2015 can start with arm64, but check which app architectures your device actually supports. If Android reports an architecture mismatch, try the universal build, which supports multiple architectures and is usually larger. If installation fails, also check available storage, system compatibility, and the signature of any existing app.
Use the client's backup or export feature to save subscription groups, custom routes, server settings, and local port settings. Then disconnect and quit the app. Before installing over the existing version, verify the client, architecture, and installation location. After updating, check subscriptions, the active server, system proxy, and TUN status.
Check your browser's download list to see whether the download started or is waiting for you to confirm a save location, then check disk space and your connection. If it was interrupted, click the original download link again. If the version shown on the page differs from the filename, check the card details and downloaded file separately; the filename alone does not confirm the installed version.
First, confirm that you imported a configuration and selected an available server. Then check that the system proxy is enabled and that your browser follows system proxy settings. The system proxy only affects apps that use those settings. To route more app traffic, configure TUN using the guide and check permissions and routes. Avoid running multiple proxy tools at the same time.