Engine asset streaming from a Miris account, embedded with the two tags shown below. Open it in the Miris player.
Every front-end developer who has put a 3D model on a product page knows the routine. A designer hands over a beautiful asset. You open the file size. Then you spend a week making it worse.
You decimate the mesh. You shrink 4K textures to 1K. You run it through a compressor, add a loading spinner, and maybe build two or three level of detail (LOD) variants so phones don't fall over. The result ships, but it isn't what the artist made. And when the artist updates a material, you do it all again.
Miris takes a different approach. It streams 3D the way video platforms stream video. And with the new Miris plugin for Adobe Substance 3D Painter, the asset can go from the artist's viewport to your page without passing through your build step at all.
The cost of preparing large 3D assets for the web
glTF is the most widely deployed runtime format for interactive 3D, for good reasons: broad tool support, an open spec, and a runtime that fits how the web works. But delivering a glTF file directly means the viewer downloads a large amount of data before anything appears.
That's the same trade-off we fight with JavaScript bundles. Every byte you ship up front is a byte the user waits on, whether their device can use it or not. So teams trim geometry and textures until load times are acceptable, and fidelity is what gets cut.
Streaming instead of downloading
Miris processes an asset once into a stream-ready format. When a viewer opens your page, the asset loads progressively: a first frame in under 1 second, then detail sharpening over the next few seconds as it streams in.
Delivery adapts to the device and the connection. A phone on hotel Wi-Fi and a workstation on fiber each get the detail they can actually show, from the same source asset. You don't write LOD switching code, because there isn't any to write. The platform manages it.
That means you can skip the three steps that usually eat the week: mesh decimation, texture size reduction, and compression. The detail the artist authors is the detail that gets delivered.
The new part: publishing straight from Substance 3D Painter
Adobe Substance 3D Painter is where a lot of production texturing happens: footwear, furniture, automotive, props. Until now, getting that work onto the web meant exporting, finding the files, packaging them, and uploading them somewhere.
The Miris plugin turns that into a menu item. Inside Painter, the artist chooses Miris > Publish, names the asset, picks a destination, and uploads. The plugin exports OpenUSD with OpenPBR materials, and it handles UDIMs (multi-tile texture layouts) and multiple texture sets up to 10 GB.
Nothing gets downsized on the way out. No matter if your asset is 8MB or 800MB, assets upload at full resolution, and Miris builds the streaming version once.
For you, the developer, the practical change is the handoff. Instead of a zip file and a request to "make it work on mobile," you get an asset ID and a viewer key.
Putting it on a page: two tags
The fastest path is the Components API, a set of web components. Add a script tag, a viewer key, and the asset ID:
<script type="module" src="https://unpkg.com/@miris-inc/components"></script>
<miris-scene viewer-key="VIEWER_KEY">
<miris-stream uuid="ASSET_ID"></miris-stream>
</miris-scene>
That's the whole integration. Prefer a package manager? npm install @miris-inc/components, then import "@miris-inc/components" registers the custom elements. Position, rotation, and scale are plain attributes:
<miris-stream uuid="ASSET_ID" position="0 5 0" rotation="0 1.571 0"></miris-stream>
The viewer key is safe to ship in client-side code; that's what it's for. It can be scoped by tag so a key only streams the assets you intend. Upload and management use a separate integration key, which never belongs in the browser.
Porcelain Horse Head asset streaming from a Miris account embedded with the code below. Open it in the Miris player.
<script type="module" src="https://unpkg.com/@miris-inc/components@0.0.8-f51dcbb/dist/components.cdn.prod.js"></script>
<miris-scene viewer-key="4YIGMPUj5-fL8n0jkp1kQpJktss_UaBDMW9jwJb08f4" style="display:block;width:100%;height:420px">
<miris-camera position="-1 0.25 1" rotation="-0.2450 -0.7702 -0.1724" controls></miris-camera>
<miris-stream uuid="b394b02d-7232-4b92-9bf3-2f687c9afbe0"></miris-stream>
</miris-scene>
Already have a Three.js app?
If you're building a configurator or a product catalog, you'll want the scene graph. @miris-inc/three gives you MirisStream, which extends Three.js's Group, so the full Object3D transform API applies:
import { WebGPURenderer } from "three/webgpu";
import { MirisScene, MirisStream, requiredLimits } from "@miris-inc/three";
const renderer = new WebGPURenderer({ requiredLimits });
const scene = new MirisScene({ viewerKey: "VIEWER_KEY" });
scene.add(new MirisStream({ uuid: "ASSET_ID" }));
Your camera and animation loop stay as they are. MirisScene is a regular Three.js Scene that holds the viewer key, so every stream you add needs only an asset ID. The one real change is the renderer: streams draw through WebGPURenderer, created with the SDK's requiredLimits.
Streams are ordinary scene objects. Put several side by side for a comparison view, rotate them individually with MirisControls, and move the camera with Three.js's own OrbitControls. To stop a stream, stream.removeFromParent() and cleanup runs automatically.
What to know before you try it
You'll get further faster knowing the edges:
- WebGPU is required. Streams draw through Three.js's
WebGPURenderer; aWebGLRendererdraws nothing. Without WebGPU,<miris-scene>only shows a short message instead. - HTTPS or localhost.
file://won't work, and the stream uses a WebSocket to*.miris.com, so corporate proxies need to allow it. - One viewer key per scene, for now. Every stream in a scene currently shares a key, so scope one key by tag to cover the whole scene.
- No animation. Miris streams static assets today, whatever format they start in.
- LOD is automatic. There's no API to request a specific fidelity level. That's the point, but it's worth knowing if you like control.
Try it
Sign up for the Miris Public Beta at app.miris.com/sign-up, upload an asset, and try streaming in minutes.
