This article addresses common questions about “how to import nodes into sing-box”: after receiving a subscription URL, a node sharing link, or a JSON file, where should you import it, and what should you check in your IP, DNS, and browser settings if the import succeeds but you still can’t access the internet? Menus and supported formats vary between sing-box graphical clients, so follow the instructions for your current client.
1. Check which client you have and what format your nodes use
Download the installer from a client listed on the official sing-box project page or from your chosen client’s official release page, and verify that it matches your operating system and version. The command-line core has no graphical import button, so most users should choose a graphical client suited to their device.
Before importing, check what you have. sing-box does not natively support importing every type of subscription or sharing link; whether they can be recognized depends on whether the client provides conversion or parsing features.
- Subscription URL: Usually an HTTPS link, but the returned content could be a Clash configuration, a node list, or a sing-box configuration. You can’t tell which just by looking at the URL.
- Node sharing link: For example, vless://, vmess://, or trojan://. You can paste one in to import it only if the client explicitly supports that format.
- JSON configuration file: It should be a complete configuration compatible with your current sing-box version. A snippet containing only a single outbound object usually won’t run on its own.
2. Import using a subscription URL
- Open the client and go to “Configuration,” “Profiles,” or a similar page. Click Add and look for an option such as “Remote configuration” or “Add from URL.”
- Copy the compatible URL provided by your node provider, paste it into the URL field, enter a descriptive name, then save or download it. Don’t copy an entire block of text that includes instructions.
- Wait for the download to finish and check for parsing errors. If the client reports that the format isn’t supported, ask the provider for a sing-box configuration compatible with your client. Don’t just change the file extension.
- Select and enable the configuration you just added, then allow the VPN connection when prompted by your system. If the configuration includes a node selection group, open the relevant page and choose a route.
- Later, use “Update” to fetch the configuration again. If the update fails, check whether the subscription has expired and whether your network can access the download URL.
Subscription URLs may contain access credentials. Don’t share them publicly or submit them to untrusted online conversion sites. Whether you use free nodes from this site or another source, first confirm the format, last update time, and supported client.
3. How to use a local file or a single node
If you have a complete JSON file, select “Import file” or “Local configuration” on the configuration page, locate the file, and save it. Then select and enable it. If your client supports importing sharing links from the clipboard, copy the individual link and use that option. If it doesn’t, obtain a complete compatible configuration; don’t paste a sharing link directly into the JSON editor.
If validation fails, first check the field mentioned in the error and your client version. Settings shown in older guides may have changed. Back up your existing configuration before upgrading, and refer to the documentation for your current version.
4. If the import succeeds but you still can’t access the internet, check these in order
A successful configuration import doesn’t mean the node can connect. First, make sure the configuration is enabled and VPN permission has been granted. Temporarily disable other VPN or proxy tools to avoid conflicts, then check the logs to distinguish between connection timeouts, authentication failures, and DNS resolution errors.
If webpages open but your exit IP hasn’t changed, check whether traffic is being routed directly and whether your browser has a separate proxy extension enabled. Your exit IP is determined primarily by the actual outbound route; clearing cookies won’t change your proxy IP.
If some domains won’t open, check the DNS settings in your configuration and temporarily turn off the browser’s “Secure DNS” to compare. Don’t change several settings at once. An incognito window can help rule out cache or extension issues, but it can’t replace correctly configured proxy and DNS settings.