Advanced

Rule / Global / Direct: Which Proxy Mode Should You Use?

Clash's main UI usually shows three mode buttons: Rule, Global, and Direct. They are a master switch for all traffic. Many users flip between them randomly when a site fails. This article explains each mode and when to use which.

Three Modes at a Glance

ModeBehaviorTypical use
ruleSplit by rules—domestic direct, overseas via proxyDaily use (recommended)
globalAll traffic through proxyIncomplete rules / temporary global
directAll traffic direct, no proxyTemporarily disable proxy

Rule Mode: The Default Choice

Rule mode matches every connection against rules in your config—proxy where rules say proxy, direct where they say direct. This is Clash's core value and what you should use most days.

Overseas services go through proxy; domestic sites, local video, and updates stay on your ISP connection—faster, lower latency, less proxy quota burned. For most of the time, stay on rule mode and avoid constant switching.

How well rule mode works depends on rule quality. If an overseas site is not covered, a catch-all might send it direct and it will fail—that is a rules gap, not a mode problem.

Global Mode: Everything Through Proxy

In global mode, every connection uses your currently selected node; rules are ignored. It helps in two situations:

The cost: domestic sites also detour through proxy—often slower, higher latency, more bandwidth used. Treat global as temporary, not your everyday setting.

Direct Mode: Proxy Off, Client Still Running

Direct mode sends all traffic without any proxy—like turning proxy off without quitting the app. Use it when you only need local services, want to test whether proxy is causing a problem, or must use plain network access on office or campus Wi‑Fi. Switch to direct and everything uses your physical connection.

Which Mode Should You Pick?

A simple decision path:

  1. Daily use → stay on Rule;
  2. Overseas site not covered, need it now → switch to Global;
  3. Suspect rules are blocking a site → try Global; if it works, add a rule and return to Rule;
  4. Want proxy off but keep the client open → Direct.

A Common Question: Why Doesn't Global Work Either?

If global mode still cannot load a site, the problem is probably not rules—look at nodes and environment. Common causes: the selected node is dead, subscription quota exhausted so all nodes fail, local network issues, or system proxy and TUN enabled together causing conflict. Try nodes in different regions, check subscription status and proxy settings, and narrow it down step by step.

Make Mode Switching Easier

Many desktop clients offer tray menu or hotkeys to flip between rule and global. The better long-term fix: add services that always needed global into your rules pointing at proxy. Once rules are solid, you rarely touch the mode switch and can stay on rule mode—that is the lowest-maintenance setup.

Modes vs. Policy Groups

One relationship to keep straight: mode is the global switch; policy groups pick the node. Mode answers "follow rules or force all proxy/direct"; groups answer "which node when proxy is used." In rule mode, rules send traffic to a group, and the group picks the active node. Knowing that separates "change mode" from "change node."

Tip: if you often need global for the same services, your rules probably need updating. Spending time on rules beats toggling global every session.

To learn how to write rules and use each type, read Clash Rule-Based Routing Explained: A Practical Guide to Writing rules on this blog, or see Documentation · Rule Types Reference.

Ultimately, the three modes are just positions on one master switch—node quality and rule completeness still drive day-to-day experience. Once you know when to use each, you can diagnose access problems quickly instead of guessing. Treat modes as diagnostic tools and rules as your long-term plan.


Continue reading