Best for
developers, technical founders, educators, and support engineers recording API walkthroughs.
Privacy-first redaction
Hide an API key in a demo video
Cover API keys, bearer tokens, secrets, environment variables, and auth headers in screen recordings before publishing.
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
- API keys
- Bearer tokens
- Environment variables
- Request headers and logs
Redaction risk checklist
- Blur can leave short tokens readable
- Terminal history may repeat secrets
- Generated thumbnails can capture one exposed frame
Export review
- Search the recording for repeated terminal lines.
- Pause on the first and last frame of each secret.
- Never rely on blur for credentials.
Workflow
- Load the demo video.
- Cover every token region instead of lightly blurring it.
- Add redaction through the full timestamp range.
- Rotate exposed keys before publishing if needed.
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.
Should I blur or cover API keys?
Use a solid cover for API keys and secrets. Blurring is not enough for credential safety.
What if the key was already recorded?
Treat it as exposed and rotate it before publishing the video.