Drop .XAPK, .APKS, or .APK File to Inspect
or click to browse from your device
Instant Client-Side Tree Inspection • Validates manifest.json & OBB PathsHow the XAPK Validation Engine Works
When an XAPK installer reports "XAPK File Validation Failed" or "Corrupt XAPK Archive", the failure almost always stems from a mismatch between the declarative manifest.json file and the actual ZIP entries inside the container.
- Split APK Presence Audit: Verifies that every entry listed in split_apks[] actually exists at the root of the archive and is non-empty.
- OBB Expansion Path Check: Confirms that every expansions[] entry (such as Android/obb/<pkg>/main.*.obb) matches the exact internal ZIP path.
- Zero-Upload Extraction: Download any individual .apk, .obb, .so library, or icon.png directly out of the container with one click.
Diagnosing "XAPK File Validation Failed" & Inspecting XAPK Manifests
Every compliant .xapk package includes a UTF-8 JSON file named manifest.json at the root of the ZIP archive. Dedicated XAPK installers read this descriptor before touching a single APK or OBB file. Depending on whether the package is an OBB Game Bundle (XAPK Schema v1) or a Split APK Bundle (XAPK Schema v2), manifest.json defines strict structural rules:
- xapk_version (1 or 2): Version 1 packages contain a monolithic <package_name>.apk plus an expansions array pointing to Android/obb/ assets. Version 2 packages contain a split_apks array listing base.apk and configuration splits (config.arm64_v8a.apk, config.xxhdpi.apk).
- Why Validation Fails on Phones: If a browser download was interrupted at 98%, or if someone manually deleted a language split from the ZIP without removing its object entry from manifest.json's split_apks array, or if total_size differs from the sum of unpacked entry sizes, the installer immediately aborts with "XAPK File Validation Failed".
- How to Repair a Failing XAPK Package: Drop the archive into the validator above. If all required base.apk and architecture splits are intact—even if manifest.json has a mismatched byte count—you can bypass the strict manifest check altogether by merging the splits into a standalone .apk on our XAPK to APK Converter, or repackage a fresh, valid manifest.json using our XAPK Builder.