How do you import nodes into sing-box? This guide helps you distinguish subscription links, single-node links, and JSON configuration files, import them using the methods supported by your client, and troubleshoot issues such as your IP address not changing or websites failing to load after connecting. Buttons and features vary between sing-box GUI clients, so you can’t assume that steps for other clients will work the same way.
1. Check the node format before importing
Install a client for your operating system from the project’s official releases page or a trusted app store, and make sure it uses the sing-box core. The sing-box command-line program is not the same as a GUI client. For everyday use, a version with a configuration management interface is usually the better choice.
- Subscription link: Usually a URL, but the content it returns may be in sing-box, Clash, or another format.
- Single-node link: For example, vless://, vmess://, or trojan://. Whether you can import it directly depends on the client.
- JSON file: It should be a complete sing-box client configuration compatible with your version, not just a node snippet.
Using the sing-box core does not mean that every subscription format is supported. When getting free nodes from sources such as freevpn-x.com, check the format details and last-updated date first. Don’t submit links containing credentials to untrusted online conversion sites.
2. Import according to the configuration type
- Open the client’s “Configuration,” “Profiles,” or similar page and find the add option. Menu names vary by version.
- If you have a subscription URL, choose the remote configuration or URL import option, paste the full link, and give it a name. Make sure the source provides a format supported by your client, then download or update it.
- If you have a JSON file, choose the local file import option. If the client provides a text editor, you can also paste the complete configuration and save it. Don’t mistake a webpage’s source code for a configuration file.
- If you have a single-node link, first look for an “Import from clipboard” or QR code scanning feature. If there’s no such option, ask the source for a compatible configuration. Don’t paste the link into a remote JSON URL field.
- Select the configuration you just imported and check the validation results. If there are no errors, start the connection and allow the VPN configuration when prompted by your system. If the client provides a node selection screen, choose the node you want to use.
A successful import only means the configuration was accepted; it doesn’t guarantee the node will work. If you see errors such as unknown fields or unsupported protocols, check the client version and configuration requirements. Don’t randomly delete fields and force the configuration to start.
3. Check your IP, DNS, and browser after connecting
Once connected, open a regular webpage, then use a trusted IP lookup page to check your outgoing IP. Rule-based routing may send domestic websites directly, so consider the destination and connection logs together. Don’t assume the connection has failed based on a single webpage.
If the client shows as connected but your browser still uses your local network, check whether the system proxy or the client’s VPN/TUN mode is enabled, and whether the target app is excluded. The system proxy may not cover every app. When testing, also turn off other proxies or VPNs to avoid conflicts.
If some domains won’t open, check the logs for DNS or resolution errors first. Browser Secure DNS, proxy extensions, and cached data can also affect the results. You can temporarily disable proxy extensions and restart the browser to compare. Don’t treat changing DNS at random as a universal fix.
4. What to do if updates or connections fail
If a subscription update fails, check that the link was copied in full, hasn’t expired, and doesn’t require an internet connection before it can be downloaded. If it times out, try switching to a trusted node or another network. If authentication fails, request a valid configuration. When asking for help, include the client version, operating system, and error message. Hide subscription tokens, passwords, and full node links to prevent credential leaks.