Lucaslhm/Flipper-IRDB
Flipper-IRDB is a community-maintained collection of .ir infrared signal files organized by device type, brand and model for use with the Flipper Zero. Contributors submit CC0-licensed IR captures (TVs, ACs, etc.) following a strict naming/format convention, and the files feed into the Flipper's built-in and community "Universal Remote" firmware features used in IR replay/hardware testing.
What it is
Flipper-IRDB's README, covering how to load its .ir files onto a Flipper Zero and the repo's licensing/naming conventions. The summary establishes what the collection is; the page carries the deployment procedures and a licensing boundary it omits.
Preconditions / Affected
Licensing caveat worth flagging for anyone reusing these captures downstream: the CC0-1.0 license only applies to commits at or after 2319685. Files from commits prior to that hash are explicitly not covered by CC0, so provenance matters if you redistribute or bundle them.
What to do
Three load paths, with a stated performance boundary between them:
flowchart TD
A[Flipper-IRDB files] --> B{How many files?}
B -->|Entire DB / fastest| C[Direct SD copy]
B -->|Several files| D[QFlipper File Manager]
B -->|Mobile / no PC| E[Flipper Mobile App]
C --> F[infrared/ folder on SD]
D --> F
E --> F- Direct SD copy (fastest, "safest" per the page): dismount the SD card, mount to computer, copy desired files into the
infrared/folder, remount to Flipper. - QFlipper: connect over USB-C, ensure firmware is fully updated first, open File Manager → SD Card →
infrared, drag files in. The page warns transfer is slow and does not recommend it for loading the entire DB. - Mobile app: copy
.irfiles to the phone, enable Connected > Options > Experimental Options, then File Manager > ext > infrared > upload. Remotes then appear under Infrared > Saved Remotes.
Contribution/naming scheme (relevant if you want captures folded into the Universal Remotes): <brand>_<model>.ir, model numbers capitalized (LG_55UN7300AUD.ir), no generic names like tv.ir. Universal Remote assets are maintained (mostly by amec0e) in unleashed-firmware and inherited by downstream forks.
Caveats
.ir files are plain text — you can hand-author a missing remote. The page notes ACs need extra care and links a separate read for them (not reproduced here).
Related in Hardware & RF

HAETAE on a Diet: Less Stack, Less Time on Low-End Microcontrollers
geo-tp/ESP32-Bit-Pirate

