Screen recording for client feedback: a faster lane than Loom

The most useful clip in any client relationship is the one where they show you what they mean. Five seconds of pointing at a button. Thirty seconds of walking through a mockup. A minute of narrating a bug.

In 2026 most of us have a tool for making that clip — Loom, CleanShot, the macOS shortcut. What most of us don't have is a clean way to receive one.

This post is about the inbound side. Same idea as Loom, opposite direction.

The "show me what you mean" problem#

You're working with a client. They want a change. The change is visual, or interactive, or behavioral — the kind of thing that takes three hundred words to describe and ten seconds to show.

You ask them to "send me a quick recording." What actually happens:

1. They try to remember if Loom is the one that needs an account.
2. They click around their menu bar looking for the screen recording shortcut.
3. They record something, then can't find the file.
4. They figure out the file is in ~/Movies/Screen Recordings/, drag it into Gmail, hit the 25 MB attachment limit, swear, and either don't send it or send a degraded version.

Or, more often: they give up and write a paragraph that doesn't actually answer your question.

The friction is on the wrong side. The person making the recording is the one who has to figure out where it lands. Their incentive to keep trying is low, because they're doing you a favor.

Why Loom (outbound) and email screenshots are the wrong shape#

Loom is excellent at what it does. It is the outbound primitive — you are recording, they are receiving. That's why every Loom share is one-way and the receiver doesn't need an account.

The shape doesn't reverse cleanly:

• If you ask your client to "send me a Loom," they need a Loom account. Account creation kills 30–50% of inbound flows.
• If they don't make one, they record on their built-in OS tool and hit the attachment-size wall.
• If they upload to WeTransfer or Dropbox, you've added two more steps and now the recording is detached from any project context.

Email screenshots are the worst of the bunch — static, no audio, no pointer movement, no clue what state the screen was in before the shot.

What you actually want is the opposite of Loom: a single link your clients hit, the browser captures their screen + voice, the clip lands in your inbox tagged by sender, no install on their side.

One link, anyone hits Record, no account