How to Collaborate on BIM Models Online — Live, Multiplayer, in the Browser

Open a real-time BIM coordination room in your browser. Invite teammates and external reviewers, comment on viewpoints together, drop 3D pins, and round-trip BCF 2.1 into any BCF-compatible coordination tool — no CDE license, no installs, no per-seat fees.

When people search for how to collaborate on BIM models online, most advice assumes you've bought a full common data environment (CDE) — thousands per seat per year. You don't need one to review a model together. BIMCamel has a Collaborate tab: open an IFC in a coordination room, invite anyone with a link, and track issues against the live 3D model, right in the browser. Free, no install, no per-seat licence.

What a coordination room is

A room is one model plus its issues and its people. You create it from any model in your workspace and seed it four ways: start empty, import an existing .bcfzip, pull the findings of a previous validation run, or reuse a BCF from your library. From that point everyone in the room is looking at the same model and the same issue list.

Getting people in — including people without an account

Invites go out as links or short codes, and each invite carries the role the joiner will get. Teammates with accounts land in the room from their own Collaborate tab. External reviewers — a client, a consultant, a subcontractor — join as guests with nothing more than a display name. No signup, no licence, and a guest only ever sees the one room you invited them to. If a room is sensitive, gate the invite with an email restriction or a password.

Four roles, so you control who can change what

Owner — full control, can delete the room.
Editor — authors topics, comments, and viewpoints, and can export.
Commenter — adds comments only.
Viewer — read-only.

Issues that carry their context

Every topic in a room carries a BCF viewpoint: the camera position, the selected elements, and a snapshot captured from the viewer. Each topic also shows up as a 3D pin in the model — click the pin to jump to the issue, or click the issue to fly the camera to its viewpoint. Topics track status, priority, assignee, due date, and a full comment thread, and @mentioning a member lands in their room notifications. This is the part a shared folder and a chat channel can never give you: the conversation lives on the model, at the exact spot it's about.

Reviewing together, live

Review sessions are live. Teammates' cameras, cursors, and selections stream into the room in real time, each person visible as a coloured camera frustum in 3D. Click a teammate to follow their camera — the "where are you looking?" phone call disappears.

It's real BCF, so nobody's locked in

The room's issue set is a genuine BCF 2.1 draft, not a proprietary format with an exporter bolted on. Import any .bcf / .bcfzip to seed a room, and export the room back to .bcfzip — or to a self-contained HTML report for people who only need to read it. Camera positions, selections, and snapshots survive the round-trip, so a topic authored in BIMCamel opens in your desktop coordination tool with the same view the author saw, and vice versa. Your data stays portable.

Straight from validation to coordination

Clash detection, IDS checks, and health reports all export their findings as BCF, which means a room can start from them. Seed a room from a validation run's findings, or push selected findings from the Validate tab into an existing room in one action. The clash that failed the check becomes a trackable, assignable issue with its viewpoint already captured.

A typical weekly coordination cycle

Monday. The architect drops an updated IFC into the workspace. Run Model Health Check on it first — if it's broken, flag it before every downstream reviewer wastes an hour on a bad file.
Diff against last week. Run Compare IFC between this revision and the last, so everyone knows the delta before they open the model.
Federate. Merge the structural and MEP files into one coordination model.
Clash check. Run Clash Detection on the federated model.
Open a room from the clashes. Seed a coordination room straight from the clash findings, assign each critical clash to a discipline lead, and invite them by link.
Meet in the room. Walk the issues live — follow each other's cameras, comment on the viewpoints, set statuses. Decisions get logged on the model, not lost in a chat scroll.
Export. Send the resolved subset out as .bcfzip for anyone still on a desktop tool.

Good habits that still apply

A room doesn't replace basic discipline, and a plain file-share or chat channel is still handy for the paperwork around a project:

Keep a clean file convention. Consistent discipline / revision names save everyone from opening the wrong model.
Scrub before you invite outsiders. Use Delete IFC Properties to strip internal notes, cost estimates, or contractor names, and Fix Broken IFC External Links to remove references to files on your internal drives, before a client or external reviewer joins.
Hand non-BIM stakeholders a lightweight view. If someone can't handle IFC at all, Export to 3D (glTF) and send the GLB — it opens in any web 3D viewer with no software.

Where a full CDE still wins

If you need formal approval workflows, document control with audit trails, or deep integration with scheduling and cost systems, a full CDE is still the right tool. But for looking at the same model, talking about the same issues on the same viewpoints, and round-tripping the result as standard BCF — small teams, students, and early-stage coordination don't need to buy one. Open a room and get everyone on the model.