Convert USDZ to STL
Convert USDZ to STL in your browser. The conversion runs on this page and the file never leaves your computer.
Result
Before you convert: what this keeps and what it destroys
Preserved
- The geometry, triangle for triangle
- Overall dimensions and proportions
- Watertightness, where the input is watertight
Destroyed
- A recorded unit: STL stores none
- Colour
- The separation between parts, merged into one body
- Animation, rigs, cameras and lights, if the file has them
↺ the reverse: STL → USDZ · about .usdz · about .stl · just view it instead
Why people convert USDZ to STL
You have an AR asset, from a product page, a furniture catalogue or a scanning app, and you want it on a build plate.
USD records metersPerUnit in the stage, so unlike most sources this one can state its scale rather than have it assumed. That value is read and the geometry is converted into the millimetres a slicer expects.
Everything else goes, because STL holds nothing else: colour, materials and the scene hierarchy all disappear and the model arrives as one body. And check the form of the file first. Only the text USDA stage can be read here; a USDZ built around a binary USDC stage, which is what most exporters write, cannot be opened in a browser and the page will tell you so.
What you get
You get a binary STL file containing the same triangles the USDZ file described. No geometry is added, removed or approximated: mesh-to-mesh conversion is a change of container, and this site's tests check that the triangle count comes out identical.
Not carried across by this conversion: a recorded unit, colour, the assembly structure.
The conversion runs in your browser. Your file stays on your computer and is not uploaded.
What to check afterwards
- USDZ declares its unit in the file. Check the output dimensions in the receiving application, especially when its import settings can override the unit.
- The numbers change. STL is read in millimetres and USDZ in metres, so every coordinate is rescaled. The result is the same physical size, but the numbers in the file are different numbers.
- Colour is lost. STL has nowhere to store it. If colour matters, pick a target that keeps it: 3MF, GLB, PLY or USDZ.
- Separate parts merge into one body. USDZ can describe an assembly and STL cannot, so a multi-part model arrives as a single mesh. 3MF and GLB both keep the structure if you need it.
- Coordinates are stored as 32-bit floats. For a part measured in millimetres that's far finer than any machine tolerance. For a model spanning hundreds of thousands of units it isn't.
If you need something this conversion cannot give you
If the unit has to be unambiguous, convert to 3MF instead. It records the unit in the file, so nobody downstream has to assume millimetres and nobody has to scale by 25.4 after the fact.
If colour has to survive, convert to 3MF for printing, GLB for the web, or PLY if the colour is per-vertex scan data.
If the parts must stay separate, convert to 3MF or GLB. Both keep a real structure, so a five-part assembly arrives as five parts rather than one merged body.
If your slicer accepts 3MF, consider it when you need a unit declaration or separate components in the output. Keep the original project for its print settings.
Going the other way
Convert STL back to USDZ. The reverse conversion also works with mesh geometry. It does not reconstruct exact CAD surfaces. Material data and part structure lost in either direction cannot be restored by converting back. Keep the original file for later edits.
How we know this conversion works
This pair was checked against 4 files from the test corpus on 2026-09-04. Each run parses its own output back in and compares the bounding box, the triangle count and, for closed solids, the volume against the input.
A pair that fails those checks doesn't get a page. That's why this site lists 120 conversions and not the several hundred a format-times-format grid would suggest.