This article addresses the practical question “How do I import nodes into sing-box?” It explains how to distinguish subscription URLs, individual node links, and configuration files, then covers importing them and testing the connection. It also explains why your exit IP, DNS, and browser environment can affect the results. Menu names may vary across systems and client versions, so refer to the interface you’re using.
1. Check the client and node format
sing-box is a proxy core, and graphical clients that use it may not all offer the same features. Download a version for your system from the project’s official website, official repository, or a trusted app store. When you first launch it, follow the prompts to allow it to create a VPN connection or network extension.
Support for the sing-box core does not mean support for every subscription format. First, check which of the following types you have:
- Subscription URL: Usually an HTTPS link. Check whether the provider identifies it as a sing-box configuration or as another format, such as Clash.
- Individual node link: For example, vless://, vmess://, or trojan://. Only clients with support for the corresponding link format can import these directly.
- Configuration file: Usually in JSON format. However, sharing the same file extension does not guarantee compatibility; the file must also meet the version requirements of the core built into the client.
2. Import the resource according to its type
- Open the client and go to “Configuration,” “Profiles,” or a similar page. Click Add and check whether options are available for remote subscriptions, local files, or the clipboard.
- If you have a compatible remote configuration, choose the option to add it from a URL, paste the complete address, and save it. Then download or update it. Do not remove or change any parameters in the link.
- If you have a JSON file, choose the local import option. If the client supports importing text, you can also paste the complete contents. If validation fails, first check the format and version compatibility. Don’t delete fields you don’t recognize.
- If you only have an individual node link, check whether the client can parse links from the clipboard or a QR code. If it has no such option, ask the provider for a compatible configuration. Simply renaming the link as a JSON file will not work.
- Select and enable the configuration you just imported. If the client lets you choose a node, select one, then connect. Confirm the permission prompt if your system asks to grant VPN access.
Subscription URLs may contain access credentials. Don’t share screenshots of them or paste them into unfamiliar conversion websites. Whether you use free nodes from this site or another source, check the format and last-updated date. Free resources may not always be available.
3. Check your IP, DNS, and browser after connecting
First, open a regular webpage, then use a trusted IP lookup page to check your current exit IP. If it hasn’t changed, check whether system proxy or VPN/TUN mode is enabled and whether routing rules send the site directly. A “Connected” status alone does not prove that all traffic is going through the proxy.
DNS resolves domain names to addresses. If some websites won’t open, check the logs for resolution errors. Your browser’s secure DNS, built-in proxy extensions, or another VPN may also cause traffic to take a different route. When troubleshooting, change only one setting at a time and keep a record of the original settings.
Browser cache, cookies, the region associated with your login account, and location permissions can also affect what a page displays. Changing your exit IP does not automatically change your browser environment or account region. You can compare results in a private window, but that does not replace checking your network settings.
4. What to do if importing fails or you can’t connect
If import fails, first check the resource format and client version. If a subscription download fails, check that the URL is complete and still valid, and that your current network can access it. If the import succeeds but the connection times out, try updating the subscription, switching nodes, and checking your system time and whether other proxy software is causing a conflict. If it still doesn’t work, note the error message and relevant log keywords. Before sharing them, redact sensitive information such as subscription tokens and passwords.