This article addresses the question “how to import nodes into sing-box“: including importing from a subscription link, manually importing a single node, and why you still need to check your IP, DNS, and browser environment after importing. It is suitable for ordinary first-time sing-box users to follow step by step.
1. What to prepare before importing
sing-box itself is a proxy core, and the common client names may differ across platforms. For example, on Android, Windows, and macOS, there are graphical clients based on sing-box. You need to prepare three things first: the client, node information, and network permissions. Nodes can come from your own subscription, or you can refer to the free node pages updated on this site, but the stability of free nodes may fluctuate, so it is recommended to prepare several backups.
- Subscription link: usually a URL starting with https, suitable for bulk import.
- Single node link: commonly vless://, vmess://, trojan://, ss://, etc.
- Configuration file: some clients support importing json files.
2. Import nodes using a subscription link
Most users are recommended to use subscriptions because subsequent updates are more convenient. The exact path varies slightly between clients, but the logic is basically the same:
- Open the sing-box client and go to the “Configuration,” “Profiles,” or “Subscriptions” page.
- Click “Add,” “New,” or the plus sign in the upper-right corner.
- Select “Import from URL” or “Subscription.”
- Paste the subscription link. For the name, you can enter “freevpn-x” or a custom name.
- After saving, click “Update Subscription” and wait for the node list to appear.
- Select a node, return to the home page, and click to start the connection.
If no nodes appear after importing, first confirm that no characters were missed when copying the link, and especially make sure there are no spaces, Chinese punctuation marks, or line breaks. Some clients also require the subscription content to be compatible with sing-box. If it prompts that parsing failed, you can try switching to a “universal subscription” or a subscription format specifically for Clash/sing-box.
3. Manually import a single node
If you only have one node link, you can use clipboard import. After copying the complete node link, click “Import from clipboard” in the client. If the client does not recognize it, check whether the beginning of the link is complete; for example, vless:// must not be copied as less://. When filling it in manually, carefully verify fields such as server address, port, UUID/password, transport method, and TLS/SNI. An error in any one of these may cause the connection to fail.
After the import is complete, do not just rely on whether the button shows “Connected.” It is recommended to open a browser and visit an IP-checking website to confirm that the outbound IP has changed. If the IP has not changed, the system proxy may not be taking over, or the browser may still be connecting directly.
4. What is the relationship between IP, DNS, and the browser environment
Many people think that once the node is imported successfully, everything is done, but in reality you still need to look at three things: outbound IP, DNS resolution, and browser fingerprinting. IP determines where websites see you as visiting from; DNS determines who resolves the domain names; and the browser environment may expose information such as language, time zone, and WebRTC.
- IP unchanged: check whether the client has system proxy or VPN mode enabled.
- DNS leak: prioritize enabling the client’s built-in DNS or remote DNS to avoid having your local ISP still perform the resolution.
- Browser anomalies: disable the risk of WebRTC leaks, or use a separate browser profile.
For ordinary use, there is no need to make things overly complicated, but at a minimum you should check your IP and DNS again after connecting. If you are just browsing web pages, enabling the system proxy is usually enough; if you want all software to go through the proxy, it is recommended to use TUN/VPN mode.
5. Quick troubleshooting for connection failures
If you cannot connect, you can check in order: first, switch nodes to rule out a single failed node; second, update the subscription to avoid using an expired configuration; third, switch networks, for example from Wi-Fi to a mobile hotspot; fourth, check the client logs, paying special attention to prompts such as timeout, handshake failed, and dns error. If all nodes fail, the issue is usually not that you “don’t know how to import,” but rather a subscription format, network blocking, or DNS settings problem.
In summary: for importing nodes into sing-box, prioritize using a subscription link, and use clipboard import for single nodes. After importing, be sure to check whether the IP has changed, whether DNS is leaking, and whether the browser is still connecting directly. Only then can you confirm that the proxy is actually working, rather than just stopping at “the client shows connected.”