H5P library directory name mismatch

Understand accepted folder names and why automatic renaming is deliberately conservative.

A library folder must match the machine name in its library.json, optionally followed by the major and minor version.

Two accepted forms

For a library named H5P.Example at version 1.2, both H5P.Example/ and H5P.Example-1.2/ are valid. A folder copied from a source repository may use a different name.

Why this MVP only diagnoses it

A library can include custom code with paths that rely on its folder name. Renaming without checking those references may introduce another error. The report explains the expected name; it does not silently rename code libraries.

Best next step

Obtain an exported H5P package from a trusted authoring tool. If you develop the library, build and package it with the project's supported tooling rather than zipping its source repository.

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.