This article explains how to import nodes into sing-box, covering subscription links, individual node links, and JSON configuration files. It also explains how teams can reduce the impact of frequent exit changes on account logins. Button names vary between clients, so before you begin, check whether you’re using the official GUI client, a third-party client, or the command-line core.
1. Check the client and node format
Install the version for your operating system from a download source listed by the official sing-box project, or from the official release page of your third-party client. Don’t confuse the sing-box core program with a GUI client: the core program usually doesn’t have an interface for scanning QR codes or pasting links.
- Full JSON configuration: Usually includes inbounds, outbounds, routing, and other settings. A compatible client can load it.
- Subscription link: Check whether it returns a sing-box configuration or a subscription format that the client can convert.
- Individual node link: For example, vless://, vmess://, or trojan://. Whether it can be imported directly depends on the client.
“Supports the sing-box core” doesn’t mean “supports every subscription format.” If your provider only gives you a Clash subscription, don’t use it directly as sing-box JSON. Ask the provider for a compatible version first. If you must convert it, avoid submitting links containing credentials to untrusted online conversion services.
2. Import nodes by type
- Open the client’s “Configuration,” “Profiles,” or similar page, then click Add. If this is your first time, you can keep the default settings.
- If you have a compatible remote configuration link, choose “Import from URL,” “Remote configuration,” or a similar option, paste the address, and download it. If the client doesn’t have this option, follow its documentation to download the configuration file and import it.
- If you have a JSON file, choose “Import from file.” If you only have configuration text, first confirm that it’s a complete configuration, then use the client’s paste option or save it as a .json file and import it.
- If you have an individual node link, use it only if the client explicitly offers “Import from clipboard” or “Import from QR code.” After importing, check that the address, port, protocol, TLS, and other details are present. If the client doesn’t support this, request a full configuration.
- Save and select the configuration, start the connection, and authorize the VPN or network extension when prompted by your system. Select the desired outbound in the node selection page, then open a webpage to verify access.
Successfully importing a configuration doesn’t mean the connection is working. Also check that the correct configuration is enabled, that the system proxy or VPN routing is active, and that your traffic matches the expected rules. For free nodes provided by this site, first check the format and confirm that they’re still valid, then import them using the steps above.
3. Troubleshoot import failures and connection issues
If you get a format error, check whether the subscription response is actually a login page, an error message, or a configuration for another client. If you get an unsupported-field error, check the client’s core version and the configuration requirements. Don’t delete unfamiliar fields at random.
If the connection starts but you can’t access anything, first pause other proxies or VPNs and confirm that your device’s clock is correct. Then check the logs for connection timeouts, DNS errors, or certificate errors. If only certain websites are having problems, check the routing rules. Don’t disable certificate verification as a troubleshooting shortcut. Before sharing logs, hide subscription links, passwords, and UUIDs.
4. Team use and account environment stability
The import method itself won’t make an account environment more stable. What matters is the exit IP, region, switching frequency, and the platform’s rules. If you need to keep your login environment consistent, avoid frequent exit changes caused by automatic speed testing. Team members can standardize client versions and procedures, but shouldn’t casually share personal subscription credentials.
Free nodes may stop working or change exit IPs, so they’re not suitable when you need a reliably fixed environment over the long term. For important accounts, keep recovery options available and follow the platform’s terms. Even a fixed node can’t guarantee that you won’t trigger security checks.