Zero to traffic

It is a client for the mihomo core: it takes your subscription, routes traffic by rules and can bypass DPI. It is not a VPN service: ReClash does not sell access, does not issue subscriptions and does not recommend providers. You bring your own server and link.

ReClash is a fork of FlClash. The main additions: smart routing that keeps a working node for the current network on its own, a much larger provider header set (theme, widgets, announcements, domain migration), a reworked dashboard with widgets, import from more formats (Amnezia among them), and a built-in DPI bypass. The routing core is the same — mihomo.

The project is not affiliated with FlClash, mihomo or FlClashX.

It is the “Auto” mode: the client picks a node that works on your current network and switches on its own when the network changes — without opening the window. Start from a region preset (Russia, Iran, China); strategy, checks and markers can be fine-tuned.

The plain modes are still there: “Auto” is the same rules plus an auto-pick you can switch off.

No. The DPI bypass works before the proxy: it fragments and disguises the start of the connection so the ISP's equipment cannot match it against a signature and cut it. The traffic still goes wherever you pointed it.

Sometimes the bypass alone is enough — when a site is blocked by SNI rather than by IP. Sometimes you need both, so that the connection to the proxy can be established at all.

TUN/VPN intercepts traffic at the network layer: it covers everything, including programs that know nothing about a system proxy. It needs privileges (administrator on desktop, the VPN permission on Android).

System proxy is simpler and needs no privileges, but only apps that respect OS settings will use it. Games, some messengers and many CLI tools will not.

On desktop, nothing: the client only reaches your subscription and, unless you turned the check off, the GitHub release list. Logs and connection statistics stay on the device for diagnostics — you can clear them at any time.

On Android the build includes crash analytics (Firebase Crashlytics). It is off by default; you can turn it on in settings, and the app tells you about it on first launch. When on, it sends device information and crash details — no personal data — and can be turned off in the same place.

It is a stable 16-character device hash the client can attach to the subscription request, so the provider can show you a readable list of your devices and your plan limit. Sharing it can be switched off in settings.

For providers: the details are on the documentation.

Most likely your provider sent a theme in the ReClash-Hex header alongside the profile. The theme belongs to the active profile: switch profiles and the old one returns. Provider styling can be turned off entirely in the theme settings.

Nothing in the client — just add headers to your subscription response. No SDK, no plugin, no agreement with us. Assemble them with the builder and paste the snippet into nginx, Caddy or your backend.

The minimum a user will notice: remaining traffic, the service name and a support link.

Not currently. The App Store does not admit clients of this kind without a separate developer programme, and sideloading on iOS is its own story. Promising a date would be dishonest.

In order:

1. Refresh the profile — the subscription may have gone stale.
2. Run the latency test: if every node is unreachable, the problem is between you and the provider, not in the rules.
3. Switch to Global mode: if it starts working, the routing rules are the cause.
4. Turn the DPI bypass on: your ISP may be cutting the handshake itself.
5. Open “Logs”. It usually says so in plain words.

Still stuck — open an issue. And scrub the subscription URL out of the logs before you post them: it carries your credentials.