FZ_graphics: Flipper Zero animations, passport art and guides

An art library, with the device in the title

The repository is described as Flipper Zero custom animations, profile and passport pictures by Kuronons, and the folder names say the same thing. There is an Animations directory, a Passport background directory, a Passport profile pictures directory, a directory of FAPs and firmware graphic assets, and a directory of BadUSB visual payloads, alongside the readme and the licence file. The primary language is listed as unknown, which is the correct classification for a repository of images rather than code, and the topics are animation, art, customisation, graphics and pixel art. What a Flipper Zero owner is looking for here is obvious from the device's design. It is a small handheld with a screen, and the screen is a canvas that people personalise, so the animation format, the theme files and the passport pictures are all things a user wants to replace with their own. The author's own framing in the readme is that you can find in the well named folders what has been made so far, and the community position is stated too, that the author is present on most Flipper related Discord servers and opened a thread dedicated to Flipper pixel art on the Momentum server.

Four kinds of asset, and why the folders are named that way

The naming is not decoration, it is part of how the device's firmware expects to find things. The Animations folder holds the custom animations that play on the device, and the author has written a guide on the Meta Settings, which is where the firmware reads the settings that control the animated background, plus a document on the most common mistakes made when making an animation, which the readme marks as strongly recommended to begin with. The two passport directories are the artwork for the built-in passport feature, with a separate background and a separate profile picture, and the author links two German video tutorials on the passport and identity picture to show how the replacement works. The FAPs and firmware graphic assets directory collects the assets used by third party applications and by custom firmware, and the readme points at the Momentum firmware documentation on asset packs as the reference for how those are installed. The BadUSB visual payloads directory completes the set with images used by payloads that display something on a connected computer. The tutorial index in the readme is the map of all of this, and it separates text guides from videos with a marker for the ones the author considers a strong starting point.

Firmware is the variable, and the readme says so up front

The first warning in the links of interest section is the one to internalise, because it changes what you can expect from any file you copy. Animations and other graphical resources may be handled differently depending on the firmware, and you can encounter discrepancies on folder architecture or even on file formats. Some of the video tutorials may be outdated even for a specific firmware, and the readme tells you to check the most recent documentation available for the firmware you are currently using. That is a real constraint on a repository of assets, and it is the honest form of the problem. These files are not a stable interface, they are shaped by whatever the current firmware expects, and the moment a new firmware changes the layout or the format, an asset set that worked yesterday can silently stop appearing on the device. The readme also links the official Flipper Zero documentation and the firmware developer documentation as the primary references, which is the right order of authority. The practical consequence for a user is that this repository is a source of artwork and a source of pointers, and the documentation for your own firmware is the source of truth for how to install it.

The guides, and the one worth reading first

The readme curates a substantial amount of third party content, and the structure tells you what the author considers authoritative. There is the official Flipper Zero documentation and the firmware developer documentation, both marked as text resources. There are Wr3nch's beginner guides, a PDF on downloading files from GitHub and copying them to the Flipper, and a second PDF on renaming the device and compiling firmware from source. The author's own guides are marked with a star as strongly recommended to begin with, and there are two of them, the in-depth Meta Settings guide hosted on the Flipper community wiki, and the document on the most common mistakes done when making an animation, which is a file in the repository itself rather than a link. Then there is a series of video tutorials from several creators, Talking Sasquach with the animation process guide and what the author calls the ultimate guide video, the LAB401 academy video on custom animations, a video on custom font packs for the latest XFW release, Pen Ace's animation starter guide, two German tutorials from Wihrus on animations and on the passport picture, Derek Jamison with two videos on customising the main menu icons and the look and feel of the main menu, and Rithim's guide on editing background animations. The instantiator links cover building an app for the Flipper in two parts. The author's own guide on common mistakes being the first document to read is a good piece of advice from someone who has made many of them.

Two tools in the list, and the honesty about the rest

The tools and apps section carries its own warning, and the honesty is what makes the list useful. The author says he has his own creating process and does not use most of the tools that follow, and that he marked the ones he tested. He also says they are all open source and that it is up to you to check their code and test their behaviour. Two entries are described in enough detail to be worth reading. The Flipper Animation Switcher is a Flipper Application Package by SLK, and it creates, manages and switches animation playlists directly on the device, using template manifest.txt files that control which background animations play, with support for up to 128 animations per playlist. The Theme Manager, by Artyom Shivtsov, manages the dolphin animation themes directly on the device, supports three theme formats, Pack, Anim Pack and Single Animation, auto-backs up, and shows theme information with an animation preview of the first frame. The difference in approach between the two is instructive, because one manages playlists of animations and the other manages the themes themselves, which are different layers of the same customisation stack.

CC0, a coffee link, and who actually does the work

The licence is the most permissive thing in the repository, CC0 1.0, which means the artwork is effectively in the public domain and can be used, modified and redistributed without attribution, although the author asks to be credited and offers a Buy me a coffee link and a Ko-fi link. The maintenance picture is the usual shape for a community asset repository. The last push was on 2026-08-03, the repository publishes no GitHub releases, and the content is organised by category rather than by version, which means the version marker that matters is the firmware you are running. The readme also carries a growing list of links to other people's work, with an offer to add your link on request, either by asking or by opening a pull request, which is a light and effective way to keep a resource current in a community that moves fast. The threads and servers it points to are where the actual exchange happens, since a thread dedicated to pixel art on the Momentum server is a better place to ask how an animation behaves in a given firmware than a readme is.

Editorial conclusion

Adopt FZ_graphics if you own a Flipper Zero and want artwork you can use without drawing it, and if you are willing to match the files to the firmware you run, because the readme states plainly that the same assets can be handled differently depending on the firmware and that the folder structure can differ. It does not fit a project that needs a maintained animation pipeline of its own, since this is a curated art repository rather than a toolchain, and it does not fit anybody who needs the assets to be stable across firmware versions. Before you copy anything onto a device, read the most recent documentation for the firmware you have, as the readme advises, and check the guide on the common mistakes in making an animation, which is the one most likely to save you an evening.

Frequently asked questions

Official sources

1. Issues
2. Kuronons/FZ_graphics on GitHub
3. License: CC0-1.0
4. README