Turn engineering models
into AR/VR-ready assets.
Upload a CAD or engineering model and Techcopter optimises, simplifies and prepares it for real-time AR, VR, WebXR and interactive use — without losing the parts that have to stay addressable.
Drop your model here
Read in your browser — nothing is uploaded, and nothing leaves this machine. CAD files are tessellated here too.
.GLB · .GLTF · .STEP · .STP · .IGES · .IGS
What a conversion costs.
Priced from the file rather than from a description of it: its size, how many parts the assembly holds, the geometry, and whatever material or level-of-detail work you ask for.
Small
Up to ~50 MB, low complexity
Ready in under a minute
Standard
50–250 MB, moderate assembly
Ready in 1–3 minutes
Complex
250–750 MB, detailed engineering model
Ready in 3–10 minutes
Large
750 MB–1.5 GB, large assembly
Ready in 10–30 minutes
Anything past roughly 1.5 GB is analysed before a figure is given rather than quoted from its size — a price on a file nobody has opened is a guess with a number on it.
Where this has got to.
- Reading .glb and .gltf in your browser — parts, triangles, materials, textures, extent and compression, measured from the file
- Reading .step, .stp, .iges, .igs by tessellating them with OpenCascade, also in your browser
- Keeping your part names, where the file carries them. An assembly export names each part and those names survive into the result, so it stays addressable part by part; a single-body export has only one name to give, and the rest are numbered. Repeated parts — the same washer used a hundred times — are numbered like a CAD tree, so each instance can still be picked out
- Pricing from those measurements, with the working shown
- Flagging what would stop parts being individually addressable before you pay for it
- Optimising, in your browser: duplicate data removed, geometry simplified toward a triangle budget, attributes quantized, optional merging and GPU instancing of repeated parts, meshopt compression — with the result measured from the file it produced, and the download alongside it
- Charging for it. Signed in, a conversion is priced from your file and the credits are held before the work is recorded and settled after — you are never charged more than the figure you were shown
- Identifying what the parts are. An assembly is mostly hardware — one real export was 964 parts of which 548 were washers, nuts and bolts. Reading the names tells us which is which, so the hardware merges into one object and the equipment is left alone. On a test assembly that took 120 objects to 11: no geometry tool can find that, because decimation reasons about triangles and this reasons about what a thing is for
- FBX and OBJ. These still need a reader that is not written, and listing them on an upload form before it exists would be selling something we do not have
- Texture resizing. It needs a native codec that does not run in a browser, and claiming a step that does not execute would be worse than leaving it out
- Draco output. It compresses better than meshopt, but ships no browser encoder — so an already-Draco file comes back larger, and the result says so rather than rounding it to zero
- Delivery beyond your own browser. The result is stored for your workspace, but nothing is emailed, published or handed to another system yet
- Very large CAD. Tessellation happens in your browser and needs roughly eighty times the file in memory — a 14 MB assembly of 964 parts took about 15 seconds and 1.2 GB. Past about 25 MB a tab is at real risk, and the page says so before it starts rather than after it has gone
When it does run, it runs unattended — there is no minimum wait, because there is nobody to wait for.