This guide answers the question “How do I import nodes into sing-box?” It’s for users who already have free nodes, a subscription URL, or an individual node share link. Follow the steps to import them into a sing-box client, then learn why your IP, DNS, and browser environment can still affect what you can access after connecting.
1. What to prepare before importing
sing-box is a proxy core. Client names may vary across platforms—for example, SFI, sing-box for Android, a compatible graphical client on iOS, or desktop software that uses the sing-box core. Regardless of the interface, the basic process is the same: prepare your node details, import the configuration, enable the proxy, and test the connection.
- If you have a subscription URL, it usually starts with https:// and is suitable for importing multiple nodes and updating them later.
- If you have a single node, it may use a format such as vless://, vmess://, or trojan://.
- If you have a complete JSON configuration, make sure it comes from a trusted source. Don’t import configurations from unknown sources.
This site collects free node details for temporary testing, but free nodes can be unstable. We recommend checking the connection after importing them.
2. Import sing-box nodes using a subscription URL
- Open your sing-box client and go to “Profiles,” “Config,” “Subscription,” or a similar section.
- Tap “Add” or the plus icon in the top-right corner, then select “Import from URL.”
- Paste your subscription URL. For the name, enter “freevpn” or another label that’s easy to recognize.
- Save, then tap “Update subscription” and wait for the client to retrieve the node list.
- Return to the home screen, select a node or policy group, and enable the VPN/proxy switch.
If the client says the format isn’t supported, the subscription may not be in the native sing-box format. Some clients can convert it automatically; others can’t. In that case, try a client that supports Clash/V2Ray subscription conversion, or use a subscription source that provides the sing-box format.
3. Import an individual node share link
If you only have a vless:// or trojan:// link, select “Import from clipboard,” “Import from clipboard,” or “Add manually” in the client. After importing, check three things: the server address, port, and transport protocol. VLESS nodes commonly use parameters such as Reality, TLS, and WebSocket; missing even one parameter can cause the connection to fail.
Don’t change fields such as UUID, flow, sni, host, or path without a good reason. Most users can simply paste the original link and let the client parse it. Unless the provider specifically tells you to, we don’t recommend changing the configuration yourself.
4. How IP, DNS, and your browser environment affect access
Successfully importing a node doesn’t guarantee that websites will open normally. After connecting, visit an IP lookup site to confirm that your exit IP has changed. If it hasn’t, the system proxy or VPN mode isn’t working.
DNS can also affect access. If a website won’t open, the node may still be connected; the problem could be that DNS requests are still going through your local network and returning incorrect results. If your client offers options such as “Remote DNS,” “Prevent DNS leaks,” or “FakeIP,” start with the recommended defaults and avoid enabling multiple conflicting rules at once.
Keep your browser environment in mind, too. Proxy extensions, old cached data, DoH settings, and privacy fingerprinting can all affect test results. To troubleshoot, use a private window, disable other proxy extensions, and test the same website again.
5. Quick checks for connection failures
- Update the subscription and try 2–3 different nodes to rule out a single failed node.
- Make sure your phone or computer has the correct time. An incorrect clock can cause TLS/Reality handshakes to fail.
- Disable other VPNs, accelerators, and proxy extensions to avoid port or routing conflicts.
- Switch between Wi-Fi and mobile data to see whether the current network is restricting access.
- Check the logs for keywords such as timeout, handshake failed, or dns error.
In short, the key to importing nodes into sing-box is choosing the right import method, keeping all parameters intact, and verifying your IP and DNS after connecting. If the node connects but websites still behave abnormally, check your browser environment and look for DNS leaks to help pinpoint the problem.