Best for
developers, technical educators, support engineers, and founders sharing coding walkthroughs.
Privacy-first redaction
Hide source code secrets in a screen recording
Cover tokens, environment variables, internal URLs, repository names, and private code comments in development recordings.
Edit and preview locally for free. Pay only when the redactions are placed and you need the downloadable PNG or WebM export; only the code is sent to the license service, never the media.
Buy only when the file is ready
Use the free workspace to place redaction boxes first. The $19 Pro export is for the moment you need to download the cleaned screenshot or recording for a client, support thread, public tutorial, bug report, or team handoff.
What to check
- Tokens and environment variables
- Internal URLs and hostnames
- Repository and branch names
- Private comments, logs, and terminal history
Redaction risk checklist
- Secrets can appear in autocomplete or terminal history
- Editor tabs may expose private repositories
- One visible frame can compromise a credential
Export review
- Pause around terminal commands and autocomplete.
- Check editor tabs, sidebars, and debug panels.
- Never rely on blur for credentials.
Workflow
- Load the recording.
- Use solid timed regions over every secret.
- Add new regions when the editor or terminal moves.
- Rotate exposed credentials before publishing.
Why local processing matters
BlurClipAI's first version runs the redaction workflow in your browser, which keeps raw media off our servers and makes it easier to handle private demos.
Does BlurClipAI scan code for secrets?
No. You identify and cover the sensitive regions manually.
What should I do if a secret was recorded?
Treat it as exposed and rotate or revoke it before sharing the recording.