If you are confused by the many different firmware types and extensions in the OpenWrt firmware downloads table, this pages tries to explain a bit about this topic.

Use when flashing from OEM ( non-openwrt ) ¹⁾

If only a sysupgrade image is available for your router, either the router is already running some kind of OpenWrt fork (which understands the sysupgrade format natively) or web flash via the OEM UI is not possible… Please consult the Table of Hardware for your device for installation instructions from OEM firmware.

Previously known as trx image, sysupgrade is designed to be flashed from OpenWrt/LEDE itself ²⁾. Commonly used when upgrading.

This firmware contains a regular ext4 Linux partition. Mostly used in x86 and x86_x64 systems.

This firmware contains a type of partition that is compressed and mounts read-only. All modifications (file edit, new files, deleted files) are committed to an overlay. .bin/.chk/.trx

• See also TRX vs. TRX2 vs. BIN

Can be loaded from an arbitrary location ( most often tftp ) and is self-contained in memory. This is like a Linux LiveCD. Often used to test firmware, as the first part of a multi-stage installation or as a recovery tool. ³⁾

An initramfs and initrd are basically the same. It’s a filesystem in memory, which contains userland software. In an embedded environment it might contain the whole distro, on bigger systems it can contain tools&scripts to assemble&mount raid arrays and stuff like that before passing userland boot to them. Both can have a uHeader, to let uBoot know what it is.

The initramfs-kernel image is used for development or special situations as a one-time boot as a stepping stone toward installing the regular sysupgrade version. Since the initramfs version runs entirely from RAM, it does not store any settings in flash, so it is not suitable for operational use.

initramfs-uImage.bin: initramfs-kernel.bin:

Used by few devices ( mvebu/RPi etc. ), most often a multi partition image which is uncompressed and written to external storage via PC.

Only the root filesystem.

Linux core, generally without compression or appended headers.

??

??

Designed to be loaded from tftp server. Device in recovery mode?

This is an image format designed for U-Boot loader. Same as initramfs-or-uImage?

This is an image format designed for U-Boot loader, generally consisting of a kernel with a header for information. Often a zImage with a 64 byte uImage header, which contains the load address & entry point of the zImage, so that uBoot knows what to do with it. Further is contains a description of the actual contents (linux kernel, version, …)

zImage is a compressed plain kernel with a ‘pyggyback’. Some extra code which can decompress the kernel before booting it.

These are raw binary data of the firmware file

These are compressed images

SDK Toolchain for compiling single userspace packages ⁴⁾

To build custom images without compiling ⁵⁾

Linux kernel for build ⁶⁾

This article describes and links to the various factory firmware image formats found.

For OpenWrt Flash Layout see: flash.layout.

Binwalk can help to analyze unknown formats.

by extension:

• BIN
• CHK
• DLF
• IMG
• TRX

• see brcm63xx.imagetag
• see headers