Skip to the tool

Extract DEB packages.

See inside Debian .deb packages — unpacked on your device.

No uploads — 100% local No ads Free & open source

Drop DEB packages here

or browse your files

Files never leave your device. Everything runs in your browser, nothing touches a server — tools you've used even work offline.

A .deb is an archive-in-an-archive: an ar wrapper holding control metadata and a data tarball with the actual files. Drop one here and the chain unwraps automatically down to the real payload — binaries, configs, docs — each file its own download, no Linux machine required.

How it works

  1. Drop files anywhere on the page, click to browse, or paste with ⌘V.
  2. Pick a quality or preset — or set an exact target size and let the tool find it.
  3. Compress, compare before/after, and download — individually or as a ZIP.

deb and rpm are cousins

Both package formats are thin wrappers around a standard archive — deb wraps a tar, rpm wraps a cpio. That is why one engine opens both, and why the files inside look so ordinary once unwrapped. For repacking extracted files, the archive tool builds any format.

Frequently asked questions

Why do other tools show me data.tar.xz instead of files?

Because they stop at the ar layer. A .deb holds data.tar.(gz|xz|zst) inside; this page detects that payload and unpacks it in the same pass, so you land on the files, not on another archive.

Does extracting a deb install anything?

No — installation is what dpkg does with the payload plus its maintainer scripts. Extraction here just reads files out; nothing runs, nothing touches your system. It is the safe way to inspect a package before trusting it.

What are the control files it mentions skipping?

Package metadata — dependency lists, maintainer scripts, checksums — that lives in a separate control tarball. The extraction focuses on the data payload where the actual files are; the note just tells you the metadata was left out.

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.