How to Import Nodes in sing-box: A Practical Guide to Team Use and Stable Account Environments

This article answers the common question “How do I import nodes into sing-box?” After receiving a subscription link, a single node, or a JSON configuration, you need to know where to import it, how to verify it afterward, and how to reduce the impact of changing egress IPs on account environments when working in a team. Menu names and subscription support vary across sing-box graphical clients, so check the client name, version, and configuration format before you begin.

1. First, identify what you have

sing-box is a proxy core, and graphical clients do not offer identical features across platforms. Being able to use the sing-box core does not mean a client can import every type of node link directly. Check the provider’s format instructions first, then choose the appropriate import method.

  • Subscription link: Usually a URL that may return a sing-box configuration, a Clash configuration, or a node list. You cannot tell which just by looking at the URL.
  • Single-node link: Common formats include vless://, vmess://, and trojan://. The client must explicitly support parsing them.
  • JSON file or text: This may be a complete configuration or just a node snippet. A node snippet alone usually cannot run directly.

Prioritize configurations that the provider explicitly identifies as compatible with your client or sing-box version. For free nodes on this site, follow the format instructions as well; do not simply change the file extension and use a different format.

2. Import based on the configuration type

  1. Install the client from the project’s official release channel or a trusted app store, then open “Configuration,” “Profiles,” or a similar page.
  2. If you have a remote configuration link, select “Add Remote Configuration,” “Import from URL,” or a similar option, paste the link, and save it. If there is an update button, update manually first and make sure there are no parsing errors.
  3. If you have a complete JSON file, select “Import File.” If the client supports clipboard import, you can also copy and import the entire text. Do not omit any braces or include explanatory text.
  4. If you only have a single-node link, look for an option such as “Import Node from Clipboard.” If there is no such option, ask the provider for a compatible configuration rather than assuming you can paste the link and run it directly.
  5. Select the new configuration, check the node or policy group options, and then connect. The first time you use it, grant VPN permission when prompted by the system, and avoid running another VPN app at the same time.
  6. Test with a regular webpage, then visit the service you actually need to use to confirm the connection works and the egress region is as expected.

Subscription links may contain access credentials. Do not post them in public groups or submit them to unfamiliar online conversion sites. If you must convert the format, use a trusted local tool if possible, and check that the converted result is compatible with your current version.

3. How teams can reduce account environment fluctuations

A successful import only means the configuration works; it does not guarantee a stable account environment. Teams should record each member’s client version, configuration source, egress region, and update time. For work that requires a consistent region, try to keep the egress selection the same and avoid frequent changes caused by automatic switching.

The same node name does not guarantee the same public IP address over time. Shared nodes may also have their egress changed, and free nodes in particular should not be treated as a guarantee of a fixed egress IP. Check the egress region before signing in to important accounts, enable multi-factor authentication, and follow the account and team usage rules of the target service.

4. Troubleshoot import failures and connection issues

If you see a parsing error, first check the subscription format, whether the link has expired, and whether the configuration is compatible with your client version. If you see an unknown field, ask the provider for a compatible configuration rather than deleting fields blindly. If the configuration imports but will not connect, check your local network and system time, update the subscription, and try another node. If only certain websites fail to load, check the policy group, routing rules, and DNS settings. When asking others for help, share the client version and redacted logs, and hide the subscription URL, password, and node credentials.

Leave a Comment

Your email address will not be published. Required fields are marked *

中文 EN
🚀

RedGate VPN

免费节点太挤太慢?
升级高速稳定专线

立即体验 →
⚡

告别卡顿

RedGate VPN
全球高速节点

免费下载 →
Scroll to Top