The Short Answer
Quick answer: Flathub wants an app icon that's an SVG, or a square PNG of at least 256 x 256. Screenshots must show just the app window, with its shadow and rounded corners, at 1000 x 700 or smaller (2000 x 1400 on HiDPI screens). No added text, no cropping, no promotional graphics. Set two brand colors, one light and one dark, and give every screenshot a one sentence caption.
Most of these rules aren't needed to publish. They decide whether Flathub can feature your app.
What I Checked
On 16 November 2026, I read Flathub's quality guidelines and its MetaInfo guidelines, the two pages that set the rules for an app's listing.
Then I pulled the 30 most popular apps from Flathub's public API, ranked by installs in the last month. For each one, I read its screenshots, captions and brand colors from its store record.
That came to 120 screenshots. The sample runs from Sober, with about 239,000 installs last month, through Firefox, Discord, VLC and Steam, to Dolphin Emulator, with about 54,000.
Required Rules vs Quality Rules
Flathub has two layers, and it's worth knowing which is which.
The MetaInfo guidelines are the floor. Every graphical app must have at least one screenshot, linked directly to an image file. If the images live in a git repository, the link should point to a tag or a commit, not a branch. Desktop apps must also install an icon.
The quality guidelines sit on top. Flathub says they aren't required for submission, and apps that miss them can still be published. But apps that pass them all can be featured in the weekly banner and as App of the Day, on a rotating basis.
The Icon: SVG or 256 x 256 PNG
The quality guidelines ask for an SVG icon, or a PNG of at least 256 x 256 pixels. Either way, it has to be square.
During the build, Flatpak's tools also make 64 x 64 and 128 x 128 PNG copies from your icon, as long as you installed a PNG of 64 pixels or more, or an SVG. Stores then show those copies in lists.
An SVG is the simplest choice. It scales to every size cleanly, and you only keep one file. If you ship a PNG, make it 256 x 256 or larger, so it stays sharp on large app pages.
What Makes a Good Flathub Icon
Size is only the start. Flathub's quality checks also look at the design.
- 1A reasonable footprint. Don't fill the whole canvas or touch the edges. Don't leave the icon tiny inside lots of empty space either. Flathub offers an icon grid template to check this.
- 2Good contrast. It must read on light and dark backgrounds, so avoid single color glyphs.
- 3The right amount of detail. Recognizable at small sizes, but not a flat one color symbol.
- 4No baked in shadows or glows. Flathub and native stores add their own shadow, so yours would double up.
- 5A current style. The GNOME and KDE icon guidelines show the kind of look Flathub means.
Brand Colors: One Light, One Dark
Flathub asks every app to set two primary brand colors in its MetaInfo file: one for light mode and one for dark. Flathub and native app stores use them on banners and app pages, often as the background behind your icon.
The guidelines are specific about good choices:
- 1Keep contrast with the icon. Don't pick a color too close to your icon's main color.
- 2Make them colorful. Avoid white, very light gray, black and very dark gray.
- 3Make the dark one darker. It should be a darker, more muted take on the light one, not the same color.
Flathub has a banner preview page where you can test pairs before you ship.
How Many Screenshots
Every app should have at least one screenshot in English. Beyond that, Flathub sizes the set to the app.
| App size | Screenshots |
|---|---|
| Medium | 3 to 6 |
| Very large, many screens | 6 to 10 |
| Any app | More than 10 is probably too many |
Put your best screenshot first. It's the first thing people see on your Flathub page, and Flathub says it may also use it elsewhere, such as featured banners.
If you take screenshots in other languages, tag each one with its language, such as xml:lang="de" for German.
Just the App Window
This is where Flathub differs most from Google Play and the App Store. Its screenshots show the real app, and nothing else.
- 1Use your system's window screenshot tool. It captures the app window and its shadow, without the desktop.
- 2No wallpaper or full desktop behind the app.
- 3Don't edit, crop or add text. No captions in the image, no device frames, no promotional graphics.
- 4Take them on Linux. Screenshots from other systems are out, especially when the window controls give it away.
So the marketing style screenshot, with a headline over a phone frame, doesn't belong on Flathub.
Keep the Shadow and Rounded Corners
Flathub wants the native window decoration in every screenshot: the title bar, the window shadow and the rounded corners.
The reason is practical. App stores don't add a shadow after the fact, so a screenshot without one can look glitchy or blend into the page background.
That's why Flathub says not to maximize your app before you take a screenshot. A maximized window loses its shadow and rounded corners.
Apps that always run fullscreen, like most games, are the exception. But then every screenshot must be fullscreen. Don't mix windowed and fullscreen shots in one set.
Window Size: 1000 x 700
Store pages shrink screenshots. To keep text and controls readable at that scale, Flathub asks for a window of 1000 x 700 pixels or smaller, or 2000 x 1400 on a HiDPI screen.
It's easy to miss this one. A 4K monitor with a large window gives you a huge screenshot, and every label in it turns tiny on the store page.
The fix takes a minute. Resize the window before you capture it, so it shows your interface at a size people can read. If your app needs more room than 1000 x 700, it's likely showing too much in one shot.
Captions: One Sentence Each
Every screenshot should have a caption, set in the MetaInfo file rather than drawn on the image. Flathub's rules for captions are short:
- 1One sentence only.
- 2No full stop at the end.
- 3Don't start with a number.
Good captions say what the screenshot shows, in plain words. Two examples from the sample: Sober's "Roblox home page showcasing a wide array of experiences" and Extension Manager's "Manage the extensions you already have installed".
Since you can't put text on the image, the caption is your only line of copy for each screenshot. Make it count.
Default Settings and Real Content
Flathub asks for screenshots taken with the platform's default settings. That covers window controls, the interface font, text size, contrast, dark style and accent color.
A few shots that show off dark style are fine, but they shouldn't be the only ones.
Content matters too. Media players, notes apps, chat apps and similar tools shouldn't show empty screens or ugly sample content. Flathub says picking good content makes all the difference.
And keep screenshots current. When an update changes how the app looks, update the screenshots in the same release.
App Name and Tagline Lengths
Text sits next to your images, and Flathub has rules for it too.
| Field | Ideal | Limit |
|---|---|---|
| App name | 15 characters or less | Under 20 |
| Summary | 10 to 25 characters | 35 |
The name should be just the name. Flathub's bad examples add what the app does, like Firefox Web Browser. Its good examples are plain names, like Krita.
The summary shouldn't repeat the name, start with an article or mention the toolkit or language. Flathub suggests a verb instead, like View images and videos, and no full stop at the end.
What 30 Top Apps Do With Screenshots
The popular apps mostly follow the count rule.
| Screenshots per app | Apps |
|---|---|
| 1 to 2 | 5 |
| 3 to 6 | 22 |
| 7 to 10 | 3 |
| More than 10 | 0 |
Heroic had the most, at 10. OBS Studio, Visual Studio Code and Lutris had one each.
Captions were common too. 24 of the 30 apps caption every screenshot. Four had no captions at all: Firefox, Google Chrome, VLC and ProtonUp-Qt.
On size, 104 of the 120 screenshots fit inside 2000 x 1400 at the largest size Flathub serves. Sober and OBS Studio match 1000 x 700 exactly, and Heroic and ONLYOFFICE match 2000 x 1400.
Brand Colors and Gaps in the Sample
Brand colors are the most skipped rule. Only 11 of the 30 apps set both a light and a dark color. OBS Studio set one color, and the other 18 set none.
The 11 include Sober, Discord, Brave, Bottles, Flatseal, Telegram and Heroic. Some pairs follow the advice closely, like Flatseal's light green #9af0cf with a darker #0c8d5c. Others don't. Telegram pairs a near white #edf0f2 with a dark gray #2d363f, the kind of shades Flathub asks apps to avoid.
Screenshot size was the next gap. The 16 large screenshots came from 6 apps, including Telegram at 2880 x 1800.
For a new app, that's an opening. Setting two colors takes a few lines, and it's one less reason for Flathub to pass you over for a banner.
Where PlayMockUp Fits, and Where It Doesn't
PlayMockUp's mockup editor puts screenshots in device frames with headline text. That works on Google Play and the App Store. On Flathub, it breaks the rules: no frames, no added text, no promo graphics.
For Flathub, take plain window screenshots instead. Our guide to capturing clean app screenshots covers getting a tidy, real view of your app.
If you also publish developer tools, the same split applies elsewhere. Our JetBrains plugin guide shows a store that does allow overlay text on screenshots.
Frequently asked questions
What size should a Flathub app icon be?
An SVG, or a square PNG of at least 256 x 256 pixels. Flatpak's tools also make 64 x 64 and 128 x 128 copies from it during the build.
What size should Flathub screenshots be?
Take them with the app window at 1000 x 700 pixels or smaller, or 2000 x 1400 on a HiDPI screen. That keeps text readable when the store shrinks them.
Can I add text or frames to Flathub screenshots?
No. Flathub's quality guidelines say not to edit, crop, add text or include promotional graphics. Put your words in the screenshot caption in the MetaInfo file instead.
How do I get my app featured on Flathub?
Pass all of Flathub's quality guidelines. Apps that meet every check can be featured in the weekly banner and as App of the Day, on a rotating basis.
Does F-Droid have similar screenshot rules?
No, it works differently. F-Droid reads your images from its own metadata folders, not from a MetaInfo file like Flathub. Our [F-Droid screenshots guide](/blog/f-droid-screenshots-metadata-guide-2026) covers where each image goes and which sizes to use.
Build the mockup in your browser.
Drop a screenshot into a real device frame and export at the exact store size — free, no signup.