The .irc File Format
An open standard for portable IR and RF remote control definitions. Hardware agnostic. Forever.
The world needed an open IR standard. Now it has one.
READYWARE .irc files store the raw physics of IR and RF signals — pulse timings in microseconds — making every remote you build immune to hardware changes, company shutdowns, and platform lock-in. Forever.
Why Every Other Format Failed
Every major IR format made the same mistake — it tied signals to hardware, platforms, or companies. When the hardware died, the signals died with it.
Two Clean Layers — One File
Every .irc file contains two completely separate layers. Apps that only need IR signals read Layer 2 and ignore Layer 1. READYWARE reads both.
- Button name, position, icon
- Color, size, shape, transparency
- Canvas layout, wallpaper
- Button timeout, opacity
- Folder / remote metadata
- type: IR or RF
- frequency: 38000
- pulses: [9042, 4484, ...]
- ir_base64: "JgBYAAAB..."
- source: flipper | user | irdb
Hardware Agnostic. Forever.
Pulses are the truth. Encodings are views.
Raw microsecond timings are the physics of the signal. They work with any IR transmitter ever made or ever invented. Hardware-specific encodings like BroadLink base64 or Pronto Hex are derived from the pulses — generated on demand for whatever device you are using today.
This means your entire library of .irc remotes:
- ✓Works with your current hardware right now
- ✓Works with any new hardware you add in the future — automatically
- ✓Survives company shutdowns, hardware discontinuations, and platform changes
- ✓Is immune to format obsolescence — pulses are physics, not software
- ✓Can be shared, traded, downloaded, and imported by any app that reads .irc
READYWARE lives forever. Not locked to any one device. Upgrade your hardware, switch platforms, change apps — your remotes come with you.
Design Principles
- 1Pulses are truth — raw microsecond timings are the ground truth signal. The physics of infrared light.
- 2Encodings are views — BroadLink, Pronto, LIRC are derived on demand, never stored as the source.
- 3Hardware agnostic — works with any IR/RF transmitter, today and in the future, forever.
- 4Human readable — plain JSON, no binary blobs. Any developer can read it in a text editor.
- 5Open forever — CC0 public domain. No license restrictions. No attribution required. No company can take it away.
- 6Two layers — UI and signals are completely separate. Hardware-only apps ignore Layer 1. READYWARE uses both.
- 7Simple to implement — any developer can parse .irc in under 100 lines of code.
The Signal Object
Every IR or RF signal stores two representations — the raw physics and the hardware encoding. Both are always present. Neither alone is enough.
"power": { "type": "IR", // IR or RF "frequency": 38000, // Hz carrier — 38kHz standard IR "pulses": [9042, 4484, 579, 552, 579, 552...], // microseconds — THE TRUTH "encodings": { "ir_base64": "JgBYAAABJZQRExITEjgR..." // fires instantly today }, "source": "flipper", // flipper | smartir | irdb | user "license": "cc0" // public domain }
Why Store Both Pulses and Encoding?
Pulses = the permanent record. They are the raw physics of the signal. Any hardware, any future device, any app — they all read pulses.
Encoding = the shortcut. Pre-calculated for zero-latency firing on current hardware. When you get new hardware, generate its encoding from pulses once. No re-learning. No re-scanning. Everything you have already saved works instantly.
Signal Types
| Type | Frequency | Use Case | Examples |
|---|---|---|---|
| IR | 30kHz – 60kHz | TVs, ACs, all consumer electronics | 38000 Hz standard |
| RF | 300MHz – 928MHz | Ceiling fans, gate openers, lights, blinds | 433920 Hz, 868000 Hz |
Bluetooth is not included in .irc v1. BT is a full protocol stack — fundamentally different from pulse-based signals. .irc v2 will add BT as a separate signal type.
Format Converter — Supported Formats
The READYWARE Signal Editor and Format Converter accepts any of these formats as input and converts instantly to any other. Paste and go — auto-detected with zero configuration.
Format Comparison
| Format | Status | Open | Layout | Database |
|---|---|---|---|---|
| Logitech Harmony | ☠️ Dead | ❌ | ❌ | 270,000 gone forever |
| Pronto / Philips | ☠️ Dead | ✅ | ❌ | Signals only |
| Flipper Zero .ir | ✅ Active | ✅ | ❌ | Signals only |
| LIRC | ⚠️ Aging | ✅ | ❌ | Linux only |
| READYWARE .irc | ✅ 2026 | ✅ CC0 | ✅ Yes | 470,000+ · Growing |
License — CC0 Public Domain
The .irc specification and all files in the READYWARE IR database are published under CC0 1.0 Universal (Public Domain).
No attribution required. No restrictions. No company can revoke it. No license to comply with. Free forever — for developers, manufacturers, researchers, and users alike.
READYWARE does not own IR pulse data. IR signals are physical phenomena — the physics of infrared light. They belong to no one. We collected, standardized, and published them for the benefit of everyone.
Share Your Creation With The World
READYWARE is more than an app — it's a community. Upload your custom remote layouts, skins, and full profiles so other users can download, use, and build on what you made. Show off your setup. Trade ideas. Find remotes for devices you don't own yet.
What you can share:
- Your .irc files — individual signals or full button sets
- Your remote layouts — the canvas, the icons, the whole look
- Your full profiles — everything exported, ready to load on any device
- Any device signals not yet in the database — help fill the gaps
See remotes and layouts that other users created. Download and use them instantly in READYWARE. The best ones get featured in the database.
"The world needed an open IR standard. Now it has one."
— READYWARE, 2026