UberGuidoZ/Flipper: a dumping ground for Flipper Zero firmware and files

A repository described as a playground and a dump

The repository description is unusually honest about what this is: a playground and dump of stuff the author made, modified, researched or found for the Flipper Zero. The README repeats the framing, describing a collection of things made, modified, researched, or found for the device.

That sentence tells you more about the repository than any feature list could. There is no single application here, no coherent design, and no version to pin. What there is, is curation: a large number of files and small projects that would otherwise be scattered across personal accounts, Discord attachments and forum posts, gathered under one name and divided by topic.

The project metadata records the language as C and the license as GPL-3.0, with a `LICENSE` file at the repository root to match. The default branch is `main`, and the last push was on 2026-07-28. There are no published releases, which is the normal shape for a collection like this: nothing here is versioned as a distributable artifact because there is no single artifact to distribute.

What the top level directories tell you

The directory listing is the index, and it is more informative than the README. Four directories map directly onto the Flipper Zero's hardware capabilities: `Sub-GHz/` for sub-gigahertz radio, `NFC/` for near-field cards, `RFID/` and `Infrared/` for the other radio and emitter paths. `BadUSB/` is the one people usually arrive for, holding keyboard-injection payloads that make a plugged-in computer type whatever the file says.

The rest is tooling and payload collections with less obvious names. `Applications/` holds complete Flipper apps. `Graphics/` and `Dolphin_Level/` are assets rather than code. `Wav_Player/` and `Music_Player/` are playback utilities, and `Music_Player/` plus `subplaylist/` together suggest handling for longer audio content, which is a different problem from playing a single WAV. `Firmware_Options/` points at custom firmware builds or modifications, which on this hardware is a different category of change from adding an application.

Two entries read as general utilities rather than Flipper content at all. `Clean_up_files.bat` is a Windows batch script, which tells you the collection assumes a mix of host operating systems, and `flipper_toolbox` has no trailing slash in the listing, so it is a file rather than a directory. The `.gitmodules` file is the more structurally important entry: it means at least one of these folders is a reference to another repository rather than a stored copy, so the contents depend on what those upstream projects currently contain.

Why some folders are hardware research instead of code

Several directories are not software in any ordinary sense, and knowing which is which saves you time.

`FlipperZero_Dimensions/` and `Hardware_Troubleshooting/` are the clearest examples. A dimensions file is data about the physical device, and a troubleshooting folder is notes from people who have opened one up and broken something. `GPIO/` is in the same territory: it concerns the expansion pins, which is where the Flipper Zero's community hardware work happens, and `Wifi_DevBoard/` names a specific external board rather than anything built into the device.

`picopass/` and `unirf/` name third-party formats rather than Flipper features. PicoPass is a card format, UniRF is a vendor, and having both as top level directories suggests captured dumps and tools for reading them, which is exactly the kind of thing a shared collection accumulates.

`wetox_scripts/` is the least self-explanatory name in the listing, and without the contents to hand it is better left described as its author's script collection than guessed at. The honest summary for all of these: this repository mixes working software, reference data, hardware notes and captured files in one tree, and the directory name is usually the only documentation you get.

The donation section, stated plainly

The README spends a substantial part of its length on donations, and it does so without pretending otherwise. It states that nothing is ever expected for the hoarding of digital files, the creations the author has made, or the people helped, then explains that donations will be used for hardware and maybe caffeine to further testing.

Five addresses are listed in the README: BTC, BCH, ETH and LTC, plus a PayPal address. There is also a Lab401 referral link with a discount code, which the author says was requested by people who wanted it in the file.

This matters when you evaluate the repository, because it tells you what kind of thing you are looking at. There is no commercial product, no support contract and no SLA. What you get is whatever the author felt was worth keeping, arranged as they saw fit, and the donation section is the honest description of the exchange. If you need Flipper Zero development with a maintainer who answers issues, the links in the README point elsewhere: the official Discord, the official documentation at docs.flipperzero.one, the official forum, the Awesome Flipper Zero list, and a tutorials repository by jamisonderek.

Two companion projects the README points at first

The very first line of the README redirects you elsewhere for the single most searched thing in this ecosystem. Looking for infrared codes is a question about the Flipper-IRDB repository, not this one, and the README links it before anything else. Infrared code databases are large, frequently updated, and structured as data rather than code, which is exactly the profile of a project that does not belong inside an unrelated collection.

The second line does the same for partial downloads: a tool at uberguidoz.github.io/DownGit for grabbing part of any repository. Both links are the author redirecting demand away from this repository toward somewhere it belongs, which is a fair signal about the boundaries of the project.

For everything else, the README's own referral list is the better map. Wr3nch's beginner guide is linked for people new to GitHub at all, which tells you the intended reader includes people who have never cloned anything before. That is consistent with a collection whose main entry point is a file browser rather than a build system.

Editorial conclusion

This repository is best understood as a landing site rather than a project with a build. Nothing here is compiled into a product, there is no manifest to satisfy and no API to integrate against; the value is that somebody has already sorted a large pile of Flipper Zero files into named directories you can browse. The Sub-GHz, BadUSB, NFC and Infrared folders are where you will find something useful, and the Donations folder is where you will find files of a different kind entirely. The last push was on 2026-07-28, so it is not abandoned, and the presence of a `.gitmodules` file means several folders pull in external repositories rather than storing everything directly. Pull the specific directory you need instead of cloning the whole tree, and read the SECURITY notes before you load an unfamiliar payload onto hardware that can transmit.

Frequently asked questions

Official sources

1. Issues
2. License: GPL-3.0
3. README
4. UberGuidoZ/Flipper on GitHub