The Content folder is where an Unreal project lives, and where it quietly gets messy. The Content folder scanner reads the whole tree in your browser and turns it into a dashboard you can reason about.
How scanning works
In Chrome or Edge, the scanner uses the browser's File System Access API to read your Content folder directly; other browsers use a file-picker fallback. It reads structure and asset names locally - the contents of your project are never uploaded - and builds an inventory of every .uasset, grouped by type.
What it recognises
It speaks Unreal, so it classifies the 50+ asset types real projects are built from - Blueprints, Materials and Material Instances, Textures, Static and Skeletal Meshes, Levels and World Partition assets, Niagara Systems and Emitters, Widget Blueprints, Animation Blueprints, Control Rigs, Data Assets, Data Tables, Physics Assets, Sound Cues, MetaSounds and Level Sequences.
From scan to action
A scan is the starting point for everything else: naming validation, the orphaned-assets check, and a full asset audit. Run it before a milestone and you will know the state of the project in a minute instead of an afternoon in the Content Browser.
Frequently asked questions
Does scanning upload my project?
No. The scanner reads structure and asset names locally in your browser; the contents of your project are never uploaded.
Which browsers can scan a folder?
Chrome and Edge support direct folder scanning via the File System Access API. Other browsers use a file-picker fallback.