Suite / SnipSnap
SnipSnap
Screenshot any region of any monitor on GNOME Wayland, with no permission dialog.
A Qt 6 capture-and-annotate tool whose GNOME Shell extension draws the selection inside the compositor.
Press a key, drag a region, annotate it, then copy or save. SnipSnap is built for GNOME on Wayland, where an application cannot read the screen and every screenshot tool either flashes a portal permission dialog before each capture or quietly stops working across a multi-monitor desktop. It is a downstream fork of Flameshot with the capture path moved into the compositor; the editor, CLI, tray icon and configuration file are Flameshot's.
What it does
The selection lives in the compositor
A GNOME Shell extension draws the dimmed screen and the selection rectangle, so one drag can start on one monitor and end on another, mixed scales and rotations included. The compositor already has the pixels: no portal dialog, no per-monitor boundary.
A full editor, in the same process
Arrows, rectangles, circles, pencil, marker, numbered pointers, text, secure pixelation, invert, undo and redo, zoom and pan — then copy or save. The editor follows your desktop theme and the overlay follows the GNOME accent colour.
Nothing leaves the machine
There is no image-host uploader and no update checker; both are compiled out, and no code path in the shipped build opens a network connection. Captures go to your clipboard or the directory you choose.
Still works where the bridge does not
snipsnap gui, the tray icon and the D-Bus interface take the desktop-portal path on every desktop. On X11, or a Wayland session that is not GNOME, that is what you use: a permission prompt and one monitor at a time, everything else the same.
Optional hand-off to satty
If you prefer satty's annotation window, snipsnap-annotator enable sends every committed capture there instead of the built-in editor.
Install
Ubuntu 26.04 — APT
Add the NorviTech APT repository once and sudo apt install snipsnap; the package carries the GNOME Shell extension and its schema. Then snipsnap-shell-bridge activate as your normal user — it hands over Print only after the bridge is proven active. Commands in the README.
Other distributions — from source
Qt 6.2+ and CMake 3.22 build SnipSnap; the GNOME Shell bridge needs Shell 50 or 51. Build with -DENABLE_GNOME_SHELL_BRIDGE=ON or you get a build without the compositor capture path — the reason this program exists. No Flatpak, Snap or AppImage.
Coming from Flameshot
Installing snipsnap replaces the Flameshot package; the flameshot command stays as a compatibility symlink, and your settings are copied into ~/.config/snipsnap/ without deleting the originals.
Where your data lives
Settings in ~/.config/snipsnap/snipsnap.ini, the last selection rectangle under ~/.cache/snipsnap/, the bridge socket in your runtime directory while the daemon runs, and your screenshots in the directory you save to — nothing else. SnipSnap makes no network connections at all. The README table lists every path.
Documentation
- Screenshots on GNOME Wayland without a permission prompt — what changed under Wayland, what the portal path costs, and why the selection is drawn in the compositor
- The GNOME Shell bridge — the socket protocol and how the extension and daemon meet
- Changelog — one entry per tagged release
- Issues · Discussions · Report a vulnerability
Deployment and operations
Install, configure and verify SnipSnap; plan authentication, backups, upgrades and recovery.