The request makes sense from the client's side: they know Google Drive, it's free, and they keep the files. Nothing wrong with that. The trap is answering with a technical reflex ("sure, no problem") when a shared folder carries hidden costs, mostly for you. The good news: you can say yes to what the client needs without saying yes to the Drive folder.
What the client actually wants
When a client asks for a Drive, they're not asking for Google specifically. They're asking for three things: something simple to open, nothing to install or sign up for, and files they get to keep. The right answer meets that need, not the named tool. A well-made delivery page ticks exactly those three boxes: a link, no account to create, and a download they hold onto.
What a Drive folder costs your brand
A Google Drive folder is a Google interface, not yours. Your name shows up nowhere, your work lands in a grey list of files, next to the client's personal folders. At the exact moment they discover your delivery, nothing recalls who produced it. We dig into that gap in our piece on the raw link versus a delivery page in your brand: the container is part of the message.
Sign-off, tracking, expiry: what a shared folder doesn't give you
Beyond the look, a Drive folder strips you of three professional levers. No clear sign-off: the client picks through files with no approval step. No reliable tracking: you don't really know whether they opened and grabbed the delivery. And no controlled expiry: the folder stays open indefinitely, with access permissions that quickly become a headache (who has the link, who can edit, who re-shared it).
A delivery page gives all three back: a presentation that frames the sign-off, visibility on opens and downloads, and an expiry window you choose project by project. You deliver, then close cleanly, instead of leaving a shared folder hanging around forever.
How to say it to the client without friction
You don't need to refuse head-on. You reframe toward their need: "I'll send you a delivery page, you click, download everything and keep it on your side, no account needed. It's as simple as a Drive, just cleaner." Nine times out of ten it lands, because you're giving them the simplicity they wanted, minus the generic folder.
If the client really wants a copy in their own Drive too, no problem: they download from your page and file it wherever they like. You deliver in your brand, they archive their way, everyone's happy. To argue it in detail, our comparison of Google Drive alternatives lays out the differences point by point.
In short
"Put it on a Drive" is a request for simplicity, not a demand for a specific tool. Meet the need (easy to open, no account, files kept) with a delivery page in your name: you gain the brand, the sign-off, the tracking and the controlled expiry, and the client still keeps their copy if they want one.