Inspector shows sales and marketing teams in seconds what's actually inside a 3D file — geometry, textures, provenance, classification. Before the asset goes to an agency, trade fair, or customer. In the browser, no upload.
Inspector reads any USDZ — even those without a USDseal stamp. Add a stamp, and the trust verification layers come on top.
Before any handoff to an agency, trade fair, or customer: Does the file run in AR Quick Look? Which textures are inside, at what resolution? Are source metadata documented — or missing, and need clarification? Polygon count, materials, format sanity check.
When a file is stamped with USDseal, provenance, version trace, and tamper checks come in: who signed it, when, against which engineering baseline, has it been altered since? Plus everything from diagnostic mode.
USDseal is a digital authenticity seal for USDZ files. It documents inside the file itself where the components come from, who assembled them, and whether the file has been altered since. Inspector is the browser-side companion — it reads the seal without any file leaving your machine. → More about USDseal
Drop file, read, decide. Three moments from Inspector. (Screenshots show the German UI — Inspector ships with a built-in DE/EN toggle.)
Three answer layers for three typical handoff questions.
Geometry components, textures with resolution and format, materials, AR Quick Look compatibility, documented sources — and a clear view of what's not documented and needs clarification before release.
For USDseal-stamped files: issuer name, timestamp, key fingerprint. Plus version trace: does this USDZ derive from a master? Which content was filtered for this released version — e.g. marketing material only, without internal engineering detail?
Inspector verifies every component hash against the manifest. A swapped texture, a modified material, an added geometry — the break becomes immediately visible.
Apple's AR Quick Look has hard requirements — miss the defaultPrim, for example, and the iPhone viewer silently fails to display anything. Inspector checks every USDZ before any handoff against 21 rules across 7 categories and color-codes what breaks or wobbles.
defaultPrim, ZIP order, no nested USDZ.
Y-up, metersPerUnit, realistic units.
Formats (PNG/JPG/WebP), size ≤ 4K, power-of-two, relative paths.
No HTTP links, no file references outside the USDZ.
For USDseal-signed files: signature and version trace verifiable.
Time codes, loop definitions, animation markers in the header.
File size ≤ 25 MB, geometry complexity, unused sub-assets.
Don't trust, verify.
USDseal signatures are reproducible. Every signed USDZ carries SHA-256 hashes per ZIP component — you can recompute them independently in 5 lines of Python. Inspector shows the same hashes live in the browser, the Independent Verifier handles the full manifest roundtrip.
Verify yourself — 5 lines of Python:
import zipfile, hashlib
z = zipfile.ZipFile('signed.usdz')
for member in z.namelist():
h = hashlib.sha256(z.read(member)).hexdigest()
print(member, h)→ Inspector shows the same hashes live in the browser.
→ Independent Verifier (Python, ~120 lines) handles the full manifest roundtrip — github.com/KopfKinoK3/usdseal-verify.
No setup, no login. Inspector is there when you have a USDZ in hand and need to decide on the next handoff.
A USDZ from engineering, from the agency, from a supplier, or from a customer.
In the browser, no installation, no account. Save the file locally for offline use.
Drag & drop. Inspector reads it in browser memory — the file does not leave your machine.
What's inside? What's missing? Take the findings back to engineering or the agency — release or clarify.
Inspector is built so that no server exists — not promised that none is used.
Inspector is a single HTML file. There is no server that could receive, log, or forward data — not even accidentally.
The USDZ is unpacked and read directly in browser memory. It does not leave your machine — not even as hashes or metadata.
Save the Inspector HTML locally, open it without a network connection — the functionality remains identical. Works in closed industrial networks too.
A USDZ is rarely done after one handoff. It originates in engineering, gets tailored for recipients, is verified, used — and sometimes returns with updates. Inspector is the point where every handoff is checked.
From CAD systems like AutoCAD, NX, or SolidWorks — or platforms like NVIDIA Omniverse — a 3D-USDZ master is built. The complete engineering state, with all components and material information.
From the master, filtered versions are exported — e.g. without internal engineering detail for the marketing agency, without NDA components for the trade fair. The exported file carries a USDseal stamp with provenance information.
Before any handoff, the recipient opens the USDZ in Inspector and checks the content. The same file then runs without custom app development on iPhone, iPad, and Apple Vision Pro — and is simultaneously usable in a configurator (e.g. USDconfig), as rendering, animation, or digital-twin asset. Additions flow back to the master with a new seal.
Inspector is the verification surface. Around it sit further viSales tools that share the same pipeline picture.
CLI with init, sign, verify, inspect, export, merge. Cryptographically stamps asset sources and license info into the USDZ file. Master / derivative workflow for rights-filtered sales versions. Open source, Apache-2.0, C2PA-compatible. Inspector is its browser-side companion.
Questions? Reach out on LinkedIn → Gerhard Schröder.
Web-based configuration plus AR preview from a single 3D master. All variants from one dataset, no asset sprawl. Runs directly on iPhone, iPad, Apple Vision Pro, and in the browser. For sales presentations, showroom AR, webshop integration.
Questions? Reach out on LinkedIn → Gerhard Schröder.
Adapts USD specs from NVIDIA Omniverse so the file runs in AR Quick Look (iPhone, iPad) and on Apple Vision Pro — pure format and spec adjustment. No polygon reduction, no material rebuilding. The engineering asset reaches sales endpoints unchanged.
Questions? Reach out on LinkedIn → Gerhard Schröder.
If you work with 3D assets in sales and have seen either compliance requests or uncertain asset handoffs: send us a USDZ from your current workflow, and we'll open it together in Inspector to see what becomes visible.