Answers to common questions for both Flow users and plugin developers.
- Check that Flow is running — look for its icon in the system tray
- Another application may have claimed the same hotkey. Try changing it in Settings → Hotkeys → Open Flow Launcher
- If you're in a game, Flow's hotkey detection may be suppressed. Press
Ctrl + F12in the search window to toggle game mode on/off
- Open Settings → Plugins and find the plugin
- Check its Action Keyword — if it has a dedicated keyword (not
*), you must type that keyword first - Make sure the plugin is enabled (toggle is on)
- Try pressing
F5or typingreload plugin datato reload all plugins - Check if the plugin requires setup (an API key, a file path, etc.) in its settings tab
- Some plugins do network calls or heavy file I/O on every query. Identify which ones by temporarily disabling plugins one at a time
- If the Explorer plugin uses Everything as its search engine, check that Everything is running. Look for a warning result in Flow when you search
- Reduce the number of global (
*) keyword plugins — they all run on every query
Flow's app index refreshes automatically, but you can force it by:
- Pressing
F5in the query window, or - Typing
reload plugin data
Type flow user data in Flow to open your UserData folder. Copy the entire folder to back up your settings, themes, installed plugins, and history.
To restore: exit Flow, replace the UserData folder with your backup, then restart Flow.
In Settings → General, Search Window Location chooses whether Flow remembers the last position or places the window on a selected monitor. Remember Last Position restores WindowLeft and WindowTop, which are screen coordinates, not a monitor-specific position; both default to 0. To correct a saved position, exit Flow Launcher and adjust these values in %APPDATA%\FlowLauncher\Settings\Settings.json.
For other location choices, Search Window Position on Monitor controls placement on the selected monitor. Custom Position uses CustomWindowLeft and CustomWindowTop offsets from that monitor's working area, not WindowLeft and WindowTop. For a predictable fallback, choose Monitor with Mouse Cursor and a non-custom alignment such as Center. If Settings is inaccessible, exit Flow Launcher and set SearchWindowScreen to "Cursor" and SearchWindowAlign to "Center" in the settings file. To use the saved coordinates instead, set SearchWindowScreen to "RememberLastLaunchLocation" and adjust WindowLeft and WindowTop.
The search window's width is set by WindowSize. which defaults to 580.
You can also adjust its width or height inside flow with the shortcuts listed in Settings → Hotkeys: Ctrl + [ / Ctrl + ] for width, and Ctrl + Plus / Ctrl + Minus for height.
If the Settings window is offscreen, exit Flow Launcher, open %APPDATA%\FlowLauncher\Settings\Settings.json and edit SettingWindowLeft and SettingWindowTop.
0 for both will put it in the top left, and null will let Flow choose a position for it when it opens.
If the size of the Settings window is an issue you can edit that in %APPDATA%\FlowLauncher\Settings\Settings.json as well, using SettingWindowWidth (default 1000) and SettingWindowHeight (default 700).
This is a SmartScreen warning, not an indication that Flow is harmful. It appears because Flow hasn't accumulated enough download volume for Microsoft to automatically trust it. As long as you downloaded from flowlauncher.com or the official GitHub repo, it is safe. Click "More info" → "Run anyway".
Similarly, antivirus false positives can occur. If you've confirmed you downloaded from an official source, submit a false-positive report to your AV vendor.
- Confirm the plugin folder is in
%APPDATA%\FlowLauncher\Plugins\ - Check that
plugin.jsonexists in the root of the plugin folder and is valid JSON - Check that the
Languagefield inplugin.jsonis one of (case-insensitive):CSharp,FSharp,Python,Python_v2,JavaScript,JavaScript_V2,TypeScript,TypeScript_V2,Executable,Executable_V2 - Restart Flow or type
reload plugin data - Check Flow's logs: type
open log locationin Flow and look for errors related to your plugin name
For JSON-RPC plugins (Python, Node, Executable):
- Check that your process is actually writing to stdout (not stderr). For v1 plugins, any output on stderr makes Flow discard the response
- Test your process manually: v1 plugins receive the request as a command-line argument, e.g.
python main.py '{"method": "query", "parameters": ["test"]}'. Verify the stdout output looks correct - Confirm you're not accidentally mixing debug output into stdout
For .NET plugins:
- Confirm your class implements
IAsyncPlugin(orIPlugin) - Check the Flow logs for assembly load errors
Check Flow's logs (open log location). Common causes:
- Missing runtime (Python not installed, Node not installed)
- A dependency import failing — check that all libraries in
lib/are correctly bundled - A syntax error in your entry point file
- Check that your
resultarray is non-empty and correctly structured - Confirm
Titleis present on each result — it's required - Verify
IcoPathpoints to a file that actually exists relative to your plugin folder, or use a valid data URI
It depends on your plugin type:
- JSON-RPC plugins (Python, Node.js, and similar): see the plugin settings guide. Define settings in
SettingsTemplate.yamland they'll appear in Flow's Settings UI. Read them at runtime from the settings object or settings JSON. - C# (.NET) plugins: implement ISettingProvider to return a custom settings panel from
CreateSettingPanel(). Your plugin can store its options in a serializable settings model that Flow persists and loads at runtime.
Develop directly inside %APPDATA%\FlowLauncher\Plugins\YourPlugin\ and use reload plugin data (or F5) to reload without restarting Flow. For .NET plugins you'll need to restart Flow to pick up recompiled DLLs.
Type open log location in Flow to open the logs folder. Each plugin gets its own log entries. You can also write your own log file from within your plugin code.
Common causes:
- Bundled dependencies are missing in the release archive — confirm your build/release workflow includes everything in
lib/ - The release ZIP doesn't contain
plugin.jsoneither at the archive root or inside a single top-level folder ExecuteFileNameinplugin.jsondoesn't match the actual filename in the release
IAsyncPlugin is preferred. It allows your Query method to be async and receive a CancellationToken, which is important if you make network requests or do any I/O. Flow runs IPlugin.Query inside Task.Run, so blocking work there doesn't freeze the UI, but it ties up a thread and can't be cancelled.