See real Clipy quality
Samples below. Not a marketing reel — actual recordings. Click play, judge for yourself.
Sample gallery
Four short clips covering the workloads people actually use Clipy for. Each plays in your browser at the original resolution — no re-encoding by us, no quality switcher hiding the truth.
UI walkthrough
Clicking through a product UI at native resolution — text in buttons, menus, and dropdowns stays crisp at every zoom level.
1080p · ~2.4 Mbps · ~18 MB / min
Code review
An editor at typical font size. The H.264 + CRF 28 combo keeps monospace glyphs and syntax colors readable without ballooning the file.
1440p · ~3.6 Mbps · ~27 MB / min
Slide presentation
Static slides with talking-head audio. Low motion means small files — most of the bitrate goes to your voice and the occasional transition.
1080p · ~1.6 Mbps · ~12 MB / min
Bug reproduction
Quick capture of a flaky interaction, mouse highlights, console output. Optimized for speed-to-link, not archival quality.
1080p · ~2.2 Mbps · ~16 MB / min
Encoding details — what you actually get
We picked settings that work across every browser and device on the web today. Here is the exact recipe:
- Video codec
- H.264 (libx264, ultrafast preset, CRF 28)
- Resolution
- Native up to 4K; auto-downscaled to a max of 2160p
- Audio codec
- AAC 128 kbps
- Container
- MP4 with +faststart (instant-start streaming)
- Why this set
- Balanced for screen-recording content — sharp text, low spatial complexity — at small file size with fast encode turnaround.
Recording quality vs file size
Every screen recorder picks a point on the quality / size / encode-time triangle. Clipy errs toward speed and crispness: the ultrafast x264 preset finishes encoding the moment you press Stop, and CRF 28 keeps text and UI elements legible without bloating the file.
For a typical 1080p UI walkthrough that lands around 2 Mbps — roughly 15 MB per minute of recording. A 5-minute Loom-style walkthrough is usually under 100 MB, well inside the limits of any email or chat tool. The tradeoff is that a slower preset would squeeze 20–30% more compression out of the same content; we skip that work so your share link is ready in seconds.
A future opt-in studio mode will swap in a slower preset for users who care more about archival size than speed-to-link — think tutorial creators uploading to YouTube, or anyone editing a recording afterwards. Until that ships, the current settings are the same ones we use ourselves.
Record yours and see for yourself
Three ways in. Pick the one that fits your workflow — same encoder, same quality on the other side.