Epic prefixes across the project

Unreal Engine Naming Convention Checker

Consistent asset names are what keep a UE5 project navigable. Validate every asset in the Content folder against Epic's naming convention and catch the ones that break it.

A naming convention only helps if it is followed. Unreal Studio Hub checks every asset in your Content folder against Epic's pattern and lists exactly what breaks it, so the standard holds across the whole team.

What Unreal asset naming conventions are

Epic's guidance follows a clear structure - [AssetTypePrefix]_[AssetName]_[Descriptor]_[Variant] - where the prefix says what the asset is, the name identifies it, and the descriptor adds detail (for a texture, whether it is a normal map, an opacity map and so on). A consistent convention makes assets searchable, prevents duplicates and keeps references legible.

Why naming consistency matters

When names drift, everything slows down: assets are hard to find in the Content Browser, duplicates creep in, and a producer cannot tell at a glance what an asset is. One mis-named Blueprint is cheap; a project full of them is a daily tax on the whole team, and a mess to hand off.

Common UE prefixes it checks

PrefixAsset type
SM_ / SK_Static Mesh / Skeletal Mesh
BP_ / BPI_ / WBP_Blueprint / Blueprint Interface / Widget Blueprint
M_ / MI_ / MF_Material / Material Instance / Material Function
T_Texture (with suffixes like _BC, _N, _ORM)
ABP_ / NS_ / DA_ / DT_Animation Blueprint / Niagara System / Data Asset / Data Table

Beyond prefixes

It validates Blueprint, material, level and Niagara naming, and checks texture suffixes in detail on the material and texture validation page. Run the check, work through the flagged assets, and export a report so the standard is visible to the whole team.

Frequently asked questions

What is the Unreal asset naming convention?

Epic's pattern is [AssetTypePrefix]_[AssetName]_[Descriptor]_[Variant] - a prefix for the asset type (SM_, BP_, M_, T_ and so on), the asset name, and an optional descriptor and variant.

Can I use my own convention?

Yes. The checker compares assets against a convention, so it flags exactly which assets and rules are out of line for your studio.

Does it check texture suffixes?

Yes, in detail. Suffixes like _BC, _N and _ORM are validated on the material and texture validation page.

Start your free trial