Package intake
Choose an APPX or MSIX file
The package stays in this browser tab. Nothing is uploaded or executed.
Manifest read
Package identity
Unnamed package
Unknown publisher
Capabilities
No capabilities found in the manifest.
Applications / entry points
No application entry point was declared.
Show manifest XML
Bundle contents
Inner packages
This bundle contains no recognized inner APPX or MSIX packages.
Package files
—| Select | Path | Size |
|---|
The export preserves package paths and never runs an installer.
Notes and limits
What this page can and cannot tell you
It can read the package structure and XML manifest locally, identify declared capabilities, show whether a signature blob is present, and export the bytes. It does not verify a Microsoft signature, establish that a package is safe, run installers, or replace signing/reputation checks. A missing or present AppxSignature.p7x is only an inventory fact, not a trust verdict.
Nothing is uploaded. The package is decompressed in the browser tab and discarded when you close or clear the page.
Why do some package paths get renamed on export?
ZIP extraction paths are normalized to block absolute paths and parent-directory traversal. Original names remain visible in the file table, but an export uses a safe relative path if a package contains a suspicious name.
Troubleshooting
It says no AppxManifest.xml or AppxBundleManifest.xml was found
The tool only recognizes a genuine APPX/MSIX/bundle package — a ZIP/OPC container with a manifest file at its root (or inside each inner package of a bundle). A renamed .zip, a manually zipped folder, or a corrupted download will produce this error even though the file opens fine as a plain ZIP.
The signature blob is missing — does that mean the package is unsafe?
Not by itself. This page only reports whether an AppxSignature.p7x blob is present in the package; it does not verify a Microsoft signature or vouch for the package's trustworthiness either way. Treat a missing signature as one more data point, not a verdict.
What's the difference between a bundle and a single package?
An APPXBUNDLE or MSIXBUNDLE is a container holding several inner APPX/MSIX packages, for example one per CPU architecture or language. This tool detects a bundle from its manifest type or file extension and lists the inner packages it declares, up to the first 200.
Does this run any code from the package?
No. The package is only decompressed and its XML manifest parsed as text — nothing inside it is ever executed, installed, or run.