A screen recording of your site looks flat on a feed. Kape gives it a background, rounded corners and a shadow — then does the parts other browser tools skip. A real timeline: cut the fumbled click out of the middle, not just off the ends. Filmstrip, waveform, frame-level zoom. Real encoding: every frame decoded from the source, never filmed off playback, so nothing drops. Audio stays in sync across cuts. Any shape: 16:9 in, 9:16 or 1:1 out. Free. No account. Nothing uploaded.
I built a site I was proud of, recorded it, posted it, and it looked flat. The recordings that do well all have the same things: a background, rounded corners, a soft shadow. The tools that do that well are paid native apps, so I built the version I wanted. Free, in a browser tab.
The interesting part came early. A browser will never tell you where the mouse is during a screen recording. getDisplayMedia hands you pixels and nothing else. No coordinates, no clicks. That's why the best tools in this space are native apps: they read the mouse straight from the OS.
So I built everything that doesn't depend on the cursor, and built it properly. Backgrounds, framing, crop, any aspect ratio out. A real timeline with a filmstrip, a waveform and frame-level zoom, so you can cut the fumbled click out of the middle instead of only trimming the ends. And an export that decodes every frame from the source rather than filming playback, which is what keeps variable-frame-rate recordings honest. Most screen recordings are variable.
Recording is next: a Chrome extension that logs the real cursor track, which unlocks zoom that follows the mouse. The editor is already built to take it the day it lands.
Free, no account, nothing uploaded. Tell me what it should do next.
I built a site I was proud of, recorded it, posted it, and it looked flat. The recordings that do well all have the same things: a background, rounded corners, a soft shadow. The tools that do that well are paid native apps, so I built the version I wanted. Free, in a browser tab.
The interesting part came early. A browser will never tell you where the mouse is during a screen recording. getDisplayMedia hands you pixels and nothing else. No coordinates, no clicks. That's why the best tools in this space are native apps: they read the mouse straight from the OS.
So I built everything that doesn't depend on the cursor, and built it properly. Backgrounds, framing, crop, any aspect ratio out. A real timeline with a filmstrip, a waveform and frame-level zoom, so you can cut the fumbled click out of the middle instead of only trimming the ends. And an export that decodes every frame from the source rather than filming playback, which is what keeps variable-frame-rate recordings honest. Most screen recordings are variable.
Recording is next: a Chrome extension that logs the real cursor track, which unlocks zoom that follows the mouse. The editor is already built to take it the day it lands.
Free, no account, nothing uploaded. Tell me what it should do next.