AASX Viewer
Drop an AASX (Asset Administration Shell) package and read it straight away — the full submodel tree, every attached file, and validation against the AAS v3 metamodel. Nothing is uploaded.
Open AASX (Asset Administration Shell) packages in your browser — no install, no account, nothing uploaded. Drag in a .aasx file and read it immediately: the full asset administration shell and submodel tree, every property and its semantic ID, and every document, drawing and certificate packed inside. It also validates the package against the AAS v3 metamodel constraints and against IDTA submodel templates including Digital Nameplate, Technical Data, Carbon Footprint and the Digital Product Passport. The package is parsed on your own device via WebAssembly and never leaves it.
Frequently asked questions
What is an .aasx file?
An .aasx file is an Asset Administration Shell package — the Industry 4.0 digital-twin format standardised by the IDTA. It is a ZIP-based OPC container holding an AAS environment (the asset shells, submodels and concept descriptions) plus the supplementary documents those submodels point at, such as manuals, drawings and certificates.
How do I open an AASX file without installing anything?
Drag it onto this page. The reference viewer, AASX Package Explorer, is a Windows desktop application, and other options upload your file to a server. This one runs entirely in your browser, so it works on any operating system and your package stays on your device.
Which AAS metamodel versions are supported?
The full v3 line — v3.0, v3.1 and v3.2 — including packages written with the older http://www.admin-shell.io namespace spelling. Files using the pre-v3 metamodels (v1.0 and v2.0.x) are detected and named explicitly rather than partially parsed, so you are told what the file is instead of getting misleading results.
What does it validate beyond the XML schema?
The named AAS metamodel constraints (the AASd and AASc series), plus the problems a schema structurally cannot see: a File element pointing at a supplementary part that is not actually in the package, a semanticId that resolves to no concept description, a broken OPC relationship graph, and values whose lexical form does not match their declared xs: value type.
Is my AASX package uploaded anywhere?
No. It is read on your own device with WebAssembly and never leaves it — enforced by a strict content-security policy, not just a promise. This matters because an AASX routinely carries a supplier's full technical documentation under NDA.
Can it handle very large packages?
Yes. The package is never loaded into memory whole: only the AAS environment part is parsed, and attached files are read on demand straight out of the ZIP, so a package that is hundreds of megabytes of CAD and PDF payload opens without stalling the browser.