H5P import troubleshooting for Moodle, Lumi and WordPress

A practical sequence to distinguish package errors from upload permissions and platform issues.

Keep the original file and copy the exact importer error before making changes. Work on a duplicate until the activity has been tested.

1. Inspect the package

Scan the archive for malformed JSON, missing files, library dependencies and extra folders. Download the report so an administrator can see the paths and versions involved.

2. Check the destination

If no blocking package issue is found, check the destination's upload size limit, permission to install libraries, available content types and H5P Core API version. These settings cannot be determined from an archive alone.

3. Apply only explained changes

Review the exact repair plan before downloading a copy. This tool can normalize packaging and remove recognized metadata debris. It cannot restore lost questions, missing images or library code.

4. Import and play through

Verify media, branching, answer checks and scoring in the destination. A successful structural scan is not a runtime certification for Moodle, Lumi or WordPress.

Technical references

H5P file structure · Package definition · Library definition · H5P validator source

This guide describes package checks, not certified platform compatibility. Reviewed for this MVP in September 2026.