Omarchy Screenshot Shortcuts and Screen Recording

Screenshots and recordings are frequent actions and an easy way to leak notifications, filenames, accounts, or API keys. Understand capture scope and destination before publishing a tutorial or bug report.

Capture scope

Current Omarchy releases generally provide region, window, and screen actions. Exact combinations can change with configuration, so search built-in hotkey help for screenshot instead of treating an old key list as permanent.

• Region: captures only the area needed for an explanation;
• window: keeps application context but may expose titles and paths;
• full screen: useful for layout bugs, but can include every display in a multi-monitor setup.

Privacy checklist

Close notifications, chats, and password managers. Inspect terminal history, browser tabs and bookmarks, usernames, hostnames, Wi-Fi names, and paths. When redacting, flatten the cover or crop the exported image; a removable layer inside an editor is not a safe redaction.

Recording

Confirm enough free space in the output directory and decide whether system audio and microphone are included. Obtain permission before recording meetings, other people, or protected third-party content. Play the complete export once and inspect beginning, end, audio, and private data before removing the raw file.

Shortcut not working

1. Verify the current action in hotkey help;
2. check the screenshot process and output-directory permissions;
3. determine whether failure is limited to one app, one monitor, or the session;
4. pause remote desktop software or a game that may intercept keys;
5. preserve logs and use the general troubleshooting guide.

A useful support screenshot

Show the issue, necessary context, and version without secrets. Include the error as copyable text when possible; a blurred camera photo is much harder to search and diagnose.

Source: official Omarchy Screenshots & Recording manual.