Cannot find Logs? Check whether capture is enabled
When a subscription update or connection fails, logs can record when the error occurred and what the app reported. However, Log level and Logcat are different settings in FlClash. Seeing or changing the log level does not mean the Logs entry is visible.
This guide covers the maintained FlClash v0.8.99 stable release on Windows 11, for amd64 / arm64, using the English interface. The steps were checked against fixed-version source code, interface translations, and upstream tests; they were not verified by clicking through the Windows application. Do not apply log paths or procedures from Clash Verge Rev, Clash for Windows, or Android to this guide.
FlClash must already open normally and let you access settings. If it crashes before startup completes, this interface procedure does not apply, nor does it establish where crash logs are stored on disk. No reinstall, patch download, or YAML edit is needed. Leave the current profile, proxy mode, and log level unchanged, and first check only the capture switch.
Enable Logcat, then return to the Logs page
- Open Tools in the main window. Find the Settings section and click General. Settings is a section heading here, not a separate page that you need to open first.
- In General, find Logs and diagnostics and record the original state of Logcat. Leave it on if it is already enabled; otherwise, turn it on. This version initially defaults to off, but an existing configuration may have changed that state.
- The switch takes effect immediately. There is no additional save button, and it does not open the Logs page automatically. Return to the main interface and open Logs in the main navigation. Do not keep looking for log entries inside General settings.
- Note the current time, repeat the failing action once, and return to Logs to inspect entries around that time. For example, retry just one failed subscription update. You do not need to change subscriptions, switch nodes, or enable TUN together just to produce logs.
If no new entries appear, first check that capture remains enabled, the relevant action actually occurred, and the core is running normally. Also check whether a search filter is hiding entries. Sparse output can reflect the current log level: do not assume it is info. This version’s initial configuration uses error, although an existing configuration can differ. This guide does not require switching to debug first; adjust the level separately if the maintainer requests more detail for your particular issue.
What do capture, log level, and filtering change?
| Setting or action | What it affects | What it does not establish |
|---|---|---|
| Logcat | Shows the Logs entry and starts or stops the core-log subscription | Turning it off does not delete existing entries or guarantee that all internal application logging stops |
| Log level | Controls which log levels the core outputs | Less output or a different level does not mean the underlying issue is resolved |
| Search and level-tag filtering on Logs | Help find relevant entries in the current list; clicking a level tag can add a filter | The filtered visible list is not the scope of the exported file |
The page can contain both core events and application logs marked [APP]. Start with the time, level, and actual error, then describe what you were doing. A single error entry does not establish that a node has failed. This guide does not explain every error or treat the Logs page as a complete browsing history.
The page displays a bounded in-memory buffer, so older entries can be pushed out. Restarting the app or reloading the configuration can also leave these entries unavailable. Save soon after reproducing the issue; do not restart first and then expect to find the same error. Pausing automatic following while scrolling up changes the list’s scrolling and display, not whether logs are collected.
Save the log and inspect the actual file before sharing
To keep a record, use the export button with the Export logs tooltip on the Logs page. In the Windows save dialog, choose a local folder you can write to, check the filename, and save. The default filename follows FlClash_YYYY-MM-DD.log; this is a format example, with the actual date taken from the system time when exporting. When saving again on the same day, use a different filename to avoid overwriting a record you still need.
After a successful export, the app displays Export successful. Open the saved file in a text editor and confirm that it contains the time window and error from your reproduction. The filename alone is not evidence that the contents are correct. Cancelling the save dialog does not count as a successful save, and an error does not mean the destination file is complete.
Filtering is not redaction. Export reads the current log buffer, not just the few entries visible after filtering. The file may contain visited domains, IP addresses, node names, subscription URLs, a Token, or local paths. Do not post an unchecked whole file, screenshot, or complete subscription link in a public Issue, group chat, or online analysis service.
Work on a local copy and keep only the entries around the error that are needed to explain it. Redact credentials and addresses you do not want to disclose, while retaining timestamps, the error type, and essential context. Then copy that redacted excerpt from the text editor and include the FlClash version, Windows version, and reproduction steps. This means ordinary copying in a text editor, not a separate “copy all” button in FlClash.
Restore the original capture state when finished
Return to Tools → Settings → General → Logs and diagnostics and restore Logcat to its original state. Turn it off if it was originally off; leave it on if it was already enabled and you still need to observe logs. Turning it off hides the Logs entry and stops the core-log subscription. It is not a clear button and does not delete any .log files already saved to disk.
Internal application logs marked [APP] may still be written to the buffer. Do not interpret this switch as a way to prohibit every kind of logging. There is no need to delete profiles, clear app data, or reset all settings for this task. Turning off capture or deleting a local file cannot retract credentials already made public. If you accidentally shared a subscription Token, revoke or reset it with the relevant provider.
The useful outcome is a checked, redacted record tied to a specific action, not the largest possible log archive. If the file does not contain the issue, check capture, timing, and the actual log level again, then perform another limited reproduction. Do not invent missing log entries or guess what caused an error.
Official sources and version scope
- FlClash v0.8.99 release
- Pinned source: Tools and General entry
- Pinned source: Logcat switch
- Upstream test: enabling capture keeps the current page
- Pinned source: log list, filtering and export action
- Pinned source: log buffer and export scope
- Pinned source: saving files and cancellation
- Pinned source: starting and stopping core log capture
- Pinned source: separate application log writes
Version numbers, filenames, and interface labels can change. Confirm them in the linked project documentation before making changes.