Extract archive

Encrypted entries need the password to decrypt, and you can enter it before extracting. Without the password the contents cannot be read, since the data itself is encrypted rather than merely hidden.

ZIP, TAR, GZ, TGZ, 7z and RAR can all be read. Writing is limited to ZIP and the TAR family, because the compressors for 7z and RAR are not freely redistributable.

The contents are only listed and decompressed, never executed, and nothing is transmitted anywhere. That said, an extracted file is exactly as trustworthy as its source, so treat unexpected executables with the same suspicion you would anywhere else.

No. The whole thing runs inside the browser tab you already have open. Your file is read straight from your own disk, worked on there, and handed back as a download. Nothing is sent anywhere, nothing is stored, and there is no account and no queue.

There is no server-side limit because there is no server. The practical ceiling is your device memory, since the file and its output both have to fit in the tab. Files up to a few hundred megabytes are usually fine on a desktop machine, while phones and older laptops will struggle sooner. If a large file fails, close other tabs and try again.

Yes, once the page has loaded once. The engine is cached by the browser, so you can turn off your connection, reload the page and keep working. That is a useful side effect of doing the processing locally rather than a separate offline mode you have to enable.