Client setup / package selection
Choose v2rayN for desktop systems and v2rayNG for Android. Confirm your operating system first, then download the file that matches your processor architecture.
Import a subscription and connect after installation →Each platform may offer different interfaces, chip architectures, or package formats. Version details appear below the client name.
v2rayN offers two interfaces: Desktop and classic WPF. Both downloads are for x64 systems. The main differences are the UI technology and layout—not the proxy protocols. For a first install, choose the interface used in your guide. If you already have a configuration, back it up before deciding whether to migrate.
Desktop offers a newer cross-platform UI for people who use multiple desktop operating systems and want a consistent workflow. WPF is the classic, stable version for users accustomed to existing Windows instructions. Check the current installer prompts for the specific OS version and runtime requirements for each version.
If security software blocks the file, check its source and review the specific alert. Pause installation if the alert is unclear rather than disabling all protection. Once the app starts, you can set up subscription imports, the system proxy, and routing.
Windows x64 · Desktop has a newer cross-platform interface; WPF is the classic, stable interface. Both downloads are ZIP archives.
Extract the archive before running the installer. Before switching interfaces, export your existing configuration and note your subscription groups and custom routing rules.
| Check | What to look for |
|---|---|
| Processor architecture | Both downloads on this page are x64 |
| Desktop environment | Windows graphical desktop; check the installer for version-specific requirements |
| Runtime | Desktop and WPF may have different requirements; install any components listed as missing |
| Folder permissions | The extraction folder must allow read and write access; the configuration folder must allow settings to be saved |
v2rayN on macOS uses its desktop interface. Before installing, identify whether your Mac has Apple Silicon or an Intel processor. Open About This Mac from the Apple menu and check the Chip or Processor field: Apple M-series means Apple Silicon; an Intel processor means you need the Intel build. Don't rely on the device name alone.
The two DMG files contain builds of the same client for different processors. Choose the native arm64 build for Apple Silicon and the x64 build for Intel. Processor architecture is separate from connection protocol, so switching builds won't fix an incorrect subscription URL or server parameter.
Troubleshoot installation errors separately from network permissions. “App can't be opened” usually occurs during startup. If the app is running but your browser isn't using the proxy, check the system proxy mode and the browser's own settings. Don't disable system-wide security protections to get past a single app prompt.
Before migrating an old configuration, back up your subscriptions and rules, then import them into the new client. After moving between desktop operating systems, check path-based settings such as local rule file locations; paths from another computer may not work.
Check About This Mac: choose Apple Silicon for an Apple M-series chip, or Intel for an Intel processor.
The download is a DMG file. See the installation guide for first-launch and network permission steps; you don't need to change server settings first.
| Check | What to look for |
|---|---|
| Apple Silicon | Apple M-series chip: choose the arm64 DMG |
| Intel | Intel processor: choose the x64 DMG |
| macOS version | Follow the current app's launch prompts and release notes |
| Permissions | Allow the app to be installed; grant network permissions only for features that need them |
For Android, v2rayNG is the recommended choice and uses the Xray core. If you need compatibility with V2Fly configurations, consider v2flyNG. These are separate apps with different menus, configuration support, and data directories—not simply two versions of the same app.
Most phones released since 2015 will use the arm64 build, but some devices have a different processor architecture or run a different system bitness. Check the ABI actually supported by your system. If you're unsure, choose the universal build. It supports multiple architectures, but doesn't make connections faster or change subscription compatibility.
If you see “App not installed,” check storage space, Android version, and architecture first, then check for a signing conflict with an existing app. Builds from different sources may not install over an app with the same name. Don't uninstall the old app before saving its configuration.
If the connection drops when the app goes into the background, check battery optimization and background restrictions. Change one setting at a time and note the result. Avoid running network interception in both v2rayNG and v2flyNG at once; Android may keep switching connection state, making it harder to troubleshoot.
Xray core · The first option is recommended for most arm64 devices. Choose the universal build if you're unsure of the architecture.
APK installer. Approve the system VPN request when connecting for the first time. Subscription links must be imported separately.
An alternative client for V2Fly configurations. Check protocol and transport support before importing; don't assume it can replace v2rayNG for every configuration.
| Check | What to look for |
|---|---|
| arm64 | Supports arm64-v8a; recommended for most recent phones |
| Universal build | Choose if you're unsure of the architecture; Android version requirements still apply |
| macOS version | Follow the compatibility information shown by the installer for your APK |
| Connection permissions | Grant install-source permission and first-time VPN connection permission separately |
On Linux, v2rayN uses a desktop client. Choose deb or rpm based on your distribution's package management system, then check the processor architecture. Debian, Ubuntu, and their derivatives generally use deb; Fedora, RHEL, and their derivatives generally use rpm. Choose the package format based on your distribution, not its desktop theme or window appearance.
Most desktop PCs use x64, which may appear as x86_64 in system information. Some development boards and desktop devices use arm64, which may appear as aarch64. These architectures aren't interchangeable. The main downloads on this page are for x64; arm64 packages are listed separately below. Check your architecture again before installing.
The graphical client requires an available desktop session. Don't use the desktop installation steps on a machine with only a command-line environment. If a shared library is missing or a dependency version is incompatible, first check which distributions are supported instead of forcing the installation past the dependency check.
On Linux, apps may differ in how they use desktop system proxy settings. A browser connecting successfully doesn't mean every terminal program is using the same proxy. After installation, test each app you actually use. Adjust routing and DNS only after the client starts normally.
The main downloads are for x64 desktops. Choose your distribution's package format, then check the dependencies listed by the installer.
Requires a graphical desktop environment. For arm64, the package format must still match your distribution's package management system.
| Check | What to look for |
|---|---|
| Package format | Choose deb or rpm based on your distribution |
| Processor architecture | x86_64 means x64; aarch64 means arm64 |
| Runtime | An available graphical desktop session and the dependencies listed by the installer |
| Permissions | Permission to install software and read/write access to the configuration folder |
Starting the app, importing a configuration, and connecting an app are three separate checks.
On desktop, open the Subscription Group menu in v2rayN, add a subscription URL, and update it. On Android, open Subscription group settings in v2rayNG, save the URL, and update the subscription. To add an individual configuration link, use Import from clipboard. Copy the full link without including explanatory text or the page URL.
Once a configuration appears in the list, select the one you want to use, then enable the appropriate connection mode. In v2rayN, Auto configure system proxy mainly affects apps that follow system proxy settings; it doesn't route all traffic automatically. For your first test, use the default routing rules or rules you understand. Avoid changing the system proxy, routing, and DNS all at once, so you can identify the cause of any issue.
Note your subscription groups, custom rules, and local listener settings, then save them using the client's backup or export feature. Subscription URLs may contain personal access tokens, so don't share backup files or screenshots publicly. When switching clients or core families, check protocol and transport support. Being able to import a link doesn't mean every field is supported.
For step-by-step instructions, read the v2rayN and v2rayNG setup guide. To check VMess, VLESS, and core compatibility, see the protocol and core reference. For DNS issues, continue with the DNS setup steps.
A checklist for package formats, processor architectures, and configuration migration.
Desktop uses a newer cross-platform interface, making it a good fit if you want a similar workflow across desktop operating systems. WPF is the classic, stable interface for users following existing Windows tutorials. Both downloads are x64 ZIP archives. Extract the archive, then run the installer inside.
Open About This Mac from the Apple menu. If the Chip field shows an Apple M-series chip, choose Apple Silicon. If the Processor field shows Intel, choose Intel. Check the actual processor rather than relying on the device's appearance or purchase date.
Most phones released since 2015 will use the arm64 build, but make sure your system supports arm64-v8a. If you can't confirm the architecture, choose the universal build. It supports multiple architectures but won't improve connection speeds by itself. If installation fails, check the Android version, available storage, and signing conflicts.
Debian, Ubuntu, and distributions with the same package management system generally use deb. Fedora, RHEL, and their derivatives generally use rpm. Check whether you need x64 or arm64, and review the installer's dependency requirements. A matching package format doesn't guarantee compatibility with every version of a distribution.
The installer includes the client app, not server configurations. Get a subscription link or individual configuration from a service you're authorized to use, then add it through the subscription group settings or by importing from the clipboard. Select the imported configuration, set a proxy mode as described in the guide, and test the connection.
Before updating, use the client's export or backup feature to save your configuration, and note your subscription groups and custom rules. Updates from the same client and signing source usually preserve data, but follow the installer prompts. If you encounter a signing conflict, don't uninstall right away. First make sure your backup is usable, then plan the migration.