Once your Meshy model lands in Blender, a short cleanup pass makes it ready for engines, renders, or slicers. This guide walks through that pass in order.
Manual export vs. Blender Bridge
You can bring a Meshy model into Blender two ways:
DCC Bridge (recommended): send the model directly from your Workspace using the Meshy Blender Plugin. This preserves materials and applies sensible defaults automatically.
Manual export/import: download the model (FBX/GLB/OBJ) and import it via Blender's standard File > Import menu. This gives you more control but means every setting below needs a manual check.
Import settings
If importing manually, confirm these on the way in:
File format: prefer FBX or glTF/GLB for the most reliable material and UV handling.
Unit scale: keep the importer's unit scale at 1.0 unless your project uses a different working unit.
+Y Up / axis orientation matching Blender's convention, to avoid models importing sideways.
Material check
After import, open the Shading tab and confirm:
Texture maps (base color, normal, roughness) are linked and loaded, not showing as pink/magenta placeholders.
The material uses a Principled BSDF node with textures wired into the correct inputs.
If textures appear missing, use File > External Data > Find Missing Files and point Blender at the downloaded texture folder.
Decimate / remesh
Meshy exports can carry more geometry than you need downstream:
Add a Decimate modifier (Collapse type) to reduce polycount while preserving silhouette — check the result in wireframe view before applying.
For uneven topology, a Remesh modifier (Voxel mode) can even out density before decimating.
Always apply modifiers before exporting so the target engine receives the final mesh.
Scale / origin
Before exporting, set the object up cleanly:
Object > Apply > All Transforms, so scale/rotation read as 1/0 in the target engine.
Object > Set Origin > Origin to Geometry (or to a specific point) so the pivot lands where your engine expects it.
UVs
Check the UV Editing tab for overlapping or stretched UV islands, especially after decimating or remeshing — these operations can distort UVs and cause visible texture seams. Re-unwrap if needed before re-baking or re-exporting textures.
Re-export to engines/slicers
With cleanup complete, export for your destination:
Game engines (Unity, Unreal, Godot, Roblox Studio): export FBX or glTF with applied transforms and baked textures.
3D printing slicers: export STL or OBJ; decimate/remesh settings matter most here since slicers care about clean, manifold geometry rather than materials.
FAQ
1. Do I need to manually export and import, or can I skip straight to Blender?
Use the Meshy Blender Plugin via DCC Bridge to send models directly from your Workspace — this skips manual export/import and its associated settings entirely.
2. Why are my textures showing as pink or missing in Blender?
This usually means the texture files weren't found alongside the imported mesh. Use File > External Data > Find Missing Files and point Blender at the folder containing the downloaded textures.
3. Why does my model look huge or tiny after import?
Check the import unit scale setting, then apply Object > Apply > All Transforms so the final scale is baked in before export.
4. My model has too many polygons for my engine — how do I reduce it?
Add a Decimate modifier (and a Remesh modifier first if topology is uneven), check the result in wireframe view, then apply the modifier before exporting.
5. My textures look seamed or stretched after cleanup — what happened?
Decimating or remeshing can distort existing UVs. Check the UV Editing tab and re-unwrap affected areas before re-baking or re-exporting textures.
Related Articles