Compress and optimize USDZ files
Make USDZ assets lighter for Apple Quick Look and AR without rebuilding the scene. The optimizer edits only oversized image payloads, keeps their filenames and formats, and leaves USD layers untouched.
Capabilities
Purpose-built for USDZ
- Preserve every USD, USDA, and USDC scene layer byte-for-byte instead of rebuilding the model through a lossy importer/exporter round trip.
- Resize oversized PNG and JPEG textures without stretching them, while keeping the original filename and image format used by USD references.
- Keep textures already within your selected limit unchanged, including their exact encoded bytes.
- Repackage with uncompressed, 64-byte-aligned USDZ entries for Apple Quick Look compatibility.
- Process the archive locally in your browser — the USDZ file never leaves your device.
Process
How it works
- Drop one USDZ fileThe archive is read locally and its USD layers, textures, and supporting files are inventoried in your browser.
- Choose a texture limitOnly PNG or JPEG images larger than that edge length are resized. Aspect ratio and referenced filenames stay intact.
- Optimize and downloadThe entries are repackaged as a standards-aligned USDZ and you get exact before-and-after size statistics.
Format safety
What stays intact — and what changes
- This preservation-safe optimizer intentionally does not rewrite USD geometry, animation, variants, materials, physics, composition arcs, or metadata.
- Texture downscaling is lossy. Use 2048 px for a quality-first AR default, and inspect 1024 px or 512 px results on the target device.
- GPU-compressed or uncommon image payloads pass through unchanged; only PNG, JPG, and JPEG entries are resized.
- Password-protected or malformed ZIP archives are not supported.
FAQ
Questions, answered
Will the optimizer change my USD scene?
No. USD, USDA, and USDC entries and every non-image asset are copied byte-for-byte. Only oversized PNG and JPEG image entries are resized.
Does it work with Apple Quick Look?
The output uses stored ZIP entries with the 64-byte data alignment expected by USDZ and keeps existing USD references and image extensions intact.
Are USDZ files uploaded?
No. Reading, image resizing, repackaging, and downloading all happen locally in your browser.
Why does it optimize textures but not polygons?
Arbitrary USDZ files can contain composition, variants, animation, custom schemas, and metadata that a mesh round trip may destroy. This tool protects that native scene data instead of pretending a destructive rewrite is safe.
Next