Client downloads / OS and architecture
v2rayN for desktop; v2rayNG and v2flyNG for Android.
Choose your OS first, then check the processor architecture. Version details appear on each client card, with installation instructions next to the relevant download.
One client, v2rayN, with two interfaces. Choose Desktop for a first install, or WPF to keep the classic interface.
7.24.1 · Windows x64
A newer cross-platform UI, suited to first-time installs and users who want a consistent desktop experience.
Download Desktop · x64ZIP archive. Extract it before running the installer inside.
The established, stable Windows version for users who prefer the familiar menus and workflow.
Download WPF · x64Both packages are x64; the difference is the interface, not the processor architecture.
| Check | What to look for | Before installing |
|---|---|---|
| OS and architecture | This page provides Windows x64 packages | Check System type under Settings → System → About. |
| Runtime | Follow the runtime requirements listed for your chosen version | If startup reports a missing runtime component, install the component for the matching architecture. |
| Permissions | Administrator rights are usually not needed for system proxy mode | For TUN mode, grant the permissions requested by the client. |
After downloading, extract the archive to a writable folder. Don’t run the installer from the archive preview window. If Windows says the program is in use, quit v2rayN from the system tray and check that no older instance is still running. Desktop and WPF may use different configuration paths or migration methods, depending on the version. Export your settings before switching interfaces, and don’t overwrite the old folder.
On first launch, import a subscription or server settings, select a configuration, then enable “Set system proxy.” The system proxy affects only apps that honor it; a working browser connection doesn’t mean every program is using the proxy. If you need a virtual network adapter to route traffic from more apps, read the TUN mode guide. Avoid changing routing, DNS and network mode all at once on first launch.
If the interface starts but connections fail, check the specific error in the logs. A missing runtime, an unreachable server and an incompatible subscription field are different problems. Reinstalling the same package won’t fix incorrect server settings or provide connection configuration.
Use v2rayN. Check About This Mac for your chip, then choose the matching DMG.
7.24.1 · macOS
If About This Mac shows an Apple M-series chip, choose the arm64 package.
Download Apple Silicon · arm64Use the native architecture that matches your chip whenever possible.
If About This Mac shows an Intel processor, choose the x64 package.
Download Intel · x64Don’t identify your chip based only on the year you bought your device.
| Check | What to look for | Before installing |
|---|---|---|
| Chip | Apple Silicon: arm64; Intel: x64 | Open About This Mac from the Apple menu. |
| OS version | Check the minimum OS version required by the current app package | Make sure your macOS version meets the requirements before installing. |
| Network permissions | System proxy and TUN have different permission requirements | Follow system permission prompts only when you use the relevant feature. |
Open the DMG and follow the installer prompts to move the app to Applications. Launch it from that folder. Running the app from a mounted disk image long-term can affect updates and permissions. Once installation is complete, eject the disk image; keep the downloaded DMG only as installation media.
If macOS blocks the first launch, check the download source and the exact warning, then use the option provided by the system. Don’t disable system security just to run one app. For an “incompatible” warning, check the chip architecture and OS version first. Permission prompts, an architecture mismatch and an incomplete download require different fixes.
After importing a configuration, test the connection in the default network mode first. Some apps have their own proxy settings, while others don’t use the system proxy. After changing the system proxy, reconnect in the app you’re testing. Before quitting the client, restore an appropriate system proxy setting so the system doesn’t keep sending requests to a local port that is no longer listening.
Start with v2rayNG. Consider v2flyNG if you need compatibility with the V2Fly core.
2.2.6 · Android
For most mainstream phones released since 2015; check the ABI supported by your system.
Download v2rayNG · arm64For compatible devices running a 64-bit Android OS.
Choose this if you’re unsure of your device’s architecture. It includes runtime files for multiple architectures and is usually larger.
Download v2rayNG · UniversalUniversal packages still have minimum OS requirements.
1.10.31 · Android
For arm64-compatible Android systems and users with existing V2Fly configurations.
Download v2flyNG · arm64Before importing, check that the protocol, transport and security-layer fields are supported.
An alternative package for devices with an uncertain architecture; connection support still depends on the core.
Download v2flyNG · UniversalDisconnect the other client’s VPN before switching apps.
| Check | What to look for | Before installing |
|---|---|---|
| Architecture | arm64 or Universal | Check your device’s system architecture. If you’re unsure, start with Universal. |
| OS compatibility | Follow the minimum OS version specified in the APK | Make sure you have enough storage and that the download is complete. |
| Installation permission | Grant permission only to the download or file manager app you’re using | Allow installation when prompted; you can turn off permission for that source afterward. |
| Connection permission | The system asks for confirmation when VPN mode starts | Review the permission prompt; typically, only one VPN can be active in a user profile at a time. |
A 64-bit phone processor doesn’t necessarily mean the OS supports 64-bit apps. If the arm64 package won’t install, don’t keep tapping the same file. Check the system ABI, then try the compatible Universal package. If installation reports a conflict with an existing app, check the signing source and version. Don’t uninstall the old app just to bypass the warning; uninstalling may also remove local settings.
After first launch, import a configuration from the clipboard, a QR code or a subscription group. Check the server address, port and transport settings, then start the VPN. The system’s VPN permission prompt is part of setting up the VPN connection; it doesn’t confirm that the remote server is reachable. Test DNS resolution, access from the target app and the log status separately.
If the system stops the connection in the background, check battery optimization, background restrictions and other VPN apps before changing packages. v2rayNG and v2flyNG don’t have identical menus or support for every field. Save the original subscription before switching; don’t assume one client can read configuration exported in another client’s specific format.
Use the v2rayN desktop client. Choose deb or rpm, then confirm x64 or arm64.
7.24.1 · Linux
For compatible distributions using the Debian package system. Open with your system’s software installer.
Download deb · x64For arm64 devices: Download deb · arm64
For compatible distributions using the RPM package system. Check dependencies before installing.
Download rpm · x64For arm64 devices: Download rpm · arm64
| Check | What to look for | Before installing |
|---|---|---|
| Package format | deb or rpm | Check your distribution’s package system in System Information or the software manager. |
| Processor | x64: amd64 / x86_64; arm64: aarch64 | Don’t identify the architecture by distribution name alone. |
| Desktop environment | A desktop session capable of running graphical apps is required | Check that the display environment and installer dependencies are available. |
| OS compatibility | The same package format doesn’t guarantee compatibility with every release of a distribution | If dependencies can’t be met, check the OS version first; don’t force the installation past dependency checks. |
deb and rpm are package formats, not proxy protocols. Open the download with your distribution’s software installer, review its dependencies and installation location, then confirm. amd64 and x86_64 both refer to the common x64 architecture; arm64 and aarch64 refer to another processor architecture. These names are not interchangeable.
Linux desktop environments don’t all handle system proxy settings the same way. Even after the client sets the system proxy, some apps may still use their own network settings. Check the proxy path in the target app before deciding whether you need TUN. Don’t run the entire graphical client with elevated privileges as a workaround; grant only the permissions required for the features you use.
If the installer reports unmet dependencies, keep your existing configuration and check the exact dependency names. Renaming an rpm file to deb, skipping dependency checks or reinstalling won’t fix binary incompatibility. When updating, use the same package-management channel where possible. Avoid keeping a manually extracted copy alongside the installed app, as you may launch the wrong version.
After installation
The package installs the app, but a connection still needs configuration. Test the simplest setup first, then adjust routing and DNS.
The client doesn’t include a working server. Prepare a subscription URL, share link or server settings you’re authorized to use. Before importing, check the format and client compatibility. Subscription paths and query parameters may contain credentials; don’t include them in public screenshots or support requests.
After importing, check the address, port, protocol, transport and TLS settings. Seeing an entry in the list only means it was parsed; verify the server status, authentication settings and transport combination with an actual connection. Keep a copy of the original configuration while troubleshooting so you can compare changes.
Read the import and connection guide →On desktop, start with the system proxy. On Android, the client’s VPN mode creates a local traffic-routing path. The traffic capture method determines which apps send traffic through the client; routing rules then decide whether that traffic is proxied, sent directly or blocked. They’re separate settings.
For your first connection, change only what’s necessary. Once access and logs look good, add subscription groups, domain rules and DNS policies one at a time. If something breaks, reverting one change at a time makes it easier to find the cause. For rule order or custom outbound settings, see Advanced Setup.
Read the routing and DNS guide →Download questions
Answers to six questions about downloads. For connection timeouts and routing issues, see Troubleshooting.
The package contains the client app, not a working server configuration. Prepare a subscription link or server settings you’re authorized to use, import them and select a configuration, then set up system proxy or VPN mode. Subscription URLs may contain credentials; don’t share them publicly.
For a first install, try Desktop, with its newer cross-platform interface. Classic WPF is the established, stable Windows version for users familiar with the original layout. Both are v2rayN, and both Windows downloads on this page are x64 packages—not different processor architectures.
Most mainstream phones released since 2015 can start with arm64, but check the ABI supported by your system. Choose Universal for older devices or if you’re unsure of the architecture. A 64-bit processor doesn’t guarantee a 64-bit OS. If installation or package parsing fails, check the OS version, available storage and the signature of any existing app.
v2rayNG uses the Xray core and is our recommended Android option; v2flyNG uses the V2Fly core as an alternative. Choose based on the protocols, transports and configuration fields your setup requires. Being able to import a link doesn’t mean every parameter will work. Back up your configuration before switching clients, and disconnect the other app’s VPN.
The version label and download link come from different manifest fields, so their update times may differ. This page reads each field as provided and doesn’t turn numbers in filenames into version labels. If they don’t match, keep your current configuration, check the app’s About screen after downloading, and then decide whether to update.
Use the client’s export or backup feature to save server settings, subscription groups, routing rules and custom DNS settings. Quit the old process before installing a new package from the same source for the same architecture. When moving between interface versions or clients, don’t assume configuration folders and every field are compatible. Test the new version before removing the old copy.