What Image to 3D for Unity Online Gets You, and What It Does Not
One reference image goes in and a textured .glb 3D mesh comes back in about a minute. What follows is the practical version: what that file contains, how it reaches a Unity project, and which passes are still yours once the 3D mesh is sitting in a scene.
The output
What Lands in Your Unity Project
One image goes in, one file comes back, and knowing what is inside it saves an argument with the importer later.
Every run returns a single textured .glb 3D mesh. Geometry, a UV layout and one baked colour texture travel inside that one file, which is why nothing loose has to arrive beside it. The 3D mesh carries no rig, no animation clip, no LOD chain, no collider and no prefab.
Unity will import it happily and then leave you looking at something that is not yet a shippable asset. What you have is a close-enough shape derived from a single image: a stand-in you can place, scale and judge in a real Unity scene hours before a hand-built blockout would be ready. One image also means one viewpoint, so the side that image never showed is inferred rather than observed.
The route
Getting the File From the Browser to the Editor
No plugin, no package, no account, so the route is the ordinary one.
The generator runs in a browser tab. Hand it one image, wait about a minute, and download the .glb 3D mesh. Nothing here talks to Unity directly, and there is no API to authorise, so the file travels exactly as any other downloaded 3D asset would. Drop it into the project's assets folder and Unity picks the 3D mesh up on the next refresh, reading the glTF without a converter and finding the texture already embedded.
| Step | Where it happens | What you end up with |
|---|---|---|
| Choose an image | Browser | One clear subject in the image, plain background |
| Generate | Browser | A textured .glb, about a minute later |
| Download | Browser | One self-contained file, texture included |
| Drop into the project | Assets folder | An imported 3D mesh with its material |
| Place and judge | Scene view | A stand-in you can look at from any angle |
Import checklist
The Import Settings Worth Checking First
Four things account for almost every “why does it look wrong” moment.
| What to check | Why it bites | What to do about it |
|---|---|---|
| Scale | Nothing in the image says how big the object really is | Set scale on import and make that one number the convention |
| Orientation | Up-axis conventions differ between formats | Rotate once on import, never per instance in the scene |
| Materials | A baked texture is colour, not a material graph | Extract the material and rewire it to your own shader |
| Colliders | None are generated for you | Add a primitive; the raw 3D mesh is a poor collision shape |
None of that is peculiar to a generated 3D mesh, which is rather the point. Check scale before the first instance is placed, though: a Unity scene full of props sized against one wrong reference is tedious to unpick.
The limits
Where the Result Is Not Ready to Ship
Honest limits, so the 3D mesh gets used for what it is actually good at.
Topology.
Reconstructed, not modelled. Not clean quad flow, and not retopologised for a real-time budget.
Rigging.
A character-shaped 3D mesh is not a character. Skeleton, weights and animation are separate work elsewhere.
Materials.
One baked colour map is not roughness, metallic and normal maps. A properly lit scene will show the difference.
Fine detail.
Thin, repeated or occluded features are where a single-image reconstruction gives up first.
Read that as scoping rather than discouragement. A greybox level needing forty props to judge composition does not need forty finished assets. When one prop earns a real pass, take the 3D mesh into Blender and rebuild it; the game asset page covers where that line usually falls.
Questions
Frequently Asked Questions
No. The generator is a browser page and hands you a .glb 3D mesh. Unity reads glTF natively, so the file arrives through the assets folder like any other download.
Nothing in the image tells the reconstruction whether the subject is a teacup or a water tower, so real-world scale is a decision you make on import.
No. What comes back is a 3D mesh with one baked texture. Attaching colliders and components to make a prefab is a step you do in the editor.
It will look flat. The texture is baked colour with no roughness or normal data, and the lighting from the original image is painted into it.
For background dressing at distance, sometimes. For anything the player inspects, treat it as reference to model against rather than final geometry.
Keep reading
More Ways to Turn an Image Into a 3D Model
Explore image to 3D
Turn Your Image Into a 3D Model — Free
No signup, no software, no modelling experience. Drop in an image or describe one, and download a textured .glb in about a minute.