Switching
Google Drive alternatives for creative studios
Most studios don’t choose Google Drive so much as inherit it. The email is already Google, the calendar is already Google, so the storage arrives as another tile in the same grid, free-feeling and already logged in. We’re Vidual Spaces, and we build storage for photo, film and music studios — a small team working out of Oxford, with the files themselves held on EU infrastructure in Amsterdam. What follows is about the specific point at which Drive stops being convenient: the moment work has to leave the organisation it was so neatly connected to.
Everything that makes Drive comfortable for a studio’s own staff is a function of the Google organisation sitting underneath it: identities, groups, admin policy. That same machinery is what a client meets when the link arrives. They tap it and get an account prompt, or a request-access screen, or a polite refusal because the sharing scope was set by an administrator they have never met and cannot email. Sometimes it works and sometimes it doesn’t, and which of the two you get depends on whether the recipient happens to have a Google login and whether the organisation’s policy allows the link to reach beyond itself.
The connectivity that helps inside is a wall outside
For a studio, that lands squarely on the two moments the work is judged: the review, and the delivery. Every failed link becomes a message you have to write, a second attempt, a file zipped and pushed through a transfer service instead, and a client whose first thirty seconds with your work were spent fighting a login box.
A share from Spaces opens for anyone. It’s a tidy page under your own logo — and on your own domain from the Team plan upwards — that a visitor can look through, play and pull files from without an account, a login, or any nudge to create one. If you want the opposite of open, that’s available too: a share can be limited to particular email addresses, so it works for the people you had in mind and refuses anyone it gets forwarded to, each of them confirming their address once with a short code. A link that has served its purpose can be withdrawn, or given an expiry date that stops it working. The client portal pagecovers the client-facing side in full, and there’s a note in the Journal on named access if you want the reasoning behind it.
Private share
Shared by Oxbow Mastering
If tim@oxbow.audio was named on this link, a 6-digit code is on its way — check your inbox.
No code arriving? Whoever sent you this link decides who’s named on it — ask them to add you.
Where Drive genuinely wins, and where that ends
For live multi-cursor co-editing of its own document formats — two people typing in the same doc, cursors visible, no conflict — Drive is very good, and nothing here pretends otherwise. If a treatment or a shot list wants that kind of simultaneous drafting, that is the tool for it.
What that doesn’t extend to is the material a studio’s day is made of. Spaces stores documents perfectly well and reads what’s inside them, so a contract turns up later by the day rate written in it rather than by the filename someone typed in haste. And around the documents sit the RAWs, the cuts, the stems and the exports, where a general-purpose drive holds the bytes faithfully and leaves everything that comes after — the review, the notes, the versions, the sign-off, the finding it again — to you.
What the studio parts of the job become
| The job | On a general drive | In Vidual Spaces |
|---|---|---|
| A client looks at the work | A link that may ask for an account, a login, or permission from an admin | A branded page anyone opens without an account; your own domain from Team up |
| Notes on a still | An email saying “top left-ish, you’ll see it” | A note dropped on the exact spot in the frame, with arrows, boxes and freehand |
| Notes on a cut | A comment box beside the file; timecodes typed out by hand | Comments welded to the second, so a note left at 00:44 is still at 00:44 tomorrow |
| Notes on a mix | Download the stem pack to hear it properly | Plays at full fidelity, drag over the waveform to set a loop, notes against the bar |
| A revision | A new file named final-final-v3 | Each version sits beside the one before it, and a note can be marked resolved once dealt with |
| RAW and camera files | A grey icon with a filename | CR3, ARW and the rest render in the browser as readily as a JPEG; no format allow-list |
| Did it arrive? | An email nobody wants to write | The share tallies opens and downloads as separate figures, and tells you when the first person arrives |
| Finding it eighteen months later | Whoever remembers the folder name | Search in ordinary words — what a photo depicts, the kit that shot it, the place, and the text held inside documents |
| An invoice’s due date, a contract’s renewal | In the file, if anyone reopens it | Read on upload, kept as a card on the file, and surfaced ahead of the date |
| Choosing between fifteen frames | A meeting, or the loudest voice | The team votes without seeing who picked what; winners tagged and gathered into their own folder |
| Bringing in a freelancer | Another account in the organisation | Unlimited team members on every plan — the bill is per storage tier, not per seat |
| Where the files sit | Varies | Amsterdam, in the EU, on Backblaze B2 — and no model, ours or anybody else’s, is trained on what you upload |
If the comparison you’re really running is against Dropbox, we’ve set that out separately in Dropbox alternatives for creative studios, and pricing shows the per-seat arithmetic side by side. If what you use today is a transfer link, the same goes for WeTransfer.
The paperwork is read on arrival
A studio’s storage holds paperwork as well as media — the contracts, releases, licences and invoices that surround every job — and Spaces treats them as more than bytes to keep safe. A PDF or a Word file previews in the browser like everything else, and search reads the text inside it, so an agreement surfaces by the counterparty’s name or the fee written in clause four long after the filename has stopped meaning anything. When the document is a contract or an invoice, Spaces goes further: it lifts out what the document says — the parties, the fee, the payment terms, the reference, and the dates that matter, from issue and due through expiry and renewal — and keeps it as a card on the file, in plain sight and yours to correct.
Those dates then work for you. A fortnight before an invoice falls due, a month and a half before an agreement ends or comes up for renewal, the date surfaces — in the app and in a weekly email, each time saying which document it was read from. The register of it all lives on one page, Noteworthy, split into what’s upcoming and what’s on the record; it assumes you’re on top of your work and saves you the lookup, and it can be switched off entirely if you’d sooner it said nothing. The reading happens on a model we run ourselves, and a document in a folder locked to its owner surfaces to that owner alone.
Common questions
Why do creative studios outgrow Google Drive?
Because a drive is built around keeping a library in sync, and a studio's week is mostly the things that happen to files after they're synced: whittling a shoot down, putting the result in front of a client, gathering what comes back, getting the nod, and turning the lot up again much later. Drive holds the bytes and leaves those parts to email, transfer services and memory. The pressure usually shows first at the client edge, where the link asks a stranger to log in.
What does Google Drive lack for photo, film and music workflows?
The media-native parts. RAW files from a camera don't preview like a JPEG, film isn't reviewed in a player that welds a comment to the second it's about, and a mix isn't heard at proper fidelity with a passage you can loop while the argument about it goes on. In Spaces those are the default: there's no allow-list of permitted formats, so WAVs, stems and project bundles live alongside everything else, and an upload arrives in pieces and picks up where it left off, so a multi-gigabyte export survives a flaky connection.
How does Vidual Spaces handle previews, approvals and versioning differently?
Previews are format-first — RAWs and vectors render where they sit, film runs in a review player, audio streams in full. Approvals happen on the file itself: a client marks the frame or the second they mean without making an account, your team's internal thread stays internal, and sign-off is recorded where the work is. Each version sits beside the one before it in the player, and a note can be marked resolved so the conversation keeps moving.
Why do people outside a company hit a wall with Google Drive share links, and what does that cost a studio?
Because Drive's sharing is anchored to the Google organisation and its admin policy: the recipient may need a Google account, and the link's reach may be limited by settings the sender doesn't control. The cost is paid at the worst moment — the review or the delivery — in re-sends, workarounds through transfer tools, and a client whose first impression of the work is an access screen.
What should a studio look for in a Google Drive alternative?
That a share opens for anyone with no account and tallies its own opens and downloads; that confidential work can be locked to named people and links revoked or expired; that RAW, film and audio are first-class formats; that feedback attaches to the frame, second or bar; that search reads what's inside the files, not the filename; that the paperwork's own dates — an invoice falling due, an agreement up for renewal — are read on upload and surfaced ahead of time; that the price moves with storage and not with headcount; and that you can name the jurisdiction your files sit in and take them out cleanly whenever you like.