DEB Extractor and Package Viewer

Inspect Debian package identity, dependencies, control files and application payloads. Maintainer scripts remain inert text. Supported packaged Java and .NET bytecode can enter existing source recovery.

Drop your .deb or .udeb 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.

DEB-SUMMARY.txt
deb.json
files/control/control
files/payload/usr/share/java/junit4.jar
recovered/payload/usr/share/java/junit4.jar/

Supported variants and limits

DEB v2 AR layout with control/data TAR payloads using gzip, XZ, Zstandard or no compression. UDEB uses the same validated layout. Packages are never installed and dependencies are never downloaded. Links and special files are skipped.

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.