You’ve finished the model — a building, a road corridor, a structural detail, doesn’t matter — and now you need the client to actually look at it and sign off. Except the client doesn’t own Revit, has never heard of AutoCAD, and the last thing you want to do is talk them through installing a 90-euro viewer over the phone. This comes up constantly, and there are a few decent ways to handle it depending on how polished you want to look and how sensitive the work is.
The wrong instinct, and the one most people reach for first, is to take a pile of screenshots and paste them into an email. I get why — it feels safe and it’s fast. But it almost never ends there, because the client always wants to see the one angle you didn’t capture, and then you’re trading emails back and forth rendering views on demand like a short-order cook. A 3D model is interactive by nature; flattening it into stills throws away the whole point and creates more work, not less. So let’s skip that and look at the approaches that actually respect everyone’s time.
The simplest thing that works
Export the model to a web-friendly format, send the file, and include a link to a browser-based viewer. The client downloads the file once, opens the link, drags the file in, and can spin it around on whatever device they happen to be holding. No install, no licence, no setup — and crucially, nothing for you to support over the phone.
For the export, reach for GLB if you possibly can. It packs the geometry, the materials and the textures into a single file, it’s small enough to email without anyone’s inbox complaining, and it loads quickly in a browser. Revit can spit it out directly, and Civil 3D work can route through Blender or 3ds Max to produce a clean one. If GLB isn’t an option for some reason, FBX is a fine second choice — bigger, but still self-contained. OBJ I’d avoid for this specific job, because the materials live in a separate file and you’ll end up sending a zip with loose texture images, which is exactly the kind of fiddly thing that confuses non-technical clients.
If you’d rather the client clicks nothing
Some clients won’t even download a file — they want a link that opens straight into a spinning model and nothing more. For that you’re looking at a hosted service like Sketchfab or Autodesk Viewer, where you upload the model once and send a viewing URL. One click for them, zero file handling.
The catch, and it’s a real one, is that the model now lives on somebody else’s server. For a public-facing concept that’s fine. For confidential client work it’s worth two minutes reading the platform’s data-retention policy before you upload, because “where exactly is this file sitting and who can reach it” is a question that occasionally comes back to bite people. Both services do offer private models behind a login or password, though Sketchfab’s private hosting sits behind a paywall.
The polished, on-brand version
If sharing models with clients is a regular part of your work rather than a once-a-year event, it’s worth setting up properly: the viewer running on a page you control, branded with your firm’s look, with the model embedded right there. The client gets a single tidy link on your own domain — no third-party logos, no “powered by” footer, just your work presented the way you’d want it presented.
On WordPress this is genuinely not much effort. A viewer plugin plus the model file hosted on your site (or on something like Cloudflare R2 if the files are large) gets you there, and after the one-time setup it’s just a shortcode on a page. The Buildref viewer is available exactly this way if you’d rather not build one from scratch. It’s overkill for a single project but pays for itself quickly if you’re sending models monthly.
A few things that’ll save you a follow-up email
Whatever route you pick, a handful of small habits prevent the most common back-and-forth. The big one: always open your own exported file in a viewer before you send it. It takes ten seconds and it’s how you catch the classic disasters — Civil 3D exporting the thing on its side, Revit quietly dropping the materials, the model coming out at a thousand times its real scale. Better you find it than the client.
Beyond that, it’s worth trimming the file down if it’s enormous — a dense mesh from a scan can be decimated in Blender or Meshlab, and your client on hotel Wi-Fi will thank you for not sending a 200-megabyte download. Toss in one screenshot as well, not instead of the model but alongside it, so that someone glancing at the email on a phone with terrible signal at least gets the gist. And one short sentence about orientation — “the entrance faces you when it loads” — heads off the inevitable “which side am I looking at” reply before it happens.
None of this is complicated once you’ve done it once. The whole point is to make the client’s side effortless — they click, they see the model, they approve it — while keeping your side to a quick export and a short email. Get that loop tight and a chunk of project friction just quietly disappears.