v2rayN Download & Guide Hub v2rayN downloadsand setup guides

Choose a client by platform, then configure subscriptions, routing, and the system proxy step by step.

Desktop: v2rayN Android: v2rayNG / v2flyNG Core ecosystem: Xray · V2Fly · sing-box

CONFIGURATION LAYERS

Subscriptions, routing, and core settings

The graphical client organizes configuration; the core handles connections. Check subscription sources, traffic entry points, and outbound rules separately to pinpoint issues more easily than by changing several settings at once.

Manage subscriptions by source without overwriting manual configurations

A subscription URL provides a set of server configurations; it is not a single server address. In v2rayN, create a subscription group, add a recognizable remark, paste the full URL, and run an update. Create a separate group for each source so you can refresh, disable, or troubleshoot them independently. Subscriptions make it easier to maintain multiple configurations over time than entering server details one by one, but an update may remove entries deleted by the source. Manage any manual configurations you need to keep separately. If an update fails, check the request error in the logs first, then determine whether you need to update through an existing proxy.

Subscription group settings
RemarksName by source
Subscription URLEnter the full URL
Subscription updates
Enable updatesSet per group
Update resultCheck the logs

Troubleshooting for connection failures, subscription errors, and DNS issues →

CLIENT DOWNLOADS

Choose a client by operating system

Use v2rayN on desktop. For Android, start with v2rayNG; consider v2flyNG if you need a V2Fly core. Package architecture and configuration protocol are separate concerns: choose the right architecture for your device, then check subscription compatibility.

Windows

v2rayN · Desktop / WPF

Windows users can choose between the desktop edition and the classic WPF edition. The desktop edition uses a newer cross-platform interface, while WPF retains the classic desktop experience. Check system requirements for either edition, then choose the one that suits your workflow. There is no need to run both just to import the same subscription.

If you already have a configuration, back up your subscription groups, routing rules, and personal settings before switching clients. After installation, check the local listening port and system proxy status in the tray to make sure your browser is not still pointing to an old instance. The system proxy affects only apps that follow that setting; check the proxy entry point inside any app configured to use its own proxy. If a port is already in use, close the old instance before changing ports repeatedly.

macOS

v2rayN · Apple Silicon / Intel

On macOS, check your chip type in About This Mac, then choose the Apple Silicon or Intel package. Move the app to the Applications folder before opening it for easier management. If macOS shows a security alert, verify the file source and alert details first, then grant the required permission under Privacy & Security.

For your first setup, avoid enabling every traffic-capture option at once. Import a subscription, select a server, then set the system proxy and test with a browser. If the browser works but other apps do not, check whether they use a separate proxy or ignore system settings. If all requests fail, check the core logs and network permissions. Clear proxy settings you no longer need before quitting the client to avoid mismatched entry-point settings the next time you start it.

Android

v2rayNG · Xray / v2flyNG · V2Fly

On Android, start with v2rayNG, which uses the Xray core. If you need a configuration for the V2Fly core, consider v2flyNG. Most recent devices use arm64; if you are unsure of your device architecture, look for a universal package. These are separate clients: installing one does not share its subscriptions or routing settings with the other.

After importing a configuration, approve the system VPN permission the first time you connect. A connected status means local traffic capture is active; it does not guarantee the remote server is reachable. If the connection drops in the background, check battery optimization, background activity, and power-saving settings. For per-app routing, confirm the target app is included. Avoid having multiple VPN connections compete for the system entry point; keep just one active connection while troubleshooting.

Linux

v2rayN · deb / rpm

On Linux desktop, choose deb or rpm according to your distribution's package system, then check whether your processor is x64 or arm64. The same package format does not guarantee identical dependencies across distributions, so review any dependency messages from your package manager. Desktop shortcuts, tray support, and system proxy integration may also vary by desktop environment.

After installation, launch the client manually and confirm subscription updates and browser access work before enabling startup at login. A desktop environment's system proxy settings usually do not carry over to terminal tools, so check proxy settings separately in terminals and developer tools. If the window opens but connections fail, first check that the core started successfully, the listening port is available, and the configuration directory has normal read/write permissions. Do not use elevated permissions as a substitute for troubleshooting.

Browse all clients →Compare the three clients →

FIRST CONFIGURATION

From subscription import to connection testing

For your first setup, establish a connection you can verify before adding custom routing or other traffic-capture options. Change one thing at a time and keep settings easy to roll back.

STEP 01 / IMPORT

Import a subscription and check the server entries

Get the full subscription URL from your configuration provider. In v2rayN, add a subscription group, enter a remark and the URL, save, then run an update. If you have a single share link, use the appropriate import option instead of entering it as a subscription URL. On Android, do the equivalent in v2rayNG's subscription settings; menu names may vary by version.

When the update finishes, check that the group contains the expected configurations, then select one as the current server. A subscription distributes connection parameters; it does not include server service. Free clients and subscription services are separate things. URLs may contain access credentials, so do not post them in public comments or screenshots. If the group is empty, check the update logs to see whether the request failed, the response could not be recognized, or the source had no available entries.

STEP 02 / ROUTE

Choose a routing mode and set the traffic entry point

On desktop, choose a routing preset suited to your network, then enable automatic system proxy configuration. The routing preset controls how requests are sent out after they enter the core; the system proxy determines which apps send requests to the local listener. They are not interchangeable. If you need access to local network devices, check the private address rules to avoid sending local traffic through a proxy outbound.

For initial testing, use a browser that follows the system proxy; there is no need to enable additional traffic-capture options at the same time. On Android, approve the VPN permission and check the scope of per-app proxy settings. If you have a browser proxy extension, another proxy client, or network filtering software, check each for conflicts. Keep the fewest possible configurations active, confirm they work, then restore your usual settings one by one. This makes differences easier to identify than switching several modes at once.

STEP 03 / VERIFY

Test websites, DNS, and shutdown behavior

After connecting, open a commonly used website, then visit a site or local network service that should connect directly. Test both the proxy and direct paths. Do not assume everything works based only on the tray icon, connection button, or a single test. If only certain domains fail, check the route that matched the request, the DNS server, and the resolution results. If every site fails, start with the system proxy, local listener, and core startup status.

Record the app, domain, and time of a reproducible issue, then compare them with errors in the logs. Troubleshoot in order from entry point to outbound: app settings, local port, selected server, routing, and DNS. Repeat the same test after each change so the results are comparable. When finished, clear the system proxy or disable the relevant traffic-capture option before quitting. If websites stop working after you quit, first check whether the system still points to a local proxy address.

PROJECT V / CORE / CLIENT

The Project V ecosystem and how its clients fit together

Client, core, and protocol names often appear together, but they serve different purposes. Understanding these three layers helps you decide whether to change a setting in the graphical interface or consult the configuration guide for the relevant core.

Project V, V2Fly, and Xray

Project V is an open-source ecosystem built around proxy communication and network configuration, with V2Ray as one of its widely used core projects. V2Fly continues related community development, while Xray grew from the same technical lineage into an independent implementation with its own extensions. They share some concepts, but their capabilities, field meanings, and release cycles are not identical. When a guide is labeled V2Ray, check which specific core its examples target rather than assuming they apply based on similar names.

VMess, VLESS, and Trojan are connection protocol concepts; transport methods and security layers are separate configuration dimensions. A protocol appearing in a client does not mean every combination of fields will work. The client must be able to import it, the core must support it, and the server parameters must match. When troubleshooting handshake or configuration loading errors, preserve the meaning of the original parameters rather than repeatedly switching protocol names.

What sets these three open-source clients apart

v2rayN is for desktop environments, with a graphical interface for subscriptions, servers, routing, and system proxy settings, and support for cores such as Xray and sing-box. v2rayNG is for Android and uses the Xray core; v2flyNG is also for Android and offers an alternative based on the V2Fly core. All three are open-source projects, but they are not simply the same app renamed for different devices. Their interfaces, import support, and background behavior differ.

The client organizes user settings into a configuration the core can understand; the core handles protocols, routing, and connections. sing-box has its own configuration structure, so do not use Xray JSON as-is. When choosing a client, start with your operating system and configuration needs, then consider the interface and maintenance workflow. Switching clients repeatedly will not fix an expired subscription source or mismatched server parameters.

Open-source licenses and configuration sources

Open source means project code is available under its applicable license. Use, modification, and redistribution must still comply with each license's terms. Clients, cores, and dependencies may use different licenses; consult the license files included with the relevant projects. Public source code does not make every distribution file, subscription source, or network environment equally trustworthy, nor does it mean every configuration suits your device by default. Understand the source of your installation and the contents of your configuration.

All three clients are free to use, but running a client and obtaining remote service are separate things. Subscription URLs may contain account identifiers, and server configurations may include authentication details. Before sharing troubleshooting logs, remove sensitive subscription URL parameters, authentication fields, and personal browsing records. Configuration snippets in this guide explain structure; they are not a substitute for valid connection details from your service provider.

Community maintenance and update order

Clients and cores are maintained by their respective communities, so interface changes, protocol support, and configuration compatibility may evolve independently. Before updating, read the release notes and back up subscription groups, custom routing, and any personal settings you need. After updating, check that the client starts, the core loads, subscriptions update, common websites work, and local network access is intact. Avoid combining a software update, subscription refresh, and routing rewrite in one operation; otherwise, it is harder to identify the cause of a problem.

If your current setup is stable, plan updates around your needs rather than comparing names or release dates alone. If a guide's menus differ from your interface, look for the feature by what it does, then consult the client and core documentation. This site provides download guidance and configuration guides, not subscription accounts or remote servers. Connection availability still depends on your local network, server status, and matching parameters on both ends.

Compare v2rayN, v2rayNG, and v2flyNG →

CONFIGURATION NOTES

Recent setup and troubleshooting guides

Start with the specific symptom. Identify which entry point the request uses, then check resolution, rules, and outbound routing layer by layer instead of attributing every issue to the client.

Advanced

V2Ray DNS Setup: Split DNS for Mainland China and Overseas Domains

Covers the V2Ray dns module's servers, domains, and expectIPs fields, with practical examples for resolving mainland China domains locally, sending overseas domains to remote DNS, and reducing DNS pollution.

Keep separate the question of which resolver handles a domain and which outbound carries the connection. Domain rules, filtering resolution results, and IP routing are distinct steps. Record the current resolution path before making changes, then retest the same domain. Changing the DNS server alone may not change the actual request path.

Read the guide →
Troubleshooting

v2rayN Connected but Websites Won't Load: Troubleshooting Checklist

If the proxy is on but websites will not load, check system proxy settings, port conflicts, server availability, time synchronization, routing mode, and DNS in order to pinpoint the issue.

The connection icon shows only part of the local status. This guide starts by checking whether the app sends requests to the client, then rules out listener, remote connection, and DNS issues step by step. Retest the same destination each time to see whether a setting change actually worked.

Read the guide →
Advanced

V2Ray JSON Configuration Explained: inbounds, outbounds, and routing

A section-by-section guide to V2Ray JSON configuration: log, local inbounds, outbounds such as freedom and blackhole, and routing rule order, with examples to follow.

For users already working with a graphical client who want to understand its generated configuration. Start with how inbounds receive traffic, routing matches rules, and outbounds handle requests, then examine individual fields. Pay close attention to tag references and rule order to avoid valid syntax that sends traffic somewhere other than the intended outbound.

Read the guide →

Browse all articles →