For people who teach
Show them the part they can't see.
A lesson built on one model. Ordered steps, labelled points, and an animation that stops on the frame you want to talk about. Your student drags it around while you explain it.
That is the product, running here, not a screenshot. If it does not load you still get the image and the description.
What the visitor does
They stop being told, and start looking.
- Move through the steps in order, or jump straight to one.
- Orbit, zoom and look inside while a step is open.
- Read a labelled point without leaving the model.
- Answer a question and find out straight away whether they were right.
What you do
Four steps, and none of them is modelling.
Upload the model you already have.
Whatever your engineer, your supplier or your agency sent you.
Drop a point on each part that matters.
Write what it says. That is the whole editor.
Put the points in order.
That order is the lesson. Drag to change your mind.
Publish and paste one line.
Into your LMS, your intranet or your page. Republishing updates it.
What you bring
One model. That is the whole list.
If it already carries an animation, you can stop it on any frame and talk about that frame. If it doesn't, the steps work anyway.
Formats
glTF · GLB · USDZ · FBX
We tell you the weight before your students find out.
Before you get your hopes up
Three things it is not.
It won't model anything
It shows what you bring. If the part you want to explain isn't in the file, it isn't in the lesson.
It is not a video
Nothing is pre-rendered. Your student can look somewhere you didn't plan — that is the point, and it is also the risk.
It won't rescue a heavy file
A 400 MB model is a bad lesson on a school laptop. We say so before you publish, not after.
The same in all three
The parts you shouldn't have to ask about.
It works without 3D
Every page carries the image and the description in the HTML. If WebGL is off, the tab is throttled or the engine never arrives, your visitor still gets the point — and so does a search engine.
Nothing follows your visitor
No analytics, no cookies, no storage, and not a single request to anyone but RTSHOW.
One line in your page
The same snippet for all three. Publish again and your page updates; you don't touch the HTML twice.
It stays out of your CSS
The embed lives in its own shadow root. Your styles don't leak in and ours don't leak out.
One subscription, three doors
Same engine, different question.
You are not buying this one. You are buying all three, and using the one that matches the job in front of you.
Teach it once. Let them turn it over.
Not open yet. Leave an address and you hear from us once, when it is.