Espanso Not Working? Common Errors & Fixes

Espanso is running but triggers do nothing. First restart it, then test with force_mode to find out whether the keys or clipboard backend works.

Wayland support is experimental. Install the Wayland build, give the binary CAP_DAC_OVERRIDE, set your keyboard layout, and start it.

On macOS, Espanso needs Accessibility permission. If it is set but nothing expands, remove and re-add the entry and restart Espanso.

When Secure Input is stuck macOS blocks Espanso everywhere. Restart the password manager and browser, or log out and in.

Replacements over 100 characters are sent via the clipboard. Raise clipboard_threshold or set the backend explicitly.

Terminals paste differently. Use an app-specific config with a different backend or paste_shortcut for the terminal.

Filters are case-sensitive regexes and only one config applies. Use #detect# to get the right values, and note Wayland does not support them.

Most config errors are indentation or unquoted special characters. Quote strings with \n, \t or leading special characters and check the log.

If Espanso times out or fails to start, check the service registration and input permissions, then try unmanaged mode.

If expansion dies after resume, restart the service. Keep auto_restart on and restart after plugging in a keyboard.

On Windows 11 test force_mode and key delays, and check Espanso is running with the same privileges as the target app.

Editors and Electron apps interfere with injection. Use an app config switching backend to clipboard and adjust delays.