APPX

Generated by scripts/gen-format-pages.py from docs/data/format-metadata/, FILE_FORMATS.csv and docs/formats-master.csv. Do not edit by hand: change the source, then run the script.

AppX/MSIX Preview.

At a glance


Purpose	A Windows app package (AppX or MSIX, or a bundle of them): an OPC ZIP with AppxManifest.xml, a block map and a signature.
Extensions	`.appx`
Poka parser	`poka-appx`
Viewer	`poka-tree-viewer`
Depth tier	Parser with a shared viewer (see Depth tiers)
Breadth tier	B4 Summary (see Breadth tiers)

How much Poka reads

B4 Summary. The container and metadata are read and summarised (counts, properties, structure), but the main content is not rendered.

Confidence: medium (the reviewer read the code). Basis: Reviewed 2026-10-26: read parsers/poka-appx/src/main.rs (906 lines) and plugin.json. Five unit tests cover the manifest and the integrity findings; corpus_appx_packages_have_no_integrity_findings runs msix-packaging_language-en.appx through that check. Covers .appx, .msix, .appxbundle and .msixbundle. The tree reads AppxManifest.xml with roxmltree: identity, display name, version, publisher, architecture, description, signed and bundle flags, manifest, block map and entry statistics, and lists applications, capabilities (elevated ones marked) and target device families. Judgement: B4: the manifest is decoded and the package summarised, but no file is shown.

What Poka does not read

Package files (executables, assets, resources.pri) are not shown or listed beyond counts
For bundles, the inner packages and AppxBundleManifest.xml are not read (judgement from the code)
The block map hashes and the signature are not verified
Visual elements (logos, tiles), extensions and dependencies other than device families are not shown

Libraries

Libraries Poka uses or has assessed for this format, with the status, licence and language the registry records.

roxmltree (used; MIT OR Apache-2.0; Rust)
zip (used; MIT; Rust)

Sources

parsers/poka-appx/src/main.rs
parsers/poka-appx/plugin.json