Online Node and Subscription Converter

Convert and import

1. Paste one node link per line into the editor. You can also paste Base64 content, Clash / Mihomo YAML or sing-box JSON. Use Import / Filter to import subscription URLs.
2. Choose the output format beside the conversion button. If you need policy groups and routing rules, review the template, Prefix and rule output settings.
3. Convert, then check the node count, servers, ports and transport fields in the result preview before copying or downloading.
4. Import into the matching client. Start with one of your own working nodes, then add more nodes and rules. The demonstration nodes can validate the format but cannot validate connectivity.

Choose an output format

• Mihomo / Clash produces YAML. Choose Mihomo for clients using that core. Older Clash cores support different protocols; converting a file does not add protocol support to an old core.
• sing-box produces JSON. Check the client’s sing-box version and supported routing fields. YAML cannot be imported directly as a JSON configuration.
• V2Ray URI / Base64 produces node share links or their encoded form. These are not complete client configurations with policy groups, DNS and routing rules.
• Surfboard produces a client configuration containing supported nodes. If the result reports skipped nodes, check the node count and protocol types.

vless://[email protected]:443?encryption=none&security=tls&type=ws&host=demo.example&path=%2Fproxy&sni=demo.example#Demo-VLESS

proxies:
  - name: Demo-VLESS
    type: vless
    server: demo.example
    port: 443
    uuid: 11111111-1111-4111-8111-111111111111
    network: ws
    servername: demo.example
    tls: true
    ws-opts:
      path: /proxy
      headers:
        Host: demo.example

Troubleshoot common problems

The client rejects a field or protocol

Record the rejected field and the client’s core version, then check the output format. Renaming the file extension does not convert its format. Do not remove the UUID, SNI or transport settings just to suppress an error.

YAML indentation or mapping values errors

Copy the complete result again. Check manually edited sections for tabs, missing quotes or incorrect nesting. Import an unedited single-node output first, then add custom rules one change at a time.

The node imports, but routing or ad blocking does not work

Converting nodes does not automatically supply every routing rule. Check whether the selected template includes the rules you need, whether rule sets loaded successfully, and which outbound each policy group actually selects. For blocking, check that the appropriate group selects REJECT.

The configuration imports, but connections fail

Import success only means the client accepted the configuration. Compare TLS, SNI, Host, Path and port against the original node, then inspect client connection logs. An endpoint connectivity check cannot replace protocol authentication or a real network access test.

A snapshot or a live subscription?

Copying or downloading gives you the current conversion result. For updates from a source, use dynamic subscription conversion or the subscription manager. Text conversion runs in the browser. Fetching an HTTP(S) subscription requires a server request to its source; saving a subscription stores the result on the server or in the selected repository. See the privacy policy for the editor and third-party services.

For client field definitions, see the Mihomo documentation and sing-box documentation.