Proxy groups define how a set of nodes gets used. The same nodes behave completely differently depending on the group type wrapping them.

select: manual choice

- name: "Select"
  type: select
  proxies: ["Auto", "HK 01", "JP 01", "DIRECT"]

Pick manually on the Proxies page; your pick sticks. The most intuitive type and almost always the first group in a profile. Members can be nodes, other groups, DIRECT or REJECT.

url-test: automatic fastest

- name: "Auto"
  type: url-test
  proxies: ["HK 01", "HK 02", "JP 01"]
  url: "http://www.gstatic.com/generate_204"
  interval: 300
  tolerance: 50

Benchmarks every interval seconds and uses the fastest node. tolerance (ms) is the switching threshold: a new node must beat the current one by that margin, preventing flip-flopping between two similar nodes.

fallback: priority failover

- name: "Failover"
  type: fallback
  proxies: ["Main", "Backup 01", "Backup 02"]
  url: "http://www.gstatic.com/generate_204"
  interval: 300

Always uses the first available node in your order; if it dies, the next steps in, and it switches back on recovery. Unlike url-test it respects your priorities rather than chasing speed. Ideal when your main node is stable but occasionally maintained.

load-balance: spreading connections

- name: "Balance"
  type: load-balance
  proxies: ["Node A", "Node B", "Node C"]
  url: "http://www.gstatic.com/generate_204"
  interval: 300
  strategy: consistent-hashing

Distributes different connections across nodes. consistent-hashing keys on the destination domain (the same site always uses the same node - kinder to risk-control systems); round-robin rotates. Useful for aggregating several modest nodes; note some sites dislike rapidly changing IPs.

Choosing at a glance

NeedType
Full manual controlselect
Hands-off, always fastesturl-test
Preferred main with failoverfallback
Spread traffic across nodesload-balance
Tip: the most popular pattern is a url-test group as the first member of a select group: automatic by default, manual override one click away.