How do you import nodes into sing-box? This guide explains the differences between subscription links, node share links, and JSON configurations, and walks you through importing them using the options your client supports. It also covers how to check whether connection failures are related to your exit IP, DNS, or browser environment. Button names and import options vary by client, so first confirm which app you have installed.
1. Check your client and node format
sing-box is a proxy core, and not every client that uses it supports the same import features. If you’re a regular user, choose a client with a graphical interface that supports your current system. Download it from the project’s official website or release page, and avoid modified versions from unverified sources.
- Subscription links: Used to retrieve and update configurations, but may return Clash, sing-box, or another format. Don’t judge the format by the appearance of the link alone.
- Node share links: Commonly begin with vless://, vmess://, trojan://, and similar prefixes. Whether they can be imported directly depends on the client.
- JSON files: Usually used to import sing-box configurations, but a single outbound section may not be a complete, runnable configuration.
Supporting the sing-box core does not mean supporting every subscription and share link. If you see a format error, first check the client’s documentation and the format specified by your node provider. Don’t repeatedly change the server address.
2. Import using a subscription link
- Copy the subscription address that the node provider says is compatible with your client. Make sure it doesn’t include any spaces or line breaks.
- Open the client’s “Configuration,” “Profiles,” or similar page, then choose the option to add a remote configuration. The exact wording varies by app.
- Paste the address, enter a recognizable name, and download or update the configuration. If automatic updates are supported, enable them if needed.
- Once the download is complete, select the configuration. If the interface offers node selection or proxy groups, choose an available option.
- Start the connection. If prompted for system VPN permission for the first time, approve it, then open a webpage to test the connection.
A successful download doesn’t guarantee that the node will work. If our free nodes page offers multiple formats, choose one compatible with your client and check the update notes. Free resources may not always be available.
3. Import using a file or share link
If you have a complete JSON configuration, look for “Import from file” on the configuration page, select the file, and save it. Some clients copy the file, while others may keep a reference to it. After importing, confirm that the configuration still loads correctly. If you see a version or field compatibility error, first look for a configuration that matches your client version rather than deleting the fields at random.
If you have a single share link, use it only if your client explicitly offers options such as “Import from clipboard” or “Import URI.” If no such option is available, ask the provider for a compatible configuration. Don’t submit links containing passwords, UUIDs, or subscription tokens to unfamiliar online conversion sites.
4. If you can’t access the internet after importing, troubleshoot in order
- Turn off the proxy and confirm that your local network is working. Also check that your system clock is accurate.
- Check the logs to distinguish between configuration parsing errors, subscription download failures, and node connection timeouts. Fix format errors before trying a different node.
- Confirm that the system VPN or the proxy mode required by the client is enabled, and check whether another VPN or proxy extension is taking over the connection.
- If the connection works but domain names won’t load, check the DNS settings in the configuration. Secure DNS in your browser may also change the resolution path, so use consistent settings while troubleshooting and test one change at a time.
Your exit IP can help you check whether requests are going through the proxy, but it doesn’t determine whether a configuration can be imported. Routing rules may also send some websites directly. Browser cache, extensions, and site cookies can affect how pages behave, so cross-check in a private window. A changed IP does not mean you’re anonymous—actions such as signing in to an account may still identify you.