V2RAY DESKTOP CLIENT · v2rayN

V2Ray PC v2rayN Client Download & Setup.

From choosing a platform to importing a subscription, learn how routing and local proxy settings work in practice.

  • Open-source code
  • Multiple core options
  • Setup guides

CLIENT SETTINGS / WORKSPACE AGENDA

How v2rayN Settings and Configuration Fit Together

First understand how traffic enters the client, then decide how it leaves.

Not every switch in the client interface maps to a configuration file field with the same name. The system proxy provides an entry point for applications; routing rules select an outbound; subscription groups organize connection details; and the core runs the generated configuration. Keeping these layers separate makes it easier to troubleshoot a client that starts but cannot connect: check the entry point, rules, and outbound in that order instead of changing everything at once. These five workspace settings are among the most commonly used when getting started.

"listen": "127.0.0.1"

The system proxy is a good place to start when testing a connection in a browser. With automatic configuration enabled, apps that follow the system proxy settings send requests to the local inbound. Apps that manage their own network connections may still connect directly. The listening address shown above belongs to the core's inbound configuration, not to the system proxy switch itself. This entry point is easier to enable and disable centrally than setting a proxy in each app, but it does not replace routing. Check the listening port, then test a webpage. Clear the system proxy before quitting to prevent apps from trying to reach a local service that has stopped.

See the configuration reference →

DOWNLOADS / PLATFORM SELECTION

Choose a V2Ray Client for Your Platform

Use v2rayN on desktop; start with v2rayNG on Android.

Check your operating system and processor architecture before choosing an installer. The client name, interface type, and core refer to different layers: the interface manages configuration, the core handles connections, and the package format determines how the system installs the software. The download page lists options for each platform with notes on compatibility. For your first setup, keep the defaults, get through import, startup, and a browser test, then add routing or virtual network interface settings one at a time.

Windows

Recommended: v2rayN

v2rayN comes in a desktop edition and a classic WPF edition. The desktop edition uses a cross-platform interface, making it a good fit if you want a consistent workflow across computers. The WPF edition keeps the classic Windows experience and suits users who already know it. Check system requirements first; there is no need to install both just because their interface names differ.

After installation, check whether another program is using the local listening port, then import your connection details. If you manually configured a proxy in your browser before, check whether it is still overriding system settings. Menus may be in different places in the two interfaces. When troubleshooting, focus on the actual proxy mode, core status, and log output rather than comparing window appearance.

macOS

v2rayN

Choose the Apple Silicon or Intel download based on your Mac's processor. Check About This Mac for the chip or processor details; this is more reliable than guessing from the year you bought it. The v2rayN desktop interface manages subscriptions and configuration, while system proxy permissions, network access, and core operation need to be checked separately.

When you first open the app, follow the system prompts to handle permissions. Avoid lowering system security settings long-term just to complete an installation. If a connection works in some apps but not others, first check whether those apps use the system proxy. For broader traffic coverage, read about TUN mode and system routing before enabling them.

Android

Recommended: v2rayNG

On Android, start with v2rayNG, which uses the Xray core; v2flyNG, which uses the V2Fly core, is an alternative. Most recent devices work with the arm64 package. If you are unsure of your device's architecture, check the universal version notes on the download page. The two apps manage their own connection details, so importing into one does not sync them to the other.

When starting a connection, approve the system VPN permission. This allows the app to create a local virtual network interface; it does not mean a working service is connected. If the connection frequently drops in the background, check battery optimization and background activity restrictions. For apps that need to bypass the proxy, configure per-app proxying and confirm whether the list uses include or exclude rules.

Linux

v2rayN

Choose deb or rpm based on your distribution's package manager, then check whether your processor is x64 or arm64. When using v2rayN on a graphical desktop, also check how the desktop environment manages the system proxy. Browsers, command-line tools, and background services on the same computer may not use the same proxy settings.

To get started, connect an app that supports manual proxy settings to the local inbound. This helps separate desktop configuration issues from core connection issues. Set up virtual interface permissions and check for routing conflicts only when you need TUN. If you get intermittent disconnects after changing network management tools, check whether DNS routing or the default route has changed.

Browse all clients →

GETTING STARTED / FIRST CONNECTION

v2rayN Setup Guide: Start with These Three Steps

Import connection details, choose an entry point, and test the connection—change one layer at a time.

STEP 01 / IMPORT

Import a Subscription or Single Connection

After installing the client, you still need connection details that you are authorized to use. A subscription URL retrieves a set of entries; a single share link describes one connection. They are not interchangeable with ordinary webpage URLs. Add and update a URL in a subscription group, or import a single link from the clipboard. Then check that the server address, port, protocol, and transport settings match the source.

Do not post subscription links in public forums or leave full access parameters visible in help screenshots. Seeing entries in the list only means the details were parsed; it does not mean the service is currently available. If the list is empty, first check that the copied text is complete and whether the subscription needs updating. Then troubleshoot proxy settings, rather than mistaking an import problem for a routing issue.

Read the import guide →

STEP 02 / MODE

Choose a Connection and Proxy Mode

Select the connection you want to use, start the core, then enable a proxy entry point that suits your apps. For an initial test, start with the system proxy so a browser that follows system settings can connect to the local service. Routing determines how requests are handled after they enter the client; the system proxy determines how apps send requests to it. These solve different problems, so changing the routing mode will not help if an app is not using the proxy.

Keep the default routing and DNS settings for now; there is no need to enable TUN or import a large set of custom rules right away. If other proxy, VPN, or traffic-interception tools are running on the computer, check whether they conflict over the system proxy, listening ports, or default route. When comparing configuration files, focus on the inbound address and port, outbound tags, and whether the tags referenced by routing rules match.

Compare routing configurations →

STEP 03 / VERIFY

Test the Connection with a Real Request

Use the same browser and test destination, then check whether the client log shows the corresponding request. A successful port test only means one connection step can be established; it does not prove that the full proxy chain works. Actual access also depends on the protocol, security negotiation, DNS, and routing. If the test fails, read the first clear error in the log before deciding whether to check the connection details, server, or local entry point.

If only one app fails, start by comparing its proxy settings. If all requests fail, check whether the core is running and the selected connection is valid. Change one setting at a time and repeat the same test, keeping a working baseline. When sharing troubleshooting details, include the operating system, client interface, selected core, and relevant error lines—but remove subscription URLs, user IDs, and authentication details.

Browse troubleshooting questions →
Read the full guide →

OPEN-SOURCE ECOSYSTEM / PROJECT V

V2Ray, V2Fly, and Xray Core Differences

The client is the interface, the core is the connection engine, and the protocol is the agreed way they communicate.

Searches for “V2Ray official website” can easily lead to project documentation, core releases, and client download pages being mixed up. This site organizes desktop client downloads and usage guides; it is not the official release source for protocols or core projects. Understanding what each project does helps you find the right information: check client guides for installation issues, the relevant core docs for field behavior, and your service provider's configuration for connection parameters.

Project V's Modular Configuration Model

V2Ray in the Project V ecosystem organizes connection handling into modules such as inbounds, outbounds, and routing. An inbound receives requests from local apps or other programs; an outbound describes how requests are sent onward; routing connects the two. This explains why choosing a server is not the whole configuration: you also need an entry point for app traffic and rules that direct requests to the right outbound. A graphical client puts common tasks in one window and makes setup more accessible, while the underlying configuration still follows these relationships.

When reading JSON, start by identifying each module's tags and references, then look at the protocol parameters. A configuration can be syntactically valid and still route traffic incorrectly. For example, a rule might reference the wrong outbound tag, or an app might not connect to the local inbound at all. The configuration reference explains fields by module. It is best read section by section after establishing a basic connection, rather than replacing an entire working configuration at once.

How V2Fly and Xray Have Evolved

The V2Fly community continues V2Ray's open-source development and maintenance. Xray grew from related code into an independently evolving core project, with its own implementations of protocols, security, and transport features. The two share some concepts and configuration conventions, but they are not interchangeable simply because one program name replaces another. To determine which core a connection needs, check its protocol, transport, and security options—not just whether it is described as “V2Ray.”

For example, when you see the VLESS protocol, also check whether it is paired with a particular security mechanism and whether the client can generate the right parameters for the selected core. Core support for a feature does not guarantee that every client interface offers the same controls. If importing succeeds but startup fails, compare the generated configuration with the core's requirements before editing the connection or switching cores. This is usually more effective than repeatedly importing it.

What Three Open-Source Clients Do

v2rayN is for desktop environments, with connection management, system proxy, routing, and multi-core configuration options. v2rayNG is for Android and primarily combines the Xray core with connection management and local VPN access. v2flyNG is also for Android and offers an alternative based on the V2Fly core. All three are maintained as open-source projects, but each client and the core it calls are separate software components, with their own release schedules, configuration support, and licensing terms.

The v2rayN and v2rayNG clients use GPL-family open-source licenses, while the V2Fly and Xray cores use MPL-family open-source licenses. Refer to the license text included with each project for the exact terms. Open source means the code and license conditions can be reviewed; it does not mean every subscription source is trustworthy. Clients also do not include connection resources that replace a server. Availability depends on the connection details, network conditions, and server configuration.

Update the Client, Core, and Rules Separately

A client update may change the interface, import behavior, or configuration generation. A core update may affect protocol support and field behavior, while an update to rule resources can change how destinations are matched. These changes affect different layers, so “everything is up to date” is not a useful troubleshooting record. Keep a working configuration and necessary settings before updating. Afterward, retest the existing connection before enabling new features; comparing each layer separately makes differences easier to pinpoint.

Likewise, updating a subscription refreshes connection details from its source; it does not necessarily update the client, core, or local custom rules. When reporting a problem, specify which layer was updated instead of saying only “it broke after an update.” If your setup is already stable, read the release notes and check whether the changes affect your protocol and operating system before updating and testing. This avoids stacking multiple changes into a single test.

LATEST GUIDES / READING NOTES

Client Selection and Advanced Routing

Once you have a basic connection, explore topics that match your needs. Interface differences affect which installer to choose; rule order affects where traffic goes; Router Setup involves the gateway and DNS for your entire local network. The articles below cover each topic, taking you from a single-device setup to more specific network environments.

Browse all articles →