This article addresses the practical question of how to import nodes into sing-box: whether you have a subscription link, a configuration file, or a single node, which import method should you choose, how do you connect after importing, and how can teams avoid frequent changes to account environments when sharing configurations? Keep in mind: the sing-box core and different GUI clients do not have the same import capabilities. Not every link can be treated as a universal subscription.
1. Check the client and node format first
Install a version compatible with your system from the official sing-box project release page or the official channel for your client. This article covers clients with a graphical interface; if you only have the command-line core, you cannot follow steps such as “import via QR code” directly. Open the app and find the “Configuration,” “Profiles,” or similar page.
- Complete configuration: Usually a JSON file containing outbounds, DNS, routing, and other settings. You can try importing it as a local configuration.
- Remote configuration: A URL that returns a complete sing-box configuration. Add it in a client that supports remote configurations.
- Single node: For example, a vless://, vmess://, or trojan:// link, which requires explicit support from the client to parse.
- Other subscriptions: Clash YAML or a Base64 node list may not work directly. Check the format first.
Having the same file extension does not mean configurations are compatible. Confirming the supported client and version with the provider is more effective than repeatedly trying different import options.
2. Import according to the node source
- If you have a remote configuration URL, open the configuration page and choose “Add” followed by “Remote Configuration” or a similar option. Enter a recognizable name, paste the full URL, save it, and refresh the configuration.
- If you have a local JSON file, choose “Import from File.” If you received the configuration as plain text, save it as a JSON file as instructed by the provider. Do not omit any brackets or include explanatory text.
- If you have a single link, check whether the client offers “Import from Clipboard” or “Scan QR Code.” If neither option is available, you usually cannot paste the link directly; request a compatible complete configuration instead.
- After importing, select the configuration, open the proxy or outbound selection page, choose an available node, and start the connection. The first time you enable it, allow the app to add a VPN configuration when prompted by your system.
- Open a frequently used website to verify connectivity and check the logs for recurring errors. If needed, disconnect other VPNs first to prevent multiple network proxies from interfering with each other.
Use free nodes from this site according to their stated format. Do not submit URLs containing subscription tokens to unfamiliar online conversion sites; these links may contain access credentials.
3. Troubleshooting import or connection issues
If you see a configuration parsing error, first check whether the downloaded content is a login page, an error page, or a subscription in a format intended for another client. Then check the required version. Keep a copy of the original configuration before updating the client. Import failures can occur if older fields have been removed or newer fields are not yet supported.
If a remote update fails, check that the URL is complete and has not expired, and that your current network can reach the subscription address. If the connection starts but websites will not open, try another node first, then check the logs for timeouts, DNS errors, or certificate errors. Do not disable certificate verification just to “fix the connection.”
4. Team use and account environment stability
Teams can standardize client versions and configuration sources, label configurations with their intended use and update date, and have a designated person test them before distribution. For work accounts, avoid switching egress locations frequently within a short period, and do not let multiple people make arbitrary changes to the same configuration.
A successful import does not guarantee a stable account environment. Egress IP, device, browser state, and login behavior can all affect platform verification; a node name alone does not guarantee that its egress IP will remain unchanged. If you are prompted to verify your account after switching nodes, follow the platform’s standard process. Teams should use member permissions allowed by the platform, avoid sharing the primary account password, and comply with the terms of service and local regulations.