Clients & ConfigurationXray · V2Fly

V2Ray CommunityDownload v2rayN

Choose an open-source client for your platform, then follow the configuration guides to import subscriptions and check routing and DNS.

  • VMess
  • VLESS
  • Routing

Browse downloads by platform

01 Downloads by platform

v2rayN, v2rayNG, and v2flyNG downloads

Start with your operating system, then check the processor architecture and package format. Use v2rayN on desktop; on Android, choose a client with the Xray or V2Fly core required by your subscription.

Windows

v2rayN comes in Desktop and classic WPF versions. If you’re installing it for the first time, start with Desktop. Choose the classic version if you’re used to WPF or following a guide that refers to its menus.

Back up your existing configuration before switching versions, then check the download page for runtime requirements. The first time you open the new interface, confirm that your subscription groups and local listening ports are still set as expected.

Go to downloads

macOS

The two v2rayN packages are built for different processors. If About This Mac shows an Apple chip, choose arm64; if it shows an Intel processor, choose x64. Don’t guess based on the computer’s appearance or purchase date.

When moving from another desktop operating system, you can import your subscriptions again, but review system proxy and startup settings for the new machine. For your first connection, test with just one browser.

Go to downloads

Android

v2rayNG, which uses Xray, is the usual choice. Use v2flyNG if your subscription or existing configuration specifically targets V2Fly. The clients have similar interfaces, but their cores may not support the same config fields.

Most recent phones can use the arm64 package. If you’re unsure which architecture your device supports, check its system information or choose the universal package. After importing, select a node and start the connection.

Go to downloads

Linux

v2rayN offers deb and rpm packages. Debian and Ubuntu generally use deb; Fedora and similar distributions use the appropriate rpm package. Then choose x64 or arm64 to match your system architecture.

Desktop environments and applications don’t all handle proxy settings the same way. A client that starts successfully only confirms that the program is running; verify in the target application that requests are going through the local proxy.

Go to downloads

Browse all clients

02 Configuration

Writing V2Ray configs and configuring clients

Start with one routing rule: decide what to match, then where to send matching traffic. Clients turn these choices into form fields, but the core still applies them from the underlying configuration.

Edit JSON directly

  • A misplaced bracket, comma, or array level can make the core exit before it even reaches the rules.
  • Routes and outbounds are configured separately. If you rename an outbound tag, check every rule that references it.
  • When updating a set of nodes, distinguish connection parameters provided by the subscription from settings managed on your device.

When reusing a configuration, review inbounds, outbounds, and routing separately. First test the connection with one inbound and one outbound, then add routing and DNS settings one at a time. This makes problems easier to isolate than copying a whole config at once.

Configure settings in the client

  • Enter a listening address and port in the form, and the client generates the corresponding inbound configuration.
  • Reorder rules in the routing list and assign an existing outbound to each one.
  • Update nodes by subscription group, keeping the node list separate from local routing settings.
routing.rules · Route domain suffixes directly
{
  "type": "field",
  "domain": ["domain:example.org"],
  "outboundTag": "direct"
}

This is a rule, not a complete configuration. It also needs an outbound tagged direct. The tag is just a name; the outbound’s protocol determines what it actually does.

03 Setup guides

From subscription import to DNS settings

Get one node working before adding routing and other settings. If connectivity changes, revert one setting at a time to find out whether the issue is with the node, routing, or DNS resolution.

Import subscriptions

A subscription URL provides a refreshable list of nodes; a single share link adds just one node. In v2rayN, create a subscription group, paste and save the URL, then update the group. Once the nodes appear, select one and test the connection. Unlike importing links one at a time from the clipboard, subscriptions let you refresh the whole group at once. In v2rayNG, the option is usually under subscription settings. If the list is still empty after updating, first make sure you have a subscription URL, then check that it’s accessible.

Subscription group settings

The client is running. Why isn’t my app using the proxy?

A connected status in the client doesn’t mean every app is using the proxy. The system proxy only affects apps that follow system settings, and some apps have their own proxy options. First reproduce the issue in an app known to use system settings, then compare the target app’s configuration. Avoid changing the port, node, and DNS all at once.

See connection checks and troubleshooting steps

Can’t find a setting with the same name?

Interface labels don’t always map one-to-one to core fields. For example, a local listening port usually belongs to an inbound object, not a global port setting. First identify whether you’re editing an inbound, outbound, or route, then compare it with a reference example. When copying a rule, keep the outbound tag it references.

Explore V2Ray config fields

04 Open-source ecosystem

Project V, V2Fly, and Xray cores

The project ecosystem, runtime core, and graphical client are three distinct layers. When working with a configuration across devices, first identify which core interprets its fields, then choose where to import it.

How traffic flows between the client and core
  1. Graphical clientOrganizes subscriptions and rules, then generates the configuration
  2. Runtime coreReads the configuration, listens for inbound traffic, and matches routes
  3. Outbound connectionConnects or rejects requests according to the outbound settings
Compare the three clients

Project V: from a single connection to composable configurations

V2Ray is a proxy core in the Project V ecosystem. A useful way to understand it is through three configuration objects: inbounds receive requests from apps, outbounds define where requests go, and routing selects among available outbounds. Because these parts are independent, you can replace a node without changing local listening settings, or add a direct rule without changing the node. Older guides often start with a JSON file; newer graphical interfaces split the same concepts across different menus. When an interface changes, looking for a field by what it does is often more reliable than following its location in a screenshot.

V2Fly and Xray: similar structures, different implementations

V2Fly is maintained by the V2Ray community, while Xray developed into an independent implementation based on V2Ray’s code. They share many inbound, outbound, and routing concepts, so examples from one can help explain the other. But supported fields, defaults, and protocol extensions may differ. For example, a node using REALITY requires a core that supports the corresponding handshake and security settings. Recognizing a VLESS link in the interface doesn’t guarantee it can connect. Successful import only means the client read some of the information; the core must still be able to interpret the generated config and complete the handshake.

How the three open-source clients differ

v2rayN is an open-source desktop client for managing nodes and subscriptions, configuring the system proxy, and calling supported cores as needed. v2rayNG is an open-source Android client primarily using Xray; v2flyNG is also open source and targets the V2Fly core. Clients and cores are separate projects, so check their licenses and release notes independently. Open source makes field handling, defaults, and changes inspectable, but doesn’t guarantee that a subscription is trustworthy or that settings transfer unchanged between tools. Choose based first on your device and node requirements, then on specific features such as LAN sharing.

Client upgrades, core updates, and subscription refreshes

A client upgrade may change the interface or how configurations are generated. A core update can affect protocol handling, logs, and supported fields. A subscription refresh simply reloads the node list provided by the server. These can happen independently. When something breaks, think about what changed most recently: if only new nodes from one subscription group fail, compare their parameters first; if several nodes stop starting after a core update, check the startup log for config errors. Keep a restorable copy of local settings before upgrading. Afterward, test a node that worked before, then check custom routing and DNS.

When migrating a configuration, separate what can be reused from what needs resetting

When using the same node on different devices, you can usually reuse the server address, protocol, and related transport parameters. Listening addresses, system proxy settings, LAN permissions, and routing rules depend on the device. A subscription refresh may not sync those local settings. During migration, import only known-good nodes first and verify that apps connect, then move routing and DNS settings over one at a time. If the results differ between devices, note the selected outbound, how the app connects, and the first relevant log entry; this makes differences easier to pinpoint than changing several switches repeatedly. Subscription URLs may contain access credentials, so don’t expose the original URL when backing up or sharing logs.

05 Recent articles

Installation, DNS, and LAN setup

For a first install, start with the desktop setup guide. Once connected, explore DNS and sharing guides to see which requests are affected by each setting.

v2rayN on Windows: installation and setup, choosing between WPF and Desktop, and troubleshooting common issues

Follow the full v2rayN setup process on Windows, from extracting the app and first launch to importing subscriptions and configuring the system proxy. Compare WPF and Desktop, and troubleshoot common issues such as missing runtimes and ports in use.

For first-time installs or anyone who can’t find settings after switching interfaces. The guide verifies that the app starts, subscriptions update, and apps actually use the proxy as separate steps.

Read the installation and setup guide

Browse all articles