A Houdini asset that looks perfect can still import into Unreal at the wrong size, facing the wrong way, or with names that break the content browser. Almost all of it is decided before export, which is exactly where a checklist pays off.
Scale and units
Houdini works in metres by default; Unreal works in centimetres. Export at the wrong scale and an asset arrives 100x too small or too large. Decide the unit convention up front - export in centimetres, or set the FBX scale so a 1-unit Houdini metre becomes 100 Unreal units - and apply it consistently across every asset so nothing needs per-import fixing.
Up axis and orientation
Houdini is Y-up. Unreal is Z-up and left-handed. Handle the axis conversion on export (FBX axis settings or a transform before the ROP) so assets stand up correctly in UE5 instead of lying on their side. Get orientation and pivot right in Houdini and you avoid rotating everything after import.
Pivots and transforms
Freeze or bake transforms so the asset's pivot is where Unreal expects it - usually at the origin for props, at the base for placed set pieces. A pivot left at an arbitrary world position is a common cause of assets that snap to the wrong place when dropped into a level.
Naming that survives the import
- No spaces or special characters. Unreal replaces them; export
SM_SHOT010_rock_v003, notrock final (2).fbx. - Prefix by type.
SM_for static meshes,SK_for skeletal,T_for textures - the Unreal convention makes the content browser navigable. - Consistent, padded versions so re-exports do not overwrite silently and history is clear.
- Collision and LOD naming. Follow Unreal's
UCX_collision and_LOD0/1/2conventions so meshes import with collision and LODs recognised automatically.
Check export naming before you deliver
Hive scans your Houdini project and export folder in the browser and flags names that will not survive an Unreal import - spaces, special characters, missing type prefixes, inconsistent versions. It is the fast way to catch a naming problem at your desk instead of in the content browser. For the Unity equivalent, see Houdini to Unity export naming, and the Unreal Studio Hub validates the assets once they are in your UE5 project.
Frequently asked questions
Why do my Houdini assets import into Unreal at the wrong scale?
Houdini defaults to metres and Unreal to centimetres. Export in centimetres or set the FBX scale so 1 Houdini metre becomes 100 Unreal units, and apply it to every asset consistently.
How do I fix up-axis problems from Houdini to Unreal?
Houdini is Y-up and Unreal is Z-up. Convert the axis on export via FBX settings or a transform before the ROP so assets stand up correctly instead of on their side.
What naming does Unreal expect?
No spaces or special characters, type prefixes like SM_ and SK_, padded versions, and UCX_ collision plus _LOD suffixes so meshes import with collision and LODs recognised.