Windows · macOS · Linux · Android clients

v2flyNG Official Site v2rayN and v2rayNG downloads

Desktop and Android client downloads, with clear setup steps for subscription import, routing, and TUN mode.

Open source Xray · V2Fly Setup guides

Choose a client for your OS

Use v2rayN on desktop and v2rayNG on Android. Check your device architecture before choosing a package; similarly named clients do not necessarily use interchangeable installers.

Windows

v2rayN · Recommended for desktop

Choose between the desktop edition and the classic WPF edition. The desktop edition uses a cross-platform interface, while WPF retains the classic Windows experience. If you’re installing for the first time, compare the two and pick the one that fits your system; there’s no need to install both for everyday use.

Before installing, check your system architecture and runtime requirements. Extract portable builds to a dedicated directory where you have write permission so settings and logs can be saved. Back up your configuration before switching builds, and close any other running client to prevent conflicts over local listening ports.

Go to downloads

macOS

v2rayN · Desktop client

Choose the Apple Silicon or Intel download for your Mac. Check your chip in About This Mac, then select the matching architecture. The arm64 and x64 labels in package names identify processor architecture, not feature tiers.

On first launch, follow the system prompts to grant any required permissions. System proxy and TUN require different permissions, so start by testing with the system proxy for ordinary web browsing. If only one app cannot connect, check whether it uses the system proxy before trying other installers or enabling multiple proxy tools.

Go to downloads

Android

v2rayNG · Xray core

Start with v2rayNG. If you need compatibility with the V2Fly core, consider v2flyNG. Both clients offer arm64 and universal packages. Most newer devices use arm64; if you’re unsure, check your device specifications or the download page.

The first time you connect, Android will ask you to approve VPN access. This lets the client create a local traffic tunnel; it does not mean the remote service is reachable. If the connection drops when you switch apps, check battery optimization and background activity restrictions. Subscription URLs contain access credentials, so don’t share them in screenshots or public discussions.

Go to downloads

Linux

v2rayN · Desktop client

Choose a deb or rpm package based on your distribution, then select x64 or arm64. Desktop environments, tray support, and permission management vary. After installing, make sure the app opens and the core starts before importing an existing subscription.

Browsers, desktop apps, and terminals may use different proxy settings. Browser access alone doesn’t confirm that your terminal is using a proxy; check each app’s settings and the local listening port. Before enabling TUN, check permissions and make sure it won’t conflict with existing virtual networking tools that may route the same traffic.

Go to downloads

The downloads page lists package architectures and requirements. The client reads configuration and connects to a service; subscriptions and remote services must be obtained separately. Installing the app alone does not create a working configuration.

Browse all clients →

Subscriptions, routing, and traffic capture

Think of configuration in three layers: subscriptions provide connection details, routing determines where traffic goes, and the system proxy or TUN determines which app traffic enters the client. Confirm each layer works before moving to the next; this makes troubleshooting easier and preserves useful clues.

Save the URL, then update the subscription

Subscription groups store configuration URLs provided by your service provider. On desktop, enter an alias and URL, save them, then update the subscription. On Android, follow the same steps from the subscription group menu. A successful update means the configuration was imported; you still need to select an available profile and start the connection. Subscriptions make it easier to keep settings in sync than entering each item manually, but they do not provide service access on their own. URLs often contain access credentials, so copy and store them securely. If an update fails, check whether the URL is unreachable, the content format is unsupported, or the service is no longer active.

Learn more →

Three steps to configure v2rayN

Start with a basic connection you can test repeatedly, then add custom rules. The same sequence helps make sense of Android setup, though menu names may vary by client build. Use the options shown in your current version.

Step 1 · Configuration source

Add a subscription group

Get a valid subscription URL from your service provider. Open subscription group settings, enter a recognizable alias, and paste the full URL. Save it, then update the subscription and confirm that profiles appear in the list. Don’t use your provider’s login page URL, and don’t copy only part of the subscription URL.

If no configuration appears, check the update message to distinguish a failed network request from content the client couldn’t parse. Routing and TUN settings won’t fix a subscription format issue; you haven’t reached the proxy mode setup yet. Keep URLs with private credentials on your own device, and hide sensitive fields before sharing screenshots.

Read the subscription import guide →
Step 2 · Traffic entry point

Choose a profile and proxy method

Select an imported profile and make sure the core starts. On desktop, enable the system proxy and test with a browser that uses it. On Android, approve VPN access when prompted during connection startup. For your first setup, keep the basic defaults and avoid changing DNS, routing, and listening ports all at once.

The system proxy determines whether an app sends requests to the client; routing determines where those requests go afterward. They are separate settings. To capture traffic from apps that ignore the system proxy, read the TUN setup guide. If other proxy or virtual networking tools are running, clarify what each one does to avoid conflicting settings.

Read about proxy modes →
Step 3 · Verify each layer

Check access and connection logs

First visit a page expected to connect directly, then a destination that should use the proxy under your current rules. Check both results, then test the app you actually need. A working browser only confirms that the browser’s path works; verify terminals, download tools, and other apps separately based on how they handle proxies.

If something fails, note the time, destination, and error message. Then check the local core, subscription configuration, routing rules, and remote connection in that order. Change one setting at a time and keep a working state for comparison. Logs can distinguish DNS resolution failures, timeouts, and authentication errors, but remove personal configuration details before sharing them publicly.

Troubleshoot connection issues →

Project V and the open-source client ecosystem

Clients, cores, protocols, and subscription services belong to different layers. Understanding how they fit together helps you choose the right setup and avoid mistaking a service issue for an installation problem.

Understanding V2Ray through Project V

Project V is an open-source project ecosystem built around network communication tools, with V2Ray as one of its widely used core components. The core manages traffic through inbound, routing, and outbound sections. A graphical client turns configuration parameters into forms, lists, and toggles. So when people say they’re “installing V2Ray,” they often mean installing a graphical client that then runs the relevant core.

This layered design lets desktop and Android clients use different interfaces while sharing configuration sources when their protocols are compatible. The same protocol name alone doesn’t guarantee full compatibility; check the transport, security layer, and specific parameters too. If you encounter an unfamiliar field, consult the quick reference before deciding whether to switch clients or cores.

How V2Fly and Xray relate

V2Fly continues the community development of V2Ray, while Xray is a separate core that evolved from V2Ray. They share technical roots, but features and configuration details vary as each project evolves. Choose based on the configuration requirements from your service provider and what the client actually supports, not on the core’s name alone.

Features such as REALITY require specific core support, and older configurations may rely on a particular implementation. Before switching, keep your existing working configuration and check that all required fields are present. Then review the logs to confirm it loaded correctly. Connection speed also depends on the remote route, destination service, and local network. Multiple core options offer compatibility paths, not a fixed performance ranking.

What each of the three clients is for

v2rayN is for desktop and manages subscriptions, local ports, the system proxy, and routing. v2rayNG is for Android and uses the Xray core, with system permission to capture traffic. v2flyNG is also for Android and offers the V2Fly core. All three clients are open source, but their interfaces and supported features may differ.

The client itself is not a subscription service. Installation, subscription import, core startup, and remote connectivity are four separate states to verify. Contact your configuration provider about expired service, changed remote parameters, or device limits. Check local permissions, port conflicts, and whether an app uses the proxy on your device. Knowing where each issue belongs can prevent unnecessary reinstalls.

Open-source licenses and routine updates

Open source means code is available under the terms of its applicable license for reading, study, and permitted use. It does not mean every related project uses the same license. Clients, cores, and bundled components may each have different terms. Before redistributing, modifying, or integrating software, read the relevant project licenses; “free to use” does not mean unrestricted redistribution.

Back up local settings before updating, and check for changes to the interface, configuration format, and core compatibility. After updating, verify subscription import, core startup, the system proxy, and your frequently used apps in sequence. Avoid changing everything at once. Subscription updates sync service parameters; client updates change software features and compatibility. Manage them separately and keep a record of important changes.

Client setup and troubleshooting guides

Choose an article based on the symptom. Startup failures, port conflicts, and apps that ignore the proxy usually need different checks. Record your current settings first, then follow the steps one at a time to avoid turning a local issue into a complete reconfiguration.