About RPM Files
RPM Package
RPM (Red Hat Package Manager) is the package format used by Red Hat, Fedora, CentOS, SUSE, and related Linux distributions. It stores compiled software with metadata, dependency information, and installation scripts in a binary format.
Family
Archives & Compressed
Extension
.rpm
MIME Type
application/x-rpm
Can Use As
HOW RPM
CAME TO BE.
RPM — Red Hat Package Manager — launched in 1997 with Red Hat Linux 2.0, superseding the earlier RPP and PMS systems. Marc Ewing and Erik Troan designed RPM with a philosophy parallel to Debian’s DEB: explicit dependencies, scriptable install/upgrade/remove, cryptographic signing, and a queryable local database of installed packages. The acronym itself was later backronymed to "RPM Package Manager" in the spirit of GNU.
Every Red Hat Enterprise, Fedora, CentOS, Rocky, Alma, openSUSE, SLES, and Oracle Linux system runs on RPM. A single .rpm file is a binary wrapper containing a cpio archive of files plus a metadata header describing dependencies and scripts. Modern RPMs use xz or zstd compression. The dependency-resolution tooling evolved from up2date → yum → dnf, each a layer atop rpm itself. In 2026 RPM-based distributions collectively power most enterprise Linux infrastructure on Earth.
CURIOSITIES &
TRIVIA.
RPM was originally "Red Hat Package Manager" but later backronymed to "RPM Package Manager" in GNU-style recursive-acronym tradition.
An .rpm file is internally a lead byte header + a signature block + an RPM header + a cpio archive of files.
RPM's local database (/var/lib/rpm) is a Berkeley DB — queryable with `rpm -qa` to list every installed package.
Every Fedora, RHEL, CentOS, Rocky, and Alma Linux install depends on thousands of RPMs for its system files.
RPM's dependency-resolution layer evolved through up2date → yum → dnf — three decades of incremental replacement without changing the underlying format.
STRENGTHS &
LIMITATIONS.
Strengths
- Explicit dependency graphs like DEB.
- Cryptographic signing and verification.
- Mature tooling (rpm, dnf, yum, zypper).
- Every enterprise Linux distro runs on RPM.
- Self-describing metadata headers.
Limitations
- Red Hat family only — incompatible with DEB.
- Cross-distro .rpms often fail due to library version mismatches.
- "RPM dependency hell" of the late 1990s was a real phenomenon before yum.
- Conversion to/from DEB is tricky (alien tool exists but fidelity varies).
Typical Sizes & Weights
Small CLI tool
50 KB - 1 MB
Desktop app (LibreOffice, Firefox)
100-250 MB
Enterprise database server
500 MB - 5 GB
Technical Specifications
- MIME type
- application/x-rpm
- Extension
- .rpm
- Container
- Lead + signature + header + cpio archive
- Compression
- gzip, bzip2, xz, zstd
- Managers
- rpm, dnf, yum, zypper
CONVERT FROM
RPM
Common Use Cases
Red Hat/Fedora/SUSE packages, enterprise Linux administration
Related Formats
Popular comparisons
RPM vs ZIP
Differences, file size, and when to choose each format.
RPM vs 7Z
Differences, file size, and when to choose each format.
RPM vs TAR
Differences, file size, and when to choose each format.
RPM vs GZ
Differences, file size, and when to choose each format.
RPM vs BZ2
Differences, file size, and when to choose each format.
RPM vs XZ
Differences, file size, and when to choose each format.
Popular RPM conversions
The most-requested destinations when starting from RPM.
Frequently Asked Questions about RPM
Frequently Asked Questions
RPM (RPM Package) is an archive format used to bundle multiple files and folders into a single compressed file. The archive preserves the directory structure and typically reduces total size via compression. RPM sits in the archives & compressed family and has specific strengths around compression ratio, speed, or platform support.
7-Zip, WinRAR, The Unarchiver (macOS), and the built-in archive utilities on Windows and macOS open most RPM files. For command-line extraction, 7z, unar, or the format-specific tool handles RPM cleanly. If your extractor does not recognise RPM, convert to ZIP first — ZIP opens on every operating system without extra software.
Upload the RPM to KaijuConverter and pick ZIP, 7Z, TAR.GZ, or RAR as the target. Our pipeline extracts the original archive and re-compresses the contents into the target format. File permissions, timestamps, and directory structure are preserved where both formats support them.
Depends on the goal. ZIP is the universal baseline — every OS extracts it out of the box. Formats like 7Z or TAR.GZ compress better but require specific tools. RPM may win on compression ratio, password support, or OS integration for specific workflows; ZIP wins on raw compatibility.