// the find
Allar/ue5-style-guide
An attempt to make Unreal Engine 4 projects more consistent
A naming and structure style guide for Unreal Engine 4 projects, covering asset prefixes, folder layout, Blueprint conventions, and mesh/texture rules. It's the de facto community standard for UE4 shops that want consistent content browsers across a team. The companion Linter plugin (sold on the Marketplace) can enforce the rules automatically.
The prefix table for asset types is thorough and practical — having SK_, T_, M_, BP_ etc. baked into filenames means you can grep the content browser without opening anything. The top-level project folder rule is the right call and the explanation of why (migration conflicts, no global asset pollution) is concrete and correct. The Blueprint graph section is more opinionated than most style guides dare to be: the 50-node function limit and the wire-alignment rule address real pain points that accumulate into unmaintainable spaghetti. Community adoption is high enough that following this guide means your assets are legible to any UE contractor you bring in.
The guide is titled UE5 but the content is UE4 — the v2/UE5 branch exists but the main branch README still says 'This is currently for UE4', which is a confusing first impression in 2024. Last meaningful update was 2023 and UE5 introduced Nanite, Lumen, and MetaSounds, none of which have asset naming entries here. The Linter plugin that actually enforces these rules is a paid Marketplace product, so automated enforcement has a paywall, leaving teams to rely on code review alone. The C++ section is explicitly missing (marked TODO), which is a significant gap for any team mixing Blueprints with native code.