Is Extracting Archives in the Browser Private? How to Check It Yourself
Many sites promise that your file "never leaves your device." Some mean it; others upload everything to a server. This guide explains how genuine in-browser extraction works, what UnpackNest does and does not send, and how you can check any site's claim yourself in two minutes with the developer tools built into your browser.
Updated 2026-10-13 · Written and tested by the UnpackNest editorial team (TECCONET)
Two kinds of "online" extractors
| Upload-based service | In-browser tool |
|---|---|
| Your archive is sent to a server and extracted there | The page downloads its code, then reads the archive on your device |
| Speed depends on your upload bandwidth | Speed depends on your device |
| The service could keep, read or leak the file | The archive bytes never reach the server |
| Works for any size the server accepts | Limited by the memory the browser allows |
| You must trust their privacy policy | You can verify the behaviour yourself |
Both can be legitimate. The difference matters most for contracts, medical records, client data, unreleased work and personal photos.
How UnpackNest extracts in the browser
When you choose a file, your browser gives the page access to that one file only. It cannot see your other files or folders.
- ZIP and TAR/GZ tools are written in JavaScript and use the browser's built-in decompression streams. They read the file in pieces, so large archives do not have to fit in memory at once.
- The 7z tool runs the official 7-Zip engine compiled to WebAssembly, in a background worker. The engine (about 1.6 MB) is downloaded when you first choose a file; your archive is mounted read-only inside the worker.
- The RAR tool runs a RAR decoder compiled to WebAssembly in the same way.
- Extracted files are handed to your browser's normal download mechanism as local "blob" data. They go from memory to your Downloads folder without a network request.
Verify it yourself in two minutes
You do not have to take our word for it, or anyone's.
- Open the tool page, for example the ZIP tool, in Chrome, Edge or Firefox on a computer.
- Press F12 (or Cmd+Option+I on a Mac) and open the Network tab.
- Tick Preserve log and clear the list.
- Choose an archive and extract a file.
- Look at the list. On UnpackNest you will see, at most, the 7z or RAR engine loading the first time and small analytics events if you allowed them. You will not see a request whose size matches your archive.
- For a stricter test, sort by Size or filter by Fetch/XHR, and check the Method column for POST or PUT requests.
On an upload-based site, step 5 shows a large POST request roughly the size of your file.
The offline test
For the ZIP and TAR/GZ tools: load the page, then turn off Wi-Fi or put the device in airplane mode, and open an archive. It still works, because everything needed is already in the page. For the 7z and RAR tools, open one small archive first while online so the engine is loaded, then go offline and try another.
What is sent over the network
Honesty matters more than a slogan, so here is the full picture for UnpackNest:
- The page itself: HTML, CSS, JavaScript and, for 7z and RAR, the WebAssembly engine.
- First-party analytics, when enabled: page path, language, device class, referrer domain, time spent on the page and simple tool events (for example "RAR extraction succeeded" or an error code), counted per day without cookies or persistent identifiers, and skipped entirely if your browser sends Global Privacy Control or Do Not Track. File names and contents are never part of these events.
- Advertising, when enabled and only after your consent choice: Google's ad scripts, which follow Google's own policies. They run in the main page; archive data is processed by the tool code and its worker and is never sent to them.
- The contact form: only what you type and send.
The privacy policy describes these in more detail.
Remaining risks you should know about
- Browser extensions. Extensions with permission to "read and change all your data on websites" can see what any page shows, including file lists. Use a profile without extensions for very sensitive files.
- Shared or managed computers. Downloads remain in the Downloads folder; work computers may be monitored. Delete extracted copies you do not need.
- Memory limits. Phones in particular may reload the tab if an archive is too large. That is a reliability issue, not a privacy one: nothing is uploaded as a fallback.
- The site could change. In-browser behaviour is a property of the current code. The network check above is how you stay sure.
Privacy is not the same as safety
Keeping a file on your device protects its confidentiality. It does not make its contents harmless. A malicious program extracted privately is still a malicious program. Read the archive safety guide for the second half of the picture.
Frequently asked questions
Does UnpackNest keep a copy of my archive?
No. The archive is never sent to UnpackNest, so there is nothing to keep. When you close the tab, the browser frees the memory it used.
Do passwords I type for 7z archives leave my device?
No. They are passed to the engine inside your browser tab and discarded when the page is closed or reloaded.
Why does the 7z tool download something when I choose a file?
That is the 7-Zip engine (about 1.6 MB), loaded only when needed to keep the page fast. It is code coming to you, not your file going out.
Is incognito mode more private?
It avoids keeping history and cookies after you close the window. Extraction works the same either way; downloads are still saved to your device.
Tools for this task
- Open and extract RAR files in your browserRAR4 and RAR5, read on your device.
- Open and extract ZIP files in your browserStore, Deflate and ZIP64, read on your device.
- Open 7z files and split .7z.001 archives onlineLZMA/LZMA2, AES-256, multi-volume.
- Extract TAR, TGZ and GZ files in your browserustar, PAX and GNU TAR, gzip streams.