Extract .rpm Packages Online
Open a Red Hat or Fedora .rpm package and take out the files it carries, without installing it and without rpm2cpio.
How to extract an RPM package without installing it
- Drop the
.rpmfile onto the box above, or click to choose it. - Browse the payload. Paths follow the target system, for example
usr/lib64oretc. - Preview a file, download it, or download a selection as one archive.
Getting files out of an RPM the short way
An RPM package is a header with metadata followed by a compressed archive of the files to install. The usual way to unpack one by hand is a two-step pipe through rpm2cpio and cpio, which assumes you are on Linux and have both tools.
Here you drop the package and get the file list. That covers the typical reasons for opening an RPM outside a package manager: fetching one library or binary, reading the default config a package ships, comparing two builds, or looking at a vendor’s driver package from a Windows or macOS desk.
What is shown and what is not
You see the payload: the files and folders the package would install. The package metadata, such as dependencies, changelog and install scriptlets, is not shown. On an RPM-based system rpm -qp --scripts package.rpm prints the scriptlets.
Not an installation
Extracting is copying. Unix permissions and symbolic links are not carried over into a repacked download, nothing is added to the RPM database and no dependency is checked. The package file is read locally, so an internal or licensed package is not handed to any outside server.
Frequently asked questions
Can I open an RPM file on Windows or macOS?
Yes. Drop it on this page in a current desktop browser. No Linux system and no command-line tools are required.
Do I need rpm2cpio?
No. The tool reads the package and its compressed payload directly and shows the files.
Can I see the install scripts and dependencies?
No. Only the payload files are listed. Scriptlets and dependency information are part of the package header, which is not displayed.
Does it show the install scripts?
No. The file list is the package payload: the files that would be installed. Scriptlets and other metadata from the RPM header are not shown.
Does this install the package?
No. Nothing is installed and your system is not changed. You get copies of the files in the package.