This guide explains how to import nodes into sing-box: how to identify node formats, import subscriptions, check your connection, and reduce the impact of exit changes on account environments when working in a team. Menu names may vary between sing-box graphical clients, so follow the interface you’re using.
1. Check the client and node format
sing-box is a proxy core, and graphical clients don’t all support the same import methods. When installing, choose a version from the project’s official website or release page, and check that it’s compatible with your operating system. The first time you launch it, follow the prompts to allow a VPN connection or add a network extension.
Before importing, identify what you have. A node link, a subscription URL, and a complete configuration are different things and shouldn’t be used interchangeably.
- Single-node link: Commonly starts with vless://, vmess://, trojan://, or a similar prefix. The client must explicitly support parsing that format.
- Subscription URL: Usually an HTTPS link, but the returned content may use a format intended for a different client, so it may not work directly.
- Complete configuration: Usually a JSON file containing settings such as outbound connections, routing, and DNS. It must also be compatible with your version of sing-box.
2. Import using a method supported by your client
- Open the client’s “Configuration,” “Profiles,” or similar page and find the add option. If the interface supports “Import from URL,” paste a subscription or remote configuration URL that is clearly marked as compatible with the client, then enter an easy-to-recognize name.
- Click Download or Save and wait for the configuration to update. The import is complete only when the URL has been saved successfully, there are no parsing errors, and the configuration can be selected.
- If you have a complete JSON configuration, choose “Import from file.” If you only have the configuration text, use the client’s text-import option. Don’t paste JSON into a subscription URL field.
- If you only have a single-node link, check for an “Import from clipboard” or QR code option. If neither is available, ask the provider for a compatible configuration. Don’t assume every sing-box client can recognize the link directly.
- Select the new configuration, choose a node if prompted, and start the connection. Grant VPN permission, open a commonly used website to test the connection, and check the logs for obvious errors.
Don’t enter your subscription URL into an online converter you don’t trust. The URL may contain an access token, which could let someone else use your subscription if it’s exposed. Even with this site’s free nodes, check the format and instructions before attempting to import them.
3. Imported successfully, but can’t connect? How to troubleshoot
First, turn off the proxy and confirm that your local network is working. Then check that your system clock is set to sync automatically. If you see a parsing error, first check the subscription format, configuration version, and whether the URL is complete. If the download fails, check whether the URL has expired, requires a login, or is accessible from your current network.
If the configuration starts but websites won’t load, check that you’ve selected a working node, VPN permission is enabled, and no other VPN or proxy tool is running at the same time. Use the logs to distinguish between a connection timeout, authentication failure, or DNS issue. Change one setting at a time and retest immediately after each change. Don’t change several settings in a row.
4. Team use and account environment stability
The import method itself doesn’t determine whether an account remains stable. The factors that matter are the exit region, IP changes, device, and login behavior. Teams can standardize client versions and configuration names, and keep a record of subscription update times. Before logging in to important accounts, check the exit region and avoid switching nodes frequently during a session.
Don’t share personal accounts or casually forward configurations containing credentials. When a team member leaves, revoke their access using the provider’s process. A shared exit doesn’t mean you have a fixed or dedicated IP, and it can’t guarantee that an account won’t be prompted for verification. If verification is required, follow the platform’s rules.