Choose a client for your platform, then configure subscription import, routing, and system proxy settings.
your-server.exampleReading path / START HERE
v2rayN is for desktop use on Windows, macOS, and Linux; v2rayNG and v2flyNG are for Android. Installing a client is only the first step: you also need server details or a subscription link, a selected server, rules for which apps use the proxy, and a working core. This page explains how those settings fit together. For step-by-step instructions, see the getting started guide.
A subscription link provides server configuration; it is not a client installer. Routing determines where traffic goes, while the system proxy controls whether apps that follow system settings can send requests through the client. Keeping these concepts separate makes connection issues easier to troubleshoot step by step, without repeatedly reinstalling the client.
Client settings / SETTINGS
These interface snapshots show setting names and illustrative values to help you find the right controls; they are not actual server configurations. Select a topic, read the notes on the right, then open the relevant guide to follow the steps.
Work profilehttps://example.com/subCreate a group under “Subscription groups,” paste the V2Ray subscription link provided by your service, then select “Update subscriptions.” The group name is only for your own reference; you must get the link from your provider, and the example URL shown in the interface will not connect. After updating, select a server in the group. If the list does not change, check that the URL is complete and the correct group is selected, then review the client logs. Create separate groups for different providers to make later updates and filtering easier to track.
See the import guide →Bypass LANDomain / IPRouting determines where requests go; it does not manage server accounts. To get started, choose an existing mode and adjust domain or IP rules to suit your needs. “Bypass LAN” keeps local devices such as printers and shared folders directly accessible. Rules only take effect if the app sends traffic through the client, so check the system proxy as well when troubleshooting. If you need different DNS resolution for different domains, see the DNS & Routing guide; routing rules and DNS resolution are separate settings.
See DNS & Routing guide →On desktop, select a server, then choose “Set up system proxy” from the system tray menu so apps that follow system settings can send requests through the client. To restore your previous settings before quitting, choose “Clear system proxy.” Terminal programs may not use the system proxy configured in the graphical interface, and browser extensions or apps with their own proxy settings may take a different route. If the browser and command line behave differently, check each app's proxy source before changing server fields.
Troubleshoot system proxy →VLESStcprealityVMess, VLESS, Trojan, and Shadowsocks are different protocol types available in the client. REALITY usually appears under transport security; it is not a server address or a routing mode. When adding a server manually, match the protocol, port, transport, and security settings to the server configuration. Imported subscriptions usually include these fields, so save the original details before making changes. Choose a protocol based on your existing service configuration and device compatibility, not just its name.
See protocol reference →XrayV2FlyThe graphical client manages subscriptions, settings, and connection controls; the core reads the configuration and handles connections. v2rayNG commonly uses the Xray core, while v2flyNG uses a core from the V2Fly family. Available cores for desktop v2rayN depend on the client's current settings. Before switching cores, check support for the protocols and transport features you need. After switching, review the logs and test access in your apps. If startup fails, check for port conflicts, misspelled fields, or incompatible settings rather than relying on the interface status alone to determine whether the server is available.
See how cores relate and which to choose →These settings have a clear order: get the configuration and select a server, confirm the core can read it, then configure routing and the system proxy. On Android, connection controls and per-app proxy options are provided by the client; desktop system tray instructions do not apply directly to phones. When troubleshooting, note the client, operating system, protocol fields, and log messages. This makes it easier to find the cause than changing several settings at once.
Platform downloads / DOWNLOADS
Use v2rayN on desktop; on Android, choose between v2rayNG and v2flyNG based on your core requirements. On the download page, check your device's processor architecture and package type. Installers are not interchangeable across operating systems, so confirm your device details before downloading.
v2rayN offers a desktop edition and a classic WPF edition. Choose based on the interface you need for everyday use, following the version notes on the download page. After installation, manage the system proxy from the system tray menu.
Go to downloadsv2rayN has separate downloads for Apple Silicon and Intel. Check your Mac's chip in system information and choose the matching installer. When using the client, make sure your browser and terminal proxy settings are consistent.
Go to downloadsStart with v2rayNG, which uses the Xray core. If you need a core from the V2Fly family, compare it with v2flyNG. Both clients offer downloads for different device architectures.
Go to downloadsv2rayN offers different downloads by package format and device architecture. Check whether your distribution uses deb or rpm, then confirm the processor architecture. Import your subscription after installation.
Go to downloadsOpen-source ecosystem / CONTEXT
Understand the three layers before choosing a protocol or client.
Project V is an important part of the history of V2Ray software and protocol development. As the project and its community evolved, V2Fly and Xray established distinct core development paths. Both parse configurations, handle inbound and outbound connections, and apply routing rules, but their feature support and configuration fields are not always identical. When reading a server configuration, distinguish the protocol being used from the core that runs it. An option appearing in a graphical interface does not mean every core handles it in the same way.
v2rayN, v2rayNG, and v2flyNG are open-source graphical clients for different devices. Their interfaces bring server editing, subscription updates, routing, and connection controls together, reducing the need to edit configuration files directly. v2rayN is for desktop systems; v2rayNG and v2flyNG are for Android and use different core families. Client, protocol, and core names refer to three different layers: choose an installer based on your operating system, then check the core and protocol for configuration compatibility.
These clients and related cores are maintained by open-source communities. Public source code lets developers review implementations, contribute improvements, and keep up with protocol features. Open source does not replace routine configuration checks: subscription providers may change server settings, and core updates may change how fields are handled. Keep the original subscription details, read client update notes, and check logs when something goes wrong. These are more reliable maintenance practices than judging by the connection icon alone. When using the same subscription on multiple devices, check each client's support for the protocols and transport options it contains.
For desktop use, start with v2rayN for your operating system and download the package that matches your device architecture. On Android, start with v2rayNG; consider v2flyNG if your existing configuration requires a core from the V2Fly family. If you already have a subscription, check which protocols and transport settings it includes. There's no need to change a server that's working just because another option sounds newer. For a detailed comparison of VMess, VLESS, Trojan, Shadowsocks, and REALITY, see the technical reference.
Read the protocol and core reference →Common questions / QUICK ANSWERS
These answers cover common points of confusion during installation and setup. For complete walkthroughs or more troubleshooting scenarios, see the getting started guide and troubleshooting page.
On desktop, create a group under “Subscription groups” in v2rayN, enter the link, and update the group. Do not enter a subscription URL in an individual server's address field. See the steps →
First make sure the core is running, then check “Set up system proxy” and your app's own proxy settings. The command line and browser may use different sources. See troubleshooting steps →
REALITY is a transport security option in the configuration, not a client you install separately. When entering settings manually, check it separately from the protocol, transport, and server parameters. See the quick reference →
Usually, you need to import it into each client and confirm that both support the subscription's protocols and transport settings. Connection controls and system proxy settings differ by device, so configure each one separately. Compare clients →
Usage notes / ARTICLES
Find the setting you need by issue, from system proxies and core logs to subscription groups. Commands and URLs in these articles illustrate where to make changes; use the settings for your own device and service.
Check the system proxy, browser extensions, and terminal environment variables separately to find how traffic is routed for each app.
Start with the error line, then check for port conflicts, misspelled fields, transport settings, and core compatibility.
Use group names, filter keywords, and update settings to distinguish server configurations from different sources.