HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
flameshot-org
flameshot
C++2018–2026
flameshot-org / flameshot

flameshot

Powerful yet simple to use screenshot software :desktop_computer: :camera_flash:

Systems & InfrastructureCreative & MediaMobile & Desktop
Explore on GitHubRead Hacker News discussions
27Distinct people
28Mentions
0Explicit recommenders
31.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Powerful yet simple to use screenshot software :desktop_computer: :camera_flash:

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year28 dated mentions

Observed mentions: 2018-01-08 20:28:30 UTC to 2026-01-30 00:44:29 UTC.

0510152018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 14 mentions; 2 submissions, 12 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC211
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC14212
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC211
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC413
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC312

What Hacker News says

28 sources
b1temy·Jan 30, 2026
I used to really like this software, and I still do. But there were a couple of dealbreakers for me. 1) As others mentioned, Wayland support. But it seems that it's gotten a lot better since I last used it. I resisted using Wayland for a long time because of several software breaking, but I've switched over now that most of the things I use now work (or because I've stopped using things that don't work). 2) it was broken for me with fractional scaling. This is the main reason why I switched, I started using fractional scaling on my second monitor and could not properly fix it for the life of me. I haven't tested it recently, but I just checked, and the github issue seems to still be open. https://github.com/flameshot-org/flameshot/issues/564
In Flameshot
alright2565·Dec 28, 2025
The Flameshot screenshot tool uses an interesting variant of pixelation that does protect the text from unredaction: https://github.com/flameshot-org/flameshot/commit/533a1b7d55... > Since pixelation does not protect the contents of the pixelated area (see e.g. https://github.com/bishopfox/unredacter), _pseudo-pixelation_ is used: > Only colors from the fringe of the selected area are used to generate a pixelation-like effect. The interior of the selected area is not used as an input at all and hence can not be recovered. The edges of the pixelated area are used the generate a color palette, and then each pixel is generated by randomly sampling from that pallete's gradient.
In Never Use Pixelation to Hide Sensitive Text (2014)
eddyb·Nov 29, 2025
> So what was the screenshot feature of X11? In case I wasn't clear enough, there was never a screenshot feature. Any X11 client could read any pixel written by any other X11 client. > Have all the best or most popular apps been updated to ensure no disruption? I am not familiar with DE-agnostic "screenshot apps" for Linux, they always seemed more common on other OSes, and I've always used the DE-specific apps (which were the first to support such mechanisms, some of them even using more direct DE-specific private protocols instead of XDG Portals). But I spent a few seconds googling for general screenshot apps, found Flameshot (which makes sense as a cross-platform app), and it turns out that support for the XDG Portal approach was added to it almost 5 years ago: https://github.com/flameshot-org/flameshot/pull/1272 And if you peek around
Read the rest
the diff, you can tell that KDE/GNOME-specific support, on Wayland - using DBus but not the XDG Portals protocol - already existed, in early 2021, in fact... https://github.com/flameshot-org/flameshot/commit/a5df852268... That's the commit that added KDE/GNOME-specific Wayland screenshot support. 8 years ago, in a 3rd-party app! > Why can't the infrastructure include the user simply allowing the app to continue to have access without a specialized infrastructure of app request (that requires updating the app)? I'd forgotten that this happened, but for screensharing from a X11 client, someone already went through the trouble of emulating it (on top of the XDG Portals + PipeWire infrastructure): https://blog.davidedmundson.co.uk/blog/xwaylandvideobridge/ It's only a temporary hack, and it only matters for X11 clients running under XWayland - if an app can run as a native Wayland client, it should have XDG Portals-based implementations of relevant features. > What's with the downplaying "just" again? Have all the best or most popular apps been updated to ensure no disruption? Am I downplaying, or are you describing a vague category of "the best or more popular apps" without giving examples? I feel like it's too easy for some of this stuff to end up in FUD-like arguments without considering the objective reality (of how far we've come in the past few years etc.). Anyway, my subjective take is that X11 took a decade or two too long to die, and most (if not all) gripes users might have with Wayland can be traced back to X11 outliving its UNIX Workstation origins and having never been designed as a Personal Computing graphical environment.
In KDE going all-in on a Wayland future
perching_aix·Aug 23, 2025
> I'm curious whether people who daily drive mac or linux encounter these sorts of system configuration gremlins Friend of mine dailies Arch. He described a few days ago a situation where he stopped being able to take screenshots from one day to the other, eventually finding out the root cause thanks to this fix: https://github.com/flameshot-org/flameshot/pull/4127 Whenever Linux package management and shared dependencies are mentioned, people always seem to be quick to mention how it's good for security that you can upgrade dependencies without the consent and knowledge of the developer of each software you're using. To me, issues like this come to mind instead. Or how I heard multiple times acquainted developers complain that packagers modified their software downstream and broke it in some ways, only for users to come complain to them
Read the rest
instead of to the distribution. There's a recent(?) trend of circumventing distro repos and static linking things though, and I work with Go software pretty often, which I believe static links by default: they're a joy to deploy and use. Just nice, single, self-contained binaries. But it's really not the "one true Linux way" from what I can tell, so I'd imagine it's pretty against the grain, which should tell you a lot about the situation overall. I know I'm not itching to switch, and these are only a sliver of my gripes too.
In Acronis True Image costs performance when not used

Showing the 15 most recent of 28 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.