Flow Launcher Plugin Store Not Loading or Empty

Plugins and comparisons · Published October 30, 2026 · Publisher: flowlauncher.app

At a glance

An empty or unavailable Plugin Store can be a network or catalog-fetch problem even when local Flow searches work. Check the app version, network policy, and the exact error. Do not disable security software or substitute an unknown plugin repository to bypass the failure.

Steps to follow

Test a local application search to confirm Flow itself responds. Then reopen the Plugin Store and note its error message.
Check whether the project’s repository and plugin catalog open in a normal browser on the same connection.
On managed networks, inspect proxy or firewall restrictions with the administrator rather than changing them blindly.
Check the Flow version and release notes, retry the store after resolving connectivity, and install only from a source you have verified.

Check the result

The store lists plugin metadata and a small known plugin can be inspected. Local app-search behavior remains unchanged.

Limits and common pitfalls

An empty search filter, unavailable catalog endpoint, and blocked network request can look similar. Clear filters before assuming the entire store is down.

Make the check repeatable

Save the timestamp and exact error text for troubleshooting. A browser reaching a repository is a helpful control but does not prove every request made by the app is allowed. Compare the specific catalog or release request reported by the application rather than broadly whitelisting unrelated domains.

Questions and answers

Can I still use Flow without the Plugin Store?

Local features and already-installed plugins may remain usable. Installing or updating extensions generally requires access to their sources.

Sources and scope

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

Related guides

Plugins and comparisons