Chrome capture
Blur webpage elements before recording
Choose page elements in the Chrome extension before you record. The blur stays on those elements during capture. This workflow does not inspect a finished video.
See Chrome recordingRedact sensitive information before you share the video.
Give your team three ways to keep sensitive information out of shared recordings: blur webpage elements before capture, place manual masks in the web editor, or start automatic redaction for the text categories your company selects.
1
Eligible MP4
Recording is complete
2
Owner starts scan
Supported text patterns
3
Review masks
Opaque, permanent output
What is Zight video redaction?
Zight video redaction helps teams hide sensitive information before sharing a recording. You can blur webpage elements in Chrome before capture, add manual masks in the web editor, or start post-recording detection that covers supported sensitive text with permanent opaque masks. Contact Zight to enable the account-level workflows.
Choose the right workflow
Redact before or after you record.
Use the fastest method for the information you need to hide, then review the final video before sharing.
Company configured
Detect sensitive text after recording
The video owner starts redaction on an eligible MP4. Zight detects supported text patterns selected in company settings and covers matches with permanent opaque masks.
Enable automatic redactionAccount enabled
Place manual masks in the browser editor
Add timed blur, pixelation, or black-box masks to a completed video in Zight’s web editor. Contact Zight to discuss enablement for your account.
Enable the web editorAutomatic sensitive-text redaction
Record, start redaction, and review the result.
-
1
Record in Zight
Capture the workflow you need to explain. For webpage content you already know should stay hidden, use Chrome element blur before recording.
-
2
Start redaction
After recording an eligible MP4, the video owner starts redaction. Zight checks for the sensitive-text categories selected in company settings and follows matches as the screen moves.
-
3
Review and share
Zight covers detected text with permanent opaque masks. Review the processed video, then share it with the intended audience.
Automatic detection starts when you ask for it
The video owner starts redaction after recording. Zight then handles detection and mask placement for the supported categories selected by the company.
Supported detection categories
Choose the sensitive text your company wants covered.
Configure the supported categories for your workflow. Review the processed video because detection can miss content or place a mask incorrectly.
- Email addresses
- Phone numbers
- Payment card numbers
- Social Security numbers
- AWS access key IDs
- Selected API keys and secrets
Where redaction fits
Remove what the viewer does not need, then control the audience.
Customer support
Remove account details, tokens, or contact information from a troubleshooting recording before it moves into a ticket or escalation.
View Zight for customer supportProduct and engineering
Protect credentials and test-account details in bug reports, demos, and technical handoffs without replacing the full recording.
View Zight for engineeringHealthcare and regulated work
Add redaction to a broader approved workflow. Detection does not replace access controls, retention rules, review, or your organization’s compliance process.
View Zight for healthcareTraining and documentation
Review names, notifications, account data, and open tabs before a recording becomes an onboarding resource or reusable guide.
View Zight for training and onboardingIncoming video replies
Use Request Video to collect customer recordings without requiring an account or install. Review each reply before it moves into a ticket, escalation, or reusable answer.
Explore Request VideoRedaction reduces what is visible in the exported video. It does not replace recording with sample data, access controls, retention settings, legal review, or a final human check.
Review checklist
Watch the full output before you share it.
Automated detection can miss content or cover the wrong area. A final review checks the actual pixels and the complete timeline.
- Watch at normal speed, then inspect dense screens frame by frame.
- Check the first and last frame of every mask as content moves or scrolls.
- Look for open tabs, notifications, filenames, avatars, and spoken sensitive details.
- Confirm the intended audience, download permissions, and retention settings.
- Keep the original restricted according to your organization’s policy.
FAQ
Video redaction questions
Contact Zight to discuss enabling post-recording video redaction and browser-editor masks for your account. Your company can select the supported sensitive-text categories used by the automatic workflow.
Zight supports email addresses, phone numbers, payment card numbers, Social Security numbers, AWS access key IDs, and selected API keys or secrets. Detection can miss content, so review the processed video before sharing.
Automatic redaction covers detected text with opaque masks. For manual editing, the browser editor supports blur, pixelation, and black-box masks through account enablement.
No. The video owner starts redaction after recording. Zight then detects and covers supported sensitive text. It does not automatically process every upload.
No. The current workflow requires the video owner to start redaction after an eligible MP4 is recorded. If you want automatic redaction for recordings collected through Request Video, tell us how your team collects replies and what sensitive information needs to be covered.
Chrome blur is a separate capture-time workflow. It hides selected webpage elements before and during a Chrome recording. It does not inspect the pixels of a completed video.