This article answers a common question: how do you import nodes into sing-box? Once you have a subscription URL, a VLESS link, or a JSON file, where should you import it, how can you check the connection afterward, and how can teams reduce frequent changes to their outbound IP? Features and menus vary across sing-box graphical clients, so first identify the format of your configuration, then choose the appropriate import method.
1. First, identify what you have
sing-box is a proxy core, and its graphical clients don’t necessarily support the same subscription formats. Being able to import a Clash subscription doesn’t mean a client can import it directly into sing-box. Check the node provider’s instructions first, and prioritize configurations or subscriptions explicitly labeled as compatible with sing-box.
- Complete JSON configuration: Usually includes outbounds, routing, and other settings, and is suitable for importing as a configuration file.
- Subscription URL: The client must support remote configurations, and the content returned by the URL must be compatible with it.
- Single node link: For example, vless:// or trojan://. Only clients with the appropriate parsing feature can add these directly.
Subscription URLs often contain access credentials. Don’t share them in group chats or submit them to untrusted online conversion sites. A node link is not the same as a complete configuration; changing its file extension to .json won’t make it usable.
2. Import and enable the configuration
- Install a client for your device from the project’s official channels or your system’s app store. Check the app documentation to confirm which configuration formats it supports.
- Open the “Configuration,” “Profiles,” or similar page and tap Add. Menu names vary by client.
- If you have a sing-box remote configuration URL, choose the option to add from a URL, paste the address, and save. If you have a complete JSON file, choose the option to import from a file.
- If you only have a single node link, first check whether the client offers “Import from clipboard” or “Add node.” If not, ask the provider for a compatible complete configuration. Don’t keep pasting the link into the remote configuration field.
- Name the configuration, for example, “Work device – Primary,” then select and enable it. When connecting for the first time, allow the VPN connection when prompted by the system.
- Open a frequently used website to check that it’s accessible, then review the client logs. If the configuration supports remote updates, update it manually once to confirm that it downloads and parses correctly.
A successful import only means the configuration was accepted; it doesn’t guarantee that the node is usable. You still need to verify the network connection, node availability, and whether the target websites are routed through the proxy as expected.
3. Troubleshooting import failures and connection issues
If you see a format error, first make sure the downloaded content isn’t a webpage, login page, or error message. Then check that it’s a sing-box configuration supported by your current version. If you see errors about unsupported fields, update the client and ask the provider which version the configuration is intended for.
If the subscription fails to download, check that the URL was copied in full, hasn’t expired, and is accessible from your current network. If the connection times out, check your local network first, then test with another known-working node. If you can connect but some websites won’t open, check the logs for DNS and routing messages. Don’t run multiple VPNs at the same time, as they may interfere with each other.
4. How does team use relate to account environment stability?
For team use, standardize client versions, configuration sources, and naming conventions, but don’t share subscription credentials publicly. After importing the configuration on each device, verify access to work websites and record the primary configuration to reduce accidental switching.
Account environment stability depends on more than whether a node connects. Frequently changing outbound regions, logging in from different locations, and changes in browser state may trigger platform verification. Keep your usage environment reasonably consistent and follow the target platform’s rules. Using a fixed node can’t guarantee that your outbound IP will never change or that your account won’t be restricted.
When using this site’s free nodes, first make sure the format is compatible and test them in practice. Check that they’re working before important tasks and keep a backup configuration to avoid interrupting work with a last-minute subscription update.