Client installation · platforms and architectures
Choose v2rayN for desktop systems and v2rayNG for Android. Check your operating system and processor architecture before downloading the matching package.
First install and subscription setup guide →Two interfaces for the same client. Both downloads below are x64 packages. Extract the archive before running the installer.
Desktop edition
Download Desktop · x64A new-generation cross-platform UI. A good fit for first-time installations and anyone who wants a consistent layout across desktop systems.
Classic WPF edition
Download classic WPF · x64The classic, stable Windows interface. Ideal if you’re familiar with its menus, settings, and subscription group workflow.
Keep one edition as your everyday client. Don’t run both instances on the same local listening ports.
Open Settings → System → About and check your system type to confirm that you’re running x64 Windows. Neither package is a native build for other architectures; if your device uses a different architecture, check that Windows supports running x64 apps. Save the ZIP to a writable folder, extract it completely, and run the installer. Don’t launch it from the archive preview.
Desktop and WPF differ mainly in UI technology and layout. Neither removes the need for a subscription, and the same rule may not produce identical results across different cores. For your first run, keep the defaults, import a configuration, and test the connection. Before switching editions, back up subscription groups, custom routing, and personal settings. Don’t overwrite a running installation directory with the other edition.
If the app reports a missing runtime, install the matching .NET Desktop Runtime as prompted. Bundled runtimes vary by release, so you don’t need to install every runtime in advance. If the app closes immediately, check your security software’s quarantine and the installation folder’s write permissions. Running as administrator is generally unnecessary for everyday system proxy use; elevate only when a specific network feature requires it.
| Item | Package type on this page | Where to check and what you need |
|---|---|---|
| System and architecture | Windows x64 | Check the system type in System Information. Refer to the specific release package for minimum Windows version requirements. |
| Installer format | Installer included in ZIP | Extract all files, close any running instance, then launch the installer. |
| Runtime | Follow startup prompts | If .NET is missing, install the required Desktop Runtime and make sure its architecture matches. |
| Storage and permissions | Writable folder | Allow space for extraction, installation, and configuration files. Check that security software hasn’t quarantined any components. |
Choose based on the chip or processor shown in About This Mac. A DMG is an installation image, not the folder to run the app from.
Apple Silicon
Download Apple Silicon · arm64Choose this package if About This Mac shows an Apple M-series chip. It’s a native build for that processor.
Intel
Download Intel · x64Choose this package if the processor is listed as Intel. Don’t guess based on the computer’s appearance, purchase year, or product line.
Drag the app into Applications before launching it. Quit any running v2rayN instance before updating.
Open the Apple menu in the top-left corner of the screen and select About This Mac. If it shows “Chip: Apple M…”, use the arm64 package; if it shows “Processor: Intel…”, use the x64 package. Even if you’ve used older apps through a compatibility layer, choose the current build that matches your hardware rather than reusing an old package. The same file extension doesn’t mean the app supports the same processors.
Double-click the downloaded DMG and follow the instructions in the disk image window to drag v2rayN into Applications. Once it’s copied, open the client from Applications, then eject the disk image. This keeps the app from running from a temporary mounted location and makes future updates easier. If macOS displays a security alert, read it and verify the app’s source. Don’t disable system-wide security checks just to install one app.
After the first launch, import a configuration, select an available entry, and then set the system proxy. The system proxy affects only apps that follow that setting, so it doesn’t mean every app uses the same connection. TUN uses a different approach to routing traffic and may require extra permissions and route changes. If you only need a proxy for your browser, verify the system proxy first, then consult the configuration guide before enabling TUN.
| Item | How to choose | Installation requirements |
|---|---|---|
| Apple Silicon | Apple M-series chip | Choose the arm64 DMG and check that your macOS version meets the package requirements. |
| Intel | Intel processor | Choose the x64 DMG; don’t use it interchangeably with the arm64 package. |
| Where to run it | Applications folder | Launch the app after copying it. Leave enough space for the app and its configuration files. |
| Network permissions | Grant permissions as needed | Test a basic connection first. TUN permissions and the regular system proxy are handled separately. |
v2rayNG, which uses the Xray core, is listed first, with v2flyNG using the V2Fly core as an alternative. Each app manages its own configuration.
arm64 architecture
Download v2rayNG · arm64The usual choice for most phones released after 2015. Check which app architectures your device supports.
Universal architecture
Download v2rayNG · UniversalAn alternative if you’re unsure of your device’s architecture. It includes multiple architectures, so the package is usually larger than a single-architecture build.
The app-level version and platform package filename may not match. Check the installed version on the About page after installation.
arm64 architecture
Download v2flyNG · arm64Choose this if you need compatibility with a V2Fly-core configuration. Check that the protocol and transport settings are supported before importing.
Universal architecture
Download v2flyNG · UniversalChoose this if you’re unsure of the device architecture. Check subscriptions, routing, and app settings separately from v2rayNG.
A similar-looking interface doesn’t mean the clients have the same core capabilities. Don’t reuse configuration fields specific to another core.
Check your phone’s device information or the system’s app compatibility details to confirm the architecture. A 64-bit processor doesn’t always mean the system can install every 64-bit app. If you see “App not installed,” also check the Android version, storage space, and source of any existing app. The Universal version reduces uncertainty about architecture, but won’t resolve signature conflicts or an outdated Android version.
When you open an APK from a browser or file manager, Android may ask you to allow installations from that source. Grant permission only to the source you’re using, and revoke it afterward if you prefer. When upgrading, keep the existing app and its data if possible. If Android reports a conflict with an installed app, don’t uninstall it right away. First export or note your subscription groups and custom settings, then check whether both packages come from the same signing channel to avoid losing local configuration.
The first time you connect, Android will ask for VPN permission. This system permission lets the client create a local traffic-routing interface; it doesn’t mean the connection is working. You’ll still need a valid configuration and an available server. If the connection often drops when the screen is locked, check background restrictions in your battery settings and make sure another VPN app isn’t already using the connection. Settings names vary by manufacturer.
| Item | Recommended choice | Check these requirements |
|---|---|---|
| App architecture | Start with arm64 on most devices | Check which app architectures your system supports. If you’re unsure, choose Universal. |
| Android version | Meets the APK’s minimum requirements | Minimum requirements vary by client release; a device’s purchase year isn’t a reliable substitute. |
| Installation permission | Current browser or file manager | Allow app installs from the source you’re using and leave enough storage for installation. |
| Connection permission | Android VPN permission | Approve the prompt on first connection. Make sure no other VPN app is using the connection. |
Choose deb or rpm based on your distribution, then select x64 or arm64 for your processor. These are graphical desktop clients.
Debian / Ubuntu-based
Download deb · x64 For arm64 devices: Download deb →Choose this for distributions that use deb packages. The amd64 package name corresponds to the common x64 architecture.
RPM-based
Download rpm · x64 For arm64 devices: Download rpm →Choose this for distributions that use rpm packages. Check that your distribution meets the package dependencies before installing.
The rpm filename includes its build target; that doesn’t mean every rpm-based distribution meets the same dependency requirements.
Check your distribution and architecture under About or System Information. x86_64 and amd64 usually correspond to the x64 package; aarch64 corresponds to arm64. deb and rpm identify package formats, not processor types, so check both. Don’t rename one package format to use it as another, and don’t bypass package manager checks when dependencies fail.
Once the download is complete, open the package in your file manager and let your system’s software installer handle it. The installer checks package dependencies and requests any required permissions. If dependencies can’t be met, check your distribution version, software sources, and the package build target rather than repeatedly installing the same file. These are graphical clients; this installation process isn’t suitable for systems with only a remote terminal and no desktop session.
After installation, launch v2rayN from your applications menu, import a configuration, and check the local listening port. System proxy settings vary across desktop environments, and not every app will use the client’s settings. Test the connection first with an app that explicitly supports HTTP or SOCKS proxies. Once the basic configuration works, set up the desktop system proxy or TUN. For TUN, check permissions, routing, and DNS separately to avoid changing too many network settings at once.
| Item | What to match | Requirements |
|---|---|---|
| Package format | deb or rpm | Use the format supported by your distribution’s package manager and make sure package dependencies are met. |
| Processor | x64 or arm64 | Check System Information; don’t infer the architecture from the distribution name. |
| Environment | Graphical desktop session | Requires a desktop environment that can run graphical apps, along with the necessary dependencies. |
| Network features | Set permissions as needed | Test system proxy and TUN separately. Avoid letting multiple clients manage routes at the same time. |
Downloading the client only prepares the app. Connection results also depend on your subscription, selected configuration, proxy mode, and app settings.
Import a configuration
In v2rayN, open subscription group settings, add a group name and subscription URL, save, then update it. In v2rayNG, add the URL from the subscription menu and update the relevant group. A single share link isn’t the same as a full subscription: a share link usually describes one configuration, while a subscription URL retrieves a group of entries. Identify what you have before choosing an import method.
View the subscription import guide →Choose a proxy mode
After importing, select a configuration and choose a proxy mode. The system proxy determines which apps that follow system settings send requests to the client; routing rules determine which outbound route the client uses for those requests. These are separate controls. Keep the rules simple while testing for the first time. Once the connection works, add domain-, IP-, or app-based rules and note the results of each change.
View routing configuration →Check compatibility
VMess, VLESS, and Trojan are protocol choices. TLS, REALITY, and transport settings must also match the server. Matching names alone don’t guarantee that the settings are complete. v2rayNG uses the Xray core, while v2flyNG uses the V2Fly core. If a configuration such as VLESS isn’t working, check the core and version support, then verify the transport, security settings, and server requirements.
View core support and configuration fields →Route more traffic
Consider TUN only if you need to route traffic from apps that don’t use the system proxy. Save your existing configuration, confirm the regular proxy works, then grant permissions as prompted by the client. After enabling TUN, test both DNS resolution and connectivity so a DNS issue isn’t mistaken for an unreachable server. TUN works differently across clients and cores; adding the same field to every configuration file won’t enable it.
View TUN configuration options →Record your current setup before replacing the app. That makes it easier to tell installation changes from configuration changes if something goes wrong.
Before updating, note your subscription group names, update settings, local listening ports, custom routing, and DNS settings. Subscription entries can usually be downloaded again, but manually added configurations, app-based routing, and custom rules may not be recoverable from a subscription. Store backups somewhere you control. Don’t publicly share URLs with credentials, configuration QR codes, or unredacted logs.
Before upgrading, fully quit the old client, including any tray or background processes. After installation, check that your configuration list is still there, then restore network features one at a time. Don’t change the client, core, subscription, and routing rules all at once; changing one thing at a time makes it easier to pinpoint the cause of connection issues. If the installer says your system isn’t supported, check the requirements instead of repeatedly downloading the package.
v2rayN, v2rayNG, and v2flyNG are graphical clients in the Project V open-source ecosystem. The client handles configuration, subscriptions, and system integration; the core handles connections and routing. A client launching successfully doesn’t mean the server settings match, and a subscription updating doesn’t mean every entry will work. Check each layer separately: import results, the selected configuration, and access from the apps you use.
Check the package type and system compatibility first, then troubleshoot subscriptions and connections.
For a first installation, consider Desktop, which features a new-generation cross-platform interface. If you prefer the familiar Windows layout, choose the classic, stable WPF edition. Both downloads are x64 packages. Back up subscription groups and custom settings before switching, and check the local listening port after the first launch.
Most phones released after 2015 can start with arm64, but check which app architectures your device actually supports. If you’re unsure, choose Universal; it includes multiple architectures and is usually larger. If installation fails, also check the Android version, available storage, and the signature of any existing app. An error alone doesn’t prove the architecture is the problem.
Open About This Mac from the Apple menu. Choose Apple Silicon if the Chip field shows an Apple M-series chip; choose Intel if the Processor field says Intel. After downloading the DMG, open the disk image, drag the app into Applications, and launch it from there.
The installer contains the client app, not a ready-to-use subscription or server connection details. Import a subscription URL or share link that you obtained and are authorized to use, then select a configuration, choose a proxy mode, and test the connection. Subscription URLs may contain credentials, so don’t post them publicly in screenshots or support requests.
The version shown on a card comes from app-level manifest information, while the filename identifies a platform package; the two may not update at the same time during a release. Check the client, operating system, and architecture you selected. Note the filename before installing, then confirm the installed version on the client’s About page. Don’t infer the filename from the card or edit version numbers in the download URL.