Check a 3D export before it reaches your game
Use a simple static prop to catch scale, orientation, and missing-material problems with a round-trip check.
First Play Studios · Edition 1 · Updated November 14, 2026
An exported .glb plus a short record of its size, orientation, and visible appearance after import.
Before you start- A saved static mesh in Blender
- No rig or animation in the practice model
- A destination that supports glTF, or Blender for a round-trip check
In this guide
Separate the source from the delivery file
Keep the .blend file as your editable source. An exported model is the version another application receives. Choose a small static prop for this exercise so an animation rig or elaborate shader does not hide the basic questions: is it the expected size, does it face the right way, and is anything missing?
Write down the prop’s intended height and which side is its front. A target of one unit is useful only if the receiving project’s unit convention is understood. Do not assume two applications assign the same physical meaning to a number.
Inspect transforms before export
Applying Scale transfers the object’s scale into its data while preserving its visible size, and the object scale returns to 1. For this unrigged practice prop, save a source copy, select the object in Object Mode, and use Object → Apply → Scale. Verify the shape did not jump or shrink.
Do not apply every transform indiscriminately. Location and rotation can carry useful placement or orientation information. Animated and rigged objects need a workflow designed for their rig; this simple exercise does not cover them.
Reimport and compare evidence
Blender’s glTF exporter is available under File → Export → glTF 2.0. Choose the binary .glb format for this exercise. A basic Principled BSDF material is a manageable starting point; complex Blender node arrangements may not transfer as you expect.
Import the exported file into a fresh Blender file, or into a separate test scene in your supported engine. Compare it with a known reference object. Inspect height, front direction, ground contact, object count, and basic color. A successful Blender reimport is an intermediate check; the receiving engine still needs its own validation.
Make an export receipt
- Save a copy of a static prop and record its dimensions and intended front.
- Apply only scale to that practice copy, then confirm the visible size remains unchanged.
- Export it as signpost_v01.glb into an exports folder, keeping the .blend separate.
- Reimport the file into a fresh scene. Record pass/fail for size, direction, ground contact, object count, and material color.
- If a check fails, change one export or import setting and compare again. Keep both observations.
Check your result.
- The editable source still opens independently of the exported file.
- The reimported prop has the expected proportions and no unintended scene objects.
- The receiving application and any untested checks are named in your notes.
Common mistakes to watch for.
- Exporting the whole scene when you intended to deliver one prop.
- Assuming all Blender materials will look identical in another renderer.
- Fixing a scale problem by repeatedly resizing in several places without recording which setting changed.
Keep the conversation useful.
Help me diagnose this static-prop export. Blender version: [version]. Destination and version: [details]. Format: [format]. Expected dimensions/front: [details]. Imported result: [details]. Ask for missing export settings, then suggest one controlled comparison. Do not assume a Blender round trip proves the engine import works.
Sources & version notes.
Based on Blender 4.5 documentation and glTF 2.0. Static meshes only; destination import behavior must be checked in your engine. No live export is claimed.
Further reading from the original documentation:
Practice times are estimates. Software-specific exercises are documentation-based unless their version note says otherwise.A question or a small win?
Tell the workshop what happened when you tried this guide. Ask for a useful next step, or share something you got working.
See discussions about this guide We’ll include the guide link in your draft. Sign in to post, then add your own question or progress before sharing.