Following a soft launch in June 2021, the H5P Group officially released the H5P OER Hub in early February 2026. This is great because now H5P users can find openly licensed content right in their editor and easily share their content with others.
All H5P users? No, unfortunately not yet. Currently, only sites using H5P.com or the H5P Moodle plugin can access the OER Hub. The H5P plugin for WordPress is expected to receive support soon — a pull request with the necessary code is ready.
But what about Moodle’s own H5P integration? Lumi? Drupal? ILIAS? Stud.IP? Joomla? TYPO3? Edlib and potentially others? The maintainers of the respective H5P integrations will need to add support for the H5P OER Hub. However, it’s not documented how to do that, so it might take a while. That made me sad.
I asked the H5P Group for a standalone webpage that would allow users to browse the contents and, optionally, share them. Here’s the response I received from their product team:
“Thanks for the suggestion. With the recent release of the OER Hub we need to review its value before deciding how to move forward with it. Sharing content is absolutely at the heart of what H5P stands for, but we need to assess its overall value for H5P and our strategic direction. Once we have a better idea of how it meets user needs, we will decide on next steps.”
To be honest, that felt quite underwhelming. The page is straightforward, simple to do. You can even reuse the H5P Hub client from the editor. Well, you know me. Open source is for builders, so I built it.
Feel free to visit snordian.de/h5p-oer-hub-explorer, where you can see what’s already on the H5P OER Hub and download content you like. Hopefully, this workaround won’t be necessary for much longer, and many other H5P integrations will follow soon.
Please note though that H5P Group may change their API without warning – or my server might get too much traffic and be shut down, so things could break. Just holler if that seems to be the case.
Great idea, Oliver!
However The “Filter by content” does not list content types.
The mini server merely fetches a response (called hub cache metadata) from H5P Group’s server and passes that data to H5P Group’s Hub Client. I had to reverse engineer that as nothing is documented. Don’t know what might be missing for content types, as there’s no relevant logic on my end.
Fixed that. The H5P Hub client expects an argument that holds the library data in a particular format. That format resembled what the H5P Hub Cache holds, so I used that – but it was slightly different. Remapped – works.