This guide explains how to import nodes into sing-box. It covers how to tell node links from configuration files, how to import a subscription through a client, and how to check whether the connection is working. For teams sharing a network setup, it also explains how changes to the egress IP can affect account environment consistency, so you don’t mistake a successful import for stable access for everyone.
1. Check what you received before importing
Download the version for your operating system from the official sing-box project or one of its listed client sources. This guide uses a client with a graphical interface as an example. Menu names may vary across platforms and versions; the command-line program does not have features such as QR code scanning or subscription management.
- Single-node link: Often starts with vless://, vmess://, or trojan://. Not all sing-box clients can parse these links directly.
- Subscription URL: Usually an HTTPS link, but the returned content may be in a format intended for another client. Confirm that the provider supports sing-box.
- Configuration file: Usually JSON. It may include DNS and routing settings in addition to nodes, so make sure it comes from a trusted source.
sing-box uses JSON configurations, but that doesn’t mean it can directly import every node link or Clash subscription. If the format isn’t supported, ask the provider for a compatible configuration. Don’t submit a private subscription to an unfamiliar online converter.
2. Import and enable the configuration through your client
- Open the client, find the “Configuration,” “Profiles,” or similar page, and click to add a new profile. Keep your existing working configuration so you can switch back if needed.
- If the client has a “Remote Configuration” or “Add from URL” option, enter the sing-box configuration URL specifically supported by your provider, give it a name, and download and save it. If not, download the configuration file and import it locally.
- If you have a JSON file, choose “Import from File” and check for parsing errors. Only try importing a single-node link if the client explicitly supports clipboard import or QR code scanning.
- Select the new configuration, start the connection, and grant VPN or network extension permissions when prompted by your operating system. Some desktop clients also require you to enable the system proxy; follow the client’s instructions.
- Open a commonly used website to test the connection, then check the client logs and the selected outbound node. Seeing the configuration name doesn’t mean your traffic is actually going through the proxy.
Test the configuration manually before enabling automatic updates. A remote configuration update may change nodes, routing, or DNS behavior. Local files usually don’t sync automatically, so you’ll need to download and import them again.
3. How does team use affect account environment consistency?
Team members importing the same configuration won’t necessarily use the same egress IP. Automatic node selection, failover, routing rules, and differences in each person’s network can all lead to different egress IPs. Frequently switching regions or egress IPs may trigger additional verification on some platforms, though it isn’t the only factor.
For work, keep a dedicated configuration and record its source, update date, and usual egress region. After an update, have one person test it first. A VPN can’t guarantee that an account won’t trigger security checks. Follow platform rules, use legitimate member permissions and multifactor authentication, and don’t share account passwords. Avoid posting node links or subscription URLs containing credentials in public group chats.
4. Troubleshooting import and connection issues
If you see a format error, first check whether you used a Clash YAML file, a webpage URL, or an unsupported node link by mistake. If a configuration field isn’t supported, check the client version against the configuration requirements. If the subscription download fails, make sure the URL is complete and hasn’t expired, and check whether your current network can reach the subscription source.
If the client starts but webpages won’t load, check node availability, system time, proxy settings, and any DNS errors in that order. Temporarily disable other proxy software to rule out conflicts. When reporting an issue to your team, include the client version, operating system version, and redacted logs. Hide subscription tokens, passwords, and UUIDs. Test free nodes using the same process, and don’t rely on them as your only connection for critical work.