A big UE5 project can have hundreds of Blueprints, cross-referencing each other and pulling in meshes, materials and data. The Blueprint manager gives you one place to see them all, check their naming, and understand the dependencies.
What it shows
- Every Blueprint in the
Contentfolder, grouped and searchable. - Blueprint Interfaces and Widget Blueprints, alongside Blueprint Classes.
- Naming issues - Blueprints that break your naming convention (
BP_,BPI_,WBP_). - Dependencies - the meshes, materials and data assets a Blueprint references.
- Approval status from the production workflow, so you know which Blueprints are final.
Why Blueprints need managing
Blueprints reference other assets, so a rename or move in the wrong place can leave a redirector or break a reference deep in the graph. Seeing Blueprints and their dependencies together - instead of opening each one in the editor - is what stops those breakages before a cook. It is especially useful when several people touch the same systems.
Part of the bigger picture
The Blueprint manager is one view in the full asset management tool. Pair it with the orphaned-assets checker to find Blueprints nothing uses, and export a report for a milestone review.
Frequently asked questions
Does it show Blueprint dependencies?
Yes. It shows each Blueprint with the meshes, materials and data assets it references, so you can see impact before renaming or moving.
Does it cover Widget Blueprints and interfaces?
Yes. Blueprint Classes, Blueprint Interfaces (BPI_) and Widget Blueprints (WBP_) are all included and name-checked.