This article answers common questions about “how to import nodes into sing-box”: once you have a subscription URL, node link, or JSON file, where should you add it? How do you troubleshoot import failures? And when using it as a team, how can you reduce the impact of changing exit IPs on account login environments? Menus vary across operating systems and graphical clients, so the steps below are organized by configuration source. They do not cover setting up your own server.
1. Check the client and node format first
sing-box is a proxy core, and graphical clients differ in the import options they provide. Install the version for your operating system from the project’s official website, official repository, or a trusted app store. When you first open it, grant VPN permissions when prompted. If you only have the command-line core, you won’t see options to scan a QR code or add a subscription. Most users should choose a compatible client with a graphical interface.
A subscription that works in Clash cannot necessarily be imported directly into sing-box. Before adding it, identify which of these three types of content you have:
- Subscription URL: Used to retrieve and update configurations. Check that the provider supports sing-box or your current client.
- Single-node link: For example, vless:// or trojan://. Whether it can be imported directly depends on the client.
- JSON configuration: This should be a complete sing-box configuration, not just a section containing outbound parameters.
2. Import a subscription URL
- Open the client’s “Configuration,” “Profiles,” or similar page, click Add, and choose Remote Configuration, URL, or Subscription Import.
- Paste the subscription URL. Check for extra spaces, line breaks, or missing parameters, and enter a name that makes it easy to identify.
- Click Download or Update. If you get a format error, check the provider’s page to confirm the output format; simply changing the file extension will not fix it.
- After the download succeeds, set that configuration as the active one. If a node selection page appears, select the node or policy group you need.
- Start the connection and allow the system to establish a VPN. Then open a webpage to verify it works. You can check your exit IP to confirm that traffic is routed through the proxy as expected.
If you use free nodes from this site or other sources, check their format and validity first. Do not post subscription URLs containing tokens in public group chats or screenshots. Others may be able to use them to access your configuration.
3. Import a link or local file
If you have a single-node link, look for an “Import from Clipboard” option or a QR code scanner. If neither is available, ask the provider for a compatible subscription or complete configuration. Do not paste a node link directly into a JSON editor.
If you have a JSON file, select “Import Local Configuration,” open the file using the system file picker, then save and enable it. If you get an error, note the field named in the message and check whether the configuration is compatible with your core version. Conversion may discard protocol parameters, so avoid giving private node details to untrusted online conversion sites.
4. Troubleshooting import failures and team account environments
If a subscription download fails, first check whether the URL has expired and whether your current network can reach the subscription domain. If configuration validation fails, check the format and version compatibility first. If you’re connected but can’t open webpages, check the node’s validity, system time, DNS settings, and whether another VPN is running. Change just one setting at a time to make it easier to identify the cause.
A successful import does not guarantee a stable account environment. Using the same subscription as a team does not mean everyone will have the same exit IP. Automatic switching, failed nodes, and network changes can all alter the login source that a website sees.
For business accounts that require consistent logins, keep a record of the devices, configurations, and exit regions associated with each account. Avoid having multiple people frequently access the same account from different regions, and verify configuration updates before using them. Selecting a fixed node cannot guarantee that the IP will never change or prevent risk controls from being triggered. You should also follow the platform’s rules and enable multifactor authentication.