Record
Record your screen right in your browser.
Private by default·Only people with your link can watch
Capture
Record your screen, make quick edits, and share a private link in minutes. Your video stays private while uploading, and we only process it when you choose to create a share link.
Accidentally recorded personal data?
No problem, we cannot see your recording anyway.
1Capture
2Trim & cut
3Share link
Screen recording is not supported on this device/browser. Use a modern desktop browser.
How it works
Edit
Trim and prepare your video.
Create link
When you are ready, create your share link.
Copy
Copy the link with one click.
Share link
Send it to anyone who should watch.
How your data stays private
- Your recording is private by default.
- Only people with your link can watch it.
- Your video is protected while it uploads and while it is stored.
- Want details? The technical explanation is in the FAQ below.
What happens when you share
- Your video is prepared on our server so sharing is fast and reliable.
- We only do that work after you choose to create a link.
- When processing is done, temporary key material is discarded.
- For full technical details, see the FAQ below.
Why server-side editing today
Coming soonWe currently do editing and final packaging on the server because it is faster and more reliable across devices today. A full local-only mode is planned. Tradeoffs: uploads may happen later in the flow and editing in-browser can be noticeably slower, especially on lower-power devices.
Security FAQ
Can you read uploaded chunks?
Raw upload chunks are encrypted in your browser with AES-GCM before upload. Storage only sees ciphertext plus IV metadata, not plaintext frames.
What happens technically when I create a share link?
The app posts your encryption key to the finalize API, which stores it in Redis under a one-time key reference with a short TTL (default 300 seconds), then queues a worker job. The worker consumes the Redis key once (read + delete), decrypts uploaded chunks, applies edits/conversion, re-encrypts final playback assets, and zeroes key buffers in memory after processing.
Can you recover a lost key?
No. There is no key recovery flow. If the `#k=...` fragment is lost, playback/decryption is not possible.
Where is the decryption key?
In the URL fragment (`#k=...`). Browser fragments are handled client-side and are not included in normal HTTP requests to the server.
Is this strict end-to-end encryption?
Not strict E2EE during finalization: a trusted server worker briefly decrypts to run edits/conversion, then re-encrypts output. At rest and in transit, recording data remains encrypted.
What if I close the page before creating a link?
No finalize job is queued, so no share-ready output is produced. Uploaded chunks remain encrypted blobs and are automatically deleted after the retention window (7 days), or sooner if you delete the recording manually.