Project V · Client & Configuration Reference

V2Ray Starter Guide Download & Setup

From importing subscriptions to routing rules, use client menus and JSON fields to check local ports, system proxy settings, and DNS.

  • VLESS / VMess
  • Trojan / REALITY
  • Xray · V2Fly
Choose a platform
Find the menu, then edit the field

Client settings
and configuration

Keep three layers distinct: subscriptions store remote connection details; the system proxy determines whether apps send requests to the client; routing determines where connections that reach the core go. A successful import only means the settings were read—it does not mean your browser is using the proxy.

The sections on the right cover six common settings. Start with one subscription group and one working connection, then adjust routing and DNS. Change one setting at a time and keep its previous value so you can link log changes to a specific action if something goes wrong.

Explore config fields →

Menu names may change

If a button has moved, look for “Subscription groups,” “Settings,” or “Routing settings.” The diagram illustrates how settings relate; it does not show connection status. In the code, `direct` must reference a defined outbound tag. Copying a single rule alone will not produce a working configuration.

Subscription links and group updates

Subscriptions are useful for managing multiple connections in one place. In v2rayN, open “Subscription group settings,” add a group, paste the full URL, save, and select “Update subscription.” On Android, enter the URL under “Subscription group settings,” return to the home screen, and update. Unlike importing individual share links, a subscription lets you refresh connections by group. If an update fails, check the URL’s expiration, system time, and network path before doing anything else; don’t repeatedly delete the original group. Subscription URLs may contain credentials, so hide the full link in screenshots and support logs.

  • Subscription group settings → Address (Url)
  • Update subscription → Direct / Through proxy
  • Auto-update interval → Set as needed
Choose your OS, then your architecture

V2Ray client downloads

For desktop, choose v2rayN; for Android, start with v2rayNG. The right installer depends on your device’s processor architecture, not the protocol used by your subscription. These links open the corresponding platform section on the download page, where you can select the right package for your device.

Windows

v2rayN · Desktop client

The download page offers Desktop and classic WPF versions. Desktop uses a cross-platform interface, while WPF retains the familiar classic layout. Check the system requirements before choosing. If the device already has a configuration, export a backup first rather than overwriting your only working copy.

After the first launch, import a subscription and select an active connection before setting the system proxy. If your browser still can’t connect, check whether another program is using the local port and whether security software is preventing the client from starting the core. Read the specific error in the log before considering a reinstall.

Go to downloads

macOS

v2rayN · Choose by processor

Open “About This Mac” in the system menu and check whether it lists a chip name or an Intel processor. Choose arm64 for Apple Silicon and x64 for Intel. Confirm the architecture before selecting the installer on the download page; don’t rely on the device’s release year alone.

After installation, check that the system proxy is applied to the current network service. Wi-Fi and Ethernet may have different settings. If the connection fails after switching networks, check the proxy address and port for the active service. Apps with their own proxy settings need to be checked separately.

Go to downloads

Android

v2rayNG · v2flyNG

Start with v2rayNG using the Xray core. If you need a V2Fly core, look into v2flyNG. Most newer devices use arm64; if you’re unsure of the architecture, check the universal package details. The two clients manage configurations separately, so installing one won’t automatically transfer the other’s subscriptions.

Your first connection requires system VPN authorization. Other VPN apps running at the same time may interfere, so first check which app is handling traffic. If you enable “Per-app proxy,” check whether you’re using an allowlist or a blocklist so you don’t accidentally exclude the browser you’re testing.

Go to downloads

Linux

v2rayN · deb / rpm

Choose deb or rpm based on your distribution’s package system, then select x64 or arm64. The desktop client is suited to managing subscriptions and routing in a graphical environment. The same package format doesn’t guarantee identical system dependencies, so read the download page’s requirements before installing.

Desktop environments and apps handle system proxy settings differently. If your browser works but another program doesn’t, check whether it reads the desktop proxy settings, then look for its own HTTP or SOCKS proxy options. Don’t mistake one app’s failure to use the proxy for an unusable subscription.

Go to downloads

The client is a local connection tool; subscriptions and remote services must be configured separately. You can reuse a compatible subscription across platforms, but check the system proxy, app scope, and local ports on each device.

View all clients →
Separate the interface, core, and protocol

Project V and the open-source core ecosystem

“V2Ray” is often used as shorthand for a family of tools and configuration practices. When troubleshooting, specify the client, core, and connection protocol. A graphical interface that can import a link does not necessarily mean its underlying core supports every parameter in that link.

Project V

The configuration and proxy tools ecosystem

Requests arrive through a local inbound and are routed to an outbound; the graphical client provides menus and configuration management for this setup.

  • V2Fly → Community-maintained continuation of the V2Ray project
  • Xray → An independent core project developed from V2Ray
  • v2rayN / v2rayNG / v2flyNG → Graphical management clients

Project V: Start with the configuration structure

Project V is an open-source ecosystem built around network proxy tools, with V2Ray among its widely used implementations. Configurations typically separate listening endpoints, remote connections, routing rules, and DNS behavior into distinct modules. This makes it easier to isolate issues step by step: if there are no request records, check the inbound; if requests appear but use the wrong outbound, check routing; if a domain fails while its IP address works, investigate DNS. Don’t replace the subscription, core, and DNS settings all at once, or you won’t know which change made a difference.

V2Fly and Xray: shared roots, not interchangeable fields

The V2Fly community continues development of the V2Ray project. Xray grew out of V2Ray and later followed its own independent development path. They share some concepts and configuration conventions, but protocol support, security parameters, and field details vary by implementation. If you see an “unknown field” or “unsupported protocol” error, first identify which core is running and consult its documentation. REALITY is a transport security configuration; a link’s title alone can’t establish compatibility. It is not a standalone node type that can be applied to every protocol.

Three clients for managing connection settings graphically

v2rayN, v2rayNG, and v2flyNG are all open-source graphical clients. v2rayN manages subscriptions, routing, and cores on desktop. v2rayNG is primarily for Android and runs with the Xray core, while v2flyNG offers an Android client with a V2Fly core option. Each project’s own license governs its client; a core’s license does not automatically apply to every client. Choose based on your operating system and required features, then check whether your existing configuration is compatible—don’t assume clients are interchangeable because their names look similar.

Client, core, and subscription updates

These updates affect different things. A client update changes the interface and configuration generation; a core update changes the connection implementation; a subscription update refreshes connection details published by the service provider. Rule files for matching domains and addresses are another resource altogether. A successful subscription update won’t enable the system proxy or guarantee that rule databases are current. Back up subscription groups and custom rules before maintenance, read the update notes, and make one change at a time. If something breaks, record the exact error instead of just noting that it “doesn’t work.”

Trace the symptom to the setting

Imported successfully, but why isn’t my browser using the proxy?

Importing only saves the connection details. Select an active connection, confirm the system proxy is enabled, and check whether your browser follows the system settings. If the client log shows no corresponding request, check the inbound before changing remote ports. See system proxy settings for the steps.

Does global proxy mode route all programs?

Global mode in routing typically affects outbound selection for connections already inside the core; it doesn’t force every program to connect. Command-line tools, games, and standalone network components may need their own proxy settings. First identify how the app’s requests enter the client, then decide whether to split-route them. See how to test a connection.

What’s the difference between a share link and a full configuration file?

A share link usually describes a single remote connection. A full configuration also includes local inbounds, DNS, and routing rules. After importing a share link, the client combines it with local settings to generate the runtime configuration. Don’t paste a configuration file into the subscription URL field; start with the JSON structure overview.

Can node speed tests replace real-world access tests?

A single test only reflects its specific target and request method. A response doesn’t mean every app, domain, or protocol is working. After selecting a connection, test it in the app you actually use and compare the client logs. If you need to change connection parameters, see the protocol configuration guide.

When reading configuration fields, trace the connection path from inbounds to outbounds, then check routing, dns, and policy. Examples illustrate how fields relate; use the ports, tags, and server parameters configured on your device.

Browse by task

Recent configuration guides

After your first connection works, move on to sharing, migration, and DNS strategies. Each guide focuses on a specific task: check whether it applies to your setup before changing client settings. Hide sensitive details in screenshots that show credentials or addresses.

Advanced

Allow LAN connections in v2rayN: Share a proxy port with a TV box or another computer

Learn how to enable LAN connections in v2rayN, find your local address and port, configure a TV box or another computer to use the proxy, and handle firewall rules.

First confirm which proxy protocols the receiving device supports, then check the listening port and network scope. A loopback address on the sharing computer won’t work when entered on another device.

Read the sharing guide →
Platforms

Sync v2rayN and v2rayNG across devices: Shared subscriptions, config backups, and QR code migration

Compare ways to sync configurations between a computer and an Android device: share a subscription link, export a configuration file, or scan a QR code to share an individual node. Find out when each method is useful.

Moving remote connections and moving local rules are different tasks. After importing on a new device, check its system proxy, app scope, and DNS settings too.

Read the migration guide →
Troubleshooting

V2Ray DNS leak tests and prevention: Combine the dns module, FakeDNS, and routing

Learn how to tell whether DNS requests are bypassing the proxy, then configure DNS server groups in the dns module and combine FakeDNS with routing rules to prevent leaks.

Interpret test results in the context of how each app resolves domains. First distinguish system DNS from core DNS, then decide which layer to change. Changing server addresses alone may leave the query path untouched.

Read the DNS troubleshooting guide →