Extract 7z Files Online
Extract 7z files online: one archive up to 50 MB is unpacked on your own device, with LZMA and LZMA2 support. Encrypted archives and split .7z.001 sets are not supported.
7z compresses solid by default: the files in one block share a compressed stream, so the whole archive is extracted in one pass. Solid compression can affect extraction time. Progress counts completed files, not bytes.
How to use
- Choose a .7z archive: Drop a .7z file onto the box or click to choose one. One archive at a time, up to 50 MB; to swap it for another, press ✕ on the file row first — that button is disabled while an extraction is running.
- Press Extract 7z: The first run fetches the extraction engine — a 60 KB worker and a 0.96 MiB WebAssembly file — so the progress bar sits at 0% for a moment; after that it counts the entries as they come out. Cancel requests cancellation: while the engine is loading or the archive is being opened, the current step may have to finish before the run reports that it stopped, and no partial result is ever returned.
- Preview the files and save them: Every file is listed with its full path inside the archive and its extracted size. Use the numbered buttons to look at one, then Download it — or Download all to save them one after another.
How to extract 7z files online without 7-Zip
Pick one .7z archive of up to 50 MB, press Extract 7z, and the files inside are listed and ready to save. The archive is unpacked on your own device and is not uploaded, and the two methods 7-Zip uses by default, LZMA and LZMA2, are both read here. Encrypted archives and split .7z.001 sets stop with a message instead.
The decoding is done by libarchive compiled to WebAssembly, running in a worker thread so the page keeps responding while it works. Both the engine and the 7z code load on demand, which means opening this page downloads no decoder at all. The first time you press the button, a worker of about 60 KB and a 0.96 MiB WebAssembly decoder are fetched from this site — the only thing that travels over the network. Those two files are served with a 30-day cache policy, so a later visit will often skip the wait, though a cache is never a promise; within one tab the engine is shared with the RAR extractor on this site, so if you unpacked a .rar first it is already loaded.
The file is identified by its bytes, not its name. The six-byte 7z signature 37 7A BC AF 27 1C is read before anything else, and the version bytes that follow it are deliberately ignored so archives written by any 7-Zip version are recognised. A .zip or .rar that somebody renamed to .7z is therefore reported as damaged immediately — without downloading the WebAssembly decoder for nothing.
Nothing is kept anywhere. The archive is read straight from your disk into the tab's memory, the extracted files stay there, and the previews and download links point at those in-memory copies. No cookie, no local storage, no upload: a refresh or a closed tab clears all of it, and only the files you saved yourself remain on your device.
Encrypted and split 7z archives: why they stop here
A password-protected 7z cannot be opened on this page, and there is no password field to type into. As soon as the archive is open, the tool asks libarchive whether any of its data is encrypted, and an encrypted archive is refused on the spot — before the file list is even read. The reason is the decoder: the WebAssembly build this site ships has no usable 7z AES decryption, so a correct password would change nothing. A field that asks for a password it cannot use would only waste your time, so the message sends you somewhere that works: unpack the archive with 7-Zip on a computer, then bring the files back here or use them directly. There is no cracking or brute-force step of any kind.
Refusing before the listing also avoids a misleading result. When the person who packed the archive encrypted the file names as well as the contents, the engine simply reports an empty list — so without that early check, an archive full of files would be shown to you as an empty archive. Both kinds of encryption, contents only and file names too, end on the same clear message.
Split .7z.001 archives are not supported here; collect all parts and extract them with 7-Zip. The drop box only takes .7z, so a volume named report.7z.001 is normally turned away as the wrong file type before anything else happens; if one does get through, the volume naming is recognised — name.7z.001, name.7z.002, with exactly three digits — and refused with a message of its own. Either way the reason is the same: a browser receives only the single file you picked and the engine reads one buffer at a time, so there is nothing to seek across, and half an archive is the best you could hope for.
An unsupported-method message can also mean damaged compressed data. Download the archive again first; if it still fails, open it with a desktop archiver.
What opens here, and the ceilings that stop an archive
Archive: 50 MB Files: 10,000 Single extracted file: 256 MB Total extracted size: 512 MB
One archive at a time, and only .7z. A larger file is stopped at the drop box with a size notice, other file types are filtered out before anything happens, and a second pick replaces the first rather than queueing behind it. ZIP and RAR each have their own tool on this site; a file name alone never changes what a tool can read.
The three content ceilings in the box above are checked before a single byte is expanded. Listing the archive reports the extracted size that each entry declares, and the whole archive is refused if it crosses one of them — more than 10,000 entries, a single file over 256 MB extracted, or more than 512 MB extracted in total. Entry names are checked at the same point, and an archive is refused if a name points outside the extraction folder: a path starting with / or \, a drive letter such as C:\, a UNC path, or any name with a segment equal to exactly .. (an ordinary report..txt is fine). There is no compression-ratio test on this page, unlike the ZIP side of the site, because a 7z listing reports no packed size per entry; the three ceilings are what stops an archive that claims to expand into more than your device can hold.
The whole archive comes out in one pass, and that is the format's doing. 7z compresses solid by default: the files in a block are packed as a single stream, so reaching one of them means decoding what sits in front of it. There is no way to list the contents here and take only the two entries you want, and solid compression can affect extraction time because files in a block share a compressed stream. It also sets the memory bill, roughly the archive plus everything extracted from it — and because 7z packs tightly, the extracted total is often several times the archive, so a file near the 50 MB limit can be slow or fail outright on an older phone. The decoding runs in a worker, so the page itself stays usable, but the memory pressure belongs to the whole tab.
The percentage counts entries, not bytes: it is the number of files already extracted divided by the number in the archive. An archive holding one large file and a pile of small ones sits on the same figure for a long time and then races to the end, which is normal rather than a sign that anything has stalled. Cancel is a request to stop, and it is honoured between entries once extraction is under way; while the engine is loading or the archive is being opened, the current step may have to finish first. A cancelled run reports no partial result and never turns back into a successful one.
What was tested: a 319-byte LZMA2 archive of four entries, which came out byte for byte, and a copy of it with 20 bytes of its compressed data flipped, which libarchive reported as "Decompression failed(9): Unknown error: -1" — the reason damaged data can land on the unsupported-method message.
| Archive or compression method | Here |
|---|---|
| LZMA, LZMA2, BZip2, PPMd, Copy | Supported |
| Encrypted 7z, contents or file names | Not supported |
| Split .7z.001 and the volumes after it | Not supported |
| External filters such as Zstd or Brotli | Not supported |
What this page reads from a .7z, and what it turns away.
If what you have is a .zip and you want to see the contents before extracting anything, ZIP Viewer lists the entries first.
Paths, download names and an accented-name quirk
File contents come back byte for byte. Extraction is restoration, not conversion: there is no re-encoding step and nothing is packed a second time, so a photo, a spreadsheet or an installer is identical to what went into the archive. The original .7z is only ever read — never rewritten, repaired or repacked — and it stays as it was on your device.
The list shows each file's full path inside the archive, docs/notes.md for instance, next to its extracted size, so the original structure stays visible. Download names are a different matter, because a browser writes single files to your downloads and will not rebuild folders: the separators become underscores, and docs/notes.md arrives as docs_notes.md. That folding does not check for collisions, so two different archive paths can produce one download name — a/b_c/report.txt and a_b/c/report.txt both become a_b_c_report.txt — and whether your browser overwrites the first file or adds a (1) is up to the browser and the operating system. Check what you saved and rename where it matters.
Some accented names come back altered: in a name such as niño.txt or báo-cáo.txt, the accented letter and the letter straight after it can arrive merged into a single Chinese character. The cause is a name-recovery step shared with the RAR tool, meant for old archives that stored names in a Chinese code page: it misreads a name made up only of Latin-1 characters when an accented letter is followed immediately by another letter. An accented letter followed by a dot, a hyphen, a space or a digit is left alone, and so is any name containing a character outside Latin-1 — which covers Vietnamese letters such as ệ, ơ and ư as well as Chinese, Japanese and Korean names. Since 7z stores its names as UTF-8, the step can only ever hurt here; it affects the list and the download name, never the contents, so rename the file after saving, or unpack that archive with 7-Zip when the names have to survive.
Some things in an archive have no file to come back as. Only file entries exist in the result — directories live on inside the paths, which is why the list has no folder rows — so an empty folder cannot come out at all. File metadata is gone too: each entry is a name and its bytes, so modification times and permission bits are not kept, and what you save carries the time you saved it. Format details belong to the container rather than to the files, so the solid-block layout, the compression method and any archive comment do not appear in the result and are not written anywhere else. There is no "test archive" function either: a file either extracts or it reports an error.
Opening a 7z on an iPhone or an Android phone
A phone is where this page earns its keep, because .7z is not .zip. The Files app on an iPhone unzips a .zip by itself but will show you a .7z and stop there, and many Android file managers do the same, which is why the usual advice is to install an archiver app. Instead, tap the drop box, choose the archive from Files, iCloud Drive or Files by Google, and press Extract 7z. When you save a file, the browser is asked to hand it to the system share sheet where that is supported, so you can store it in Files or send it on; where it is not, the file downloads the ordinary way. If you dismiss the share sheet, nothing is saved — press Download again. Download all saves the files one after another, which on a phone can mean one prompt per file, so for a big archive it is usually quicker to pick the two or three entries you actually need.
Images and PDFs get an inline preview. An MP4 is handed to the browser's video player, which plays it when it understands the encoding and falls back to a download card when it does not; other formats stay available to download without a preview. The numbered buttons follow the same order as the list above them, so entry 7 in the list is button 7. And if the archive turns out to contain nothing — or its file list could not be read, which looks the same from here — the page says so plainly and offers Start over.
To bundle the extracted files into one ZIP archive, use Create ZIP.
Frequently asked questions
- Is my 7z file uploaded to a server?
- No. The archive is read from your disk into the tab's memory and decoded inside your browser, and the previews and download links point at copies held there. The one thing that comes over the network is the extraction engine — a 60 KB worker and a 0.96 MiB WebAssembly file, served from this site — and that is fetched the first time you press the button, not when the page opens.
- Can it open a password-protected 7z file?
- No, and there is no password field, because the WebAssembly decoder on this page has no usable 7z AES decryption — the right password would not help. Encryption is detected as soon as the archive is opened and the run stops with a message. Unpack the archive with 7-Zip on a computer instead; archives with encrypted file names end the same way.
- How do I open a 7z file on an iPhone without installing an app?
- Open this page in Safari, tap the drop box, pick the .7z from Files or iCloud Drive, and press Extract 7z. The Files app can unzip a .zip but not a .7z, which is why it normally sends you to the App Store. Saving a file opens the system share sheet where the browser supports it, so the file can go into Files or on to someone else.
- Why won't it extract my .7z.001 file?
- Split .7z.001 archives are not supported here; collect all parts and extract them with 7-Zip. A browser receives only the single file you picked, so the other volumes are out of reach and there is nothing to join. The drop box takes .7z alone, which usually turns a .001 volume away as the wrong file type; a volume that does get past it is recognised by the three-digit naming and refused with its own message rather than half a result.
- What is the largest 7z I can extract here?
- Up to 50 MB per archive, one archive at a time. The contents are capped as well: 10,000 entries, 256 MB for any single extracted file, and 512 MB extracted in total. An archive declaring more than any of those is refused before extraction starts. Peak memory is roughly the archive plus everything in it, which matters most on older phones.
- Why don't the folders come back when I download the files?
- Because a browser saves single files and will not rebuild directories, so the separators are folded into underscores: docs/notes.md arrives as docs_notes.md. The folding does not check for collisions, so two archive paths can produce the same download name and your browser decides whether to overwrite or add a (1). The full paths stay in the list, so you can rebuild the structure yourself.
- Can I create a .7z file here?
- No. This tool only extracts; no 7z is ever written, which also means there is no way to rename, delete or add an entry inside an existing archive. When you need to bundle files up again — the ones you just extracted included — use Create ZIP: .zip is the format most computers and phones can open without extra software.