Choose v2rayN for desktop or v2rayNG for Android.
Check your operating system and processor architecture before downloading.
Free, open-source clients · Install and configure subscriptions separately
One client, two interfaces. Both downloads are for x64. Extract the ZIP before running the installer inside.
The Desktop version features a next-generation cross-platform UI, while classic WPF retains the familiar Windows interface and layout. New users can start with Desktop; if you're used to WPF, you can stay with the classic version.
Package: ZIP containing the installer. Choose one version; you don't need to install both.
| Check | What to look for |
|---|---|
| Processor and system | This page offers x64 packages. Check your system type under Settings → System → About. |
| Windows version | Use a supported Windows release where possible. Check the selected package's release notes for its minimum requirements. |
| Installation | Extract all files to a writable folder, then run the installer. Follow its instructions if it prompts you to install a runtime. |
| Network permissions | System proxy and TUN are different modes. TUN may require administrator access and support for a virtual network interface. |
Don't run the program from a compressed file preview. It may need to access files in the same folder, and incomplete extraction can cause startup errors. After installation, launch it without administrator privileges first. Grant elevated permissions only when prompted for a feature that requires them.
Before moving from an older version, note your subscription groups, routing mode, and custom listening ports. Settings may be in different places in each interface; don't assume they're migrated based on how the window looks. After launch, check for subscription updates, confirm the selected server and system proxy status, and exit any old background process to avoid local port conflicts.
Choose a DMG for your processor. Open About This Mac: select arm64 for Apple silicon or x64 for an Intel processor.
Apple silicon and Intel packages target different processor architectures. Choose the version that matches your chip to avoid mistaking an architecture mismatch for a configuration problem.
Package: DMG. Mount it, copy the app to Applications, then launch it from there.
| Check | What to look for |
|---|---|
| Apple Silicon | Choose the arm64 DMG for Apple silicon devices. |
| Intel | Choose the x64 DMG for Intel devices. |
| System compatibility | Check the selected release's minimum macOS requirement. A matching processor doesn't guarantee your macOS version is supported. |
| Permissions | Grant the requested permissions when prompted to change system proxy settings or enable a virtual network interface. |
After installation, don't keep running the app from the mounted disk image. Copy it to a permanent location for easier updates and permission management. If a security warning appears on first launch, check the download source, selected architecture, and reason for the warning. Use the system's per-app approval process rather than disabling security protections altogether.
System proxy settings only work with apps that use them. If your browser connects but another app doesn't, check how that app handles network settings instead of repeatedly downloading a different package. Before enabling TUN, close other tools that manage network traffic and note your existing proxy settings. If connectivity changes after quitting the client, check whether the system still has an old proxy configured.
For most phones released since 2015, arm64 is a good first choice. If you're unsure which app architectures your device supports, choose universal. Always check your device's actual architecture support.
Uses the Xray core. A good starting point: import a subscription, select a server, then grant Android VPN access to route the selected traffic.
Package: APK. The universal version includes components for multiple architectures and is usually larger.
Uses the V2Fly core. Consider it if you already use compatible configurations. Protocol and settings support depends on the core version; make sure it can parse your subscription before switching.
Package: APK. Each client manages its own settings; installing the alternative won't migrate subscriptions automatically.
| Check | What to look for |
|---|---|
| App architecture | Choose arm64 for most devices that support 64-bit apps. If you're unsure of the architecture, choose universal. |
| Windows version | Check the installer and release notes for the minimum Android version. A universal package doesn't lower the system requirements. |
| Install permission | Allow installs from the browser or file manager you're using to open the APK. You can revoke this permission afterward. |
| VPN permission | Confirm the Android VPN prompt when connecting for the first time. Running multiple VPN apps at once may cause conflicts. |
If Android says “App not installed,” check available storage, system architecture, and where the existing version came from. Apps signed through different distribution channels may conflict; choosing a universal package won't fix that. Export any settings you want to keep before deciding how to update or migrate, so you don't lose subscription groups or custom rules by uninstalling.
Background disconnects are usually unrelated to the APK architecture. If the connection drops when you lock the screen, check battery optimization, background activity, and your device manufacturer's auto-start restrictions. Per-app proxy settings determine which apps use the VPN, so check that your browser is included before testing. After changing the app list, reconnect as instructed by the client and check again.
Choose deb or rpm for your distribution, then check whether you need x64 or arm64. These GUI client packages require a working desktop session.
Debian- and Ubuntu-based distributions generally use deb; Fedora- and RHEL-based distributions generally use rpm. Dependencies can still vary between distributions, even for the same package format. Follow your package manager's compatibility warnings.
x64 is also labeled amd64 or x86_64; arm64 may appear as aarch64.
| Check | What to look for |
|---|---|
| Package format | Choose deb or rpm based on your distribution's package manager, not the file size. |
| Processor architecture | Check the architecture in your system information. amd64 and x86_64 mean x64; aarch64 means arm64. |
| Runtime requirements | Requires a graphical desktop and the dependencies listed for the package. Older distributions may not include the required system libraries. |
| Proxy and permissions | System proxy behavior depends on your desktop environment. TUN also involves network interface permissions, routing, and DNS settings. |
After downloading, open the package with your distribution's software installer. If it reports missing dependencies, check your distribution version and architecture. Don't force past dependency checks or extract another distribution's package into system directories. The same file extension doesn't guarantee identical dependencies, especially across distributions or major releases.
Not every desktop app uses the system proxy. Browsers, terminal apps, and background services may each use different proxy settings, so be clear about what you're testing. Before enabling TUN, check for existing VPNs, container networks, and custom routes to avoid multiple tools changing the network path. Keep logs and note any network setting changes if something goes wrong.
The platform determines the package format, the architecture determines whether it can run, and the client and core determine which configurations it supports. Check all three separately.
Version labels on the cards come from client listings, while each button links to a separate installer. Release schedules may differ, so the filename version may not match the card. To check the installed version, refer to the downloaded file and the app's About page, not just the heading.
Before updating, check the client name, platform, and architecture. v2rayN, v2rayNG, and v2flyNG are separate apps; similarly named packages aren't interchangeable. Choose and manage Desktop and classic WPF as separate interface versions.
The package provides a GUI and its runtime components, not a ready-to-use subscription. You'll need to obtain a subscription link, server settings, and access separately. Check that the source is trustworthy and that your chosen client and core version support the configuration format before importing.
A client can store multiple servers, but importing settings successfully doesn't mean every server will connect. Start with one server, confirm the local proxy mode, and test an actual request. Add routing and per-app proxy settings gradually so you can identify what caused any change.
Start with the minimum settings needed to connect, then adjust which traffic uses the proxy. Avoid changing subscriptions, cores, routing, and DNS all at once.
Find the subscription or subscription group section in the client. Give the group a clear name, paste the full subscription URL, and update it. The link may contain access credentials, so preserve all parameters and encoding; messaging apps may truncate it. After updating, check that server entries appear. If the list is empty, read the update message before enabling TUN or reinstalling.
On desktop, test a browser request using the system proxy. On Android, grant system VPN access to connect. TUN uses a virtual network interface and involves permissions and routing; it's not a default fix for every problem. Confirm the selected server, routing mode, and app proxy scope before testing. If system proxy and TUN are both enabled, check how the client handles traffic between them.
Open a webpage for testing and check the client logs for the corresponding request. Distinguish DNS failures from handshake failures and connection timeouts. A latency test only reflects its specific test conditions, not how every website will perform. Once the configuration works, note your current mode and custom settings. Back up subscription groups and rules before updating or moving to another device.
First identify whether the problem is with installation, importing settings, or connecting. Each calls for different checks.
For a first install, try Desktop, which uses a next-generation cross-platform interface. The classic WPF version keeps the familiar Windows interface for users accustomed to it. You don't need both versions running. Back up your settings before switching, then check subscriptions, routing, and local listening ports.
Most phones released since 2015 are best suited to arm64, but check which app architectures your device actually supports. If you're unsure, choose universal. It includes components for multiple architectures and is usually larger; it won't resolve an outdated Android version or a signing conflict.
The client manages settings and proxy traffic, but the installer doesn't include a ready-to-use subscription. Import a valid subscription or server configuration, select a server, then enable a proxy mode that suits your system. When troubleshooting, check the subscription status, system clock, routing rules, and core logs.
Make sure the download has finished and the file extension matches the package format, then check available storage and system architecture. Extract Windows ZIP files completely before use. Retry interrupted downloads. If you see a security warning, check the file source and warning details rather than disabling system-wide protection.
Usually, try an in-place update using the same client and distribution channel. Back up subscription groups, routing, and custom settings first. If Android reports a signing conflict, verify the installation source before uninstalling. When changing interface versions or installation sources, follow the relevant migration instructions.
Both are Android GUI clients. v2rayNG uses the Xray core, while v2flyNG uses the V2Fly core; supported protocols and settings depend on the version. v2rayNG is a good starting point. Consider v2flyNG if you already use V2Fly configurations. After switching clients, re-import your settings and grant VPN access.
For platform-specific proxy permissions, subscription setup, and compatibility tips, see the cross-platform guide.