RPM Extractor and Package Viewer

Read RPM identity, version, architecture, dependency declarations and scriptlets, then browse the actual CPIO application payload. Supported packaged bytecode can use existing source recovery.

Drop your .rpm file here
Choose file

⚠ Drag-and-drop upload could not load — an ad blocker is most likely blocking it. Please disable your ad blocker and reload the page to upload a file.

Browse metadata, source and assets

Processing runs on our servers. Upload a package to browse its extracted files and readable format report, inspect partial results, download individual files or download the complete result ZIP. Extraction and supplied source viewing are identified separately from bytecode recovery.

RPM-SUMMARY.txt
rpm.json
files/archive/payload
files/payload/usr/share/java/junit.jar

Supported variants and limits

RPM lead v3 and header v1 with declared CPIO payloads using gzip, XZ, Zstandard, bzip2 or no compression. Newc, CRC and ODC CPIO are supported. Packages and scriptlets are never installed or run. Signatures and publisher trust are not verified.

Shared defaults are five minutes per job, 1 GiB expanded data, 256 MiB per member, 25,000 entries and four nested layers. Metadata reads are bounded to 4 MiB. Each nested compression or container layer shares these limits. Larger or damaged inputs can produce partial results; DECOMPILATION-NOTES.txt and extraction.json explain skipped files and recovery outcomes.

Related inspectors: DEB, RPM, macOS PKG, MCPACK, MCADDON, MCWORLD and MCTEMPLATE, Scratch, App Inventor and Unity packages.

For Unity runtime .assets, .bundle, .assetbundle or .unity3d files, use the Unity runtime asset extractor. For compiled applications, use the Java decompiler or APK decompiler.