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:

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 4:35:25 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

14 sources
> For screenshots or screensharing, please use the xdg-desktop-portal API. That should work correctly in X11, Wayland, and within a sandbox. As Blikkentrekker said, it isn't sufficiently flexible for making a screenshotting app, it is only useful for requesting that some other (possibly compositor native) application take a screenshot and return it to you. Flameshot for example, evaluated using xdg-desktop-portal and determined it wasn't suitable (seeh ttps://github.com/flameshot-org/flameshot/issues/446#issuecomment-774372329). It is also notably missing a way to request a screenshot/screenshare of a single window or of a region of the screen rather than the whole screen. > For generating fake inputs, a library is being worked on called libei, that also should work in X11, Wayland, and within a sandbox. Well that's still a work in progr
Read the rest
ess isn't it? My response is about what currently doesn't work, not what will work in the future. > Generally you should not be using random applications to configure monitor outputs, only your compositor's configuration tool is going to be reliable there. 1. For minimal compositors such as sway, creating an advanced monitor configuration tool that handles hotplugging outputs, or with a GUI is out of scope for the project. 2. Being able to script changing monitor configuration, and bind those scripts to hotkeys is pretty important to me. Thankfully that is pretty trivial with sway, but isn't really possible if the only way to manage monitors is the "compositor's configuration tool". And even if it is, such a script isn't portable between compositors. 3. Maybe it is different with wayland, but my experience in X11 was that configuring monitors with xrandr or arandr was much more reliable than any of the DE's designated monitor configuration tools. And even if reliability is no longer an issue, users might prefer a different UI. > Worst case scenario if you need to duplicate parts of the code for all three, I don't think that's a problem. Just put it in a library if it needs to be re-used, the only alternative there is that upstream maintains the relevant bits of that duplicate code, which I'm sure you can see why they would be reluctant to do that. Maybe libraries would help, although afaik, such libraries don't currently exist. And some compositors don't have public APIs for some of this functionality at all, and don't really want third party apps to have access, although it is frequently possible to use internal APIs if you can deal with it changing in backwards incompatible ways without any notice. I don't really understand your argument about "upstream" maintaining duplicate code. If there were standardized APIs, there wouldn't be any need for duplicate code. I did neglect to mention before that all of these are to some extent, somewhat privileged operations, and it does make sense from a security perspective to limit what applications can do these things. However, a big missing piece of wayland is a standard way to grant certain application elevated privileges. From what I can tell most compositors either take the approach of not letting third party apps do a privileged action, or letting all third party apps do a privileged action. Granted it's a difficult problem for a variety of reasons, but the "third party apps aren't allowed to do privileged operations" stance obviously breaks things that worked in X.
In Wayland on Wine: A First Update
I was referring to the gif on the GitHub README here: https://github.com/flameshot-org/flameshot/#preview (sorry if I was vague) In this project's case, it showcases a lot of features as they're actually used, rather than some bullets that say what it _should_ do. In general, I appreciate a gif like this for explaining because it boils down some essential features into one easily digestable clip. It's a preferable medium for me over a long YouTube video or text explaining how something works.
In Flameshot – Superb Screenshot Tool
Looks great! I'm on Windows and I use https://getsharex.com/ which is open source too but only for Windows https://github.com/ShareX/ShareX Will check Flameshot, if is good enough to match my experience with ShareX I will consider make the switch. I prefer use tools that are available on Linux to increase the visibility of Linux! I believe that if we make more popular (by using and recommending) tools that are available in Windows/Mac _and_ Linux, more people will have no issues to switch to Linux (eg: VLC, Inkscape, Gimp, Krita, LibreOffice, Kdenlive). I have Ubuntu as a secondary OS because sadly I'm hostage of Adobe CS :( Will spread the word! Now looking for the Windows installer on the download page https://flameshot.org/download/ to install it on my PC, I see that is not very handy, the download page links to the latest release page
Read the rest
on GitHub who don't have the Windows installer yet https://github.com/flameshot-org/flameshot/releases/tag/v0.8... The previous version have it! https://github.com/flameshot-org/flameshot/releases/tag/v0.8... I think that an UX improvement for most users of the download page will be have the direct link to download the latest installer (.msi) instead of link to the latest release page on GitHub with all the binaries, witch can be confusing (besides that now is not even in the latest release). And put the link of latest release page on GitHub as a secondary link.
In Flameshot – Superb Screenshot Tool
Probably not unless the reply to this issue from 2018 https://github.com/flameshot-org/flameshot/issues/381 is hinting about a rc file instead of recompiling with the button disabled in qmake. Edit: I went on reading the code. The image uploader is hardcoded into https://github.com/flameshot-org/flameshot/blob/97c195452293... and I didn't find anything to conditionally remove it from the UI. But I won't bet a coffee on it after only a 10 minute cursory scan of the code.
In Flameshot – Superb Screenshot Tool

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.