BIM viewer navigation: explore your models

In a coordination review, the camera is your cursor. For every property you check or clash you flag, you make dozens of camera moves — orbit, pan, zoom, reframe. You navigate a model roughly ten times more than you do anything else to it, which makes navigation fluency the difference between a review that covers three storeys in an hour and one that gets lost in the first corridor.

This guide covers every way to move through a model in the free browser viewer: the three core camera gestures, the faster ways to change vantage, and the tools that go past the camera entirely. If you haven't opened a model yet, the step-by-step tutorial gets you to that point first.

Orbit — circle the model

Drag with the left mouse button held down: the camera swings around the model while it stays put. Orbit is the move for understanding a single place — circling a steel-to-concrete junction to see all four faces, tilting above a roof to read the drainage falls, coming down to eye level to judge how a space will actually feel. Slow, small orbits around a suspect detail reveal more than any static screenshot of it.

A habit worth stealing from experienced coordinators: never judge a clash from one angle. Two elements that overlap from the front may clear each other by half a metre in depth — orbit a quarter turn before you write anything down.

Pan — slide across the model

Hold the right mouse button and drag: the camera slides sideways, up or down, without turning. Pan is the move for traveling — following a duct run along a corridor, stepping down a facade bay by bay, tracking a gridline across a slab, all at a constant zoom so your sense of scale never resets. If orbit is for understanding one spot, pan is for patrolling between spots.

Zoom — close in on the detail

Roll the scroll wheel forward to move in, back to move out. The productive pattern is a rhythm, not a level: zoom out to establish where you are, pan to the area in question, zoom in hard to read the detail — the gap between a pipe and a beam flange, the seating of a lintel — then out again before moving on. Sitting at one fixed zoom level for a whole session is the single most common habit that makes reviews slow.

Close-in inspection pairs naturally with selection: once you're near, click the element and its attributes, property sets and quantities open in the panel. Geometry tells you where; properties tell you what.

Change your vantage — Fit view, the tree, selection

Manual flying is the slowest way to get anywhere. Three tools reposition you faster:

Fit view reframes everything loaded — the reset button for "I've lost the building". With a federation open it frames all models together, which makes it the natural first and last click of every review pass.

The model tree is teleportation by structure. Instead of flying up to level 3, expand the hierarchy — site, building, storey — and work from the storey's branch: click a row to select an element and light it up in the scene, and use the eye icons to blank out every level you're not reviewing. The tree turns "somewhere in this building" into "third item under storey 03".

Selection anchors you. Click an element in the scene — it highlights and its data opens — and you now have a fixed visual reference to orbit around while you examine everything near it. When the question is about data rather than geometry, skip the scene entirely: the properties explorer searches a whole model's element data without rendering a single triangle.

Navigation by subtraction — isolate, hide, show

In a dense mechanical room the camera alone can't save you: from any angle, forty pipes stand between you and the valve you care about. The coordinator's trick is to stop moving the camera and start removing geometry. Select what matters and click Isolate selection — everything else vanishes. Or invert it: select the obstruction and click Hide selection. When you're done, Show everything restores the full scene in one click.

Those three buttons turn an unreadable MEP federation into a sequence of readable questions — one system, one storey, one clash at a time. In the second half of a serious review they get used more than any camera gesture, especially with several disciplines loaded (and if a federation you build on screen needs to become a single file, that's IFC Merge's job, not the camera's).

Section planes as navigation

A section plane is a way of traveling through a building without moving the camera: enter the mode, click the model to place a plane, then drag its arrow and watch the interior sweep past the cut — storey by storey, bay by bay. For inside spaces it beats any amount of orbiting through walls. Sections have enough depth — placement, pairing with measurements, documenting clearances — that they get a dedicated guide.

Navigating on a touch screen

On a phone or tablet the mapping is: one finger drags to orbit, two fingers drag to pan, pinch to zoom. The tree and properties live in a bottom sheet pulled up from the edge of the screen, so panels and gestures never compete. Reviewing on a tablet at the site hut is entirely workable — just keep federations light there, since mobile browsers get less memory and the viewer warns earlier about combined model size.

Habits that make reviews fast

Five habits, each one earned in real coordination sessions:

Work by storey, from the tree. Hide every level except the one under review. Vertical disorientation is how people get lost in 3D; removing the other floors removes the problem.

Isolate before you measure. A distance taken in a clean, isolated view lands on the edge you meant. One taken through visual clutter often snaps to geometry you didn't notice was in front.

Snapshot as you go. The moment a finding is framed, hit Save PNG snapshot. Reconstructing the same view tomorrow costs far more than capturing it did.

Esc is your exit. It cancels a measurement in progress and leaves whatever mode you're in; while a mode is active, the red trash button clears all planes or measurements in one go.

End whole. Finish each question with Show everything and Fit view, so the next question starts from a complete scene instead of yesterday's leftovers.

None of this needs a license or an install. Open one of your own models and run each move once — ten minutes of deliberate practice is enough to make navigation disappear as an obstacle, which is exactly what it should be.