For the people who document, support and teach

Capture what you saw. Keep it yours.

Quikap freezes the screen before it shows a thing, so the capture is what you saw. QuikapStudio edits on top of it and never changes the original. Both write to your own disk and nowhere else.

An illustration of the QuikapStudio window. On the left, the library lists recent captures. On the right, a capture is open on the canvas with an arrow, a callout and a redacted region as layers, and a toolbar under it shows the zoom and the size of the source.

What changes when capture is local-first

Nothing leaves your computer. A capture is a folder of files on your disk. There is no upload, no link that anybody can open, no account to lose. You decide where a capture goes, if it goes anywhere.

The capture is what you saw. The screen is frozen first, the overlay comes second. An open menu stays open; a tooltip stays put; the overlay itself is never in the picture.

Editing is reversible, except where you say it is not. Every arrow, blur and callout is a layer on the original. Secure redaction is the one thing that is final: it removes the pixels from the export, on purpose.

What it will not do behind your back

  • It will not send a capture, a frame or a line of text anywhere.
  • It will not record keystrokes unless you switch that on for a recording.
  • It will not install an update that the release key has not signed, wherever the update came from.
  • It will not count, track or profile you. There is no telemetry in either program.

Where it is today

Both programs are being built; nothing is released yet. The status page says what exists, and the features page lists every planned feature with its state. When a release is published, it appears on the downloads page.

Quikap and QuikapStudio are being built

Nothing is released yet, and this site will say so until a release is published. Licenses are issued to teams we can support well while the products take shape; one license covers both programs.