An orphaned asset is one that no map or referenced asset points at any more - the imported texture you replaced, the test Blueprint you forgot, the material nothing uses. They bloat the project and slow cooks and syncs, and Unreal does not make them easy to find in bulk.
Why orphans are hard to spot in Unreal
Unreal links assets by hard and soft references, and moving or renaming an asset can leave a redirector behind. The Reference Viewer traces one asset at a time, but there is no simple project-wide "what is unused" view - so orphans hide in plain sight until a cleanup or a cook complains.
How the checker helps
It walks references from your maps and assets and surfaces the content nothing points at, grouped by type so you can scan it quickly. It flags rather than deletes: you review the list, keep anything loaded dynamically or referenced only at runtime, and remove the rest in the editor. It is the safe way to shrink a project without breaking a cook.
Part of a clean project
Finding orphans is one step of an asset audit. Combine it with the naming check and export a report so the team can agree on what to cut before anything is removed.
Frequently asked questions
What is an orphaned asset in Unreal?
An asset that no map or referenced asset points at any more. Because Unreal uses hard and soft references and redirectors, these are hard to spot by hand, so the checker surfaces them for you.
Is it safe to delete what it finds?
Review first. Assets referenced only at runtime, or loaded dynamically, can look orphaned but are used, so the checker flags rather than deletes.