This guide addresses the practical question of how to import nodes into sing-box: from checking which formats your client supports to importing a subscription, testing the connection, and reducing account verification triggered by changes in your exit IP when working with a team. Menus and import capabilities vary across sing-box GUI clients, so first identify whether you have a subscription URL, a single-node link, or a complete configuration file.
1. Check the client and node format before importing
Install a client that supports your operating system from the project’s official website, official repository, or another explicitly listed source. Avoid modified versions from unknown sources. The sing-box core does not provide a universal graphical interface, and clients differ in their subscription support. A client bearing the sing-box name is not necessarily able to import every type of link.
- Subscription URL: Usually an HTTPS link. Check whether the provider says it supports sing-box and whether your client supports remote configurations.
- Single-node link: Examples include vless://, vmess://, and trojan://. You can import these directly only if the client explicitly supports parsing the relevant format.
- Configuration file: Often in JSON format. A valid file extension does not guarantee compatible content, so validate the file in the client.
A Clash YAML subscription cannot be used directly as a native sing-box JSON configuration. Ask the provider for a compatible format first. If you need to convert a configuration, use a trusted tool and avoid submitting subscriptions containing credentials to unfamiliar websites.
2. Import a subscription or node step by step
- Open the client and find the add option under “Configuration,” “Profiles,” or a similar menu. Menu names depend on the version.
- If you have a compatible remote configuration URL, choose “Add from URL” or an equivalent option, paste the full URL, enter a recognizable name, then download and save it.
- If you have a configuration file, choose the file import option. If you have a single-node link, check for an “Import from clipboard” option. If there is no such feature, do not paste the node link into the remote configuration URL field.
- Select the new configuration and validate it or try starting it. The first time you enable it, follow your system’s prompts to allow a VPN connection or network extension.
- Select a node from the proxy group provided in the configuration. Test the connection first, then visit your target website to verify it. A successful latency test does not guarantee that every website will be accessible.
If you use free nodes provided on this site, check their format, validity, and suitability for your intended use first. A subscription URL acts like a credential. Don’t share it in public group chats or include it in screenshots.
3. How does team usage affect account stability?
Importing a node simply gives the client connection details; it does not automatically provide a fixed IP. Subscription updates, automatic switching, or manually changing nodes may change your exit IP and region. Some platforms may then require you to verify your account again, though account status also depends on the device, login activity, and platform rules.
Teams can standardize client versions and configuration names so members know which exit they are using. For important accounts, try to stick to familiar devices and exit regions, and avoid frequent switches between regions. Choosing the same node every time does not guarantee that its exit IP will never change. Don’t treat a proxy as a guarantee against platform security checks, and avoid sharing sensitive accounts among multiple people.
4. Troubleshooting import failures and connection issues
If you see a format error, first check whether you’re trying to use a Clash subscription or an unsupported single-node link. If a download fails, check that the URL is complete, the subscription hasn’t expired, and your current network can reach the subscription domain. If the configuration imports but won’t start, check the logs for compatibility messages and consult the client documentation.
If websites won’t open after the client starts, check in turn whether the node is unavailable, the system time is correct, another proxy or VPN is running, and the system proxy or TUN is enabled as instructed by the client. Change one setting at a time and test again. Before sharing logs, remove sensitive information such as subscription URLs, passwords, and UUIDs.