Step Player

This is the site's signature tool, and it shows exactly what a knot's own page shows: a rotatable 3D model of the rope, with the written steps underneath it. Pick a knot here, or arrive from a knot's own page, and you get the same thing either way.

Each knot is a real path through space rather than a picture of one. Drag to turn it over, scroll to zoom, and step through the tie one numbered stage at a time — the model builds up as you go, because every step is the same rope revealed a little further. That means a step cannot show you something the finished knot contradicts.

Flat line drawings were tried here twice and withdrawn twice. Both times the failure was the same: in a drawing, which strand passes in front has to be decided by hand, and that decision kept being wrong — the second attempt shipped an overhand knot with two crossings where the real knot needs three. A model has no such decision to get wrong, because the crossings fall out of the geometry. Each one is checked before it ships: that the rope never passes through itself, that the knot shows the crossings it actually requires from most angles, that anything meant to thread a loop genuinely does, and that no two knots are the same shape under different names.

99 of the 100 knots have a model. The marlinspike hitch does not, and shows its written steps instead — it exists only while a spike traps the rope against itself, which the model cannot hold. Turning a knot over is the point of all this: most tying mistakes are depth mistakes, the end going in front when it should have gone behind, and that is the one question a flat picture can never settle.

How to actually read one. Start at the last step, where the knot is finished, and turn it until you can see which strand lies on top at each crossing - that is the knot. Then step back to the beginning and watch those crossings appear in order. Most people find the sequence makes more sense backwards the first time and forwards every time after. If a step looks impossible, rotate rather than assuming the model is wrong: a crossing seen edge-on can read as a strand passing through itself when it is doing nothing of the kind.

What the machine checks cover. Before any model reaches this page, four things are verified. The rope must never pass through itself - measured as the smallest distance between any two parts that are not neighbours along the same rope, which has to stay above one rope diameter. The knot must show the crossings that knot genuinely requires, tested from two hundred viewing directions rather than one, because a knot seen edge-on can look far simpler than it is. Anything that threads a loop must be shown genuinely passing through it, measured as a signed crossing of the loop's own spanning surface - a rope draped over a bight and wrapped round its legs looks convincingly tangled and is not a bend. And no two knots may ship as the same shape under different names.

What they do not cover. None of that proves a knot is the knot it claims to be. Geometry can clear every check and still be threaded the wrong side of a strand - a granny instead of a reef. The checks catch the failures that have actually shipped here; a person looking at the render is what catches the rest. Where a model could not be made honestly, the page says so and shows the written steps instead, which is the case for the marlinspike hitch: it exists only while a spike traps the rope against itself, and nothing here can hold that.

On a phone. Drag with one finger to turn, pinch to zoom, and use the numbered buttons rather than trying to scrub - they are sized for a thumb. The model stops rendering entirely once you scroll past it, so it costs nothing to leave the page open while your hands are busy with rope.