.rpm File Extension

What kind of file is a .rpm?

A .rpm file is an RPM Package Manager package. It can be a binary package ready for a particular system and architecture, or a source RPM containing source material, patches, and build instructions. Both variants use the same extension and application/x-rpm MIME type. That media type is widely used but is not registered by IANA.¹²

An RPM holds files plus structured metadata such as the package name, version, architecture, dependencies, ownership, and installation scripts. Version 4 packages have four logical sections: a lead, signature, header, and compressed payload. Their first four bytes are ED AB EE DB.¹³

How do I open a .rpm on my computer?

On Fedora, Red Hat Enterprise Linux, and other RPM-family Linux distributions, inspect an unfamiliar package before installing it:

rpm -qip package.rpm
rpm -qlp package.rpm
rpm --checksig package.rpm

These commands show package information, list packaged paths, and check available signatures and digests without installing the payload.⁴ When you trust the package, DNF5 can install a local file while resolving dependencies from configured repositories:

dnf5 install ./package.rpm

On Windows or macOS, use a Linux virtual machine or container with RPM tools when you need package-aware inspection. An archive utility may extract some payloads, but that is not a correct installation and does not apply dependencies or lifecycle scripts.

Poly support for .rpm

Poly recognizes RPM packages and stores, syncs, shares, versions, downloads, and finds them by filename and ordinary file properties.

Poly does not parse package headers, validate signatures, extract the payload, generate a thumbnail, or provide an in-app package browser. Package metadata and files inside the RPM are not content-indexed, and the Poly agent cannot read them. Download the file and use RPM or DNF when you need to inspect or install it.

History of .rpm

Marc Ewing and Erik Troan developed RPM at Red Hat after work on earlier package systems. The official timeline records RPM 1.2 in September 1995 and the first commit to the C implementation that November. RPM 2.0 followed in March 1996.⁵

The initials first meant “Red Hat Package Manager.” In 2000, the project adopted the recursive name “RPM Package Manager” as the technology spread beyond Red Hat systems.⁵ Today RPM is used by Fedora, Red Hat Enterprise Linux, openSUSE, SUSE Linux Enterprise, and other distributions.⁶

Working with .rpm and alternatives

The filename often indicates the package's role, but its header is authoritative:

Choose a package built for the exact distribution, release, and CPU architecture. Converting a DEB or another installer may lose dependency rules, script behavior, file ownership, or distribution integration. For sharing files without installation behavior, use a general archive such as TAR or ZIP.