หน้านี้ยังไม่ได้แปลเป็นภาษาของคุณ — แสดงผลเป็นภาษาอังกฤษ

GLB vs OBJ vs STL vs FBX vs USDZ: Which 3D Format to Export

Five export formats, five different jobs. What GLB, OBJ, STL, FBX and USDZ each carry (mesh, textures, materials, animation), and which to pick for printing, games, web and AR.

After generating a model, the next click is “download as”, and the dropdown has five options. They are not five flavours of the same thing. Each format was built for a different job, each carries a different subset of your model (some drop the textures, one drops the colour entirely), and picking the wrong one means a second conversion step or a model that opens as grey plastic.

Image to 3D Model exports all five from the same generated mesh, so the choice is purely about where the file is going. This guide explains what each one actually contains and which destination it fits. If you are new to the whole pipeline, start with the beginner’s conversion guide and come back here for the export step.

What a 3D file can carry

Before the formats, the four things a file may or may not hold:

  • Mesh: the vertices and triangles, the shape itself. Every format has this.

  • UVs and textures: the image maps wrapped onto the mesh (base colour, and for PBR, metallic and roughness). Without these, the model is a single flat colour.

  • Materials: how the textures combine and respond to light. Some formats describe this fully, some only partially, one not at all.

  • Animation, rigs, scene hierarchy: bones, keyframes, multiple objects with parent-child relationships. Only relevant for characters and complex scenes.

A generated model from a single image is a static mesh with baked PBR textures: mesh, UVs, textures and a material, no animation. So the formats that matter are judged mainly on how well they carry textures and materials, and on what opens them.

GLB (glTF 2.0 binary)

Carries: mesh, UVs, textures, full PBR material, optional animation and scene hierarchy, all in one binary file.

Built for: the web and real-time engines. glTF is often called the JPEG of 3D: a compact, standardised, single-file format that browsers, Three.js, Babylon.js, Unity, Unreal, Blender and most viewers open directly with the textures and materials intact.

Choose it when: you are putting the model on a web page, in a WebXR scene, in a product configurator, or sending it to someone who just needs to open and see it. It is also the safest “I don’t know yet” choice because almost everything imports it losslessly.

Watch out for: nothing serious. It is the format we recommend by default. The only reason to pick something else is that the destination demands it.

OBJ (Wavefront)

Carries: mesh and UVs in the .obj file; materials in a separate .mtl file; textures as separate image files alongside. Three or more files, not one.

Built for: 1990s 3D software, and it never left. Every tool ever made can read it, which is its whole appeal.

Choose it when: a legacy tool, a plugin, or a pipeline specifically asks for OBJ, or when you want the mesh in a human-readable text format you can inspect or process with a script.

Watch out for: the loose files. If the .mtl or the texture images are moved, renamed or forgotten, the model opens as untextured grey. OBJ also has no notion of PBR; metallic and roughness maps are either approximated or dropped, so the material will look flatter than in GLB. No animation, no hierarchy worth using.

STL

Carries: mesh only. No UVs, no textures, no colour, no materials. Just triangles.

Built for: 3D printing and CNC. Slicers (Cura, PrusaSlicer, Bambu Studio) and CAD tools speak STL natively, and a printer does not care what colour the model was.

Choose it when: the model is going to a printer or a slicer. Nothing else.

Watch out for: the two things slicers care about that STL cannot express: scale and watertightness. STL has no units, so the slicer will ask or assume; check the dimensions before printing. And a mesh that is not watertight (has holes or self-intersections) will slice unpredictably. The image to STL guide covers checking and repairing both. Do not use STL for anything that needs to look like the original object; you will lose every texture permanently.

FBX (Autodesk)

Carries: mesh, UVs, textures (embedded or referenced), materials, plus rigs, animation, cameras, lights and full scene hierarchy.

Built for: the Autodesk ecosystem and, by extension, game engines. Unity and Unreal import FBX natively and it remains the most common interchange format in game and VFX studios.

Choose it when: the model is going into a Unity or Unreal project alongside other FBX assets, or into Maya or 3ds Max, or when a studio pipeline is FBX-based. For a static prop there is little practical difference from GLB in the result, but matching what the rest of the project uses saves friction.

Watch out for: FBX is proprietary and has versions; an old importer may choke on a new file. Material definitions are less standardised than glTF’s PBR, so metallic and roughness can import slightly differently between tools. Textures may be embedded or external depending on the exporter; check which you got.

USDZ (Apple)

Carries: mesh, UVs, textures, PBR materials, and optionally animation, packaged in a single uncompressed zip. A constrained profile of Pixar’s USD.

Built for: Apple AR Quick Look. Tap a USDZ link on an iPhone or iPad and the model opens in AR, placed on the floor in front of you, with no app install. Safari, Messages, Mail and Notes all handle it.

Choose it when: the destination is an iOS or macOS user looking at the object in AR: product previews, furniture try-before-you-buy, sharing a model with a client who has an iPhone.

Watch out for: it is Apple-only in practice. Android does not open it (Android AR uses GLB via Scene Viewer). Outside the Apple ecosystem, GLB does the same job with wider support. Editing USDZ in general 3D software is also less convenient than editing GLB or FBX.

The decision in one table

Destination

Format

Why

Web page, Three.js, WebXR, “just open it”

GLB

Single file, full PBR, universal support

3D printer or slicer

STL

Mesh only is all a printer needs

Unity / Unreal project

FBX (or GLB)

Native import, matches studio pipelines

Blender, Cinema 4D, rendering

GLB (or FBX)

Full materials, single file

iPhone / iPad AR Quick Look

USDZ

Opens in AR with no app

Android AR

GLB

Scene Viewer standard

Legacy tool or script processing

OBJ

Text format, read by everything

A note on “which is highest quality”

They are all the same mesh and the same textures. No format makes the model better; some formats throw information away (STL throws away all of it except shape; OBJ loses PBR detail). If quality is the question, the answer is to choose a format that keeps everything (GLB, FBX, USDZ) and to pick the texture resolution at generation time, not at export. Formats are not where quality is won or lost. The photo is; see how to photograph an object for image-to-3D.

FAQ

Can I export the same model in several formats?
Yes. Export is from the generated mesh, so you can download GLB for the web and STL for the printer from one job without regenerating.

Which format should I keep as my master copy?
GLB. It holds everything the generation produced in one file and converts cleanly to the others later in Blender or any converter.

Why does my OBJ open without textures?
The .mtl file or the texture images are missing or in a different folder from the .obj. Keep all the files together, with their original names.

Why does my STL have no colour?
STL cannot store colour or textures. That is by design; printers do not use them. If you need a coloured printable file, some printers accept 3MF or OBJ with textures, but that is a separate workflow.

Will a GLB work in Unity?
Yes, with the glTF importer package (glTFast or UnityGLTF), which is standard now. If the project already uses FBX for everything, exporting FBX avoids the extra package.

Is USDZ the same as USD?
USDZ is a packaged, read-only-in-practice subset of USD aimed at AR delivery. Full USD is a much larger scene-description system used in film pipelines; the generated model does not need it.