flameshot  0.8.5
About: Flameshot is a screenshot software (with markup tools).
  Fossies Dox: flameshot-0.8.5.tar.gz  ("unofficial" and yet experimental doxygen-generated source code documentation)  

flameshot Documentation

Some Fossies usage hints in advance:

  1. To see the Doxygen generated documentation please click on one of the items in the steelblue colored "quick index" bar above or use the side panel at the left which displays a hierarchical tree-like index structure and is adjustable in width.
  2. If you want to search for something by keyword rather than browse for it you can use the client side search facility (using Javascript and DHTML) that provides live searching, i.e. the search results are presented and adapted as you type in the Search input field at the top right.
  3. Doxygen doesn't incorporate all member files but just a definable subset (basically the main project source code files that are written in a supported language). So to search and browse all member files you may visit the Fossies
  4. flameshot-0.8.5.tar.gz contents page and use the Fossies standard member browsing features (also with source code highlighting and additionally with optional code folding).


Powerful yet simple to use screenshot software.

GNU/Linux Build Status Windows Build Status Latest Stable Release Total Downloads License Docs
Get it from the Snap Store





  • Customizable appearance.
  • Easy to use.
  • In-app screenshot edition.
  • DBus interface.
  • Upload to Imgur.


Executing the command flameshot without parameters will launch a running instance of the program in background without taking actions. If your desktop environment provides tray area, a tray icon will also appear in the tray for users to perform configuration and management.

Example commands:

  • Capture with GUI:

    flameshot gui
  • Capture with GUI with custom save path:

    flameshot gui -p ~/myStuff/captures
  • Capture with GUI after 2 seconds delay (can be useful to take screenshots of mouse hover tooltips, etc.):

    flameshot gui -d 2000
  • Fullscreen capture with custom save path (no GUI) and delayed:

    flameshot full -p ~/myStuff/captures -d 5000
  • Fullscreen capture with custom save path copying to clipboard:

    flameshot full -c -p ~/myStuff/captures
  • Capture the screen containing the mouse and print the image (bytes) in PNG format:

    flameshot screen -r
  • Capture the screen number 1 and copy it to the clipboard:

    flameshot screen -n 1 -c

In case of doubt choose the first or the second command as shortcut in your favorite desktop environment.

A systray icon will be in your system's panel while Flameshot is running. Do a right click on the tray icon and you'll see some menu items to open the configuration window and the information window. Check out the About window to see all available shortcuts in the graphical capture mode.

CLI configuration

You can use the graphical menu to configure Flameshot, but alternatively you can use your terminal or scripts to do so.

  • Open the configuration menu:

    flameshot config
  • Show the initial help message in the capture mode:

    flameshot config --showhelp true
  • For more information about the available options use the help flag:

    flameshot config -h

Keyboard shortcuts


These shortcuts are available in GUI mode:

Keys Description
, , , Move selection 1px
Shift + , , , Resize selection 1px
Esc Quit capture
Ctrl + C Copy to clipboard
Ctrl + S Save selection as a file
Ctrl + Z Undo the last modification
Spacebar Toggle visibility of sidebar with options of the selected tool, color picker for the drawing color and history menu
Right Click Show the color wheel
Mouse Wheel Change the tool's thickness

Shift + drag a handler of the selection area: mirror redimension in the opposite handler.


If you want use Flameshot as a default screenshot utility, chances are you want to launch it using the Prt Sc key. Flameshot doesn't yet offer a fully-automated option to do so, but you can configure your system to do so.

On KDE Plasma desktop

To make configuration easier, there's a file in the repository that more or less automates this process. This file will assign the following keys to the following actions by default:

Keys Description
Prt Sc Start the Flameshot screenshot tool and take a screenshot
Ctrl + Prt Sc Wait for 3 seconds, then start the Flameshot screenshot tool and take a screenshot
Shift + Prt Sc Take a full-screen (all monitors) screenshot and save it
Ctrl + Shift + Prt Sc Take a full-screen (all monitors) screenshot and copy it to the clipboard

If you don't like the defaults, you can change them manually later.

Steps for using the configuration:

  1. The configuration file configures shortcuts so that Flameshot automatically saves (without opening the save dialog) screenshots to ~/Pictures/Screenshots folder. Make sure you have that folder by running the following command:

    mkdir -p ~/Pictures/Screenshots

    (If you don't like the default location, you can skip this step and configure your preferred directory later.)

  2. Download the configuration file:

    cd ~/Desktop
    wget https://raw.githubusercontent.com/flameshot-org/flameshot/master/docs/shortcuts-config/flameshot-shortcuts-kde
  3. Go to System SettingsShortcutsCustom Shortcuts.

  4. If there's one, you'll need to disable an entry for Spectacle, the default KDE screenshot utility first because its shortcuts might collide with Flameshot's ones; so, just uncheck the Spectacle entry.

  5. Click EditImport..., navigate to the Desktop folder (or wherever you saved the configuration file) and open the configuration file.

  6. Now the Flameshot entry should appear in the list. Click Apply to apply the changes.

  7. If you want to change the defaults, you can expand the entry, select the appropriate action and modify it as you wish; the process is pretty mush self-explanatory.


  • Experimental Gnome Wayland and Plasma Wayland support.

  • If you are using Gnome you need to install the Gnome Shell Extension Appindicator extension in order to see the systemtray icon.

  • Press Enter or Ctrl + C when you are in a capture mode and you don't have an active selection and the whole desktop will be copied to your clipboard! Pressing Ctrl + S will save your capture in a file! Check the Shortcuts for more information.

  • Flameshot works best with a desktop environment that includes dbus. See this article for tips on using Flameshot in a minimal window manager (dwm, i3, xmonad, etc)

  • In order to speed up the first launch of Flameshot (DBus init of the app can be slow), consider starting the application automatically on boot.

    • Quick tip: If you don't have Flameshot to autostart at boot and you want to set keyboard shortcut, use the following as the command for the keybinding:
    ( flameshot &; ) && ( sleep 0.5s && flameshot gui )


Flameshot can be installed on Linux and Microsoft Windows currently.

There are no macOS port of flameshot now. Please participate in the development of flameshot and help us make a macOS port.

Prebuilt packages

Some prebuilt packages are provided on the release page of the GitHub project repository. Click here to visit the release page..

Packages from Repository

There are packages available in the repository of some Linux distributions:

Expand this section to see what distros are using an up to date version of flameshot Packaging status

Tray icon

Note that for the Flameshot icon to appear in your tray area, you should have a systray software installed. This is especially true for users who use minimal window managers such as dwm. In some Desktop Environment installations (e.g Gnome), the systray might be missing and you can install an application or plugin (e.g Gnome shell extension) to add the systray to your setup. It has been reported) that icon of some softwares, including Flameshot, does not show in gnome-shell-extension-appindicator.

Alternatively, in case you don't want to have a systray, you can always call Flameshot from the terminal. See Usage section.


To build the application in your system, you'll need to install the dependencies needed for it and package names might be different for each distribution, see Dependencies below for more information. You can also install most of the Qt dependencies via their installer. If you were developing Qt apps before, you probably already have them.

This project uses CMake build system, so you need to install it in order to build the project (on most Linux distributions it is available in the standard repositories as a package called cmake). If your distribution provides too old version of CMake (e.g. Ubuntu 18.04) you can download it on the official website.

Also you can open and build/debug the project in a C++ IDE. For example, in Qt Creator you should be able to simply open CMakeLists.txt via Open File or Project in the menu after installing CMake into your system. More information about CMake projects in Qt Creator.



  • Qt >= 5.9
    • Development tools
  • GCC >= 7.4
  • CMake >= 3.13


  • Qt
    • SVG


  • Git
  • OpenSSL
  • CA Certificates


# Compile-time
apt install g++ cmake build-essential qt5-default qttools5-dev-tools libqt5svg5-dev qttools5-dev

# Run-time
apt install libqt5dbus5 libqt5network5 libqt5core5a libqt5widgets5 libqt5gui5 libqt5svg5

# Optional
apt install git openssl ca-certificates


# Compile-time
dnf install gcc-c++ cmake qt5-devel qt5-qtbase-devel qt5-linguist

# Run-time
dnf install qt5-qtbase qt5-qtsvg-devel

# Optional
dnf install git openssl ca-certificates


# Compile-time
pacman -S cmake base-devel git qt5-base qt5-tools

# Run-time
pacman -S qt5-svg

# Optional
pacman -S openssl ca-certificates


After installing all the dependencies, finally run the following commands in the sources root directory:

mkdir build
cd build
cmake ../


Simply use make install with privileges. Note: If you install from source, there is no uninstaller, you will need to manually remove the files. Consider using CMAKE_INSTALL_PREFIX to install to a custom location for easy removal.


Info: If I take code from your project and that implies a relicense to GPLv3, you can reuse my changes with the original previous license of your project applied.

Privacy Policy

This program will not transfer any information to other networked systems unless specifically requested by the user or the person installing or operating it.

Code Signing Policy

Free code signing provided by SignPath.io, certificate by SignPath Foundation.

Code signing is currently a manual process so not every patch release will be signed.


If you want to contribute check the CONTRIBUTING.md


Thanks to those who have shown interest in the early development process:

Thanks to sponsors:

  • JetBrains
  • SignPath