• Features
• Usage
  • CLI configuration
  • Config file
• Keyboard Shortcuts
  • Local
  • Global
    • On KDE Plasma desktop
    • On Ubuntu
    • On XFCE 4
• Considerations
• Installation
  • Prebuilt Packages
  • Packages from Repository
  • MacOS
  • Windows
• Compilation
  • Dependencies
    • Compile-time
    • Run-time
    • Optional
    • Debian
    • Fedora
    • Arch
  • Build
  • Install
• License
• Privacy Policy
• Code Signing Policy
• Contribute
• Acknowledgment

• Customizable appearance.
• Easy to use.
• In-app screenshot editing.
• 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.

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

You can also edit some of the settings (like overriding the default colors) in the configuration file.
Linux path : ~/.config/flameshot/flameshot.ini.
Windows path : C:\Users\{YOURNAME}\AppData\Roaming\flameshot\flameshot.ini.

When copying over the config file from Linux to Windows or vice versa, make sure to correct the savePath variable,
so that the screenshots save in the right directory on your desired file system.

These shortcuts are available in GUI mode:

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

Flameshot uses Print screen (Windows) and cmd-shift-x (macOS) as default global hotkeys.

On Linux, Flameshot doesn't yet support Pr Scr out of the box, but with a bit of configuration you can set this up:

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:

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.khotkeys

3. Make sure you have the khotkeys installed using your package manager to enable custom shortcuts in KDE Plasma.

4. Go to System Settings → Shortcuts → Custom Shortcuts.

5. 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.

6. Click Edit → Import..., navigate to the Desktop folder (or wherever you saved the configuration file) and open the configuration file.

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

8. 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 self-explanatory.

9. If you installed Flameshot as a Flatpak, you will need to create a symlink to the command:

   ln -s /var/lib/flatpak/exports/bin/org.flameshot.Flameshot ~/.local/bin/flameshot

To use Flameshot instead of the default screenshot application in Ubuntu we need to remove the binding on Prt Sc key, and then create a new binding for /usr/bin/flameshot gui (adaptated from Pavel's answer on AskUbuntu).

1. Remove the binding on Prt Sc using the following command.

gsettings set org.gnome.settings-daemon.plugins.media-keys screenshot '[]'

2. Ubuntu 18.04: Go to Settings > Device > Keyboard and press the '+' button at the bottom. Ubuntu 20.04: Go to Settings > Keyboard and press the '+' button at the bottom.

3. Name the command as you like it, e.g. flameshot. And in the command insert /usr/bin/flameshot gui.

4. Then click "Set Shortcut.." and press Prt Sc. This will show as "print".

Now every time you press Prt Sc, it will start the Flameshot GUI instead of the default application.

1. Go to Keyboard settings

2. Switch to the tab Application Shortcuts

3. Find the entry

   Command Shortcut xfce4-screenshooter -fd 1 Print 

4. Replace xfce4-screenshooter -fd 1 with flameshot gui

Now every time you press Prt Sc it will start Flameshot GUI instead of the default application.

• Experimental Gnome Wayland and Plasma Wayland support.

• If you are using Gnome you need to install the AppIndicator and KStatusNotifierItem Support extension in order to see the system tray 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 to a file. Check the Shortcuts for more information.

• Flameshot works best with a desktop environment that includes D-Bus. 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 (D-Bus 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, Microsoft Windows, and macOS.

Some prebuilt packages are provided on the release page of the GitHub project repository.

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

• Arch: pacman -S flameshot
  • Snapshot also available via AUR: flameshot-git.
• Debian 10+: apt install flameshot
  • Package for Debian 9 ("Stretch") also available via stretch-backports.
• Ubuntu 18.04+: apt install flameshot
• openSUSE: zypper install flameshot
• Void Linux: xbps-install flameshot
• Solus: eopkg it flameshot
• Fedora: dnf install flameshot
• NixOS: nix-env -iA nixos.flameshot
• Snap/Flatpak/AppImage
• Docker
• Windows

• MacPorts: sudo port selfupdate && sudo port install flameshot
• Homebrew: brew install --cask flameshot

Note that because of macOS security features, you may not be able to open flameshot when installed using brew. If you see the message “flameshot” cannot be opened because the developer cannot be verified. you will need to follow the steps below:

1. Go to system preferences -> security & privacy;
2. Click on the General tab;
3. Click on the lock and authenticate;
4. In the section Allow apps downloaded from select the option App Store and identified developers;
5. Click on the button Open Anyway close to the message "flameshot" was blocked from use because it is not from an identified developer;
6. Click the Open button in the popup.

After following all those steps above, flameshot will open without problems in your Mac.

• Chocolatey

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

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-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

First of all you need to install brew and than install dependencies

brew install qt5 brew install cmake

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

mkdir build cd build cmake ../ make

NOTE: for macOS you should replace command

cmake ../

to

cmake ../ -DQt5_DIR=$(brew --prefix qt5)/lib/cmake/Qt5

When make command completed you can launch flameshot from project_folder/build/src folder

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.

https://flameshot.org/docs/guide/faq/

• The main code is licensed under GPLv3
• The logo of Flameshot is licensed under Free Art License v1.3
• The button icons are licensed under Apache License 2.0. See: https://github.com/google/material-design-icons
• The code at capture/capturewidget.cpp is based on https://github.com/ckaiser/Lightscreen/blob/master/dialogs/areadialog.cpp (GPLv2)
• The code at capture/capturewidget.h is based on https://github.com/ckaiser/Lightscreen/blob/master/dialogs/areadialog.h (GPLv2)
• I copied a few lines of code from KSnapshot regiongrabber.cpp revision 796531 (LGPL)
• Qt-Color-Widgets taken and modified from https://github.com/mbasaglia/Qt-Color-Widgets (see their license and exceptions in the project) (LGPL/GPL)

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.

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

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:

• lupoDharkael
• Cosmo
• XerTheSquirrel
• The members of Sugus GNU/Linux
• ismatori

Thanks to sponsors:

• Namecheap
• JetBrains
• SignPath
• AnonAddy