Screenshot / Snip Tool
The Snip Tool is the image half of Omniscio's built-in screen capture: trigger a snip and a region selector appears; when you finish selecting, Omniscio saves the PNG to the Screenshots library, copies it to the clipboard, and fires a shutter sound and toast per your notification settings.
On this page
What it is
The Snip Tool is the image-capture half of Omniscio's built-in screen capture — trigger a snip and a region selector appears; when you finish selecting a region, Omniscio saves the PNG to the Screenshots library, copies it to the clipboard, and fires a shutter sound and toast per your notification settings. On Windows the selector is a fast native Win32/GDI overlay (a bundled helper, snip-overlay.exe); on macOS/Linux it is the OS-native region tool. It's the sibling of the Screen Recorder: both write to the same screen_recordings table (a snip is a row with type='image'), so the store, viewer, and share surfaces are shared infrastructure rather than parallel features — but each has its own type-scoped library (see below).
The Snip Tool lives in its own sidebar entry, "Screenshots" (__screenshots__, Image icon, sky-400, under the Communication group), split out of the former unified "Screen Capture" panel 2026-08-03. It is a distinct integration from Screen Recording (__screen_recordings__, the video half). The two share the screen_recordings table and the store, but each has its own independent on/off toggle (split 2026-08-08): Screenshots is gated by screenshotsEnabled, Screen Recording by screenRecorderEnabled — turning one off hides only that area (and, for Screenshots, unbinds the snip hotkey) and leaves the other running. Both default off for a new install; an existing install that had the former unified "Screen Capture" on is carried forward to screenshotsEnabled = true by a one-time migration, so nobody loses their Screenshots area on upgrade. A snip appears in the Screenshots library as a Snip card; clicking it opens the snip viewer (a zoomable lightbox with rename / share / discard / reveal). The Screenshots library shows only snips (no videos), with its own Recovered section.
Desktop app only. Capture uses the OS native snipping experience and Electron's clipboard/file APIs — not available in a headless CLI or a mobile/web browser.
Where to find it
How to trigger a snip
Three entry points start a snip:
- Global hotkey — default
Ctrl/Cmd+Alt+S, rebindable in the Screenshots settings panel (the settings row at the foot of the Screenshots sidebar,screenshotSnipHotkey). The hotkey registers only whilescreenshotsEnabledis on. On macOS the default registers normally; a shortcut that would take one of the system's own screenshot shortcuts (Cmd+Shift+3, 4, 5 or 6) is not claimed, so the snip never shadows it — that includes a rebind to one of those combinations, which shows as unbound instead of registering. A shortcut must include a real key: a modifier on its own (Shift, Ctrl, Alt) can't be a system-wide trigger, so the recorder refuses one with a hint instead of saving a binding that could never fire — and a value like that already saved by an older build shows as unbound rather than breaking anything. The library shows a hint naming the current binding and refreshes it live on a rebind via thescreenshot:hotkey-status-changedpush. - Tray menu → Take Snip — right-click the Omniscio tray / menu-bar icon and choose Take Snip.
- New snip button — the New snip action at the top of the Screenshots sidebar.
How it behaves
How region selection works (per platform)
Windows — native GDI overlay (v5, resident helper)
Triggering a snip runs a small native Win32/GDI helper (snip-overlay.exe, bundled with Omniscio). It captures every monitor to a frozen backdrop at true physical pixels, then draws an instant topmost selection overlay across your whole desktop (the frozen capture, dimmed, with a live drag rectangle). You drag a rectangle and it crops exactly that region natively. Because the desktop is frozen at the moment you triggered, open menus and hover states are captured just as you saw them.
This is the AutoHotkey-style native approach, and it replaced the earlier Electron selection window (v3) — which was correct but slow (each snip reloaded a window carrying the full app preload, ~3–4s). Drawing the overlay natively opens it in milliseconds, with no Electron window in the path. It is declared Per-Monitor-V2 DPI-aware and works entirely in physical pixels, so the crop is pixel-exact on any mixed-DPI multi-monitor arrangement — including a rotated portrait monitor at a negative origin (the exact case that broke the original v1 overlay; a native window has no Chromium work-area clamp). Esc always cancels system-wide via a low-level keyboard hook, even if the overlay never took keyboard focus.
Resident helper (v5). The helper is launched once at startup (behind the renderer-ready gate, so it never competes with the app's own boot) and kept idle in the background; each press just signals the already-running helper instead of launching a new process. This matters because Windows Defender scans an unsigned executable on every launch (~¼ second measured) — so the earlier launch-per-press design still paid that scan on each snip, while a resident process is scanned once. The full-screen dim is also computed with a fast parallel darken (identical look). The result is a snip that opens instantly, matching a resident AutoHotkey tool. If the resident helper is ever unavailable or crashes, Omniscio automatically falls back to launching it per-press, so snipping never breaks; the helper also exits with the app (it can't linger as an orphan process).
Scope: the overlay spans all monitors — drag anywhere. If the capture itself fails, Omniscio shows a clear error — it never silently saves a full-screen image.
Cancelling — Esc, or a click without a drag — saves nothing and is silent.
macOS
Triggering a snip runs screencapture -i, the native macOS crosshair/selection mode. Drag to select a region, click a window, or use the on-screen controls; press Esc to cancel. Omniscio collects the resulting capture file from the known output location.
Linux
Omniscio tries the best available tool in order: gnome-screenshot -a (area selection), spectacle -r, slurp | grim -g - — the first one found is used.
How the result lands in the library
After a successful capture on any platform:
- The instant a real crop exists (a non-empty PNG), a
screenshot:capture-soundpush fires and the renderer plays the shutter tone — before any of the save work below — so the "captured!" feedback is immediate instead of trailing the whole pipeline. - The PNG is written to
<userData>/screen-recordings/screenshots/<uuid>.png(plus a sidecar<uuid>.sidecar.jsonfor annotations). - A
screen_recordingsrow is inserted withtype='image'. - The PNG is copied to the system clipboard.
- A
screenshot:capturedpush fires with{ recordId, clipboardCopied }, and the post-capture toast appears per your notification settings (the shutter sound already played in step 1). See the native-snip contract I18 for why the sound is decoupled from this receipt.
When Omniscio isn't focused, the toast comes to you. You usually snip while working in another app, so if the Omniscio window isn't focused/visible the post-capture toast — with its Annotate and Share buttons — appears as a small floating window over whatever app you're in, instead of staying hidden inside Omniscio. Clicking Annotate brings Omniscio forward with the snip open in the editor; Share copies a link right there. When Omniscio is focused you get the normal in-app toast. The floating toast never steals focus from your current app, auto-dismisses after a few seconds, and obeys the same capture-notification level (all / errors only / off).
Copy-only mode (screenRecorderSnipCopyOnly) puts the capture on the clipboard only — no library row is written.
Snips share the recordings' storage and its clean-up. Snips live in the same library store as screen recordings, so the Screen Recording Storage panel counts them, and its automatic cleanup and Clean up now permanently delete snips too when they match the age or size rule. In that preview a snip with no name shows as "Untitled capture". See Screen Recorder (part 4) — Storage & retention for the settings, and set cleanup back to Off there if you want snips kept.
Cancelling the selection saves nothing and fires no events.
Settings (Screenshots settings panel)
The settings row at the foot of the Screenshots sidebar opens the Screenshots settings page — its own page since the 2026-08-08 split (Screen Recording has a separate page; neither shows the other's options). Snip-specific controls:
- Snip hotkey (
screenshotSnipHotkey) — rebind the global trigger. DefaultCtrl/Cmd+Alt+S. A modifier on its own is refused as you record it, because a system-wide trigger needs a real key. The library shows a hint if the binding couldn't register.
The same shortcut is reachable from Settings → Features, where the Snip hotkey row shows the current combination and carries an Open Screenshots settings button. Searching Settings for snip hotkey (or asking the CLI GET /settings/open?q=snip%20hotkey) lands on that row. Screenshots itself is turned on or off by installing or uninstalling it from Marketplace → Inbuilt; while it is off the row reads "Install Screenshots from Marketplace → Inbuilt to use the snip hotkey. The shortcut is set in the Screenshots settings page."
- Capture notifications (
screenRecorderSnipCaptureNotifications) —All(default) shows a success toast after every snip;Errors onlysilences the routine toast but still warns on failures;Offsuppresses all snip toasts. Applied live — no restart needed. - Capture sound (
screenRecorderSnipCaptureSound) — plays a short synthesized shutter tone the instant a snip is captured. Default on. It fires on a dedicatedscreenshot:capture-soundpush the moment a real crop exists — before the PNG is saved, the row written, or the clipboard set — so it's immediate rather than trailing the save; the sound means "captured", not "saved" (a rare post-capture save/clipboard failure still plays it, then shows an error). Pressing the hotkey firesscreenshot:snip-armedfirst, which warms the background-suspended audio during your selection so the tone has no wake-up lag. Independent of the notification level (plays even when toasts areErrors only/Off); never plays for a cancelled snip, a genuinely failed capture, or Snip-to-Text (OCR). Deliberately not routed through the throttled notification-sound system. See native-snip contract I18. - Copy-only (
screenRecorderSnipCopyOnly) — when on, snips go to the clipboard only; no library row is saved. Off by default, so the save-and-copy path stays the safe default. - Snip to Text (OCR) (
screenshotOcrEnabled) — off by default. When on, a Snip to Text button appears (Windows only for now) that reads the text out of a captured region via Claude Vision. Each capture is a paid Anthropic API call, tracked in your spend under thescreenshot-ocrsource (model viascreenshotOcrModel, default Sonnet).
Removed settings (no longer present in Settings UI): default snip type, toolbar visibility, loupe, and — as of 2026-10-14 — the Capture engine selector. That last one chose the capture library for the old Electron selection window, and the v4 native overlay always self-captures, so the toggle had no reader at all: the row promised behaviour it could not deliver and simply wrote a settings key nothing read. The stored key (screenRecorderSnipCaptureEngine) has since been removed from the settings schema, and a one-time start-up migration deletes any value an older install still carries — nothing reads or writes it.
Snip to Text (OCR)
Snip to Text turns a captured region into editable text using Claude Vision — the same drag-a-region selection as a normal snip, but on release the crop is sent to Anthropic's vision model and the transcribed text comes back in an editable window with a Copy button. It's off by default; enable it with screenshotOcrEnabled. Windows only for now (it rides the native overlay path); the button is hidden on macOS/Linux.
Flow:
- Click Snip to Text in the Snip view → the same native selection overlay opens; drag the region whose text you want.
- On release the region is cropped and sent to Claude Vision (
screenshot-ocr-service); a result window opens in a loading state. - The transcribed text appears in an editable textarea — fix anything, then Copy it. Empty region ⇒ a "No text found" state; no API key configured ⇒ an actionable "add an Anthropic API key" message; an API failure ⇒ a friendly retry toast (never a raw provider error).
Cost: each Snip to Text is one paid Anthropic vision call, recorded in the spend ledger under the screenshot-ocr source. The plain image snip and the annotation editor are unaffected — OCR is a separate, opt-in mode.
IPC: screenshot:snip-to-text (invoke; desktop-only — blocked over the mobile/web bridge) triggers the OCR snip; screenshot:ocr-started / screenshot:ocr-result (pushes) carry the loading + result states to the renderer.
The snip viewer
Clicking a snip card opens the snip viewer modal — the image-shaped counterpart to the recording Review Window:
- A zoomable lightbox of the full PNG (served over the
screenshot://custom protocol —file://is CSP-blocked). - A Name field to rename the snip inline (writes
source_label). - Link expires after dropdown (1 day / 7 days / 30 days / Never).
- Footer — before sharing: Delete · Annotate · Share (Ctrl+Enter shares). After sharing: Delete · Annotate · Stop sharing · Copy link · Done — Delete stays available after a share, and the share link is shown and auto-copied.
Share, discard, and reveal reuse the recorder's screen-recorder:share / delete-recording / reveal-recording channels — the backend share() branches on type === 'image' to build an image viewer document. The minted link has the same form as a recording's: https://shares.omniscio.com/s/<shareToken>/run. If the snip has annotations, sharing flattens them into the published PNG first (the rebake step), so the link shows what you drew.
Annotating a snip
Get into the editor three ways: Annotate in a snip's library card ⋯ menu, the Annotate button on the post-capture toast (editing is one click away right after you grab a shot), or by clicking a thumbnail in the Snip section's recent-snips gallery.
- Tools: select · text · arrow · box · highlight (translucent marker) · line · ellipse · numbered step badges (auto-numbered, and stable after a delete) · blur (redaction). Each has an inspector for styling — color, thickness, opacity, stroke style.
- Undo / redo —
Ctrl/Cmd+ZandCtrl/Cmd+Shift+Z(or the toolbar buttons). A whole gesture — a drag, a slider sweep, a text edit — is ONE undo step, never one pixel or one keystroke. - Crop — the crop tool draws a rectangle; Apply crop bakes a new cropped snip with the current annotations flattened in, leaving the original + its annotations untouched.
Annotations persist to the sidecar (screenshot:save-annotations); Save as copy bakes them into a new snip, Copy image flattens the current (even unsaved) marks to the clipboard, and publishing a link flattens them into the shared PNG — the original capture stays untouched on disk. One shared renderer (draw-annotations.ts) draws the live editor canvas AND the offscreen flatten, so every tool looks identical wherever the image lands.
Agent / CLI capture route
The POST /capture/screenshot CLI control-server route triggers a capture programmatically from an agent session and feeds the same save pipeline as a user-triggered snip (library row, clipboard copy, push event). See the CLI server docs for authentication and payload details.
Where the data lives
- Files:
<userData>/screen-recordings/screenshots/<uuid>.png+<uuid>.sidecar.json(the annotation overlay document). - DB:
screen_recordingstable,type='image'rows; the video-specific columns are unused for images. Soft-delete via the sameis_deletedflag.
Related
- Screen Recorder — the video sibling in its own Screen Recording sidebar area; same
screen_recordingstable + store and shared share/editor surfaces, but a separate video-only library (the Screenshots and Screen Recording libraries are type-scoped, not shared).
Last verified 2026-10-26