Extract RPM packages.
Open RPM packages in your browser — the payload files out.
Drop RPM packages here
or browse your files
Paste with ⌘V · or drop files anywhere on the page
Files never leave your device. Everything runs in your browser, nothing touches a server — tools you've used even work offline.
Fedora, RHEL and SUSE ship software as .rpm — a header stapled to a compressed cpio payload. The classic unix answer is rpm2cpio piped through cpio; the browser answer is this page. Drop the package and the payload unwraps to its actual files automatically.
How it works
- Drop files anywhere on the page, click to browse, or paste with ⌘V.
- Pick a quality or preset — or set an exact target size and let the tool find it.
- Compress, compare before/after, and download — individually or as a ZIP.
rpm2cpio, retired
The rpm payload chain (rpm → cpio.xz → cpio → files) is exactly the kind of nesting the extractor chases automatically — same as deb packages and tarballs. Plain cpio archives open directly too.
Frequently asked questions
Why does my rpm show a .cpio file in other tools?
Those tools peel only the first layer. The payload inside an rpm is a cpio archive (gzip-, xz- or zstd-compressed); this page detects it and unpacks that too, so you get files instead of homework.
Can I extract an rpm on Windows or macOS?
That is exactly the point — no rpm tooling exists there by default, and installing a Linux VM to peek at one package is absurd. Everything runs in the browser, on any OS.
Does this install or run the package?
No — scripts and triggers inside packages never execute. Files are read out passively, which makes this a safe way to audit what a package would put on disk.
Is it private?
Yes. The archive is opened and unpacked on your own device — its contents are never uploaded, and a password, if one is needed, is used locally and never transmitted. The server does nothing but deliver this page. Want proof? Run one file through, switch your connection off, and run another — it still works.