This article explains how to import nodes into sing-box. First, distinguish between subscription links, single-node links, and configuration files. Then import them using a method supported by your client, and check your IP, DNS, and browser settings to avoid situations where you’re “connected” but can’t open webpages. Menus may vary across platforms and client versions; the steps below use common graphical clients as examples.
1. Install the client and identify the node format
Download the installer from the official sing-box project or a trusted release page for your chosen client, and make sure it supports your operating system. The sing-box core program is not the same as a client with a graphical interface. Most users should choose a version that includes configuration management.
Before importing, identify which type of content you have:
- Subscription URL: usually an HTTPS link. The client downloads configuration or node information from it.
- Single-node link: for example, a string starting with vless://, vmess://, or trojan://.
- Configuration file: usually in JSON format, with settings for outbound connections, routing, DNS, and more.
sing-box does not support every subscription format. Clash YAML files, single-node links, and sing-box JSON files are not interchangeable just by changing the file extension. Whether a format can be imported directly depends on the client’s parsing capabilities.
2. Import nodes by type
- Import a subscription: Open the client’s “Configuration,” “Profiles,” or similar page, choose to add a remote configuration, and paste in a subscription URL compatible with sing-box. Give it a name and save it, then download or update it. Once the import succeeds, set it as the active configuration.
- Import a local file: If you have a complete sing-box JSON file, save it to your device, then use the configuration page to import it. If the client reports unsupported fields, check which core version the provider requires; don’t remove fields at random.
- Import a single node: Paste a link directly only if the client explicitly offers a feature such as “Import from clipboard” or “Scan QR code.” If it doesn’t, ask the provider for a complete configuration or a compatible subscription. Don’t use a node link as a remote configuration URL.
- Select the configuration and start the connection. The first time you connect, follow the system prompts to grant VPN or network interception permissions. If the configuration includes a node selection group, choose an available node.
When using free nodes from sites such as freevpn-x.com, check the format instructions and supported clients first. Free resources may stop working, and a successful import does not guarantee a successful connection. Subscription URLs may contain access credentials, so don’t share screenshots of them or upload them to unfamiliar conversion sites.
3. What to check if the connection doesn’t work after importing
First, check whether the configuration loads. Parsing errors are usually related to the format, file contents, or version compatibility. If a subscription download fails, check that the link is complete and hasn’t expired, and that your current network can reach the subscription URL.
Next, check the connection errors in the logs. A timeout may indicate that the node is unavailable or that the network is restricting access; an authentication failure means you should check your credentials. Try updating the subscription, then test another node. Avoid changing several settings at once.
Finally, distinguish between IP, DNS, and browser issues. Whether your exit IP changes depends on whether the test traffic is routed through the proxy, so the connection icon alone isn’t enough to confirm this. If the IP is reachable but domain names won’t open, check the DNS and routing settings in your configuration. Secure DNS in your browser and proxy extensions may also change how traffic is routed. Try temporarily disabling relevant extensions or testing with another browser for comparison.
If only some apps fail, check whether the client has system proxy or TUN/VPN mode enabled, and whether routing rules are sending that app’s traffic directly. An IP check can verify only part of the network path; by itself, it cannot prove that all traffic is being routed through the client or that your browser environment is anonymous.