Unzip files

Why a browser can do this at all

Every current browser ships the same decompression that ZIP and gzip use internally, because it needs it for the web itself — compressed pages arrive that way. That machinery is available to a page, so opening an archive is a matter of reading the file's index and handing each piece to something already present. There is nothing to download and nothing to install, which is why this works on a phone as readily as a desktop.

What it will not open, and why

RAR and 7z are not supported. Neither compression method exists in a browser, so each would mean shipping a decompressor of several hundred kilobytes to everyone who opens the page, on the chance they have that kind of file — and RAR's format is proprietary on top of that. A tool that claims to open them and then fails is worse than one that says which formats it handles.

Password-protected archives are detected and refused rather than extracted into noise. ZIP64 archives — over 4GB, or more than 65,535 files — are recognised and reported clearly.

The folder problem

Most archives are not one file. They are a directory of tax documents, a project handover, a photographer's delivery, or a year of statements. Uploading that to a website to unpack it hands over every one of those files to somebody else's machine, usually to retrieve one of them. Doing it locally removes the question entirely.

Questions

Which archive formats can I open here?

ZIP, TAR, GZ and TGZ (also written .tar.gz). Those cover almost everything you will meet in practice — ZIP for anything from Windows or a website, and the tar family for anything from a Unix system or a developer.

Can I open a RAR or 7z file?

No, and it is worth being honest about why. Browsers can decompress the ZIP and gzip family natively, which is how this page works with nothing to download. RAR and 7z would each need their own decompressor shipped to the page — somewhere between 300KB and 2MB — and RAR is a proprietary format besides. Rather than load that on everyone, BriskFile says plainly which formats it opens.

Is there a size limit?

No fixed one. The archive is opened in your browser’s memory, so the practical limit is what your device can hold — comfortably hundreds of megabytes on a laptop, less on an older phone. There is no account tier and no daily cap, because there is no server deciding.

Can it open a password-protected archive?

No. Encrypted entries are detected and reported rather than extracted as noise. Decryption would need the password and a cipher implementation, neither of which this page has.

What about ZIP files larger than 4GB?

Those use the ZIP64 extension, which is not supported yet. The archive is detected and you get a clear message rather than a corrupted extraction.

Is the archive uploaded to open it?

No. It is read by this page on your own device. That matters for archives more than for most files, because a ZIP is usually the way people move a whole folder — tax documents, a project, a set of photos — and uploading it to unpack it means handing over all of it at once.

What BriskFile will not do to you

• Your files never leave your device

  Every conversion runs in your browser. Open DevTools, watch the Network tab, and you will see no upload — because there is not one.

• No account, no email, no watermark

  Nothing to sign up for and nothing stamped on your images. There is no step between choosing a file and getting it back.

• No limits at the download button

  No daily cap, no file counter, no "upgrade to download". If the tool starts a job, it finishes it.

• Checkable, not just claimed

  Open the Network tab and convert something — nothing goes out. Or load the page, disconnect, and watch it keep working: the tool is already on your machine, and your file never leaves it.