Why Google Drive isn't built for video client review (and what to use instead)

Google Drive is a great place to store a video and a bad place to review one, because the comments live next to the file instead of on the frame they’re about — so the reviewer downloads the cut, watches it somewhere else, and sends the notes back through a different app entirely. Drive moved the file. It never ran the review.

For a lot of editors and small agencies, the default handoff is a Drive link plus a WhatsApp message. It feels free and familiar. It’s also where a clean job turns into three rounds of “which part again?” Here’s where it actually breaks, point by point.

Comments aren’t attached to the video

This is the core problem. In Drive you can leave a comment on a file, but you can’t pin it to 0:37 on the timeline. So feedback comes back as:

• “The bit near the start feels slow.”
• “Fix the text at around thirty seconds.”
• “The music is too loud somewhere in the middle.”

You then have to guess which frame each note means, scrub back and forth, and hope you matched them up right. Half the back-and-forth in a review isn’t the fix — it’s working out where the fix goes. A timestamped comment sitting on the exact frame removes that entire step.

Reviewers end up watching a downloaded copy

Drive’s in-browser player is unpredictable with real edit files. Large or 4K exports either sit on “processing” for ages, play back at a squeezed-down quality, or just push the reviewer to Download to watch properly.

The moment they download it, the review has left Drive:

• They watch in QuickTime or VLC, offline from any comment box.
• The notes come back over WhatsApp, email, or a phone call.
• That downloaded file becomes a stray copy that goes stale the second you export again.

A review only holds together when the watching and the commenting happen in the same place, in the browser, with no download and no account required from the client.

Versions turn into a pile of links

Every new cut is a new file, so the client collects edit_v2, edit_v3, edit_final as separate Drive links. Nothing tells them which one is current, so they comment on whichever they open first — often two versions behind. Drive’s “Manage versions” option keeps one link, but it’s buried, and there’s still no per-version comment thread, so you lose the history of what was said on which cut. (There’s a whole separate mess hiding in here — see how to manage video edit versions without the “final_FINAL_v3” chaos.)

There’s no real “approved”

Drive has no sign-off step. A “looks good, ship it 👍” in a comment or a chat isn’t tied to a specific version, so a week later nobody’s sure whether it was v4 or v5 that got the yes. When approval is recorded on the cut itself, that exact version is locked as the one everyone agreed on — and anything after it is clearly understood as a new request, not a re-do you’re expected to eat.

Access friction slows the whole thing down

Half of a Drive review is admin: “request access” emails, the wrong Google account, permissions set to “anyone with the link can view” but comments turned off. For an external client — who often doesn’t want to sign into anything — it’s just enough friction that they put it off, or reply “can you just WhatsApp it to me?” And now you’re back on WhatsApp, which breaks a review for its own reasons.

What running the review on one link looks like instead

The fix isn’t a more disciplined Drive folder — it’s a link built for reviewing, not just storing:

• One link, current cut opens by default. No hunting through versions.
• Comments land on the frame. The reviewer pauses, types, and the note is pinned to that timecode — or they draw straight on the frame for a visual note.
• No account, no download for the client. They click, watch in the browser, comment. That’s it.
• New versions stack under the same link, each with its own comment thread, so you can compare v3 against v4 side by side.
• A real approval closes the version, so “yes” means one specific cut.

Where price quietly forces you back to Drive

Here’s the trap. The proper review tools most people know are priced per seat — you pay again for every person who needs access. So editors ration it: they put the main client on the tool but leave the manager, the second reviewer, or the client’s client off the link. Those extra people get sent a Drive copy on the side to keep costs down. That side copy is exactly how a stale version gets approved and a round gets wasted.

A tool priced on storage instead of seats removes the reason to fall back to Drive at all — you can put everyone who has an opinion on the same link, on the current cut, for free. That’s the whole idea behind Editlock being priced on storage, not per person: a flat ₹ plan with unlimited free reviewers, timestamped comments, version stacking, and a clean approval, all on one link.

The short version

Keep Google Drive for what it’s good at — storage and backup. Just don’t run the actual review there. The comments aren’t on the frame, the reviewer ends up watching a downloaded copy, versions scatter into a pile of links, and there’s no real sign-off. Move the review itself onto a single link where the client can watch and comment in the browser without an account, and most of the back-and-forth disappears.

If your next cut is going out on a Drive link this week, start a project on the free tier and send that one on a review link instead — it’s enough to feel the difference on a single job.