Folder Structure

Everything a feature needs goes in one folder. Meshes, textures, blueprints, animations, all together. This is what Epic recommends for most projects.

All meshes in one folder, all textures in another, all blueprints in a third. You pick the type first, then find the specific asset. This is common in smaller projects and familiar if you've worked with other engines.

Feature folders for most things, plus a _Shared folder for assets that don't belong to any single feature. For example, master materials, utility blueprints, and common textures. This comes from Allar's UE style guide.

Each content module (base game, DLC, seasonal event) is its own self-contained folder. You can cook and ship them independently. This is how live-service games handle content drops.

This is how Epic built Lyra. Most content lives inside Game Feature Plugins rather than the Content folder. Each plugin registers its own assets, abilities, and input. The Content folder stays minimal.

Epic requires this layout for Fab and Marketplace submissions. Everything goes under one top-level folder named after your product. Nothing at the Content root.

Five top-level folders. _Shared holds project-wide art and data. Framework holds engine-instantiated classes like game modes, player controllers, and characters. Systems holds gameplay features that don't depend on each other. Modules holds content that ships together. Assets specific to a module stay in that module.

This is what you get from the engine's "New Plugin" wizard. One module, optional content, done. It covers most single-purpose plugins.

Runtime code in one module, editor code in another. The editor module gets stripped from shipping builds automatically. It's ideal to use this for any plugin that has custom detail panels, asset factories, or editor tooling.

A plugin that bundles its own content alongside code. For example, inventory systems, dialogue frameworks, or interaction systems. Drop it into a project and it brings its data assets, input configs, and default blueprints with it.

Editor-only. No runtime module, nothing ships with the game. This is where custom tools, pipeline scripts, and editor extensions live.

Puts an external SDK or library behind an Unreal-friendly interface. For example, analytics middleware, networking libraries, or audio engines. Your game code talks to the wrapper, not the vendor SDK directly.