How to Share 3D Renders With Clients Without Downloads
A 4K walkthrough render can easily run to several gigabytes, and a download link is the wrong way to send it. Here is how I share 3D renders with clients so they open one link and watch.
A 90-second walkthrough render exported at 4K in a high quality codec can easily come out at 3 or 4 GB, and on a 30 Mbps office line that is roughly 15 minutes of downloading before your client sees a single frame. Then they spend a few more minutes working out whether VLC or QuickTime should open it, so the real cost of sending that file is the 20 minutes of friction you put between your work and the person paying for it, right, and your own upload time barely registers next to that.
So when people ask me how to share 3D renders with clients, I answer from the review side of the table, right, because I run PlayPause and also a video editing agency where our long cuts are every bit as heavy as an archviz walkthrough, and the file being a render instead of a talking head changes very very little about the problem.
And the short answer, to be very honest, is that you stop sending the file at all. You send a link that plays in the browser, with a password whenever the project is unannounced, and you keep the ability to switch that link off the second the scope or the relationship changes. At the end of the day that is the whole method, right, and the rest of this post is the detail underneath it.
How to share 3D renders with clients the usual ways
There are basically four routes people take, and each one breaks in its own way. Email dies immediately, because a still frame of an architectural rendering might squeeze through at 8 MB but a walkthrough never will, so you compress until the glass looks like plastic. A transfer service gives the client a download button and a countdown, and the file lands in their Downloads folder next to three other versions called final_v2_REAL.mp4.
A cloud drive feels like the grown up option and half works, since short clips may preview, but for a big ProRes export it often gives up and hands them the download button anyway. And an unlisted upload on a public video platform plays beautifully, except your unreleased hotel project now sits on somebody else's host and the notes land in a comment box that has no idea what frame 1,412 is.
For stills I would not overthink it, honestly, because high quality JPEGs in an email or a shared folder do the job. None of these routes are stupid, right, they were just built for moving files, and a walkthrough review needs a place where the client can watch, point at a moment and say yes. Once you separate review from delivery, most of the pain around how you send renders to clients stops being something you argue about internally.
You send 3 GB, the client waits, downloads, hunts for a player, then types notes into an email with no frame numbers.
They open one link, it plays right in the browser, and every note sticks to the exact frame it belongs to.
Why email and drive links fail for walkthroughs
A walkthrough is a different animal from a still, because it is long and heavy and the feedback on it is tied to moments in time. "The light looks wrong" is a useless note on a 90-second flythrough, right, because somebody now has to scrub the whole thing guessing which light and which second the client meant, and that guessing costs you a full revision round.
The catch here is that even when a drive preview loads, your client writes notes somewhere else, in an email or a WhatsApp voice note or a PDF of screenshots, and you end up doing the translation work. In my agency, notes that arrive over WhatsApp reliably double the length of the round, because half the round is just asking what they meant.
Then there is version drift, where you send MV1, start MV2 while they reply late, and someone in their office is still raising things on MV1 that you fixed on Tuesday. In PlayPause new versions stack on the same card, so MV1, MV2 and MV3 sit together instead of floating around as loose files, and on Agency and up you can compare two versions side by side, which is really really useful when the client swears the kitchen looked better before. If revision rounds are your real bleeding wound, my write up on cutting rendering revision rounds goes deeper.
Browser playback without downloads or installs
Here is the part that actually solves the problem. When you upload a render to PlayPause, we make a streaming copy for playback in the browser and your original file is never touched. The client opens one link and it plays, with no install and no account, which matters more than people expect, right, because the fastest way to kill a review is asking a developer's project manager to create a password just to look at a lobby.
Here is one concrete send, the way I would set it up for an archviz team, because it is the same flow we run for long cuts in my agency. Say you have a two-minute walkthrough of a four-bedroom villa that the client has not announced yet. You export the master at full quality, name it Villa_Walkthrough_MV1, and upload it into that client's project from the browser or the Mac or Windows desktop app. PlayPause builds the streaming copy, you put a password on the share link, and you email the link to one named contact while the password goes over a call, so the two never travel together. As the client watches they leave frame-accurate timestamped comments, and when a note is about a thing rather than a moment they draw on the frame, a circle around the ceiling detail, an arrow at the skirting and so on, with threaded replies and @mentions keeping the argument in one place.
There are two practical checks worth doing first. On Creator the maximum upload is 10 GB per file, which covers most walkthroughs, while Agency and Enterprise have no upload cap for heavier masters. And if you finish in After Effects or DaVinci Resolve, the loop is export, upload, review, and then you work through the notes back in your editor. If buffering on huge exports is your real bottleneck, I covered reviewing massive Lumion and Enscape walkthroughs separately.
Because the original stays untouched, your delivery file and your review file never drift apart, and when the client needs the master for their archive you hand it over deliberately once approval is done. Does that make sense, right, the review copy and the deliverable are two different jobs and most ways of sharing smash them together.
PlayPause plays a streaming copy in the browser for your client, while your full quality export sits untouched in the project.
Who-watched analytics help here too, from Creator upward, because you see who opened the link, when and from which city. So for instance, when a principal architect swears the client never looked, it is useful to know that three people watched it twice on Thursday night before you chase anyone.
Frame-accurate note, everyone sees the exact same thing.
Password protection and revoking a link instantly
Now the security half, which archviz people care about most, right, because you are usually sitting on a project that has not been announced. Every plan lets you put a password on a share link and revoke a link instantly, and between those two you cover almost every real-world scare you will have.
A password is for when the link is going to travel, because your contact forwards it to their investor, the investor forwards it to someone you have never met, and that is simply how approvals move. The password means the link alone is not enough to get in, which is why I send it through a different channel. Revoking is for the moment nobody plans for, when a project goes on hold or a contact leaves the firm and you want that walkthrough offline in ten seconds rather than ten emails.
Treat every share link like a door you opened on purpose, and close it the day the project stops needing it.
I'm pretty sure revoking is the most underused feature in this whole category, because people treat a share link as permanent by default when it should really be a tap you open and close on purpose. My longer thinking on securing a video review link covers the general case, and password protected review links for confidential footage covers the paranoid end of it. If your link keeps getting forwarded past the approval group, I wrote separately about stopping clients from sharing review links.
- Password on any project that has not been publicly announced
- Password sent separately from the link itself
- One named contact per link, so you know who to chase
- A revoke plan for the day the project pauses or the contact leaves
How long a share link should stay live
This is a real planning decision. On Creator share links live 30 days and then the files expire, on Agency links run 90 days, and on Enterprise links never expire, which maps almost exactly onto how projects behave, right, so pick your plan from the shape of your work.
A freelance visualiser doing three interiors a month does not need a link from February, so thirty days is fine, as long as you remember the files expire too and keep your masters in your own archive. A firm doing a residential tower, where the walkthrough is reviewed in March, revisited in June when the facade changes and pulled up in September for the sales suite, needs 90 days at least and probably links that never expire, because someone will ask for it a year later.
Pricing is flat per workspace rather than per member, so you are not paying per person to let a junior visualiser upload a test render. The step from Creator at $9 a month to Agency at $19 buys the longer links, unlimited upload size and unlimited projects, which for a busy archviz practice is usually the deciding line. The expiring share links page walks through expiry on each plan, and the sharing and security page lists what sits where.
Sharing under your own firm's domain
The last piece is presentation, which matters more for architecture practices than for most of my video clients. On Enterprise you get white-label and a custom share domain, so the review page sits at something like review.yourbrand.com, and when you are pitching against two other practices for a masterplan that detail quietly works for you, right.
Enterprise also carries SSO and SAML, which matters once your practice has an IT policy and your people already use single sign-on for everything else. If a client's security team asks how access is managed on your side, saying your internal members sign in through SAML based identity federation is a much shorter conversation than a password spreadsheet, and your external clients still comment without an account.
If you work with outside rendering partners, the same access logic keeps the chain clean, and on Agency and up a partner can push a new version through guest version upload, with their name and email collected, without becoming a member. I covered that side in outsourcing architectural rendering without losing control. The architectural visualization review page shows the flow end to end, getting client sign-off on a walkthrough is its own discipline, and for product rather than property, 3D product animation review is the closer read.
Frequently asked questions
Can a client watch a 3D walkthrough without installing anything?
They can, and that is the point of browser playback. PlayPause makes a streaming copy, so your client opens one link and it plays on a laptop, a tablet or a phone on site, with no account and no player to install. Your original export is never touched, so the file you deliver later is exactly the file you rendered, right, and nobody approves a squashed preview by mistake.
Should I password protect every render link?
I would not put one on every link, honestly. I put passwords on anything unannounced or under NDA, and on any link going to a contact I expect will forward it, whereas for a quick internal check with your own team it just adds a step. Password protection is on every plan, so you choose per link rather than paying extra for the option.
How long should a client review link stay live?
Match it to how long the project can realistically come back to you. Creator links run 30 days and then the files expire, Agency links run 90 days, and Enterprise links never expire. Short turnaround interiors are fine on 30 days, but anything a facade change or a sales suite might reopen months later belongs on 90 days or never.
What if the client wants the original render file?
Send it as the delivery, deliberately, once approval is done, and keep review and handover as two separate moments, because once a client has the master you lose track of which version is being shown around. On Agency and up, guest version upload also lets a client or partner push a file back into the project with their name and email collected, so the trail stays in one place.
If you want to feel this with your own render, every plan has a 7-day free trial, so upload one real walkthrough rather than a test clip and send the link to a client you trust. The PlayPause pricing page lays out what each plan carries, and trust me on any level, the first time a client leaves a note on frame 1,412 instead of writing that the light is off, you will not go back to sending files.
So yeah. That's my way of saying it.
Saumyajit co-founded PlayPause after years watching review and approval quietly eat creative teams' deadlines. He writes about the workflow side of video, feedback, versioning, and getting to a clean sign-off.
Related resources
Keep reading
Bring your team into one review space
Centralize feedback, lock approvals, and deliver faster, start free today.
Sign Up for Free