A Windows screenshot tool that freezes instantly and stays sharp across monitors

Is the built-in Windows screenshot enough?

Often, yes. A rectangle, a window, the whole screen — the built-in tool does all of that, and records video too. Where it starts running out is usually a specific moment: you want to pin a screenshot on top of everything while you copy from it; you want something taller than the screen in one image; you want the text in a picture as text; or you plug in a second monitor and find the selection box no longer lines up with the cursor.

None of those are advanced features. They are the things that come up once a day. kuaika puts them on the same toolbar: once the selection is set, eight annotation tools, undo and redo, scrolling capture, pin, save-as and text extraction are all right there, with no save-then-reopen-somewhere-else step in between.

The other thing that is easy to underrate is latency. A screenshot tool is used often and briefly, which makes waiting unusually conspicuous — a beat of hesitation after the hotkey gets amplified into "this app is slow".

About 0.2 seconds, and why that number moved

The path from hotkey to a frozen, dimmed screen used to take 2.3 seconds. It now takes about 0.24. The difference is not one optimisation but a rule: nothing stays on the critical path unless the user cannot see a reaction without it.

Capture itself is native GDI rather than a desktop capture API, and the overlay windows are a resident pool that is never shown and hidden — hiding and showing a window on Windows invites the system entrance animation, so the pool parks off-screen and only changes z-order. Everything else — rebuilding the pool, enumerating windows, the large memory copies, encoding the background image — was moved to after the moment you first see something happen.

Two smaller things matter more than they sound. Occlusion detection is disabled for those pooled windows, because Chromium treats a fully off-screen window as invisible and stops compositing it, which costs roughly 150 milliseconds for the first frame when it comes back. And the process asks Windows for an exemption from background power throttling: an app that lives in the tray with no visible window gets classified as background and demoted to efficiency cores, so the entire critical path would otherwise run at low clock exactly when you press the key.

Multiple monitors and mixed DPI

Mixed scaling is where most screenshot tools quietly go wrong, because the relationship between logical and physical pixels stops being one global factor. With the main display at 150% and a second at 125%, a selection dragged across the boundary has to be converted per display, not once for the whole desktop.

kuaika converts through global physical coordinates: a point goes from window CSS pixels to global physical, then the display containing that point is found, then it converts back using that display's scale factor. The practical effect is that the selection box tracks the cursor across the boundary and the exported image is pixel-aligned instead of blurry or offset by a few pixels.

Hover snapping works across the same boundary. Move the cursor over a window and it is outlined; click to take it. In applications with reasonable accessibility support the snap goes further down — to a button, an icon, a single line of text. Applications that draw their own interface (games, some editors) fall back to the whole window rather than guessing.

Full shortcut list

Global shortcuts work whenever the app is running in the tray; you do not have to focus a window first. The in-selection keys only apply while a capture session is open. All five global shortcuts can be re-recorded in Settings, and a combination that is already taken is rejected before it is saved, so recording a conflicting key can never break an existing binding.

Free, open source, and auditable

The client, the native addon and this website are all in one repository. That matters more for a screenshot tool than for most software, because a screenshot tool can see your entire screen — and the only honest way to answer "why should I trust it" is to let you read what it does.

It also works with the network unplugged. Capture, annotation, pinning, scrolling capture and text extraction never wait on a server. There is no account and no telemetry, and the three places the app does go online are listed openly: a version check five seconds after launch, model downloads you explicitly request, and page fetching you explicitly enable.

Frequently asked

Is it really free, and is there a paid tier?

It is free, and there is no paid tier or account system. The source is public, so you can build it yourself if you prefer not to run someone else's binary.

Can I change the shortcuts?

Yes, all five global shortcuts are re-recordable in Settings. Conflicts are checked before saving, so a combination already used by another action or held by another application is rejected rather than silently overwriting a working binding.

Why is my screenshot blurry on a high-DPI display?

Usually because the tool scaled once for the whole desktop instead of per display. kuaika converts coordinates through global physical pixels and back using the scale factor of the display each point lands on, and annotations are stored as vectors and redrawn at physical resolution rather than being scaled up.

Does closing the window quit the application?

No. Closing the console hides it; the app stays in the tray so the hotkeys keep working. Quit from the tray menu when you actually want it gone.

Read next