Use Windows Search as Flow Launcher’s Search Engine

File search · Published October 30, 2026 · Publisher: flowlauncher.app

At a glance

Windows Search can provide indexed results to Flow Launcher’s Explorer plugin. Its results depend on Windows indexing scope and the selected search type. Check the file in Windows Search first, then use the same file as a test in Flow.

Steps to follow

  1. Find a known local document using Windows Search. If Windows cannot locate it, check Windows indexing settings and whether its folder is included.
  2. Open Flow Settings, select Explorer, and choose Windows Search for the relevant search-engine field.
  3. Use the configured Explorer keyword and search for the same file. Check Flow’s excluded paths if Windows finds it but Flow does not.
  4. Allow a newly added directory to be indexed before evaluating coverage. Keep a second already-indexed file as a control query.

Check the result

A stable indexed filename is returned by both Windows Search and Flow. A new file may become available later than an existing control file.

Limits and common pitfalls

Rebuilding a large Windows index is a broad change, not the first response to one missing result. Confirm scope, excluded paths, and the intended search engine before considering it.

Make the check repeatable

Keep Flow’s configuration and Windows’ indexing configuration separate in your notes. Flow may filter an otherwise available result, while Windows may never have indexed the folder in the first place. Identifying which layer omits the file is more effective than repeatedly reinstalling the launcher.

Questions and answers

Why can filename search work while content search fails?

Content search also depends on the file type, indexing configuration, and availability of searchable local content.

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