GLB, USDZ, and OBJ: A Fashion File Format Guide (2026)

GLB, USDZ, and OBJ are the 3D file formats fashion brands actually use. Here is what each one is, when to use it, and how to turn the file into product images.

What are GLB, USDZ, and OBJ?
Why file formats trip up fashion teams
GLB and glTF: the web and render default
USDZ: the Apple and AR format
OBJ: the old reliable mesh
The other formats you will meet: FBX, CLO, USD
GLB vs USDZ vs OBJ at a glance
Which format should you use, and when
How to export the right format from CLO3D
Common file format problems and fixes
What to check before you trust a 3D file
How file formats affect your launch
How Kampana turns 3D files into product images
Frequently asked questions
The bottom line

Someone sends you a 3D garment file. It ends in .glb, or .usdz, or .obj. You are not sure if it will open, if it carries the fabric, or if it can become a product image. So it sits in a folder.

That is the real cost of file format confusion. The 3D is fine. The handoff is what breaks. Your DPC investment should not stop at design review because nobody was sure which format to send.

This guide explains GLB, USDZ, and OBJ in plain language. What each one is, what it carries, when to use it, how to export it from CLO3D, and how to turn it into product images.

If you only read one thing

GLB is the modern default for web and rendering. It is compact, carries geometry and materials in one file, and is an open standard from the Khronos Group.

USDZ is the Apple and AR format. It is what iPhone, iPad, and Safari use to show a 3D object in a room with AR Quick Look.

OBJ is the old reliable mesh format. It moves geometry between almost any 3D tool, paired with an MTL file for materials.

CLO3D exports all three. Your garment is portable. The format is a delivery choice, not a dead end.

A file is an input, not a product. Kampana turns GLB, USDZ, OBJ, and CLO files into product-accurate images, with a fidelity check before anything ships.

What are GLB, USDZ, and OBJ?

GLB, USDZ, and OBJ are 3D file formats. Each one stores a digital object: its shape, and usually its color, texture, and material. In fashion, that object is a garment built in a 3D tool like CLO3D, Browzwear, or Blender.

A 3D file is more than a picture. A photo is flat. A 3D file is the actual geometry, so it can be turned, lit, and rendered from any angle. That is what makes it useful for product pages, AR, and campaign images.

The three formats do the same basic job. They differ in what they carry, how big they are, and where they open cleanly. Picking the right one is like picking between a PDF, a PNG, and a PSD. Same content, different use.

Here is the short version of each:

Format	One-line summary
GLB	Compact, modern, open standard. Best for web and rendering.
USDZ	Apple's 3D and AR format. Best for iPhone, iPad, and Safari AR.
OBJ	Old, universal mesh format. Best for moving geometry between tools.

Why file formats trip up fashion teams

Fashion teams are not 3D engineers. A technical designer knows grading and seam allowance, not codecs and mesh topology. So when a file does not open, or opens gray and flat, the instinct is to give up and shoot the garment in a studio instead.

The confusion has three common sources.

The format does not match the destination. An OBJ sent to an AR viewer that wants USDZ. A USDZ sent to a render tool that prefers GLB.
The materials got lost. The geometry arrived, but the color and fabric did not, because the export dropped the texture or the partner file.
Nobody owns the handoff. The 3D lives with design. The product page lives with ecommerce. The file format question falls in the gap between them.

None of this means 3D does not work. It means the file needs to be sent in the right shape, to the right place, with its materials intact. That is a process problem, and it is fixable.

GLB and glTF: the web and render default

GLB is the binary version of glTF. glTF is an open standard from the Khronos Group, the same industry body behind OpenGL and Vulkan. Khronos calls glTF "the JPEG of 3D," because it is built for fast, efficient delivery.

The difference between the two is simple. A glTF file can split its data across several files (the model, the textures, a binary buffer). A GLB packs all of that into one single binary file. For sending and rendering, GLB is easier because it is self-contained.

GLB carries geometry, materials, textures, and even animation in that one file. It uses physically based rendering (PBR), which means the material data describes how a surface reacts to light: how metallic it is, how rough, how it reflects. For fabric, that is what makes a render look like real cloth instead of flat paint.

glTF 2.0 is mature and widely supported. In 2022 it was published as an ISO/IEC international standard, which is rare for a 3D format and a good sign of stability. Web tools like Google's model-viewer display GLB directly in a browser.

For most fashion 3D work that ends in a render or a web view, GLB is the safe default. CLO3D exports it directly. See CLO3D's glTF 2.0 (GLB) export for the steps.

USDZ: the Apple and AR format

USDZ is a 3D format based on OpenUSD, the Universal Scene Description system originally built by Pixar. The "z" means it is a zipped package: the model and its textures bundled together, like GLB.

USDZ matters for one big reason. It is the format Apple uses for AR. As Apple's own AR Quick Look documentation explains, built-in apps like Safari, Messages, and Mail use Quick Look to show USDZ files in 3D, and let a user place the object in their real room through the camera.

For a fashion brand, that is the "see it in your space" or "view in AR" button on a product page, on iPhone and iPad. If you want a shopper to drop a handbag on their table or see a jacket at true scale, USDZ is how that happens on Apple devices.

USDZ is less of a render workhorse and more of a viewing and AR format. You will often produce a GLB for web rendering and a USDZ for the AR view, from the same source garment. They are siblings, not rivals.

OpenUSD itself, documented at openusd.org, is bigger than fashion. It is a scene system used across film and 3D. USDZ is the slice of it that reaches consumers through Apple devices.

OBJ: the old reliable mesh

OBJ is one of the oldest 3D formats still in daily use. It was created by Wavefront Technologies decades ago, and almost every 3D tool can read and write it. That universality is its whole value.

An OBJ file stores the mesh: the points, edges, and faces that make up the shape. On its own, it has no color. Materials live in a separate file called an MTL, and the textures are usually more files alongside it. So an OBJ is rarely one file. It is a small set that has to travel together.

That is the catch with OBJ. If you send only the .obj and forget the .mtl and the texture images, the garment arrives as a gray, untextured shape. The geometry is perfect and the fabric is gone.

So when is OBJ the right call? When you need maximum compatibility, especially moving a garment between two 3D tools that both speak OBJ but disagree on newer formats. It is the lowest common denominator, and sometimes that is exactly what you want. CLO3D supports OBJ import and export directly.

The other formats you will meet: FBX, CLO, USD

GLB, USDZ, and OBJ cover most fashion handoffs, but a few other extensions show up.

CLO / ZPAC are CLO3D's native files. Use them inside CLO. They keep everything, including the pattern and simulation data, but other tools cannot open them.
FBX is a common interchange format, strong for animation and used in some game and 3D pipelines. Heavier than GLB, less open.
USD / USDA / USDC are the broader OpenUSD family. USDZ is the packaged, AR-friendly member. The others are used more in production pipelines.

CLO3D documents the full list of formats it can import and export. The takeaway is that your garment is not trapped in one tool. You can export the format your destination needs.

GLB vs USDZ vs OBJ at a glance

Here is the side-by-side. Use it as the quick reference when someone asks "what format do you need."

	GLB	USDZ	OBJ
Based on	glTF (Khronos)	OpenUSD (Apple/Pixar)	Wavefront
One file?	Yes	Yes (zipped)	No (OBJ + MTL + textures)
Carries materials	Yes, PBR	Yes, PBR	Via separate MTL
Best for	Web, rendering, transfer	Apple AR Quick Look	Tool-to-tool transfer
Standard type	Open ISO/IEC standard	Apple ecosystem standard	De facto industry standard
File size	Compact	Compact	Larger, multi-file
Watch out for	Few issues	Mostly Apple devices	Lost MTL or textures

The pattern: GLB for most rendering and web, USDZ for AR on Apple, OBJ for broad compatibility. Many brands produce more than one from the same garment.

Which format should you use, and when

The right format depends entirely on where the file is going. Here are the three most common destinations for a fashion brand.

For web and product pages

Use GLB. It is compact, self-contained, and renders cleanly in browsers and render tools. If you want an interactive 3D spin on a product page, GLB through a viewer like model-viewer is the standard path. It is also the best format to feed into a render workflow that produces flat PDP images.

For example, a brand with a 3D handbag exports a GLB, renders the front, back, and detail shots from it, and also drops the same GLB into an on-page 3D viewer. One file, two jobs.

For AR and Apple devices

Use USDZ. If the goal is "view in your space" on iPhone or iPad, USDZ is what AR Quick Look expects. You will usually generate it alongside a GLB, not instead of one. The GLB covers web and rendering, the USDZ covers the AR button.

A footwear brand, for instance, might let a shopper place a sneaker on their floor at real scale. That is a USDZ feature on Apple devices.

For moving between 3D tools

Use OBJ (or FBX) when two 3D tools need to exchange a garment and you want maximum compatibility. Just remember to send the MTL and texture files with it, or the materials disappear. OBJ is the format you reach for when GLB or USDZ is not supported on both ends.

How to export the right format from CLO3D

Most fashion 3D starts in CLO3D, so here is the practical path. CLO3D exports all the standard formats, so you choose by destination.

Finish the garment in CLO. Get the fit, drape, color, and fabric right. The export only carries what is in the file.
Pick the format for the destination. GLB for web and rendering. USDZ for Apple AR. OBJ for tool-to-tool transfer.
Export with materials intact. Keep textures and material settings on. This is the step most often skipped, and it is why files arrive gray.
Keep partner files together for OBJ. If you export OBJ, zip the .obj, .mtl, and texture images into one folder so nothing gets separated.
Test it opens. Open the file in a free viewer before you send it. A GLB can be checked in model-viewer. A USDZ can be checked on an iPhone.

CLO3D documents the GLB export, the OBJ export, and the full format list. For the full path from a CLO file to a finished page, see the 3D to PDP guide.

Common file format problems and fixes

The garment opens gray, with no color or fabric

The materials did not travel. For OBJ, the MTL or texture files were left behind. Re-export with textures included, and for OBJ send all the partner files together. For GLB or USDZ, re-export with materials turned on.

The USDZ will not show in AR

AR Quick Look is an Apple feature. Check the file on an actual iPhone or iPad in Safari, not on a desktop browser that does not support it. Apple lists working examples in its AR Quick Look gallery.

The GLB is huge and slow to load

Large textures bloat a GLB. Compress the textures before export, or use a tool that optimizes the file. Khronos publishes optimization tools through the glTF project for exactly this.

The file opens, but the color is off

Color drift is a render and material issue, not just a format one. Lock the color against a real reference, and confirm it in a fidelity check before any image ships. A wrong color on a product page drives returns.

The render looks like generic cloth

The fabric behavior was lost in export, or the render ignored the material data. Re-export from CLO with materials intact, and use a render path that respects PBR so the cloth behaves like the real material.

What to check before you trust a 3D file

Before you build a product page or an AR view from a 3D file, run a quick check. It saves hours later.

Does it open? Open it in a viewer that matches the format. GLB in model-viewer, USDZ on an iPhone.
Are the materials there? The garment should show its real color and fabric, not a gray shape.
Is the scale right? A garment at the wrong scale ruins AR and looks wrong in render. Check it against a known size.
Is the color accurate? Compare to a real swatch or an approved reference. Color is the most common drift.
Is the geometry clean? Look for holes, flipped faces, or stray points that will show up in a render.

A file that passes these is ready to become images. A file that fails one of them will waste a render cycle, so catch it now.

How file formats affect your launch

Here is the part that matters beyond the tech. File formats decide whether your 3D investment reaches the storefront or dies in a folder.

When the format is right and the materials are intact, the same garment becomes a web 3D view, an AR experience, PDP renders, and campaign images. One file, many outputs. Ecommerce can start with the product instead of weeks after it.

When the format is wrong, every handoff stalls. The file does not open, or it opens broken, and the team defaults back to a studio shoot of a physical sample. You pay twice and launch late, and the 3D you already built sits unused.

So the format question is not trivia. It is the difference between 3D that ships and 3D that gets parked. The brands that move fast treat the file as the start of the storefront, not the end of design review.

How Kampana turns 3D files into product images

Kampana is an AI product creation OS for fashion brands. It takes your 3D and CAD files, in the formats above, and turns them into product-accurate images on a node-based canvas. You drop a file at the center and wire it to the nodes you need. Every output is a real, channel-ready asset, and each one passes a product-fidelity check before it ships.

What you get

Product images from your GLB, USDZ, OBJ, and CLO files
Front, back, side, and detail crops generated from one source
On-model and lifestyle versions where you need them
Channel-ready exports that meet marketplace image rules
Reusable campaign renders from the same approved product

The old way vs Kampana

	The old way	With Kampana
File handoff	Stalls when format is wrong	Takes GLB, USDZ, OBJ, CLO
Images	Studio shoot after sampling	Rendered from the file you have
Variants	Reshoot per colorway	Re-render per colorway
Approval	Ad hoc	Product-fidelity check on every render
Pricing	Per seat	Shared credits, unlimited users

How it works

Drop your 3D file on the canvas: GLB, USDZ, OBJ, or CLO.
Wire it to the PDP and campaign render nodes.
Approve each product-accurate image in the fidelity check.
Export channel-ready files, or feed them into the full PDP and social stages.

Pricing is credit-based. One shared pool for the whole workspace, unlimited users, no per-seat fees, and credits do not expire. As a rough guide, the 3D assets to ecommerce and campaign renders workflow runs 2,500 to 7,000 credits depending on how many images you generate. You spend on what you actually create. See pricing for the current credit packs.

The same approved renders can feed the ecommerce PDP asset pack, the marketplace feed optimization, and the social campaign launch. To run the whole sequence from one product, see the end-to-end fashion collection launch.

Frequently asked questions

What is the difference between GLB and glTF?

glTF is the open 3D format from the Khronos Group. GLB is the binary version that packs the model, materials, and textures into one single file. glTF can split that data across several files, while GLB keeps it together, which makes GLB easier to send and render. For most fashion work, GLB is the more convenient of the two.

What 3D file format is best for fashion product pages?

GLB is the best default for web and rendering, because it is compact, self-contained, and widely supported in browsers through viewers like Google's model-viewer. If you also want an AR "view in your space" feature on Apple devices, produce a USDZ from the same garment. OBJ is better kept for moving files between 3D tools.

What is USDZ used for in fashion?

USDZ is the format Apple uses for AR. As Apple's AR Quick Look docs explain, Safari and other built-in apps can show a USDZ in 3D and let a shopper place it in their real room on iPhone or iPad. For fashion, that powers the "see it in your space" or "view in AR" button on a product page.

Why does my OBJ file open with no color or texture?

OBJ stores only the mesh. The materials live in a separate MTL file, with the textures as more files alongside it. If you send just the .obj and leave those behind, the garment arrives gray. Always send the .obj, the .mtl, and the texture images together, ideally zipped into one folder.

Can CLO3D export GLB, USDZ, and OBJ?

Yes. CLO3D exports the standard formats, including GLB and OBJ, and documents its full format list. Your garment is portable, so you choose the format based on where the file is going.

Is glTF a real standard or just a popular format?

It is a real standard. glTF 2.0 was published as an ISO/IEC international standard in 2022, which is uncommon for 3D formats and a strong signal of long-term stability. That is part of why GLB is a safe choice for a brand investing in 3D.

Do I need different files for web and AR?

Often yes. A common setup is a GLB for web display and rendering, plus a USDZ for AR on Apple devices, both made from the same source garment. They serve different destinations, so producing both from one CLO file is normal rather than redundant.

Can a 3D file become a real product page image?

Yes. A 3D file is the input, not the finish line. A tool like Kampana takes a GLB, USDZ, OBJ, or CLO file and renders product-accurate PDP and campaign images from it, with a fidelity check so each image matches the real garment before it ships. See the 3D to PDP guide for the full workflow.

The bottom line

The file format question is smaller than it feels. Three formats cover almost everything a fashion brand needs.

GLB is the modern default for web and rendering: one compact file, an open standard, materials included. USDZ is the Apple and AR format, the one that powers "view in your space" on iPhone and iPad. OBJ is the old reliable mesh for moving geometry between tools, as long as you send its material files with it. CLO3D exports all three, so your garment is never trapped.

The brands that win with 3D are the ones that send the right file, with materials intact, to the right destination, and then turn it into product images instead of parking it. If you want your GLB, USDZ, OBJ, or CLO files to become product-accurate PDP and campaign visuals, with a fidelity check on every render, that is exactly what Kampana is built for. Start creating, free, or explore the fashion workflows to see each stage.