This article addresses the practical question of “how to import nodes into sing-box” and explains why, in a multi-user or team environment, your import method, subscription updates, and account usage habits can affect connection stability. It’s intended for everyday users who already have VLESS, VMess, Trojan, or Shadowsocks node links or subscription URLs.
1. First, check what you have
sing-box supports multiple proxy protocols, but the import options vary slightly between client apps. There are two common scenarios: a single node link, such as one that starts with vless://, vmess://, or trojan://; or a subscription URL, usually an https link containing multiple nodes. For team use, a subscription is generally preferable, as it makes it easier to update configurations and switch nodes later, while reducing errors from manual copying.
If you’re using a sing-box graphical client on Windows, macOS, Android, or iOS, install the appropriate version first and make sure it supports importing from the clipboard, importing subscriptions, or importing configuration files. We also compile free nodes for testing, but free nodes can be unreliable, so they’re suitable for temporary testing and not recommended as a team’s only connection.
2. Basic steps for importing nodes into sing-box
- Copy the node link or subscription URL. Make sure you don’t include extra spaces, Chinese instructions, or line breaks.
- Open the sing-box client and go to “Configuration,” “Profiles,” “Subscriptions,” or a similarly named page.
- For a single node, select “Import from Clipboard” or “Add Node.” For a subscription, select “Add Subscription.”
- Paste the link and save it. Tap “Update Subscription” and wait for the node list to load.
- Select a node, start the proxy, and open a test website in your browser to confirm it works.
If the client asks you to import a JSON configuration file, you’ll need a configuration in a format compatible with sing-box. Unless you’re an experienced user, avoid writing complex JSON by hand. Use the client’s subscription conversion or built-in import feature instead to prevent formatting errors that could stop it from starting.
3. In a team, your import method can affect stability
When multiple people share a connection, stability depends not only on node quality but also on the account environment. A common problem is that everyone uses the same single node for a long time. If that node changes or gets rate-limited, the whole team can lose its connection at once. A more reliable approach is to use a shared subscription URL maintained by an administrator, with members simply updating the subscription regularly.
- Avoid switching regions frequently: Some websites may flag changes in login IP addresses as suspicious activity, especially for team accounts.
- Avoid having multiple people use the same exit node at once: If a business platform is sensitive, assign different nodes by member or use case where possible.
- Stick to a regular update schedule: For example, update the subscription once before starting work each day instead of refreshing it repeatedly while connected.
- Keep a record of available node names so you can switch quickly and report issues when problems arise.
4. Troubleshooting import failures and connection problems
If a node fails to import, first check that the link is complete, that the subscription URL opens in a browser, and that your client isn’t outdated. If the node imports but won’t connect, check your system clock, network permissions, proxy mode, and DNS settings in that order. On mobile, make sure VPN permission is enabled. On desktop, check whether security software is blocking the connection.
For team troubleshooting, have one member test the subscription first, then share the results with everyone else. Don’t have everyone change their configuration at the same time. If only one account has login issues but web browsing works normally, the target platform may be flagging the account; the sing-box configuration isn’t necessarily at fault. Try switching to a more stable node, keeping the login environment consistent, and avoiding logins from different regions.
In short, importing nodes into sing-box is straightforward: copy a link, add a subscription, update it, and select a node. For teams, the key is to use a subscription that’s easy to maintain, avoid unnecessary switching, and establish a simple process for reporting problems. These steps do more for reliable use than simply aiming for a larger number of nodes.