How to Import Nodes into sing-box: Subscriptions, Config Files, and Team Use Tips

This guide explains how to import nodes into sing-box, troubleshoot subscription links that cannot be added, and address inconsistent account environments after team members connect. First, keep in mind that sing-box is a proxy core, and import options and supported formats vary between graphical clients. Following the order “check the format—import the configuration—authorize the connection—verify the exit” is more likely to work than simply pasting a link.

1. Check the node format before importing

Install a client for your system from the project’s official release page or an app store it links to. Avoid modified versions from unknown sources. Open the client’s “Configuration,” “Profiles,” or “Subscription” page and check whether it supports remote configurations, file imports, or share links.

  • Addresses starting with https://: These may be subscriptions or web pages. Check whether the content they return is compatible with your client.
  • Content starting with vless://, vmess://, trojan://, or similar: These are node share links, and not all sing-box clients can parse them directly.
  • JSON files: These may be sing-box configurations, but you should still check the client’s core version and configuration fields.

Clash subscriptions and sing-box configurations are not automatically interchangeable. Even if a link downloads successfully, an incompatible format can still cause the import to fail. If you get free nodes from this site or another source, check the format notes and last-updated date first.

2. Import via subscription or file

  1. Go to the configuration management page, select “Add configuration,” then choose “Remote,” “URL,” or a similar option.
  2. Paste a subscription URL that the provider explicitly says is compatible with sing-box. Enter a recognizable name, such as “Work backup,” then save and update or download the configuration.
  3. If you have a local JSON file, choose “Import from file” and open it using the system file picker. If you only have a node link, first check whether the client supports importing from the clipboard. If it doesn’t, ask the provider for a compatible configuration; don’t try to insert the link into a JSON file.
  4. Select the imported configuration and click Start. Allow the client to create a VPN connection when prompted by the system. On desktop, if you enable TUN, grant the required permissions as instructed by the client.
  5. Test the connection by opening your target website, then check the client logs and your current exit IP. If the configuration includes multiple exits, make sure the correct node is selected on the proxy selection page.

A successful import does not mean the connection is working. Configuration parsing, node connectivity, DNS resolution, and routing rules can all affect whether you can access sites.

3. Team use and account environment stability

The import method itself does not determine whether an account remains stable. What matters is whether the exit changes frequently, whether multiple people log in from different locations at the same time, and the platform’s own security rules. Teams should give members clearly named configurations and note their usual exit regions. Avoid automatic switching that could change the exit during a login session. Free nodes may become unavailable or change exits, so don’t rely on them as the only connection method for important business activities.

Don’t share subscription URLs or complete configurations in public group chats, as they may contain access credentials. For shared accounts, use the member permissions provided by the platform instead of sharing passwords. A fixed exit also cannot guarantee that you won’t be asked to verify your identity.

4. Troubleshooting import or connection failures

If you see a parsing error, first check the subscription format and client version. If a download fails, check that the address is complete and hasn’t expired, and that your current network can reach the subscription source. If the client starts but websites won’t open, try another working exit, check for conflicts with other VPNs, and look in the logs for DNS, timeout, or authentication errors. Keep a working backup before updating the configuration, and change only one thing at a time to make it easier to identify the cause.

Leave a Comment

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

中文 EN
🚀

RedGate VPN

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

立即体验 →
⚡

告别卡顿

RedGate VPN
全球高速节点

免费下载 →
Scroll to Top