Package Inspector (APK, IPA, JAR, MSI)

Drop an APK, IPA, JAR, WAR or MSI to see its file list (largest first) plus the JAR MANIFEST.MF, the IPA Info.plist, the APK AndroidManifest.xml (package name, version, permissions) or the MSI summary information. It shows whether signature files exist but does not verify them. For the contents of an EXE or DLL, use the PE Viewer; to unpack a ZIP, use another tool.

On-device・No uploadMobile friendlyWorks offline

Your files and input are processed only inside your browser on this device and are never uploaded to our servers.

Package file

Drop an APK, IPA, JAR, MSI or similar

or

Files are neither unpacked nor run. Only the list and config files are read, inside your browser (up to 500 MB).Accepts: APK / AAB / IPA / JAR / WAR / EAR / MSI / ZIPPaste (Ctrl+V) also works

The file is read only inside your browser. Nothing is sent to a server.

This tool does not detect malware or verify signatures. Do not install or run a file from an unknown source, whatever this result says.

Contents

Files are neither unpacked nor run. Only the list and config files are read, inside your browser (up to 500 MB).

How to use

  1. Drop an APK, AAB, IPA, JAR, WAR, EAR or MSI file onto the frame, or choose it with "Choose file" (up to 500 MB).

  2. Check the Overview for the format, file size and number of entries. The format is detected from the contents, not the extension.

  3. Read the format-specific part: the main MANIFEST.MF attributes for a JAR, the bundle ID and versions from Info.plist for an IPA, the package name, version, SDK levels and permissions for an APK, or the summary information and streams for an MSI.

  4. Review the File list, largest first, and filter it by text. Whether signature files exist is shown under Signing.

  5. To try it without a file, press "JAR sample" or "IPA sample". The tool builds a small file in code and shows it.

What it does

Reads without unpacking

Reads the list at the end of the ZIP (the central directory) to show every name, size and compressed size. Only config files are read, up to 16 MB each.

Detects the format from the contents

Uses the presence of AndroidManifest.xml, Payload/*.app, WEB-INF and META-INF/MANIFEST.MF to tell APK, AAB, IPA, WAR, EAR and JAR apart, and the compound-file structure to recognise MSI. ZIP64 is supported.

Reads the APK binary XML

An APK AndroidManifest.xml is binary XML (AXML). The tool extracts the package name, versionName, versionCode, minSdkVersion, targetSdkVersion and uses-permission, and marks permissions that the Android permission reference lists as "dangerous" (the list is not exhaustive).

Signatures: presence only

Shows whether META-INF signature files, an APK Signing Block, IPA _CodeSignature and embedded.mobileprovision, or an MSI signature stream exist. It does not verify that a signature is valid.

Keeps going on broken files

Offsets and lengths are checked to lie inside the file before any read. Broken parts are listed under "parts that could not be read" and the rest is still shown. Data that would expand hugely is not read.

Use cases

  • Check the package name, version and requested permissions of an APK without installing it
  • Check the bundle ID and minimum OS version of an IPA
  • Read Main-Class or the build tool version of a JAR from its MANIFEST.MF
  • Check whether a WAR has WEB-INF/web.xml
  • See which streams an MSI contains, and who created it and with what
  • Find what makes an app large by listing its files largest first

Supported formats

Input

.apk and .aab (Android).ipa (iOS).jar, .war and .ear (Java).msi (Windows Installer)Other files that are ZIP archives

Output

On-screen view (overview, format-specific info, file list)Copy or save as JSON

Capability matrix

FeatureSupportNotes
ZIP file list (name, size, compressed size)SupportedUp to 100,000 entries. ZIP64 is supported
JAR MANIFEST.MF and whether WEB-INF/web.xml existsSupported—
IPA Info.plist (XML and binary)SupportedMain fields such as bundle ID, versions and minimum OS
APK AndroidManifest.xml (binary XML)PartialMain fields and permissions only. Activities and so on are not shown
AAB AndroidManifest.xmlNot supportedInside an AAB it is Protocol Buffers, which is not read (file list only)
MSI stream list and summary informationPartialTable contents (Property, File, and so on) are not read
Showing whether signatures existSupported—
Verifying signatures or certificatesNot supportedDoes not say whether a signature is valid or whose it is
Extracting or saving files, showing file contentsNot supportedOnly the config files above are read
Contents of password-protected ZIPsNot supportedThe list is shown; encrypted config files are not read
Detecting malware or malicious appsNot supportedThe permission mark is a hint, not a verdict
Offline useSupportedWorks without a network connection after the page has loaded once

Limits & notes

  • Files up to 500 MB. Larger files are refused before they are read.
  • The file list is limited to 100,000 entries. Entries beyond that are not listed (the count is shown).
  • Config files that are read (MANIFEST.MF, Info.plist, AndroidManifest.xml) must be 16 MB or less both compressed and expanded. Files that are larger, or that expand beyond their declared size, are not read.
  • The ZIP central directory is read up to 64 MB, and the MSI stream list up to 100,000 entries.
  • The list on screen shows the top part after filtering; the full list can be saved as JSON.

Privacy & safety

The file is read only inside your browser. Nothing is sent to or stored on a server. The file, and any program inside it, is never run.

FAQ

Can I check an APK without installing it?
Yes. The tool shows the file list and the package name, version, SDK levels and permissions from AndroidManifest.xml. It does not read the code (dex) or screen layouts.
Where can I see the bundle ID and version of an IPA?
The tool reads Payload/AppName.app/Info.plist inside the IPA and shows CFBundleIdentifier, CFBundleShortVersionString, MinimumOSVersion and more. Both XML and binary plists work.
Can I read MANIFEST.MF of a JAR without unzipping it?
Yes. The main attributes of META-INF/MANIFEST.MF (Main-Class, Implementation-Version, Created-By and so on) are shown, with wrapped long lines joined.
Can I see the files inside an MSI?
An MSI is a compound file. The tool shows the stream list and summary information (title, author, creating application). The files in the cabinet and the table contents are not shown.
Can I check that a signature is valid?
No. The tool only shows whether signature files or blocks exist. Verify signatures with the official tools for each platform, such as apksigner, jarsigner, codesign or the file properties in Windows.
Does "dangerous" for a permission mean the app is dangerous?
No. It means the kind of permission that Android asks the user to grant at run time. It does not mean the app is malicious. The mark is a hint, and the list is not exhaustive.

EXE/DLL Info Viewer (PE Viewer)

Drop an .exe, .dll or .sys file to see its processor, build time, ASLR and DEP settings, section permissions and entropy, the DLLs and functions it imports, and its version info. The file is not run, and this is not a virus check. For the contents of XML or images, use another tool.

No upload

Archive Studio — ZIP, TAR & tar.gz Viewer, Extractor & Creator

Drop a ZIP, TAR, tar.gz or gz to list what is inside — including ZIPs made on Japanese Windows whose file names are normally garbled. Extract safely, re-create a ZIP with UTF-8 names, or build a ZIP / tar.gz from folders. Everything runs on your device.

No upload

Universal File Inspector

Drop any file to see its real format (from the content), its structure and metadata, what to watch out for, and which tools can process it — before opening it, or before sending it to someone.

No upload

3D Model Viewer

Open 3D models in STL, GLB (glTF), OBJ, FBX or PLY right in your browser, with no 3D software. Rotate them, check the size, volume and holes, and save the current view as a PNG or convert the model to GLB, STL or OBJ. Your files stay on your device.

No upload

G-code Viewer

Drop or paste a G-code file to see the toolpath layer by layer from above, and check the size, filament use and an estimated print time on the spot. It reads 3D printer output and CNC NC files, and the file never leaves your device.

No upload

GeoJSON Studio

Open GeoJSON, TopoJSON, KML, GPX, CSV or WKT, draw the coordinates on a simple plain map, and check them against RFC 7946. You can also convert between formats and measure area and length on a sphere. Files are never sent to a server.

No upload

Last updated: