Streaming services such as Netflix and Disney+ do not necessarily need the same network path as local websites, domestic applications, or work tools. A useful Clash setup can send selected streaming domains through a dedicated proxy group while keeping local traffic on DIRECT. This split-routing design reduces unnecessary latency, makes troubleshooting easier, and prevents a streaming node from handling traffic that does not need it.
The important point is that a streaming rule is not simply a list of two homepage domains. Netflix and Disney+ load content from multiple domains, use separate authentication and API endpoints, resolve content delivery networks, and may open connections from applications that do not follow the operating system proxy. A reliable configuration therefore combines an appropriate rule source, correct rule order, a tested policy group, and a clear understanding of how the target device sends traffic into Clash.
Clash Netflix & Disney+ Streaming Setup: Split-Rule Guide
Plan the routing structure before editing YAML
A Clash configuration usually has four related parts: proxy nodes, proxy groups, rule providers, and the final rules list. The nodes are the available exits. A proxy group decides which exit should be used. A rule provider supplies reusable domain or IP entries. The rules section connects a matching request to a policy group such as STREAMING, DIRECT, or REJECT.
For Netflix and Disney+, create a separate group instead of sending both services directly to a general-purpose group that is also used by every foreign website. A dedicated group lets you test streaming nodes independently and switch to another exit without changing unrelated routing. It also makes connection logs easier to read because the intended policy is visible in the matched rule.
proxy-groups:
- name: STREAMING
type: select
proxies:
- Streaming-US
- Streaming-JP
- Streaming-SG
- PROXY
- DIRECT
rules:
- RULE-SET,streaming-domains,STREAMING
- GEOSITE,cn,DIRECT
- GEOIP,cn,DIRECT,no-resolve
- MATCH,PROXY
The example assumes that the node names already exist and that the selected core supports the rule syntax being used. A configuration imported into Clash Verge Rev or another Mihomo-based client may support more rule-provider and GeoSite features than an older client using the original Clash core. Before copying a field from a current guide, check the running kernel name and version in the client’s settings or startup log.
Do not treat DIRECT as a security or privacy guarantee. It means that the connection leaves through the normal local network path rather than through a configured proxy node. If a local website is unavailable from the current network, changing it to DIRECT will not make it reachable. Conversely, if a streaming service rejects the selected exit, moving the rule to another proxy group may help, but the result still depends on the service’s regional licensing and network detection.
Choose a dedicated policy group
A select group is convenient while testing because the active node can be chosen manually. Once several nodes have been tested, an url-test group can automatically select the node with the lowest measured delay, although a low HTTP latency does not prove that Netflix or Disney+ will accept the exit. A node can respond quickly to a test URL and still be unsuitable for a particular streaming platform.
Keep the group name stable. Rules reference the exact policy-group name, including capitalization and spaces. If a subscription update renames a node or replaces a group, the rule may point to a group that no longer exists. The client can then show an error, fall back unexpectedly, or refuse to load the configuration.
Write Netflix and Disney+ split rules
There are two common ways to maintain streaming rules. The first is to use a rule provider containing domain entries. The second is to write individual DOMAIN, DOMAIN-SUFFIX, or DOMAIN-KEYWORD rules directly in YAML. A provider is usually easier to update and reuse, while explicit rules are useful for a small test configuration.
rule-providers:
streaming-domains:
type: http
behavior: domain
format: yaml
url: "https://example.invalid/streaming.yaml"
path: ./ruleset/streaming.yaml
interval: 86400
rules:
- RULE-SET,streaming-domains,STREAMING
- GEOSITE,cn,DIRECT
- GEOIP,cn,DIRECT,no-resolve
- MATCH,PROXY
The URL above is a placeholder rather than a download address. Replace it only with a rule source that you trust and that is compatible with the running core. If the provider is unavailable, the client may keep a cached copy, depending on its implementation, but a newly installed configuration may have no entries to match. For a portable configuration, store a local provider when appropriate and verify its update status in the client.
For a quick local test, a small provider might contain entries like the following. The exact set must be verified from connection logs because service infrastructure changes over time:
payload:
- DOMAIN-SUFFIX,netflix.com
- DOMAIN-SUFFIX,netflix.net
- DOMAIN-SUFFIX,nflxvideo.net
- DOMAIN-SUFFIX,disneyplus.com
- DOMAIN-SUFFIX,disney-plus.net
These entries are examples of routing scope, not a guarantee that every login, catalog, image, API, or video request for the service will use only these suffixes. Do not add a broad keyword such as netflix to the entire rule list without testing. Keyword rules can match unrelated domains and may send more traffic through the streaming group than intended. It is safer to begin with narrow domain suffixes, inspect missed connections, and add only domains that are clearly part of the service workflow.
Respect top-to-bottom rule order
Clash evaluates rules from top to bottom and normally stops at the first matching rule. If a broad rule such as GEOSITE,geolocation-!cn,PROXY appears before the Netflix and Disney+ entries, the streaming-specific policy may never be reached. If a general GEOIP,cn,DIRECT rule appears too early, an IP-based connection can bypass the intended streaming group after DNS resolution.
A practical order is to place explicit streaming rules first, followed by private-network and local rules, then regional direct rules, general proxy rules, and finally MATCH. The exact order depends on your goals. If a streaming endpoint must always use the dedicated group, its rule must be more specific and earlier than any broader category that could match it.
| Rule layer | Example policy | Purpose |
|---|---|---|
| Streaming domains | STREAMING |
Send verified Netflix and Disney+ domains to tested exits. |
| Private networks | DIRECT |
Keep local services and LAN addresses on the local route. |
| Regional domains | DIRECT |
Reduce latency for domains that should use the local connection. |
| Unmatched traffic | PROXY |
Provide a predictable fallback instead of silently bypassing rules. |
Test nodes for compatibility, not only latency
Node testing should answer more than “which server has the smallest delay?” A streaming exit must provide stable DNS behavior, sufficient throughput, and a destination region accepted by the service. A node with a measured delay of 80 ms may perform better than one with 250 ms, but latency alone says nothing about video throughput, concurrent connections, packet loss, or whether the address has been identified as a hosting-provider or datacenter network.
First select one node in the STREAMING group and open the Clash connection log. Look for the request domain, the matched rule, the selected policy group, and the final node. If the connection is shown as DIRECT, the rule did not match, the group selection is wrong, or the application did not enter Clash. If the domain matches STREAMING but the final node is unexpected, inspect the group’s current selection and health-check behavior.
Test the services in a clean browser session or private window after changing nodes. Close existing tabs and, when necessary, restart the application so that old DNS answers, HTTP connections, cookies, or media sessions do not obscure the result. A previously established connection can continue using the old route for a short time, which may make a correct rule change appear ineffective.
Rule match
The rule that sends a request to STREAMING, DIRECT, or another policy. Verify this before changing nodes.
Node test
A real service check involving login, catalog access, playback startup, and sustained video traffic.
DNS path
The resolver used before the connection is opened. Its behavior can affect CDN selection and rule matching.
Netflix and Disney+ can apply different availability rules by country or region. A successful page load does not mean that every title is available, and a proxy route that works for one service may fail for the other. Record the selected node, observed region, login result, playback result, and approximate time when comparing nodes. This turns trial and error into a repeatable test rather than a sequence of unexplained switches.
Account for DNS, TUN, and device-specific behavior
System proxy mode and TUN mode do not cover exactly the same traffic. System proxy mode affects applications that honor the operating system’s HTTP or SOCKS proxy settings. Some desktop browsers and tools do, while games, media players, background services, and native applications may connect directly. TUN mode creates a virtual network interface and can capture more traffic, but it requires operating-system permissions and may interact with antivirus software, VPNs, firewalls, and other virtual adapters.
On Windows, check whether the client’s system proxy is enabled and whether the selected port is the one shown in the active configuration. If streaming works in a browser but not in a dedicated desktop application, compare the connection log in system proxy mode and TUN mode. On macOS, confirm that the client has permission to change network settings and that another VPN profile is not taking priority. On Android, inspect the VPN status and battery restrictions; Android generally allows only one VPN-style service to control the active tunnel at a time.
DNS settings also matter. Fake-IP and redirection modes can change how domains are represented internally, while TUN routing may depend on the client’s DNS hijacking or virtual-interface implementation. Avoid adding random DNS overrides merely because a page fails. First check whether the DNS request appears in the Clash log, whether the domain is resolved by the expected resolver, and whether the resulting connection matches the intended rule.
For a family or home-network setup, allow-lan: true exposes the local proxy service to other devices when combined with a suitable bind address and firewall policy. This is different from enabling the proxy only for the host machine. Do not enable LAN access on an untrusted network without restricting the listen address and firewall rules. A reachable unauthenticated mixed port can allow other devices to consume the proxy or access services through the host.
mixed-port: 7890
allow-lan: false
bind-address: 127.0.0.1
mode: rule
dns:
enable: true
enhanced-mode: fake-ip
The snippet is a starting point for a local desktop example, not a universal recommendation. DNS fields, fake-IP filters, TUN options, and service-specific exclusions vary between Clash and Mihomo versions. If a configuration uses a subscription-generated YAML file, place persistent changes in the client’s supported override or profile mechanism so that the next update does not erase them.
Diagnose common Netflix and Disney+ failures
If local websites unexpectedly use the proxy, inspect the rule order and the fallback policy first. A broad PROXY rule near the top can capture traffic before local rules are evaluated. Also check whether the client is running in global mode rather than rule mode. In global mode, the selected global policy can override the split-routing design, so changing YAML rules will not produce the expected result until rule mode is restored.
If Netflix or Disney+ still connects directly, search the connection log while loading the login page, catalog, and playback screen. The first visible domain is not always the only required domain. Add narrowly scoped entries to the provider only after confirming that the missed domain belongs to the service. Then update or reload the rule provider, clear stale connections, and repeat the test.
If the page opens but playback fails, compare the node’s bandwidth and stability with another exit. Check whether the media domain is going to the same policy group as the login and API requests. A configuration may route the homepage through STREAMING while a CDN hostname falls through to DIRECT or a general group. The connection log during playback is more useful than the browser error message alone.
If a node works briefly and then stops, consider address reputation, rate limits, account security checks, and provider-side changes. Repeatedly switching nodes while leaving many active sessions can create additional authentication challenges. Sign out of unused sessions where appropriate, avoid automated repeated retries, and test one controlled change at a time.
| Symptom | Likely area | First check |
|---|---|---|
| Everything uses one proxy | Operating mode | Confirm the client is in rule mode, not global. |
| Streaming rule never appears | Rule source or order | Reload the provider and move its rule above broad regional rules. |
| Browser works, app fails | Traffic capture | Compare system proxy and TUN logs for the application’s connections. |
| Catalog loads, video fails | CDN or node quality | Inspect playback domains and test another stable streaming exit. |
| Local services stop working | LAN or DNS routing | Check private-network rules, local DNS behavior, and TUN exclusions. |
After each change, reload the configuration and verify that the client reports a successful parse. YAML indentation errors, duplicated keys, invalid provider formats, and misspelled policy names can prevent the new rules from becoming active. Always confirm the active profile name and its last update time; editing a downloaded file that is not currently selected will have no effect.
FAQ: Clash split rules for streaming services
Should Netflix and Disney+ use the same proxy group?
They can share a group when the same tested exits work for both services, but separate groups are easier to troubleshoot. A shared group is convenient for a small configuration; separate groups provide more control when the services require different regions or behave differently on the same node.
Why does a streaming homepage load while playback fails?
The homepage, authentication service, catalog API, and video CDN may use different domains. Inspect the Clash connection log during playback and confirm that the media-related requests match the intended provider and policy group. Also test the node’s sustained bandwidth and stability rather than relying only on its delay measurement.
Can TUN mode guarantee that every streaming application is routed?
No. TUN captures more traffic than ordinary system proxy mode, but coverage depends on the operating system, permissions, DNS handling, firewall rules, and application behavior. Some applications use their own transport, certificate checks, or network policies. Confirm coverage in the Clash connection log instead of assuming that the presence of a TUN interface proves every request is proxied.
What should be checked after a subscription update?
Verify that the STREAMING group still exists, its node names are valid, the rule provider loaded successfully, and the streaming rule remains above broad rules. Subscription updates can replace local groups or overwrite unmanaged edits, so persistent customizations should use the client’s supported override mechanism.
A stable streaming setup is built through observation: identify the application path, confirm the matched rule, test the selected exit, and keep local traffic on the route that best fits your network. Start with a small rule set, document each tested node, and expand the provider only when the connection log shows a genuine missing domain.