This article addresses the practical question, “How do I import nodes into sing-box?” It covers importing subscription links, JSON configurations, and individual node links, and explains how teams can reduce login verification caused by frequent changes to their exit IPs. Menus may vary between sing-box GUI clients, operating systems, and versions, so refer to the interface you’re using.
1. First, identify what you have
sing-box is a proxy engine. GUI clients typically build on it to provide a configuration management interface. When installing, get a version compatible with your system from the project’s official release page or a trusted app store. Avoid modified packages from unknown sources.
- Subscription link: Usually an HTTPS address used to retrieve a configuration, but the returned content may not be compatible with sing-box.
- JSON configuration: Should be a complete configuration compatible with the current client’s engine version, not just an individual outbound section.
- Individual node link: For example, a vless://, vmess://, or trojan:// link, which requires explicit support from the client to parse.
The sing-box engine cannot directly handle every subscription format. Clash YAML, Base64 node lists, and sing-box JSON cannot be converted between one another simply by changing the file extension. If this site’s free nodes page offers multiple formats, choose the version explicitly supported by your client.
2. Import based on the configuration type
- Open the client, go to “Configuration,” “Profiles,” or a similar page, and click Add. If you’re using a command-line program with no such options, you’ll need a different client that supports GUI-based configuration management.
- For a subscription, choose “Remote Configuration” or “Import from URL,” paste the full address, and save. If you need to select a format, follow the provider’s instructions, then update the configuration.
- For a local JSON file, choose “Import from File” and use the system file picker to open it. After importing, run the client’s available check or validation feature.
- For an individual node link, look for an option such as “Import from Clipboard.” If the client doesn’t offer this, don’t paste the node link into the remote JSON address field; ask the provider for a compatible configuration instead.
- Select the imported configuration and start the connection. Allow VPN permissions if prompted by your system. On desktop, enable system proxy or TUN mode as instructed by the client.
A successful import does not mean your traffic is going through the proxy. After starting the connection, check the logs and test a website you normally use. To verify your exit IP, use a trusted IP lookup service. Turn off other VPNs during testing to avoid routing conflicts.
3. Keeping account environments relatively stable for team use
The import method itself does not make an account more trustworthy. What matters is the exit IP, device, browser session, and platform rules. Teams can standardize client versions and configuration sources, use a relatively consistent exit IP for recurring tasks, and avoid manually switching nodes while working in an account. Automatic switching policies can also change the exit IP.
Using the same node does not guarantee a fixed public IP. A node’s name or region label also cannot prove that its actual exit IP remains unchanged. Free nodes can be used for temporary access and compatibility testing, but important business operations should not rely on their unverified ongoing availability. Team members should use separate accounts and permissions allowed by the platform, avoid sharing login credentials, and not use proxies to evade platform risk controls.
4. Troubleshooting import or connection failures
If you see a format error, first check the subscription’s returned content and the engine version. If an update fails, check whether the link has expired, whether the network can reach the subscription address, and whether the device’s clock is accurate. If the connection starts but webpages won’t load, check in order whether the node is available, whether system proxy or TUN mode is working, and whether DNS is reporting errors. Change only one setting at a time while troubleshooting, and keep the original configuration so you can restore it.
Subscription addresses and configuration files may contain access credentials. Don’t upload them to unfamiliar conversion websites or post logs containing tokens or passwords in a group chat. Redact sensitive information before asking for help.