This article explains how to import nodes into sing-box and why, when multiple people on a team use the same set of nodes, some have a stable connection while others experience frequent disconnections. It’s intended for everyday users who already have a subscription link or individual node details and want to import and use them consistently across Windows, macOS, Android, or iOS clients.
1. Check the node source and format before importing
sing-box is a general-purpose proxy core. Client interfaces vary, but the import process is similar. Nodes usually come from one of two sources: a subscription link or an individual node link. Subscriptions are better suited to teams because nodes can be updated or replaced more easily; individual nodes are useful for temporary testing.
- Subscription link: usually a single URL that the client can update automatically.
- Individual node link: typically starts with vless, vmess, trojan, shadowsocks, or a similar protocol name.
- Local configuration file: usually a JSON file, suitable for advanced users or centralized distribution.
If you use the free nodes provided on this site, we recommend copying the full subscription address rather than just one node listed on the page. This helps prevent connection issues caused by missing parameters.
2. General steps for importing nodes into sing-box
- Install a client that supports sing-box. For Windows or macOS, choose a sing-box client with a graphical interface; for Android or iOS, choose a proxy tool that supports the sing-box core.
- Open the client and look for “Configuration,” “Profiles,” “Subscriptions,” or “Import.”
- Select “Import from URL” and paste the subscription link. For an individual node, select “Import from clipboard.”
- Save the configuration, then select “Update subscription” or “Sync configuration” and wait for the node list to appear.
- Choose a node with low latency and a clear name, then enable the proxy.
- Open a browser and test a website you normally use. If it won’t load, try another node.
For team use, we recommend that an administrator provide everyone with the same subscription link and client setup instructions. This helps avoid situations where different people search for and use different configuration versions.
3. For teams: how importing nodes relates to account environment stability
Many people assume importing nodes is just a matter of copying and pasting. In practice, connection stability for teams also depends on the account environment, including client version, system network, DNS, proxy mode, and subscription update frequency.
First, keep client versions as consistent as possible. The same subscription may be parsed differently by different clients, especially when rules, DNS, or TLS parameters are complex. Older versions may fail to recognize some settings.
Second, don’t rely on a shared temporary node. Free nodes can become unstable as the number of users or network conditions change. Teams should prepare several backup nodes and agree to use available nodes from the latest subscription update first.
Third, standardize the proxy mode. People using Global mode and Rule mode may get different results. For most teams, we recommend starting with Rule mode and switching to Global mode temporarily to test if something won’t load.
Fourth, avoid repeatedly importing old configurations. Importing multiple subscriptions can lead to rule conflicts, duplicate node names, or DNS issues. To troubleshoot, delete old configurations first, then reimport the latest subscription.
4. Quick troubleshooting for connection failures
- The node list is empty: Check that the subscription link is complete and that you haven’t copied any extra spaces.
- A node imports but won’t connect: Update the subscription first, then test two or three other nodes.
- Some apps work, but the browser doesn’t: Check whether the system proxy is enabled.
- Only one person on the team has connection issues: Have them restart the client, turn off other VPNs, delete old configurations, and reimport the subscription.
- Latency looks normal, but webpages won’t load: Change the DNS settings or switch to Global mode to test.
In short, importing nodes into sing-box is straightforward. The key is to use a reliable subscription source, keep client versions consistent, and standardize team configurations. When issues arise, don’t focus on just one node. Troubleshoot in this order: subscription, client, proxy mode, and system network. This usually helps identify the cause quickly.