Choosing an installer / Client and architecture

Download V2Ray clients

Choose your operating system first, then check your processor architecture. Use v2rayN on desktop platforms; v2rayNG is the recommended Android option, with v2flyNG as an alternative.

Free clients Open source No nodes included

Choose an installer by platform

Version details and installer information are shown as recorded for each release. Check the release notes and installer prompts for compatibility; the client name alone doesn't tell you whether it will work on your system.

Windows downloads

v2rayN

Recommended

Windows · x64 · 7.24.1

Desktop edition

A newer cross-platform UI; a good starting point for a first install.

Download Desktop · x64

ZIP archive. Extract it fully before running the installer inside.

Classic WPF edition

The familiar, established Windows interface for users who prefer the classic workflow.

Download WPF · x64

Useful when following guides for the classic interface; menu locations may vary by version.

Choosing between the two interfaces

Both are v2rayN clients, not separate subscription services. Desktop uses a cross-platform interface, while WPF retains the classic Windows UI. Buttons, menus and settings may be in different places, so a guide screenshot alone doesn't mean your installation is wrong. If you already have a setup, check which interface you're using before switching.

Both Windows downloads on this page are x64. In Windows, open Settings → System → About and check System type; the exact labels may vary. A processor's architecture does not guarantee that the installed OS or its compatibility layer meets the requirements. Check the release notes for other architectures rather than renaming a file to make it fit.

Extracting, installing and launching for the first time

Save the download to a local folder you can write to, and wait for the browser to show that it has finished. Extract the entire ZIP archive to a folder, then run the installer inside; don't launch it from the archive viewer's temporary preview. After the setup wizard finishes, launch the client from the system's app menu to avoid mistaking an older folder's copy for the installed version.

If startup fails, keep the original error message. Missing runtime components, write-permission failures and core startup errors have different causes and require different fixes. First install any runtime required by that edition, then check the logs. For your first connection, import a subscription, choose a node, set the system proxy and confirm the app can access the network. See the quick-start guide for full steps.

Windows requirements and setup

Check	Downloads on this page	Before installing
Processor and OS	x64	Check System type in system information; don't rely on the computer brand alone.
Installer format	Installer included in ZIP	Extract the archive fully before running the installer; the working folder must be writable.
OS and runtime	Varies by Desktop or WPF edition	Check the release notes for the selected installer's supported OS versions and runtime components.
Network setup	Subscription or server configuration	Prepare a valid configuration before setting the system proxy; installing the client does not create nodes.

macOS downloads

v2rayN

macOS · DMG · 7.24.1

Apple Silicon

Choose arm64 if About This Mac shows an Apple chip.

Download macOS · arm64

Prefer the installer that matches your chip architecture.

Intel

Choose x64 if About This Mac shows an Intel processor.

Download macOS · Intel

The 64 in the filename corresponds to this x64 download.

Check your chip before opening the disk image

Open the Apple menu and choose About This Mac. Check the Chip or Processor field: choose arm64 for Apple silicon or x64 for an Intel processor. Don't guess based on the year you bought the Mac or its appearance. The two DMG files are for different architectures, not different paid tiers, and you don't need to install both just to test a connection.

When the download finishes, open the DMG and follow its instructions to move the app into Applications, then launch it from there. Running the app from the mounted disk image can make its location unclear after you eject it. Before updating, quit any older running copy to avoid having multiple instances open.

First launch and proxy coverage

If macOS shows a security prompt, first confirm the file source, selected architecture and supported OS version, then follow the system's authorization process. Don't disable system-wide security settings to fix every startup issue. If the app won't open, can't write its configuration or starts but can't connect, record the message and troubleshoot each issue separately.

After importing nodes, check whether the apps you need to use are set to follow the system proxy. Some apps have their own proxy settings and won't automatically use the system setting. If a browser works but another app doesn't, compare where each app gets its proxy configuration. The system proxy and client routing are separate layers; see routing and proxy troubleshooting for details.

macOS requirements and setup

Check	How to choose	Before installing
Apple Silicon	arm64 DMG	About This Mac shows an Apple chip in the Chip field.
Intel	x64 DMG	About This Mac shows Intel in the Processor field.
OS version	Depends on the selected release	Check the supported OS versions first; a matching chip doesn't guarantee your macOS version is supported.
App permissions	Installation, configuration access and proxy settings	Follow the system's prompts for permissions; work devices may also be subject to management policies.

Android downloads

v2rayNG

Recommended

Android · Xray core · 2.2.6

arm64

A good first choice for most phones released after 2015; check your device's supported architecture.

Download v2rayNG · arm64

For systems that support arm64-v8a apps.

Universal

For devices with an unknown architecture; includes multiple app architectures.

Download v2rayNG · Universal

Usually a larger download; it does not replace checking Android version compatibility.

Installation and VPN permission

For your first install, allow app installation from the source you are using, such as your browser or file manager, when prompted. After installing, import a subscription or node, choose a configuration and start the connection. Android uses VpnService to request a VPN connection; approve the request only after confirming it came from the client you just launched. This permission does not provide a remote server—you still need a valid node configuration.

If the client works in the foreground but disconnects when you switch apps, check the system's restrictions on background activity and battery use. Menu names vary by manufacturer; look in the app info page for battery, background activity or auto-start settings. Change settings only for the client if needed; there's no need to apply the same policy to every app. Also check whether per-app proxy rules include or exclude the intended apps, so they aren't assigned to the wrong list.

v2flyNG

Alternative

Android · v2fly core · 1.10.31

arm64

For devices that support arm64 apps; choose based on your existing configuration needs.

Download v2flyNG · arm64

Before switching clients, check compatibility with your subscription and protocols.

Universal

Includes multiple architectures for devices where the app architecture is unknown.

Download v2flyNG · Universal

The Android version must still meet the requirements for this release.

When to use the alternative client

v2flyNG uses the v2fly core and may suit users with compatible configurations who want to keep using its behavior. A client being able to import a subscription doesn't mean it supports every node feature in it. For specific protocol extensions or transport parameters, check which fields the client actually supports. Don't overwrite its configuration with another client's entire private data folder.

When testing the two Android clients, stop the current VPN connection before starting the other one. This avoids mistaking the VPN that's already active on the system for the app you just selected. If installation reports a signature conflict, keep your configuration and the error message, then check whether the installation source changed. Don't uninstall a client with unbacked-up settings just to clear a prompt.

Android requirements and setup

Check	Recommendation	Notes
App architecture	Check arm64 first on most modern devices	Processor capability and the app architectures supported by the OS may differ. Choose Universal if you're unsure.
OS version	Depends on the selected APK release	Universal does not mean compatible with every Android version.
Installation permission	Allow installs from this source	Grant permission to the browser or file manager only if needed.
Connection permission	System VPN authorization	Confirm which client is currently active before connecting; check battery settings separately if it disconnects in the background.

Linux downloads

v2rayN

Linux · desktop client · 7.24.1

deb · x64

For desktop distributions that use the deb package system.

Download Linux · x64 deb

amd64 is the x64 architecture label used by this package.

rpm · x64

For desktop distributions that use the rpm package system.

Download Linux · x64 rpm

Check your distribution and dependency requirements, not just the file extension.

arm64 desktop systems

Confirm that the system architecture is arm64 / aarch64, then choose the package format used by your distribution.

arm64 · deb arm64 · rpm

Match both the package format and architecture

Check your distribution and architecture in System Settings → About or the system information page. Debian and Ubuntu use the deb package system; Fedora and RHEL use rpm. Even packages with the same format can differ in dependencies or supported distribution versions. If the filename identifies a particular distribution, check its requirements. Being able to open a package doesn't mean all its dependencies are met.

Linux may label x64 as x86_64, while deb package filenames may use amd64; arm64 generally corresponds to aarch64. Choosing the wrong architecture can't be fixed by changing the package format. Once downloaded, open the file with your system's software installer or package manager to review dependency and conflict details. Don't rename the extension or force installation by ignoring dependencies.

Desktop environment and proxy coverage

The client on this page has a graphical interface and requires a working desktop session. After installation, launch it from the app menu, import your configuration, choose a node and set the proxy. Desktop environments and apps differ in how they read system proxy settings, so browsers, terminal programs and apps with their own proxy settings may use different routes.

If the client runs normally but an app still doesn't use the proxy, check the proxy type and listening address in that app's settings. Don't assume a port shown in a guide is the port on your system, and don't confuse clearing the system proxy with deleting nodes. After changing settings, reopen the app and test the same destination to help identify which layer is causing the issue.

Linux requirements and setup

Check	Available downloads	Before installing
Processor architecture	x64 / arm64	Check system information for an architecture such as x86_64 or aarch64.
Package system	deb / rpm	Choose the format used by your distribution and check its compatibility requirements.
Runtime environment	Graphical desktop session	Let the system installer handle dependencies, and keep the original message if installation fails.
Permissions and proxy	Installation permissions and app proxy settings	Handle installation and everyday app permissions separately; grant only what's needed.

Before and after downloading / Configuration setup

Installers, nodes and subscriptions

↗

The installer provides the client only

v2rayN, v2rayNG and v2flyNG manage configurations and start proxy connections. Downloading a client does not provide a server address, account or subscription link, and won't automatically change how every app connects to the internet. Before use, prepare a server configuration you're authorized to use and confirm that its protocol and transport are supported by your chosen client.

A subscription link can usually import multiple nodes, but it is also sensitive access information and should be kept private. Don't post the full link in public screenshots when troubleshooting. Before sharing logs, check for server addresses, user identifiers and subscription parameters. If import fails, first check that the link is valid, then check whether the client supports its format.

Understand the client and core separately

Project V is a useful starting point for understanding this proxy ecosystem. V2Fly and Xray are common related core families. A graphical client handles subscriptions, nodes, routing settings and connection controls; the core processes the traffic itself. Client versions and core versions are different things, and similar-looking interfaces don't guarantee identical protocol support.

This page lists graphical clients, so you don't need to find a separate core installer first. If you need a specific node feature, check which core the client uses and what it supports. Support for a protocol name, for example, doesn't necessarily mean support for every extension of that protocol. See the glossary for related terms.

Connection steps after installation

Finishing the download is only the first step. For your first setup, install and configure one client at a time. Get one connection working before changing routing, DNS or per-app rules. This makes it easier to distinguish an installation failure from a configuration parsing issue or an app that isn't using the proxy, rather than changing several settings at once.

Import and check your configuration. Use the client's subscription or share-link import feature. Confirm that nodes appear in the list, then select one. A successful bulk import doesn't guarantee that every node will connect; older configurations may use transport fields that the current client handles differently.
Start the client connection. On desktop, check that the core starts normally, then set the system proxy. On Android, approve the VPN connection request from the system. If an error appears, read the current message first. Switching to global routing is not a substitute for troubleshooting and won't fix installation, authorization or remote configuration errors.
Check that your app is using the proxy. The system proxy affects only apps that follow that setting; an app-specific proxy or an existing VPN may change the route. Check the listening address and port shown in the client, then enter a supported proxy type in the target app. Don't copy values from screenshots of another version.
Verify the connection before changing routing. Test one specific destination first, then enable the routing rules you need one at a time. A node latency test and real app access measure different things; a test result doesn't directly predict download speed. Don't judge the entire client by a single test value.

Updating and migrating an existing configuration

Before updating, note the client name, interface edition, architecture and how its configuration is stored. Use the client's backup or export feature to save the settings you need. If you back up the files directly, exit the client first so you don't copy files while they're being written. Backups may contain subscription and account details; store them somewhere only you can access.

When upgrading the same client, keep the original installation source and architecture where possible. When moving to another client, re-import the subscription or a standard share link, then check routing, DNS, per-app rules and system proxy settings manually. Configuration folders belong to their respective clients; even if folder names look similar, don't copy an entire folder over another client's data.

Troubleshoot installation and connection errors separately

For “Unable to parse package,” check the architecture, OS version and whether the installer finished downloading. For “The app won't start,” check the runtime environment, folder permissions and the original system message. For “Node connection timed out,” check network reachability, system time, node settings and server status. Note which stage the error occurs at to avoid repeatedly reinstalling in the wrong direction.

If every app suddenly loses access after the client has exited, check whether the system proxy still points to a local listener that is no longer running. If only one app is affected, check its own proxy settings first. For connection issues, see the V2Ray troubleshooting guide and narrow down the cause based on the symptoms; there's no need to change the protocol, port and DNS all at once.

Downloads and installation / FAQ

Choosing an installer: FAQ

Which should you choose for Windows: Desktop or classic WPF?

For a first install, consider v2rayN Desktop, which uses a newer cross-platform interface. The classic WPF edition retains the familiar Windows interface and may suit users who prefer its established workflow or need to follow guides for the older UI. Both Windows downloads on this page are x64. Check your system type and the requirements for your chosen edition before installing.

Which Android version should you choose: arm64 or Universal?

Most mainstream phones released after 2015 can start with arm64, but check which app architectures your device supports. Choose Universal for older devices or when you are unsure; it includes multiple architectures and is usually larger, not faster. If installation reports an incompatibility, also check your Android version and whether an existing install has a conflicting signature.

Can I connect as soon as the client is installed?

The installer does not include usable nodes or a subscription. Prepare a server configuration or subscription link you are authorized to use, import it and select a node, then enable the system proxy or approve the VPN connection request for your platform. Finally, confirm that the target app is actually using the proxy; launching the client doesn't mean the connection is complete.

What should I do before updating an existing client?

Note the client name, interface edition and processor architecture. Back up your configuration using a method supported by the client, then exit the running app. When updating, stick with the same client, installation source and architecture where possible. To move to another client, re-import your subscription or nodes rather than overwriting the entire configuration folder.

What if a download is interrupted or the installer won't open?

Check that the download finished, there is enough disk space, and the file extension matches your platform. Delete incomplete downloads and get the correct installer again. If installation fails, note the exact system message and check for an architecture mismatch, an unsupported OS version, missing runtime components or insufficient permissions. Don't repeatedly rename files or disable system protection.

Why might the displayed version differ from the installer filename?

The displayed version comes from the app's version field, while the filename comes from the installer record for each platform. These may be updated at different times. Check the client, platform and architecture before downloading, then verify the installed version in the app's About or version information. Don't infer or edit a download URL from the filename.