Open-source project
Lucaslhm/Flipper-IRDB avatar
Lucaslhm/Flipper-IRDB

Flipper-IRDB and the forty-seven folders that decide what your Flipper can learn

A collective of different IRs for the Flipper

4,487 stars1,447 forksUnknownCC0-1.0

At a glance

What is it?
Flipper-IRDB is a shared directory of plain text infrared files that people copy onto a Flipper Zero's SD card. The interesting part is not the copying, it is the naming convention and the lint config that keep the collection usable.
Who is it for?
Adopt Flipper-IRDB if you own a remote whose brand and model appear in the collection and you want a stored signal you can replay from the device without capturing it yourself. Skip it if your remote is missing, since hand-building an .ir file is a separate manual job with no verification, and treat it as the wrong tool for a device class rather than a model, because that is what the firmware universal remotes cover.
Can I use it commercially?
Yes. CC0-1.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Activity is slowing. The repository last received commits 7 months ago.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 14, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • Lucaslhm/Flipper-IRDB4,487 ★ · +109
Star history
Repository2026-09-232026-11-14
Lucaslhm/Flipper-IRDB4.4k4.5k

109 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

A .ir file is plain text, so the whole database is a folder copy

The thing to understand first is that nothing here is a binary blob or a firmware image. Flipper-IRDB is a directory tree of text files ending in .ir, named by brand and model, and the device reads them straight off the SD card. The README points at that fact directly, noting that .ir files are plain text and that a missing remote can sometimes be built by hand when the database has no entry.

That changes the audience. You do not need a toolchain, a package manager or a flashing cable. You need a text editor, an SD card reader, and enough patience to find the right subfolder. The word database also oversells the scope. This is one device type, infrared, and the tree covers remotes for televisions, air conditioners, projectors, light fixtures and similar consumer hardware. Sub-GHz files are a separate thing entirely and are not part of this repository.

Every submission is released into the public domain, so a contributor's capture of their own remote ends up with no restrictions attached. Commits made before 2319685 sit outside that grant, which is the one legal wrinkle worth knowing before you rely on the history.

Fifty device-type directories, then brand, then series

The layout does real work. Files sit in descending order of device type, then device brand, then device series where that is known. At the top level you find folders such as TVs/, ACs/, Projectors/, LED_Lighting/, Cable_Boxes/, Dust_Collectors/, Bidet/ and a long tail of others, including a _Converted_/ folder and Universal_TV_Remotes/ for the firmware-wide remotes.

That hierarchy is the search key. Someone looking for a television remote descends into TVs/ and then into a brand, while a universal remote lives in a different place entirely and is maintained by a different route. Folders like Head_Units/, Heaters/ and Humidifiers/ exist because real remotes exist for those things, and the presence of a folder is a decent signal that at least one person has submitted a file for it.

The counter is that nothing in the repository indexes quality. A directory holding twenty files and one holding two hundred look identical from the outside. There is no manifest, no rating, no record of whether a given file was learned from an original remote or reconstructed by hand. You are trusting a filename and a convention, not a test report.

Copying to the SD card beats the QFlipper file manager once the file count climbs

The fastest route is to remove the SD card from the Flipper, mount it on your computer, copy the wanted .ir files into the infrared folder on the card, then put the card back. The README calls this the fastest and safest method, and the mechanical cost is that you have to dismount the card and plug it into the computer directly.

Over USB, QFlipper can do the same job through its File Manager. You connect the device, wait for the Connected indicator, make sure the firmware is current by pressing the green Update button and letting the Flipper reboot, open the File Manager icon, select SD Card, double-click into infrared, then drag files from your file explorer into the window. That path works, but the README warns that the transfer can take a long time depending on how many files you move, and it states plainly that loading the entire Flipper-IRDB this way is discouraged in favour of the direct card copy.

For a handful of remotes the drag and drop is fine. For the whole collection the same README points you at the card. The mobile route is a third option: put the .ir files in your phone's Download folder, open the Flipper Mobile App, turn on Experimental Options under Connected, and use the File Manager that exposes ext, infrared and the upload icon. The remotes then appear on the hardware under Infrared and Saved Remotes. That last menu path is the moment a copied file becomes usable, and it applies equally to all three methods.

The file itself is a header comment followed by raw timings

Because the format is text, you can inspect what you copied. The README shows the shape of a file for a television identified in its own header comment, and the header carries a filetype line and a version line ahead of the signal name.

bash
Filetype: IR signals file
Version: 1
#
# Dynex EN-21669D TV <--
#
name: Power

Reading that back tells you two things a filename alone cannot. The comment can record make, model, a link or a short description, and the README asks contributors to put that kind of note directly into the file. The name field is the label the device shows, so Power is a better choice than Button7.

The alternative when the database has nothing for your remote is to write this structure yourself and capture the timings from the original handset. That path has no tooling described in this repository, so it is a manual job rather than a workflow the project supports.

The lint config and the button table are the only quality gate

Quality control is convention plus a configuration file. The repository root carries a .fff-ir-lint.json, and the README sets out the naming rules the collection depends on. A file should be named brand_model.ir with capitalised model numbers, so LG_55UN7300AUD.ir is right while lg_55un7300aud.ir is wrong on case, tv.ir is wrong because it is too generic to identify anything, and a .txt extension is simply not a signal file.

The button vocabulary is fixed too, so that universal assets can be assembled later. Audio and video use names such as Power, Vol_up, Vol_dn, Mute, Play, Ch_next and Back. Air conditioners use Off, Cool_hi, Cool_lo, Heat_hi, Heat_lo and Dh. LEDs use Power_off, Power_on, Brightness_up, Brightness_dn and the colour names Red, Green, Blue, White and Yellow. Deviating from these strings is what stops a file being folded into a universal remote later.

This is the honest limitation of the project. What exists is a lint config, a naming table, and the judgement of the maintainers, who are mostly amec0e for the universal remote additions and are listed alongside Lucaslhm, UberGuidoZ and ezod.

A QFlipper transfer of the whole collection is the failure mode the README names

Ask what breaks and the documentation gives one clear answer: the USB transfer path through QFlipper becomes slow as the file count rises, which is why bulk copying onto the dismounted card is advised instead.

The second failure mode is quieter. A remote can sit at the wrong nesting level, or carry a name too generic to be useful, and the device will still list it. It will appear under Infrared and Saved Remotes whether or not the timings are correct or whether the brand folder matches. The collection gives you replay, not proof of correctness, so a file that does not work tells you nothing about whether the capture was bad or the send path was.

Two further gaps are worth stating. The repository has no GitHub releases, so there is no versioned download to pin your install to, and the last push was on 2026-04-12, so the tree you clone today is whatever main happens to be. Both make a local clone, kept in your own version control, more sensible than treating any single copy as canonical.

Hand-building an .ir file and the firmware universal remotes take different routes

Two alternatives exist and neither replaces this collection. The first is manual construction. The README links to irdb by RandomDebugError for the case where your remote is missing, and the approach is direct: capture the signal from the original handset and write the timings into a text file yourself. The difference in approach is editorial rather than technical. Flipper-IRDB gives you a capture someone else already made; the manual route gives you full control over the timings and none of the shared verification, because a hand-built file has never been checked by anyone but its author.

The second is the universal remote built into firmware. The maintainers add individual contributions to the universal remotes in unleashed-firmware, which other firmware options adapt, and the README links the firmware documentation on universal remotes for air conditioners specifically. A universal remote is not a file you copy in. It is an asset built from the naming convention, assembled under rules that the collection has to follow, and it covers a device you own without the exact model being known.

So the two answer different questions. Copying a file from Flipper-IRDB targets one brand and model. Contributing to the universal remote targets a whole device class and requires the button names and file structure to be right. For air conditioners the README flags the universal remote documentation as an important read before contributing.

Editorial conclusion

Adopt Flipper-IRDB if you own a remote whose brand and model appear in the collection and you want a stored signal you can replay from the device without capturing it yourself. Skip it if your remote is missing, since hand-building an .ir file is a separate manual job with no verification, and treat it as the wrong tool for a device class rather than a model, because that is what the firmware universal remotes cover. Check three things before you install: that the infrared folder on your card is not already full of half-transferred files from an interrupted QFlipper run, that the brand and model folder you copy from actually matches the handset in your hand, and that the file you pick opens as text with a Filetype line and a readable name field. With the last push on 2026-04-12 and no GitHub releases, keep your own clone under version control so you can see what changed when the tree moves.

Frequently asked questions

Where do Flipper-IRDB files go on a Flipper Zero?

They go into the infrared folder on the SD card. After copying, the remotes appear on the device under Infrared and Saved Remotes.

Can I load the whole Flipper-IRDB onto a Flipper Zero at once?

You can copy the files, but the README warns that a QFlipper transfer takes a long time as the file count grows and advises copying directly to the SD card for the entire collection.

Can Flipper-IRDB be installed on Android?

There is no app from this repository. The README points to the Flipper Mobile App, where activating Experimental Options under Connected reveals a File Manager that can upload .ir files from the phone's Download folder to the infrared directory.

How do I add a remote that is missing from Flipper-IRDB?

Contributions are welcome. Name the file brand_model.ir with a capitalised model number, place it under device type, then brand, then series, and add make, model or a short description as a comment inside the .ir file.

What licence covers Flipper-IRDB contributions?

Submissions are released under CC0-1.0. Commits made before 2319685 are not covered by that grant.

Official sources

  1. Issues
  2. License: CC0-1.0
  3. Lucaslhm/Flipper-IRDB on GitHub
  4. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/lucaslhm-flipper-irdb.svg)](https://hysenlabs.com/projects/lucaslhm-flipper-irdb)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/lucaslhm-flipper-irdb.svg)](https://hysenlabs.com/projects/lucaslhm-flipper-irdb)

Was this useful?