Tutorial
This document explains the standard FlClash setup in deployment order: subscription onboarding, proxy activation, node evaluation, then rules and auto-start settings - suitable for office and development environments.
Onboard Your Subscription
FlClash obtains node information through a subscription (subscription URL or config file). On first use, choose either of the following methods:
Method 1: URL Protocol Handoff
In supported environments (browser, email or IM client), opening the subscription link will ask whether FlClash should handle it. Confirm, and the import completes automatically - ideal for rapid setup.
- Copy the subscription link from your provider's console
- Open the link in a browser
- Select FlClash when prompted
- Verify that the node list has loaded
Method 2: Manual URL Entry
When protocol handoff is unavailable, enter the link manually inside the app:
- Open FlClash and enter the "Configuration" module
- Tap "Add Configuration"
- Set the import type to "URL"
- Paste the subscription link and save
- Wait for the remote config to finish downloading
Activate the Proxy Service
Once the configuration is ready, return to the dashboard. Turning on the main switch lets FlClash take over the system proxy:
- Return to the FlClash dashboard
- Locate the main switch
- When the status shows "Connected", the proxy is active
- Verify connectivity to Google, YouTube, GitHub and similar services
π‘ Note: Android requests VPN permission on first activation; macOS/Linux may ask for an administrator password. Complete the authorization in a managed terminal environment.
Node Selection and Evaluation
FlClash supports automatic and manual node strategies; switch between them according to the business scenario:
Automatic Selection Strategy
The default "Auto Select" strategy has the client pick nodes based on latency, making it a reasonable default for routine use.
Fixing a Specific Region
When the egress must stay in a specific region (e.g. Hong Kong, Japan, Singapore):
- Switch to the "Proxy" view
- Locate the target node under its regional group
- Select the node to switch the egress immediately
Latency Testing
To evaluate node quality at scale, use the built-in test:
- In the proxy view, tap "Speed Test" (lightning icon) at the top right
- The client probes latency across nodes
- Adjust the node strategy based on the results
Advanced Settings
Launch at Startup
For devices that should stay online, enable auto-start to reduce manual intervention:
- Enter FlClash "Settings"
- Enable "Launch at Startup"
- Confirm the client loads at system sign-in
System Proxy Mode
When the system proxy is on, the client manages system traffic. "Rule Mode" is recommended so domestic sites connect directly and overseas traffic goes through the proxy, avoiding the side effects of global proxying.
- Enable "System Proxy" in Settings
- Select "Rule Mode" for the proxy type
- Adjust between system proxy and TUN modes as needed
Routing Rules
FlClash is built on the ClashMeta engine; the default rule set already covers common websites and services. Teams with stricter access policies can layer custom rules on top.