Setup guides constantly use terms like "node," "subscription," and "routing rules" — if you've never used this kind of software before, they can be confusing at first glance. This article skips the setup steps entirely and just explains these concepts in plain English; once you're done, following the quick-start guide will go a lot more smoothly.
1. Node: The "Relay Server" You Connect To
Think of a "node" as a server that forwards your network requests for you. Your device connects to that server first, and it then reaches the site you want to visit — so the site sees that server as the visitor, not you directly. Different nodes usually correspond to different regions and network routes, with varying speed and stability, which is why clients often show names like "HK-01" or "JP-02" — the location name is just a hint about where that server (or its route) is based, helping you pick the lowest-latency option.
One thing worth noting: nodes are set up and maintained by your subscription provider — the client itself doesn't "generate" nodes, it just displays the node info you already have and lets you connect. Whether a node stays stable and available long-term depends on that provider. If a specific node stops working for a long time, the right move is usually to contact your provider, not reinstall the client.
2. Subscription: Getting a Whole Batch of Nodes at Once
In the early days, you had to add nodes one by one, typing in the address, port, and encryption method for each — tedious, and one typo would break the connection. Subscriptions solved this: it's essentially a URL your provider maintains behind the scenes with an up-to-date list of nodes. Your client visits that URL and gets all the node info at once, no manual entry required.
Subscriptions also have a handy feature: auto-update. You can set your client to check the subscription link automatically every so often (say, every 24 hours). If your provider adds new nodes or removes dead ones, your client picks up the latest state without you having to watch for changes. That's also why guides always say to update your subscription first — a lot of connection issues are simply caused by an outdated node list.
3. Routing Rules: Deciding What Goes Through the Proxy
Not every request needs to go through a node — accessing a device on your local network, or a domestic site that already loads fine, would only add unnecessary latency if forced through a distant node. Routing rules are traffic-splitting logic that decides, based on domain or IP region, which requests connect directly, which go through a node, and which get blocked outright.
Most clients come with a community-maintained default ruleset covering the vast majority of common sites — beginners can just use the defaults without learning to write rules themselves. Once you're more familiar with things, if a specific site isn't being routed the way you expect, you can go into the client's routing settings and adjust the rule later.
4. Latency: The Number That Tells You If a Node Is Any Good
Next to each node in the client, you'll usually see a number in milliseconds — that's the latency (ping), representing how long a round trip to that node takes. A lower number means a faster connection and usually a smoother experience; a very high number (say, over 500ms) or a "timeout" usually means that node isn't a good choice right now.
Latency is just one reference point, not the only one that matters — some nodes look fine on paper but have an unstable connection in practice, cutting in and out. If a node has normal latency but still feels unstable, switching to a different low-latency node is usually easier than repeatedly retrying the same one.
5. Protocol: How the Node and Client Talk to Each Other
The protocol determines how the client and node server encrypt and transfer data — common ones include VMess, VLESS, Shadowsocks, and Trojan. Each has different strengths in speed, security, and resistance to interference, and some layer on TLS encryption to make traffic look more like normal web browsing at the network level.
Beginners don't need to study protocol implementation details at all — the subscription link already includes the matching protocol config, and the client detects and applies it automatically when fetching the node list. You just need to focus on which node to pick and when to connect.
Now That You Understand the Concepts, What's Next
Now that you understand node, subscription, routing rules, latency, and protocol, you have everything you need to follow the guides — nearly every step from here on will make intuitive sense. Head to the Download page to get the client for your system, then follow the quick-start guide to download, install, and connect. If you get stuck on a specific step, check the FAQ.
Do These Concepts Apply Across All Platforms?
Yes. Whether you end up using v2rayN — which covers Windows, macOS, and Linux — or v2rayNG / V2flyNG on Android, node, subscription, routing rules, latency, and protocol all mean exactly the same thing — only the menu names and layout differ slightly between clients. You don't need to relearn this for every platform; understanding it once applies everywhere.