Discofork
Repository brief

flameshot-org/flameshot

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T15:52:58.811Z
1mo ago

flameshot-org/flameshot

Flameshot is a mature, actively maintained screenshot tool with a large community footprint: 29,606 stars, 1,876 forks, and a push on 2026-03-30. The repo is focused on a desktop app with editing and sharing features, and it ships across Linux, Windows, and macOS with packaging and build support already in place.

GitHub
Loading tags...
Stars29,606
Forks1,876
Default branchmaster
Last pushed2026-03-30T12:01:51Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer this fork if you want a localized, downstream-tuned Flameshot build and can tolerate being behind upstream. Prefer upstream if you want the latest fixes, broadest platform support, and the lowest maintenance burden.

Prefer this fork only if the custom command uploader is the feature you need and you are comfortable living on an old, diverged codebase. For general use, upstream Flameshot is the safer choice because it is active and materially more up to date.

Prefer upstream unless you specifically want this fork’s older snapshot and its small upload/localization tweaks. For most adopters, the staleness and large upstream gap make it a poor default choice.

Prefer this fork only if you specifically need its packaging, compatibility, or downstream-maintenance changes. For most end users, upstream is the better default because this fork is far behind and likely missing important fixes and new behavior.

Choose this fork if you want Windows-specific usability improvements and are comfortable carrying forward upstream gaps yourself. Stick with upstream if you value faster bug-fix uptake, broader platform parity, and lower maintenance burden.

Choose upstream unless you specifically need the fork's small set of convenience and packaging changes. The fork looks more like a customized snapshot than a healthier alternative, and it is materially behind on upstream fixes.

Choose this fork only if the grim-based Wayland adapter or its older capture behavior is the main requirement. For most adopters, upstream is the better choice because it is much more current, better maintained, and has broader recent bug-fix and platform coverage.

Choose this fork only if OCR is the main value and you can tolerate a stale codebase; otherwise upstream is the safer default because it is much more current and actively maintained.

Prefer upstream unless you specifically want an old, lightly modified Flameshot snapshot. This fork is too stale and too far behind for most adopters, but it may suit someone who values a fixed workflow over current fixes and features.

Choose upstream unless you specifically need this older snapshot or are prepared to maintain a large divergence yourself. This fork is best seen as a legacy customization, not a drop-in replacement for current Flameshot.

flameshot-org/flameshot · Discofork