APPX Extractor Online
Browse Windows app manifests, application files and every supplied architecture without installing the app.
Open APPX packages and bundles
Upload .appx or .appxbundle to inspect its manifest and files. Processing runs on our servers. The same viewer supports MSIX, APPX, MSIXBUNDLE and APPXBUNDLE. Bundles retain their supplied x86, x64, ARM64 and resource packages separately; inspection does not select a package for the server's architecture.
Start with MSIX-SUMMARY.txt or msix.json for declared identity, version, publisher, architecture, dependencies, application entry points and requested capabilities. Original AppxManifest.xml, bundle manifests, resources, configuration, block maps and signature files remain under files/.
From bundle to package to supported assembly
Example.appxbundle/
MSIX-SUMMARY.txt
msix.json
files/AppxMetadata/AppxBundleManifest.xml
files/apps/Example_x64.appx
files/apps/Example_arm64.appx
files/resources/Example_scale-400.appx
recovered/apps/Example_x64.appx/
MSIX-SUMMARY.txt
files/AppxManifest.xml
files/Example.dll
recovered/Example.dll/source.cs
Open original files or recovered source in the normal result browser, download individual members, or download the result ZIP. Each child has its own path, manifest identity and architecture in the report. Missing referenced parts and unsupported children receive notes; nothing is retrieved from Microsoft Store or another location.
Managed C# and native application files
Supported managed PE assemblies are decompiled with ILSpy. A native launcher can sit beside a managed DLL, so the executable alone does not determine C# availability. Native and AOT binaries remain downloadable data. Resource-only packages are useful results without recovered C#. Recovery reports identify each original assembly and any shared output for identical content.
Supported variants and limits
This viewer handles unencrypted ZIP/OPC packages with Windows 8, Windows 8.1 or Windows 10 app manifest namespaces, and the 2013 bundle namespace with schema versions 1.0 through 5.0. ZIP64 packages use the same bounded extraction limits. Encrypted EAPPX/EMSIX variants, encrypted members, split ZIPs and unsupported manifests receive explicit diagnostics. Optional/external bundle declarations remain metadata only.
Metadata is limited to 1 MiB per manifest. Extraction and nested recovery share a five-minute parent budget, 1 GiB expanded data, 256 MiB per file, 25,000 entries and four nested layers. Each assembly recovery gets up to 30 seconds within the parent budget; worker limits may stop work earlier. Complete files and useful partial results remain available. Read DECOMPILATION-NOTES.txt for missing tools, unsupported payloads and limits.
Publisher names are declarations. Signature authenticity, certificate trust, full block-map integrity and installability are not verified. No installation, registration, DRM removal, repair, repacking, signing, Windows emulation, entry-point execution or dependency downloads are performed.
Related viewers: MSIX packages and MSIXBUNDLE, APPX packages and APPXBUNDLE, .NET DLL decompiler and NuGet package viewer.