To make 3D models for Unreal Engine with AI, generate a clean reference image of each prop, convert it with Meshy's Image to 3D, texture it with PBR maps, export as FBX, and wire the maps into a master material inside UE5. A scene's worth of props takes hours instead of days.
The video above proves it at volume: a UE5 bakery scene where every pastry, bread loaf, and donut on the shelves was generated with Meshy's real workflow. The creator's summary: work that would normally take days of modeling was assembled in a few hours. Just as important, the video shows the UE5-side material setup that makes generated assets controllable after import.
How to Get AI 3D Models into UE5 in 6 Steps
Step 1: Generate a reference image built for 3D conversion
Before touching the 3D tools, generate a reference image of the prop, and shape the prompt for geometry reading, not for beauty. The rules from the video: gray background, even lighting, no shadows, no environment. Just the object. This is deliberate: a clean, evenly lit subject lets the AI read shape and texture without baked-in shadows corrupting the result.
You can generate these references directly in Meshy's image generation panel without leaving the workspace. Treat this prompt discipline as the highest-leverage step in the whole pipeline. For more on prompt phrasing, see the 3D prompt guide.
Step 2: Convert the reference with Image to 3D
Drop the reference into Image to 3D. The settings used for every asset in the video: Model Type Standard (denser, higher-quality mesh for hero props), the latest AI model available, and Image Enhancement on, which helps the AI read detail from the reference before generating. About a minute later you have a base mesh: raw geometry, no texture yet.
Step 3: Texture with PBR maps, using the same reference
Hit the Texture step and feed it the same reference image. Three settings matter in the video's walkthrough, and each has a reason:
-
Remove lighting: on. Strips baked lighting from the reference so the texture stays clean and responds correctly to Unreal's own lights.
-
Generate PBR maps: on. You get albedo, roughness, and normal maps, so the material behaves realistically under any lighting condition.
-
HD texture: on. Higher resolution, worth the extra credits for assets the camera gets close to.
Another minute, and the prop is fully textured. The full texturing feature is covered in the AI texture generator page and the PBR texturing guide.
Step 4: Export as FBX and import into UE5
Download the asset as FBX. When you import it into Unreal, the texture maps (albedo, normal, roughness) come along automatically. Formats and their tradeoffs are covered in the export formats guide; FBX is the default choice for Unreal pipelines, and the Unreal Engine integration page covers the Meshy side.
Step 5: Build a master material for your AI assets
This is the step that separates "dropping AI assets into a scene" from "integrating them," and it is the video's core lesson. Create one master material in UE5 and route every generated asset through it:
-
Albedo chain: a tint (vector parameter) multiplied into the texture, then a desaturation node with a scalar parameter, a brightness multiply, and a power node for contrast.
-
Normal: a flatten normal node with an intensity parameter, so you can dial surface detail down when it fights your scene lighting.
-
Roughness: straight to output.
The payoff: an asset you had zero control over during generation becomes fully adjustable in real time, non-destructively, from a material instance. Brightness, contrast, saturation, tint, normal strength, all sliders. Every new Meshy asset gets the same material and instantly fits the scene's look.
Step 6: Dress the scene
From here it is familiar Unreal work: place the assets, adjust lighting for a warm, cohesive read, and frame your shots. In the video, the bakery shelves and display cases fill up with generated pastries, and the result holds up in lit, graded cinematic shots.
Why Do Reference Images Matter So Much for UE5 Assets?
Because everything downstream inherits their quality. A reference with baked shadows produces a model with shadows painted into its albedo, which then double-shadows under Unreal's lighting. A reference with a busy background confuses the geometry read. A reference at a weird angle hides half the object's shape.
The gray-background, even-light, no-shadow recipe is not aesthetic preference. It is feeding the model exactly what it needs to reconstruct clean geometry and delightable textures. If you take one habit from this workflow, take this one.
Is AI Asset Generation Worth It for Real UE5 Production?
For props and set dressing, yes, and the video's framing is the honest one: "a few years ago, generating a usable 3D asset from a single image wasn't even close to production quality." Now the pipeline produces clean geometry with PBR textures in about two minutes per asset, and the master material technique closes the control gap that used to make AI assets feel foreign in a graded scene.
The realistic boundaries: hero assets with extreme close-ups still deserve reference-first control and per-asset scrutiny, and every generated asset still needs your lighting, shading, and art direction. The assets are a starting point that removes the modeling bottleneck, not a finished shot.
FAQs
What format should you use for Meshy models in Unreal Engine?
FBX. It imports with textures attached and slots directly into UE5's material workflow. GLB also works for quick tests, but FBX remains the standard for Unreal production pipelines. Both carry your PBR maps.
How long does one Unreal-ready asset take to generate?
About two minutes of processing in the video's workflow: roughly a minute for the base mesh and another minute for PBR texturing, plus the seconds it takes to generate a reference image. The scene-level math is the real story: a shelf full of unique bakery props in an afternoon.
Do AI generated models work with Unreal's lighting?
Yes, if you texture them correctly. The two settings that make it work: remove lighting (so no shadows are baked into the albedo) and PBR map generation (so roughness and normals respond to your scene lights). Skip either and assets will look pasted-in under dynamic lighting.
Should you use Standard or Smart Topology for UE5 props?
Standard for hero props where surface detail matters, which is what the bakery video uses throughout. Smart Topology generates lighter meshes suited to background pieces and performance-sensitive scenes. If a Standard mesh is too heavy, Remesh it down after the fact; textures carry over.
Can you batch generate multiple props for one scene?
Yes. Batch image-to-3D conversion accepts multiple references at once, and Meshy's 3D Agent can generate a matching set from one conversation, keeping style consistent across props. The game environment assets guide covers the volume workflow.
How do you keep AI assets looking consistent in one scene?
Two layers: generate consistently (same style keywords, same reference discipline, or one agent conversation with a locked style), then unify in-engine with a shared master material. The tint, desaturation, and contrast controls let you pull every asset toward the same palette without regenerating anything.
