The information contained in `info.json` is combined with the `config.h` and `rules.mk` files, dynamically generating the necessary configuration for your keyboard at compile time. It is also used by the [QMK API](https://github.com/qmk/qmk_api), and contains the information [QMK Configurator](https://config.qmk.fm/) needs to display a representation of your keyboard. Its key/value pairs are ruled by the [`data/schemas/keyboard.jsonschema`](https://github.com/qmk/qmk_firmware/blob/master/data/schemas/keyboard.jsonschema) file. To learn more about the why and how of the schema file see the [Data Driven Configuration](https://docs.qmk.fm/#/data_driven_config) page.
You can create `info.json` files at every level under `qmk_firmware/keyboards/<keyboard_name>`. These files are combined, with more specific files overriding keys in less specific files. This means you do not need to duplicate your metadata information. For example, `qmk_firmware/keyboards/clueboard/info.json` specifies information common to all Clueboard products, such as `manufacturer` and `maintainer`, while `qmk_firmware/keyboards/clueboard/66/info.json` contains more specific information about Clueboard 66%.
* A free-form text string describing the keyboard. This will be used as the USB product string. Can include Unicode characters, escaped to ASCII eg. `\u03A8` (Ψ).
* A free-form text string describing the keyboard's manufacturer. This will be used as the USB manufacturer string. Can include Unicode characters, escaped to ASCII eg. `\u03A8` (Ψ).
* Example: `"Clueboard"`
*`url` (Required)
* A URL to the keyboard's product page, [QMK.fm/keyboards](https://qmk.fm/keyboards) page, or other page describing information about the keyboard.
* Example: `"https://clueboard.co"`
*`bootloader_instructions`
* Instructions for putting the keyboard into a mode that allows for firmware flashing.
* Example: `"Press the button marked RESET on the back of the PCB"`
* The debounce algorithm to use. Must be one of `asym_eager_defer_pk`, `custom`, `sym_defer_g`, `sym_defer_pk`, `sym_defer_pr`, `sym_eager_pk`, `sym_eager_pr`.
*`firmware_format`
* The format of the final output binary. Must be one of `bin`, `hex`, `uf2`.
Configures the [Encoder](feature_encoders.md) feature.
*`encoder`
*`rotary`
* A list of encoder objects.
*`pin_a` (Required)
* The GPIO pin connected to the encoder's `A` pin.
*`pin_b` (Required)
* The GPIO pin connected to the encoder's `B` pin.
*`resolution`
* The number of edge transitions on both pins required to register an input.
* Default: `4`
## Indicators :id=indicators
Configures the [LED Indicators](feature_led_indicators.md) feature.
*`indicators`
*`caps_lock`
* The GPIO pin connected to the Caps Lock LED.
*`compose`
* The GPIO pin connected to the Compose LED.
*`kana`
* The GPIO pin connected to the Kana LED.
*`num_lock`
* The GPIO pin connected to the Num Lock LED.
*`on_state`
* The logical GPIO state required to turn the LEDs on.
* Default: `1` (on = high)
*`scroll_lock`
* The GPIO pin connected to the Scroll Lock LED.
## Layouts :id=layouts
The `layouts` portion of the dictionary contains several nested dictionaries. The outer layer consists of QMK layout names, for example `LAYOUT_60_ansi` or `LAYOUT_60_iso`.
Each key dictionary in a layout describes the physical properties of a key. If you are familiar with the Raw Data format for [Keyboard Layout Editor](https://keyboard-layout-editor.com), you will find many of the concepts the same. Key names and layout choices are reused wherever possible, but unlike KLE each key is stateless, inheriting no properties from the keys that came before it.
The ISO enter key is represented by a 1.25u×2uh key. Renderers which utilize info.json layout data (such as `qmk info -l` and the QMK Configurator) should display this key as expected.
* A dictionary of layouts supported by the keyboard.
*`LAYOUT_<layout_name>`
*`layout`
* A list of key dictionaries comprising the layout. Each key dictionary contains:
*`matrix` (Required)
* The matrix position for the key.
* Example: `[0, 4]` (row 0, column 4)
*`x` (Required)
* The absolute position of the key in the horizontal axis, in key units.
*`y` (Required)
* The absolute position of the key in the vertical axis, in key units.
*`h`
* The height of the key, in key units.
* Default: `1` (1u)
*`label`
* What to name the key. This is *not* a key assignment as in the keymap, but should usually correspond to the keycode for the first layer of the default keymap.
* Example: `"Escape"`
*`r`
* The rotation angle in degrees. Currently not implemented.
*`rx`
* The absolute X position of the rotation axis. Currently not implemented.
*`ry`
* The absolute Y position of the rotation axis. Currently not implemented.
* A dictionary of effects to enable or disable. Effects which are absent default to `false`.
* Example:
```json
{
"breathing": true,
"rainbow_mood": true,
"snake": false
}
```
*`brightness_steps`
* The number of brightness adjustment steps.
* Default: `17`
*`driver`
* The driver to use. Must be one of `apa102`, `custom`, `ws2812`.
* Default: `"ws2812"`
*`hue_steps`
* The number of hue adjustment steps.
* Default: `8`
*`layers`
*`blink`
* Enable layer blinking API.
* Default: `false`
*`enabled`
* Enable RGB Lighting Layers.
* Default: `false`
*`max`
* The maximum layer count, from 1 to 32.
* Default: `8`
*`led_map`
* Remap LED indices.
* Example: `[4, 3, 2, 1, 0]`
*`max_brightness`
* The maximum value which the HSV "V" component is scaled to, from 0 to 255.
* Default: `255`
*`rgbw`
* Enable RGBW LEDs.
* Default: `false`
*`saturation_steps`
* The number of saturation adjustment steps.
* Default: `17`
*`sleep`
* Turn off the LEDs when the host goes to sleep.
* Default: `false`
*`split`
* Enable synchronization between split halves.
* Default: `false`
*`split_count`
* When `rgblight.split` is enabled, the number of LEDs on each half.
* Example: `[10, 10]`
## RGB Matrix :id=rgb-matrix
Configures the [RGB Matrix](feature_rgb_matrix.md) feature.
*`rgb_matrix`
*`animations`
* A dictionary of effects to enable or disable. Effects which are absent default to `false`.
* Example:
```json
{
"alpha_mods": true,
"breathing": true,
"cycle_left_right": false
}
```
*`center_point`
* The centroid (geometric center) of the LEDs. Used for certain effects.
* Default: `[112, 32]`
*`driver` (Required)
* The driver to use. Must be one of `aw20216`, `ckled2001`, `custom`, `is31fl3731`, `is31fl3733`, `is31fl3736`, `is31fl3737`, `is31fl3741`, `is31fl3742a`, `is31fl3743a`, `is31fl3745`, `is31fl3746a`, `ws2812`.
*`hue_steps`
* The number of hue adjustment steps.
* Default: `8`
*`layout` (Required)
* List of LED configuration dictionaries. Each dictionary contains:
*`flags` (Required)
* A bitfield of flags describing the type of LED.
*`x` (Required)
* The position of the LED in the horizontal axis, from 0 to 224.
*`y` (Required)
* The position of the LED in the vertical axis, from 0 to 64.
*`matrix`
* The key matrix position associated with the LED.