Frame.io Review Link Not Working for Your Client? Five Causes and Fixes
A client call derailed by a Frame.io review link that would not open taught me the five usual causes. Here is the tree I run through now, and how each fix looks in PlayPause.
The Frame.io review link I sent for MV3 of a 90-second launch film was not working for the client, right, and I found out in the first minute of the call, when their head of marketing said she had clicked it and landed on a sign-in page. This was back when my agency still ran client reviews through Frame.io. Her boss had clicked the morning email she forwarded and got a blocked page from his company's web filter, and the third person, on her phone in a cab, could see the player but had nowhere to type a comment.
We burned 25 minutes of a 30-minute call on that link, and the notes finally came in as a WhatsApp voice note at 9 pm, the worst format there is for notes on a cut. To be very honest, almost none of it was the tool's fault, because when I traced it back, the link I resent at 3:55 was my address bar URL instead of the share link, the morning link was one I had reused from an internal round with comments switched off, and I had never asked whether their office network allowed that domain.
So this is basically the troubleshooting tree I wish I had open on that call, the five things that stop a client from opening, playing or commenting on a review link, and how I fix each one while the client is still on the line.
The five reasons a Frame.io review link is not working for a client
When a client says the link doesn't work, that sentence tells you almost nothing, so I first turn it into a better question, which is where exactly it stops. A link that won't open, a video that won't play and a missing comment box are different problems, right, with different fixes. If the link also fails for me in a private window with no login, the problem is on my side, and if it works for me, it lives somewhere in the client's account, network or device.
Almost every case I have seen lands in one of five buckets, an account or app wall, a link that has expired or been revoked or sits behind a mistyped password, a file too heavy for the browser, a corporate network or a phone getting in the way, and a link that plays but won't take comments. The same buckets keep coming up in threads on Frame.io's community forum and on Reddit, which tells me most of these failures start with how the link was made and sent.
Two complaints from those threads look like a broken link when the link itself is fine, right. If the client can watch but a download stalls, often in Safari on a Mac, that is a download problem, so I suggest a second browser and ask whether they need the file at all. If the thing failing is the review panel inside your own editing software, that lives on your machine and has nothing to do with the client, and if the service itself is down, I check the vendor's status page and send a plain review file for today.
The first reply I send is one line saved in my notes app: "Sorry about that, does it stop at a sign-in page, at a spinning player, or does it play with nowhere to comment?" Most of the time the answer points straight at one bucket, and the client feels looked after instead of blamed.
When a review link asks the client to log in
The sign-in page is the most common one in my agency, and it usually comes from the sender, right, because the URL in your address bar inside a project points into your workspace, which is supposed to ask for a login. The share link is a separate URL made for outsiders, and on a busy afternoon the two look similar enough that you paste the wrong one, which is exactly what I did at 3:55.
The URL in your browser while you work inside a project points at your workspace, so it will always ask an outside client to sign in.
The second version is the invite, where an editor adds the client as a team member, and now the client has to create an account and verify an email that can sit in a corporate quarantine folder for an hour. That invite can also cost you, since Frame.io prices from $15 per user per month, while PlayPause is flat per workspace. The third version is the app prompt, and a client on a managed company laptop usually has no admin rights to install anything, so they close the tab and tell you it doesn't work.
This is the bucket we built PlayPause around. The client opens one link in a browser with no account and no install, clicks the exact moment that bothers them and leaves a comment that sticks to that frame, or draws on it, which is the whole idea behind our client review portal. I wrote about reviewers who don't edit in a director's cut for a non-technical artist, and my roundup of review apps for clients puts the main options side by side.
A client who hits a login wall closes the tab and tells you the link is broken, and from where they sit that is a perfectly fair thing to say.
Expired, revoked or password protected links
The next bucket is links that worked and then stopped, and usually the link is doing exactly what it was set up to do, right, it's just that nobody told the client. On PlayPause the lifetime comes from the plan, so it is worth knowing the numbers before a client back from holiday clicks a five-week-old email.
On Creator, share links run for 30 days and the files expire with them, which suits fast social work and bites on slow corporate work, for instance a brand film where legal sits on MV2 for six weeks. Agency gives you 90 days and Enterprise links never expire, so if your clients are the slow kind, the plan is really really a troubleshooting decision as much as a pricing one.
Revoking is the one I cause on purpose, since every plan lets me switch a link off instantly and I kill the MV2 link the moment MV3 goes out. The catch here is that the client still clicks the old MV2 email on Monday and gets a dead page, so I reply in the same thread with the new link and one line saying the older link is off on purpose. The revoke and password controls are on our sharing and security page.
Passwords fail in small, silly ways, right, a trailing space picked up while copying, an iPhone capitalising the first letter, or the password sitting in the same email as the link and getting forwarded around. I send the password through a different channel, the full setup is in how to password-protect a review link, and I compared when a password is even the right protection in Vimeo private links versus passwords.
Files too heavy to play in the browser
This one shows up when the link is really a Drive or Dropbox link to the master file, and the client gets a preview that spins forever, right, or a 38 GB download button. A ProRes master is enormous by design and most browsers won't play it, and phone footage is often recorded in the HEVC codec, whose browser support is still uneven, so a clip that plays on your Mac can show a black box on the client's Windows laptop.
The quick fix is exporting a proper H.264 review file, and I walk through the options in sharing large video files for review. The better fix is never putting the original in front of the client's browser at all, because streaming players start quickly by pulling small pieces instead of one giant file, which is the general idea behind HTTP Live Streaming.
a huge original that stalls, refuses to preview or turns into a download on the client's laptop
the client plays a streaming copy in the browser while the original file stays untouched
On PlayPause I upload whatever I have, the original is never touched and the client's browser plays a streaming copy, which is what our proxy and transcoding page is about. Creator caps a single upload at 10 GB while Agency and Enterprise have no cap, so big ProRes masters mean Agency, or a review export on Creator.
Corporate networks and phones
Corporate networks are where I have learned to stop troubleshooting on the call, because neither the client nor I can change their firewall. Web filters block streaming video or unfamiliar domains, and some email security tools rewrite every incoming link through a scanner, which is how one person gets a blocked page while everyone else watches fine.
The test that settles it is the client opening the same link on their phone with Wi-Fi off, right, because if it plays on mobile data, the link is fine and the office network is what's blocking it. You see what I mean here, the fix has moved from your link to their IT team, and I'm pretty sure a custom share domain like review.yourbrand.com, which PlayPause offers on Enterprise, is an easier allowlist request than a vendor domain IT has never heard of.
Phones fail in a different way, and the big one, right, is the in-app browser, where a link tapped inside WhatsApp, Instagram or LinkedIn opens in a cramped built-in view, so I tell phone reviewers to choose open in browser. Then there is the train with two bars of signal against a raw 4K file, and so on. A PlayPause link plays in the phone's browser with nothing to install, while our mobile app is for my side of the work, uploading from the camera roll, changing statuses and sending share links.
When the client can't comment on the review link
This is the one from the cab, where the link plays but there is nowhere to leave a note. Usually the link was made view only or with comments off, like my reused internal link, and the fix is a fresh share link with commenting on. If a fresh link still fails, I ask for a screenshot, because an ad blocker or an ancient browser on a locked laptop shows up in five seconds that way.
On PlayPause every plan includes frame-accurate timestamped comments, range comments, drawing on the frame, threaded replies and @mentions, all from the link without an account. On Creator and up, who-watched shows who opened the link, when and from which city, and Slack posts every comment to a channel, so if the client opened it an hour ago and Slack is silent, I message them before they message me. Does that make sense, right, you find the problem before the client does.
A link check to run before you hit send
All of this is cheaper to prevent than to fix live, so every client link in my agency gets a two-minute check, which beats the 25 minutes I burned on that call.
- Opened in a private window with no login
- Played on a phone over mobile data
- Comments switched on and tested with one note
- Expiry date later than the client's likely reply
- Password sent separately and typed, not pasted
- Streaming copy plays, not the raw master
Run that check against my launch film call and the private window would have shown me the sign-in page on the 3:55 link, while one test comment would have exposed the reused internal link. The only thing it misses is the boss's web filter, which is why I now ask new corporate clients at kickoff whether their office blocks streaming sites. Trust me on any level, the phone test matters most because it catches three buckets at once, and writing "this link is live until 14 October" in the email turns an expiry from a mystery into a reminder.
For a first link from scratch, getting a shareable review link walks through it. At the end of the day the client's attention should go to your cut, right, and the link should be the part they never have to think about.
Frequently asked questions
Why does my Frame.io review link ask my client to log in?
Usually the client was sent the wrong URL, either the address bar link from inside the project or a team invite, and both are meant for people with accounts, right. Create a proper share link, open it yourself in a private window, then send it. If a genuine share link still asks for a login, check its settings and the vendor's help pages.
Why does my Frame.io share link work for me but not for my client?
You are almost certainly still signed in, right, so your browser quietly lets you through a wall the client hits head on. Open the link in a private window with no login, then on your phone over mobile data, and you will see what the client sees. If it plays there, ask the client where exactly it stops.
Why can my client watch the video but not comment on the review link?
Almost always the link was created view only or with comments switched off, often because it was reused from an internal round. Make a fresh share link with commenting on and leave one test note from a private window before sending it. If it still fails, ask for a screenshot, since an extension or an outdated browser is usually the culprit.
Can a client review a video link on their phone without installing an app?
On PlayPause the link opens in the phone's browser with no account and no install, and playback runs from a streaming copy, so it copes with mobile data far better than a raw file. My one tip is opening it in Safari or Chrome rather than inside WhatsApp or Instagram, because those built-in browsers are where most phone problems start.
If your clients keep telling you the link doesn't work, send your next cut through a link they can open in any browser without signing up for anything, and see whether those messages stop. Every plan on our PlayPause pricing page starts with a 7-day free trial, so you can run it on a real client round first.
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