Skip to main content
Snap is an early build. This page is the accurate list, so nothing on the other pages has to be read hopefully.

​
Status

​
The annotation editor

The largest gap. Opening a capture shows it, fitted or at natural size, and that is all — the tool rail, numbered steps, text callouts, spotlight and crop handles do not exist. The pieces already in place: the .snap.json sidecar format, the undo and annotation shortcuts, the single-letter tool keys, and the rule that annotations are only ever burned into a copy.

​
Screen recording

Not built, and the bar for building it is deliberately high. Compose shipped a screen recorder built on Qt’s own capture and recording classes, and it was removed: it produced files that would not play back, and had no trimming or stitching. Repeating that is not worth doing. When recording lands it should drive FFmpeg as a separate process rather than using Qt’s recorder. Note that the Recordings filter and the recording shortcut already exist in the interface — they are there so the library does not have to change shape when recording arrives.

​
Scrolling capture

Grab, scroll the target, grab again, and stitch the results by matching the overlap. Not built. The mode is visible and disabled rather than hidden, so it is clear it is coming rather than missing.

​
Send to Compose

The button exists, the shortcut exists (Ctrl Return), and the settings exist — where Compose is installed, whether to launch it if closed, where a sent capture is placed, and whether annotations are burned in first. Pressing it tells you the handoff is not built yet rather than appearing to work. This is also the one thing that will require a Mauvely account.

​
Cloud backup

Planned as part of Mauvely Cloud, and account-gated on a paid plan — it carries real recurring storage cost, which is a legible thing to charge for in a way that charging for capture would not be. Three commitments already fixed:
  • The local folder stays the source of truth. Backup mirrors your library; it is never an import step and never a proprietary container.
  • The .snap.json sidecar travels with its image, because separating them orphans the annotations.
  • Signing out never deletes anything local. Cancelling a subscription leaves every file exactly where it already was.
None of it is implemented.

​
Availability

There is no packaging or release pipeline yet, so there is no installer for any platform. When Snap ships it will be Windows first, as a per-user installer that updates without administrator rights, matching Compose. Linux builds exist and are maintained for development, but will not be distributed — see why.