Skip to content
All use cases
video

Anonymize CCTV footage, irreversibly and automatically

Upload your surveillance recording, select faces and license plates, and download a version where every identity marker is permanently erased on every frame. The blur is re-encoded into the video — not an overlay — so it cannot be removed or reversed, keeping you on the right side of GDPR.

Anonymizing CCTV footage means permanently destroying the pixels that identify people — faces, license plates, and any other visual PII — on every frame of the recording, then writing a new video file that retains the scene context while making individuals unidentifiable. Done correctly, the result is irreversible and legally defensible under GDPR.

This page explains why surveillance video requires a different approach from standard face blur, how automated detection outperforms manual redaction at scale, and when your organization is legally required to anonymize before sharing or retaining footage. Start anonymizing a clip now — no account needed.

Why surveillance video is a special case for GDPR

CCTV footage is personal data the moment it captures an identifiable person. Under GDPR, retaining it beyond the minimum necessary period, sharing it with third parties, or using it for purposes beyond the original collection intent all require a legal basis — and that basis is hard to maintain indefinitely.

Anonymizing the footage changes the legal picture: truly anonymous data falls outside GDPR scope, meaning it can be retained for evidence review, analytics, staff training or incident reporting without ongoing data-subject obligations. The critical word is truly — regulators and DPAs have been explicit that reversible blurs, mosaic overlays that can be lifted, or low-resolution substitutions do not qualify as anonymization.

How automated CCTV anonymization works

Medianonymizer runs two coordinated processes on each uploaded file:

  1. AI detection scans frames for faces and license plates, producing bounding-box coordinates for every identified region.
  2. Deterministic blurring via ffmpeg applies a Gaussian blur to each bounding box and re-encodes the result frame-by-frame into a new video file. No mask is stored; no original layer is preserved.

Between frames, a geometric tracker interpolates positions to maintain stable coverage even when a face turns, is partially occluded, or the footage is motion-blurred — the common failure modes of per-frame detection alone. The output video is structurally identical to the input (same scene, same timestamp overlay if present) except that identifying regions are gone at the pixel level.

Why automated beats manual redaction for CCTV

Manually redacting faces in surveillance footage is impractical at any meaningful scale:

  • A one-hour recording at 25 fps contains 90,000 frames. Keyframing a blur across them by hand is measured in days, not hours.
  • Humans systematically miss faces in corners, reflections, crowds, or fast motion — the exact frames most likely to leak identity.
  • Most video editor "blur" effects are non-destructive overlays that sit on top of the original, meaning the source file still contains the unblurred frames.

Automated detection and tracking resolves all three problems: every frame is checked, background faces are caught, and the output is a new encoded file with no recoverable original layer.

Real situations where organizations anonymize CCTV footage

  • Retail incident reports — a store shares footage with insurers or legal counsel after a slip-and-fall. GDPR requires that uninvolved shoppers visible in the same clip are not disclosed unnecessarily. Automated blur covers all bystander faces while leaving the incident scene intact.
  • Public sector and local government — councils and transport operators publish anonymized clips for public-interest transparency reports (road safety analysis, crowd management reviews) without exposing identifiable citizens.
  • Security contractors and facilities management — service providers hand back archived footage to client organizations or dispose of it at contract end; anonymizing before transfer removes the data-subject obligations from the receiving party.
  • Research and AI training datasets — academic institutions and technology teams need video data for pedestrian detection or behavior analysis models. Anonymizing the source footage avoids the consent burden for each individual in the dataset.

In all cases the footage remains useful — the scene geometry, timing, and event sequence are preserved — while the personal data is gone.

Don't overlook the audio track

CCTV systems with microphones capture spoken names, addresses, card numbers, and other PII that faces and plates do not cover. A surveillance clip where every face is blurred but a name is spoken clearly is not fully anonymized under GDPR. Medianonymizer can beep or mute identified PII segments in the audio within the same job, so you are not left with a visually clean video that leaks identity through sound.

Anonymize your CCTV footage now

Upload a clip, select faces and license plates (and audio redaction if needed), confirm the exact price, and download an irreversibly anonymized file. No account, no subscription — pay only for what you process.

Frequently asked questions

Can the blur on CCTV footage be reversed to recover the original faces?
No. Medianonymizer re-encodes the pixel regions containing faces and license plates directly into a new video file. There is no mask layer or separate track sitting on top of the original — the identifying pixels are destroyed during encoding. A reversible overlay placed in a video editor is not true anonymization; our deterministic pipeline eliminates that risk entirely.
Does blurring CCTV footage satisfy GDPR obligations?
Irreversible blurring of direct identifiers — faces and license plates — removes the personal data from the footage, which is the core requirement. To take surveillance video fully out of GDPR scope you should also address any spoken names, numbers, or other PII in the audio track. Medianonymizer can blur visuals and redact audio in the same job, so the whole file is treated consistently.
Which video formats from CCTV systems are supported?
Common surveillance container formats including MP4, MOV, MKV, and WebM are supported. Output is delivered as a standard MP4. If your NVR or DVR exports a proprietary format, convert it first to MP4 or MKV using free tools such as HandBrake or ffmpeg, then upload.
Can I process multiple CCTV clips in one go?
You can run several uploads in parallel by submitting each clip in its own browser tab — there is no queue and no account required. For high-volume workflows such as end-of-day batch exports from multiple cameras, contact us about API access for programmatic processing.
How is CCTV footage priced?
Video is priced at €3.00 per job plus €0.05 per minute of footage. You see the exact total before you confirm payment — no subscription, no account, no hidden fees. A typical 30-minute camera recording costs €4.50.

Related use cases