V2Ray ClientsDownloads and Setup Guide

v2flyNG Downloadv2rayN and V2Ray Setup Guides

Choose an open-source client and follow the Chinese instructions to import a subscription and configure routing.

Subscription Management Local Proxy Xray · V2Fly
socks/http 127.0.0.1:10808Routing: Bypass mainland China

Client settings example · Open Getting Started with the connection button

Choose a client for your platform

Use v2rayN on desktop; for Android, start by looking at v2rayNG. Check your device architecture before choosing an installer, and keep client names distinct from core names.

Windows

v2rayN offers desktop and classic WPF downloads. The newer cross-platform interface and classic interface have different menus, but the basic steps—importing a subscription, choosing a server, and setting the system proxy—are the same.

Check your device type in system settings, then choose the matching download based on the platform notes. After installation, keep the configuration in its original location. Avoid placing files from different client builds in the same folder, so you can tell them apart when troubleshooting.

Go to downloads

macOS

v2rayN offers separate downloads for Apple Silicon and Intel Macs. Check your chip under About This Mac and choose an installer that matches its architecture.

Follow the system prompts to grant app permissions the first time you open it. After launching the client, check your subscription and system proxy settings. Whether a browser uses the proxy also depends on whether it follows system settings.

Go to downloads

Android

v2rayNG uses the Xray core, while v2flyNG offers an alternative based on V2Fly. Most newer phones can start with the arm64 package; if you are unsure of your device architecture, check the universal build notes.

After importing a configuration, approve the system VPN request on first launch. If another app using the same system interface is running, check for conflicts. For background connection drops, review battery management and background-running permissions.

Go to downloads

Linux

v2rayN offers deb and rpm packages. Check your distribution's package format first, then confirm your processor architecture. The desktop environment, system dependencies, and the app's proxy options can also affect how it works.

GUI apps and terminal programs may use different proxy settings. After configuring the client, test an app that follows the system proxy, then configure any terminal tools that need a proxy separately. Don't rely on the tray icon alone to determine where traffic is going.

Go to downloads

Subscriptions, Routing, and Local Ports

The client turns configuration into connection settings. Follow these five sections to understand what each setting does before changing it.

Importing a Subscription and Updating Groups

A subscription URL retrieves a set of server configurations; it is not the same as a share link for one server. Add the URL to a subscription group in v2rayN, save it, then update the group and check that usable entries appear. Keep different sources in separate groups to make updates and filtering easier. Subscription contents may include credentials, so don't post them publicly. After an update, select an active server and confirm your system proxy and routing settings. Subscriptions are easier to maintain than entering servers one by one, but parsing still depends on the client supporting the subscription format.

  • Open: Subscription Groups
  • Add: Group name and subscription URL
  • Update: Fetch the server list
  • Select: Set as active server
  • Check: System proxy and routing mode

Map Interface Options to Configuration Fields

Subscription imports determine where server parameters come from; routing determines where requests go; local listening determines how apps connect. Track these as separate issues. If a connection fails, identify which layer is involved and check its settings. This makes results easier to reproduce than changing several options at once.

In a configuration file, inbounds defines inbound connections, outbounds defines outbound connections, and routing handles matching and routing. DNS and policy settings also affect resolution and connection behavior. Configurations generated by the GUI can vary by core, so these snippets can't be combined into a universal configuration. For a field-by-field reference, see the V2Ray Configuration Reference.

Three Steps to Set Up a Client

Installing the client is only the first step. You also need a valid server configuration and proxy settings that match how your apps work. Run through the checks in order, then add automatic updates or custom rules.

  1. Step 01

    Import a Subscription and Check the List

    Get a subscription URL from a trusted source, add it to a subscription group, and update the group. When the update finishes, check the server entries' protocol types and group assignments, then select an active server. Use the appropriate import option for a single share link; don't enter it as a subscription URL.

    If the list is empty, check the client message first. Make sure the URL is complete, contains no extra spaces, and is still valid. You haven't reached the connection stage yet, so changing the routing mode usually won't fix a subscription format error.

  2. Step 02

    Check Routing and Start the Connection

    On desktop, check the system proxy option and choose a routing preset that suits your needs. On Android, approve the connection when prompted by the system. Make sure the local port is listening before testing access. If startup fails, start with the first specific error in the logs.

    “Global” usually describes the scope of routing; it doesn't mean every app will automatically use the client. Some apps have their own proxy settings, and terminal tools may rely on environment variables. Check how traffic enters the client separately from how it is routed.

  3. Step 03

    Test Requests and Keep Working Settings

    Open a destination in the app you actually plan to use, then check the client logs to see whether the request reached the core. A latency test shows only the result of a particular probe; it can't replace checks of real-world scenarios such as page loads, downloads, or long-lived connections.

    Once everything works, note the client, core, local port, and routing mode. Change only one variable at a time later, and keep the original settings. After testing, if you no longer need the client, check that the system proxy has returned to the expected state.

Project V and the Core Ecosystem

Distinguishing projects, cores, and GUI clients makes it easier to know where to look for a feature. Open-source status describes how software is developed and licensed; actual compatibility still depends on the configuration and runtime environment.

Ecosystem Background

Project V

Understanding V2Ray's Modular Proxy Design

Connection Processing

V2Fly / Xray

Handle protocols, transport, resolution, and routing

GUI Management

v2rayN / v2rayNG / v2flyNG

Manage subscriptions, servers, and app settings

Project History and Modular Configuration

Project V is a good starting point for understanding the V2Ray ecosystem. Its configuration model separates local access, remote connections, and routing into distinct modules that can be combined as needed. The V2Fly community continues related V2Ray development and maintenance, while Xray has evolved from the same technical lineage into its own implementation. They share a background but have followed different development paths, so similar-looking configurations don't guarantee they can be swapped directly.

For users, understanding how inbounds, outbounds, and routing relate is more useful than memorizing every field. A protocol defines how two sides communicate; transport carries the connection; TLS and similar options belong to another layer. Checking each layer in turn helps distinguish DNS resolution failures from protocol incompatibility and avoids unnecessary core switches.

Open-Source Status of the Three Clients

v2rayN, v2rayNG, and v2flyNG are all open-source GUI clients. v2rayN organizes subscriptions, servers, and core settings for desktop environments; v2rayNG uses the Xray core on Android; v2flyNG offers another Android option based on V2Fly. Options in the interface are implemented by the client, while supported protocols and extensions also depend on the core.

Each open-source project sets its own terms for use, modification, and redistribution through its license. A client, its core, and bundled components may use different licenses, so check each one's terms separately. Project background can help explain where components come from, but software licenses aren't server service terms and don't guarantee the quality of any external subscription.

Check Compatibility Before Updating

Client updates may change menus, configuration storage, or core management; core updates may change supported fields or default behavior. Back up a working configuration before updating, and note your current routing and local port settings. With custom configurations, pay close attention to changed fields. Don't assume migration is complete just because the program opens.

After updating, test with the same app, destination, and routing mode. If results differ, check the logs and generated configuration before deciding whether to roll back. Subscription updates and client updates are separate: the former refreshes the server list, while the latter updates software capabilities. Keeping them distinct makes problems easier to describe.

Configuration Resources and Service Boundaries

This site organizes client downloads, usage instructions, and configuration references; it doesn't provide server subscriptions. Local addresses in the documentation illustrate listening behavior, and JSON snippets explain structure. Neither contains usable remote connection parameters. For actual setup, follow the current client interface, core documentation, and configuration provider's requirements.

When using network tools, follow the laws and network service rules that apply where you are. For help understanding configuration fields, see the configuration reference; to choose a client, read the client comparison. See the About page for project background and the scope of this site.

Configuration Guides and Troubleshooting

Start with an article that matches the issue. Choosing a server, managing subscription groups, and configuring app proxies each require a different troubleshooting path. Identify the scope first, then take action.