Short answer

WireGuard is a VPN-style tunnel that can be used as an outbound node in Clash/Mihomo, with fields closer to tunnel configuration. In real use, trust the provider subscription first and then verify whether the selected client core supports this exact type.

What It Means

In Clash/Mihomo configuration, wireguard identifies the outbound type used by the node, policy or group. The same display name in a GUI can hide different transport fields, so the YAML or subscription output is more reliable than the node nickname.

Common Fields

type: wireguard
private-key
server / port
ip / ipv6
public-key
allowed-ips
reserved

When to Use It

The provider supplies WireGuard nodes.
Specific traffic needs to go through a VPN-style tunnel.
The profile includes peer keys, addresses and allowed IP ranges.

Support Checks Checks

private-key, public-key and reserved values are sensitive.
Rules decide which traffic enters WireGuard; it does not automatically take over everything.
Platform permissions, TUN and firewalls affect behavior.

Minimal Shape

proxies:
- name: "wg-node"
  type: wireguard
  server: server.example.com
  port: 51820
  private-key: BASE64_PRIVATE_KEY
  ip: 172.16.0.2/32
  public-key: BASE64_PUBLIC_KEY

Compatibility Notes

Client support changes with the bundled core. A maintained Mihomo-based client usually supports more modern node types than historical Clash clients, but mobile clients and iOS alternatives still vary by app and release.

If a subscription contains this type but the client filters it out, switch to a compatible client, ask the provider for a compatible subscription format, or use a converter only when you understand what fields are being changed.

Official Reference

WireGuard in Mihomo docs

WireGuard Protocol