This guide addresses the practical question of how to import nodes into sing-box. First, distinguish between node links, subscription URLs, and configuration files. Then import them using a method supported by your client. For team use, we’ll also explain how to reduce account verification caused by changes in network egress. Button names may vary between clients, so refer to the interface you’re using.
1. Check Your Client and File Type Before Importing
sing-box is a proxy core, and graphical clients that use it do not necessarily have the same features. Install a client that is compatible with your operating system and is still maintained, and download it from the project’s official website or release page. If the first launch prompts you to add a VPN configuration or authorize network traffic routing, allow it only after confirming that the source is trustworthy.
- Node link: Commonly begins with vless://, vmess://, trojan://, or a similar prefix. Your client must explicitly support parsing it.
- Subscription URL: Usually an HTTPS link. The returned content may be a node list or a complete configuration, so you can’t determine its format from the URL alone.
- Configuration file: Usually JSON, but it must meet the configuration requirements of the sing-box version used by your client.
Using the sing-box core does not mean your client can directly import every share link or Clash subscription. Before importing, check your client’s documentation and the format specified by your node provider.
2. Import Nodes Using a Supported Method
- Open the client’s “Configuration,” “Profiles,” or similar page, and look for an “Add” or “Import” option.
- If you have a subscription for a complete configuration, select “Remote Configuration” or “Add from URL,” paste in the address, and save. If needed, manually download or update it.
- If you have a local JSON file, select “Import from File.” After importing, check for parsing errors. Don’t import a configuration from another client just by changing its file extension.
- If you only have a single node link, first check whether the client supports a feature such as “Import from Clipboard.” If it doesn’t, ask the provider for a compatible configuration. Don’t paste the link directly into a JSON editor.
- Select the configuration you just added, start the connection, and complete any system authorization prompts. If the configuration includes a node selection group, open the relevant page and select the node you want to use.
- Test access by opening a regular webpage, then check the target app. A status of “Connected” alone doesn’t mean all traffic is going through the proxy.
Free nodes from this site should also be used in the format actually provided. A subscription URL may contain access credentials, so don’t upload it to an untrusted online conversion tool. If you share a screenshot for help, redact the full URL, password, and user identifiers.
3. How Does Team Use Affect Account Stability?
The import method itself won’t make an account more stable. What matters is the egress region, how often it changes, and device and sign-in behavior. Teams can standardize client versions and configuration sources, and keep a record of when configurations were updated. This makes it easier to troubleshoot issues caused by different rules across team members.
For business accounts that need to remain signed in, use authorized devices and familiar network environments whenever possible, and avoid frequently switching between egress regions in a short period. A fixed node name does not guarantee a fixed egress IP, nor does it guarantee that you’ll avoid verification or trigger no risk controls. For collaboration, use the member permissions provided by the platform instead of sharing accounts or using subscriptions to bypass service restrictions.
4. Troubleshooting Connection Issues After Import
If you see a format error, first check the subscription type and core version. If the download fails, check whether the link has expired, whether it was copied in full, and whether your current network can reach the subscription URL. If the configuration imports but you can’t connect to the internet, check node availability, system time, VPN authorization, and conflicts with other proxy software—in that order.
If only some apps are affected, check the configuration’s routing rules and DNS settings. Don’t start by changing parameters at random. Before updating, keep a copy of a working configuration. Change only one setting at a time while troubleshooting. If the issue persists, ask for help with your client version and a redacted error log.