ZIP File Inspector — List Archive Contents
Upload a ZIP archive and list every entry with compressed size, uncompressed size, and path.
How it works
- 1Paste or type your text in the input field
- 2Click "Inspect" — processing happens in your browser
- 3Copy the result or download as a text file
What to do next
About ZIP File Inspector
ZIP File Inspector is a self-contained web and productivity utility workspace. Upload a ZIP archive and list every entry with compressed size, uncompressed size, and path. Open the page, get the result, close the tab — that is the entire workflow.
Internally the tool runs on standard browser APIs — the same processing stack used by professional desktop pipelines, just compiled for the browser. 0 MB is the practical ceiling, set so the tool stays responsive on phones and older laptops.
Common audiences for ZIP File Inspector include researchers gathering quick references and site owners auditing pages, but plenty of people land on the page through a one-off search and never come back — that is also fine. The tool is built to be useful even when you only ever need it once.
ZIP File Inspector is structured so the question "where is my file processed?" has a single answer: in your browser tab. The engine, the controls, and the result panel are all on one page. Navigating away or closing the tab clears the page's memory the way it does for every other tab.
ZIP File Inspector works well as a bookmarked utility you reach for when you need it. The first visit shows you what the tool does; the second is when you realise it is a low-friction option for the task and worth keeping in your tab list.
When the job finishes, ZIP File Inspector hands you the result as a sensibly named file. Filenames are derived from your input where possible, so a quick batch of jobs leaves you with a tidy folder rather than a pile of generic "output (3)" files. Nothing is auto-saved on Favtoo's side because nothing was ever sent there.
The only practical limit is the 0 MB per-file ceiling, which keeps the tool responsive across a wide range of devices. Run the tool ten times in a row, run it ten thousand times — it behaves the same way and produces the same quality of result.
As a workflow component, ZIP File Inspector is the part you reach for when a single, well-defined web and productivity utility step needs to happen. It performs that step and returns a standard file you can carry into the next part of your pipeline.
ZIP File Inspector keeps the control set focused. Every option on the page is there because a real workflow needs it, and the defaults aim at the most common case so a first-time user can get the right output without changing any settings.
ZIP File Inspector is structured around the idea that a useful tool should be its own page. Open the page, do the work, close the tab — the page is the entire product. There is no onboarding flow because there is nothing to onboard into.
ZIP File Inspector fits the gap where opening a desktop app feels heavy and writing a script feels overkill. The page handles the common web and productivity utility task with sensible defaults so a single visit usually completes the job; for highly specialised work, a dedicated desktop application can offer more knobs to turn.
If you want to get the most out of ZIP File Inspector, three small habits help. Drag-and-drop is faster than the file picker once you get used to it. The keyboard shortcut for downloading the result is whatever your browser uses for "save link as," because the result is a normal download. And if you are working on a sensitive file, processing in an Incognito or Private window is a good extra layer — it leaves no trace in browser history when the tab closes.
When something goes wrong, the cause is usually one of three things: a malformed input, a browser that is out of memory, or a corporate proxy that is interfering with the page's static assets. The first two are easy to diagnose; the third typically requires asking your IT team to allow standard browser APIs to load.
If ZIP File Inspector solved your problem, sharing the page link with someone who has the same problem is the most useful thing you can do. The catalog grows mostly through word of mouth; visitors arriving through a recommendation tend to be the ones the tool serves best.
How it works
- 1Land on the ZIP File Inspector page. The tool is ready to use the moment the page renders.
- 2Drop a web utility file onto the upload area, or click to pick one from your device.
- 3Adjust the options to match what you need. Sensible defaults cover the most common case, so you can usually skip this step.
- 4Click to start the job. The engine (standard browser APIs) processes the input in the page; you can watch the progress indicator until it completes.
- 5Grab the output as soon as the run completes. You can also copy the result instead of downloading if the next tool in your workflow accepts pasted input.
- 6Re-run with different settings as often as you want. Each run produces a fresh output and the original file on disk is never modified.
Common use cases
- Run a one-off check during a meeting without context-switching using ZIP File Inspector.
- Pull a quick reference number for a status update.
- Generate a temporary asset for a social post.
- Sanity-check a webhook response while debugging.
- Run a fast accessibility check before publishing.
- Preview how a result looks before deploying it.
- Generate a campaign asset in seconds for a quick test.
- Audit a marketing page before launch.
FAQ
Do I need to extract the ZIP?
No — the tool reads the central directory so you can browse the file list without unpacking.
What metadata is shown?
Entry path, compressed size, uncompressed size, and last-modified time when present in the archive.
Does it support nested folders?
Yes — folder paths inside the ZIP are shown exactly as stored in the archive.
Can it repair corrupt ZIPs?
It only lists readable entries. Severely damaged archives may fail to parse completely.
Is my archive private?
Yes — parsing happens in your browser memory; we never receive your ZIP file or filenames.
Which browsers are supported?
Chrome, Edge, Firefox, and Safari with modern JS; very large archives may need a 64-bit browser tab.
Can I trust the output of ZIP File Inspector for important work?
ZIP File Inspector is built on standard browser APIs, which is the same class of engine used by professional web and productivity utility pipelines. For deterministic operations, the output is byte-identical to what an equivalent CLI run would produce; for operations involving a codec or a model, the result is well within the range of what comparable tools generate. If you have a specific reference output you need to match, run a small test job first to confirm the configuration produces what you expect.
Does ZIP File Inspector need an internet connection to run?
Once the page is loaded, ZIP File Inspector can complete jobs without an active internet connection — the engine is bundled with the page, so there is no per-job network call. The initial page load does require a connection (to fetch the static assets), but after that you can disconnect entirely and the tool will still work. This is a side-effect of the local-first architecture, not a deliberate "offline mode" feature.
How is ZIP File Inspector different from desktop apps that do the same thing?
Desktop apps usually have more advanced features but require installation, maintenance and (often) a licence. Paid online tools are convenient but route your file through their servers and gate downloads behind accounts. ZIP File Inspector sits in between: free, instant, and private, but intentionally narrow in scope. For one-off jobs and the common web and productivity utility operations, it is usually the lowest-friction choice; for highly specialised work, a dedicated app is still the right answer.
Is ZIP File Inspector lossless?
ZIP File Inspector is built to preserve quality wherever the underlying web utility format allows it. Operations that are mathematically lossless (e.g. structural transformations, lossless re-encoding) round-trip with no perceptible change. Operations that involve a lossy codec inevitably introduce small artefacts at the byte level, but the defaults aim at the sweet spot where output looks or sounds the same to a normal viewer or listener while still being meaningfully smaller or faster than the input.
Is ZIP File Inspector licensed for business use?
ZIP File Inspector can be used for personal and commercial work alike — there is no separate "business" licence to purchase. The output you generate is yours to use however you want, including in client deliverables, internal documents, or commercial products. Favtoo's only ask is fair, individual use; the tool is not designed to be embedded as a backend service or wrapped behind an API for resale.
Does ZIP File Inspector work on a phone or tablet?
ZIP File Inspector runs in any modern mobile browser — Safari, Chrome, Firefox and the in-app browsers in most messaging apps all support the underlying APIs. Performance depends on the device: a recent phone handles typical inputs nearly as fast as a laptop, while older devices may take a few seconds longer near the 0 MB ceiling. The interface lays out cleanly on small screens, so you do not need to pinch-zoom to see the controls.
Does ZIP File Inspector work with screen readers?
ZIP File Inspector uses native HTML controls wherever possible, which means keyboard navigation, focus rings, and screen-reader labels work the way the platform expects. The drop zone accepts files via the keyboard-accessible file picker as well as drag-and-drop, and result downloads use standard browser download flows. If you spot an accessibility gap, Favtoo treats it as a bug worth fixing.
Is the source for ZIP File Inspector available?
ZIP File Inspector is a static page running an open-source engine in your browser, so a typical corporate firewall does not get in the way as long as it allows JavaScript to load from Favtoo. For teams that need to host it themselves on an internal network, the underlying engine (standard browser APIs) is open-source and can be packaged into a private build with the same behaviour. Reach out via the Contact page if that is something you are exploring.