Runs locally No signup No watermark
Pixlane

Blur Faces in Video

Core access Supported local processing No Pixlane watermark AI on-device

Apply an elliptical blur to faces detected frame by frame by an on-device AI model, then review the result for missed or partial detections.

Frame-by-frame detection attempt

A WebAssembly face detector evaluates processed frames and can miss or lose a face during movement, occlusion, blur, or pose changes.

Elliptical, padded masks

Masks extend beyond detected boxes and use a soft elliptical clip, but coverage can still be incomplete; review hairlines, chins, and partially hidden faces.

Scoped local processing

Supported video contents are processed on your device and are not uploaded for processing; site analytics and the assistant are separate.

How to blur faces in a video

  1. Open the tool and add your video Select a compatible file for Blur Faces in Video.
  2. Review and adjust Choose a blur strength, process the clip, then review every section for missed, drifting, or partial face masks before export.
  3. Export and download Review the exported result from Blur Faces in Video, then download it.

Frequently asked questions

Does it track faces between frames?

The detector evaluates frames and may reuse recent boxes across short gaps. Tracking can drift or miss a face during occlusion, fast motion, or large pose changes, so review the complete output.

Why is there a 30-second cap?

Per-frame neural inference is heavy. Split longer footage with Trim Video first, then blur each part.

Can I choose the blur amount?

Yes: light, medium, or strong.

Will it blur faces that turn away or are partly hidden?

Detection is more likely to work on visible front or three-quarter faces. Turned-away, small, blurred, or occluded faces can be missed or only partly covered; use an appropriate blur strength and review every section.

Is this enough for GDPR or anonymization?

No compliance or anonymization guarantee is provided. The tool can assist with face masking, but you must review the full result, correct missed or partial masks, and confirm that it meets your legal and publishing requirements.

How to verify a Blur Faces in Video export

Treat the page preview and the downloaded file as separate evidence. Use a representative clip, keep the untouched source, and record the result that the task actually requires before changing any control.

  1. Before processing, note the source container, video and audio codecs when known, duration, dimensions, frame rate, orientation, audio-track count, and intended destination. Also record the exact cut, crop, timing, visual correction, or extraction you expect. These observations create a baseline for comparing the export instead of relying on memory.
  2. Run a short representative sample first and change one setting at a time. Browser codec support, available memory, hardware acceleration, and input structure can affect which processing path is available. A successful preview for one sample shows only that observed case; it does not establish compatibility for every file with the same extension.
  3. Inspect the preview around the portions most likely to expose defects: the beginning and final frame, cut boundaries, rapid motion, fine text, faces, object edges, gradients, orientation changes, and any section where sound should align with a visible event. For model-assisted tools, look for missed regions, unstable masks, invented detail, or frame-to-frame drift.
  4. Open the downloaded file in a separate current player rather than reviewing only the in-page preview. Confirm that it starts and ends where expected, plays through without an unexpected stall, and has the intended duration, dimensions, orientation, frame rate, audio presence, and synchronization. Check the file again in the platform or editor that will consume it.
  5. Compare the exported clip with the untouched source at the same viewing scale and, when useful, matched playback volume. Look for unexpected crops, padding, stretch, softness, banding, halos, color shifts, temporal jumps, repeated or missing frames, and changes in file size or codec that matter to the destination. Decide whether any difference is acceptable for the stated task.
  6. If the result is missing, fails to play, or differs from the preview, first confirm that the source opens independently. Reload the page, retry with a small controlled sample, reset optional controls, and preserve the exact on-page message. Testing one controlled change at a time makes browser, input, setting, and destination failures distinguishable.
  7. Record the Blur Faces in Video URL, relevant settings, browser and device, date, source identity, output filename, and observed checks. Keep before-and-after files when the result matters. This record supports a reproducible comparison later and avoids treating a changed input, capability, or destination requirement as the same run.