Local by default
Your screen stays on your machine unless you deliberately send it somewhere.
Independent, and small
Recording should not need an editor afterwards
Clipio started from one irritation: every screen recording needed a second pass in a video editor before it was watchable. Zoom in so the UI is legible. Smooth the cursor. Cut the twelve seconds where nothing happened. Same work, every time.
What we decided to build
If the editing pass is the same every time, the recorder should do it. So Clipio records what the cursor did and where it clicked, and uses that to write the first draft of the edit — zooms that follow the work, a cursor that moves like it was animated, the idle stretches flagged for cutting.
The important part is the word draft. Every one of those decisions lands on the timeline as an ordinary keyframe you can drag, retime or delete. A tool that guesses and then refuses to be corrected is worse than one that does not guess at all.
Why it started on Windows
Because that is where the gap was. The good screen recorders — the ones that make a tutorial look designed — have mostly been Mac-only for years, and Windows users were choosing between a bare capture tool and a full video editor.
Clipio now runs on both, from one codebase. The renderer has no platform-specific code at all; only the capture layer dispatches, taking DXGI on Windows and AVFoundation on macOS. The editor, the effects and the export path are the same code on both sides, which is why a feature does not have to be built twice.
Why it runs on your machine
Screen recordings are a strange kind of file. They contain whatever was on your screen — internal tooling, customer data, a Slack thread you forgot was open. Uploading them to a stranger's server as a matter of course is a bad default.
So capture, editing, transcription, OCR, sensitive-info detection and export all run locally. The only time a file leaves your machine is when you press Share, and even then it goes to your Google Drive rather than to us — we host nothing, which is also why we cannot lose anything.
Where it is now
Early access, free, and honest about it. The app is genuinely usable — people are recording real work with it every day — and there are also rough edges, a changelog with a “what's coming” tab, and a bug report button we actually read.
If you use it and something is wrong, tell us. At this size, one clear report from one person changes the next release.
2platforms, one codebase
3capture tools, three editors
0files uploaded unless you share
Freeduring early access
What we hold to
Four rules that have settled more product arguments than anything else.
Automatic, then editable
Every automatic decision is a keyframe you can override. Nothing is baked in.
Fast enough to use
A native capture path and an FFmpeg export. A recorder you wait on is a recorder you avoid.
Say what it actually does
The changelog lists what is missing next to what shipped. Overselling costs more than it earns.
Try it on your next recording.
Free during early access, on macOS and Windows.