Flow Launcher Shows No Results: A Decision Checklist

Troubleshooting · Published October 30, 2026 · Publisher: flowlauncher.app

At a glance

An empty Flow Launcher result list should be diagnosed by result type. Test a known app, a simple calculation, and a known filename separately. Their success or failure helps distinguish a disabled plugin, an action-keyword mismatch, an index issue, and a broader application problem.

Steps to follow

  1. Confirm the search box accepts text and clear any previous action keyword or query.
  2. Search for a known installed app with Program enabled, then test a basic calculator expression.
  3. Type ? to inspect active keywords and explicitly invoke the plugin that should provide the missing result.
  4. For files, test the same filename in the configured search engine. For network plugins, test the service separately.

Check the result

At least one controlled query identifies a working result source, or every source fails in a way you can describe precisely.

Limits and common pitfalls

No results for one vague abbreviation is not the same as no results for every query. Use exact known names to avoid confusing poor matching with a broken provider.

Make the check repeatable

Build a small decision record: app found or not, calculation returned or not, file found directly in the engine or not. This narrows the problem far more quickly than cycling through unrelated tweaks and makes a support report easier to understand.

Questions and answers

What should I try before resetting settings?

Check enabled plugins, action keywords, and the underlying search engine. Preserve a backup before any broader reset.

Sources and scope

Documentation-based guidance, with source review on October 30, 2026. What was and was not tested.

Related guides

Package information and verification