Client Side Forensic Utility With Zero Data Upload
Free Surveillance Video Tamper Check
Find out what an exported security camera clip can prove before you rely on it. The footage never leaves your computer. This tool is in beta.
Beta
Open the tamper check workbench
Drag a rectangle over the burned in timestamp on the first decoded frame. The region is saved as a fraction of the frame and recorded in the report.
The players, the frame views of the tested window, the executive triage and every layer of observations appear here once you choose a clip or load the sample. Your footage stays on this device.
The check reads the vendor protection the export carries or lacks, the keyframe and timing structure across the whole clip, the compression traces inside the frames where the timeline points, and the on screen clock, then writes it all into a report you can hand to counsel.
Choose the exported clip and what came with it
Select the clip you were given. When the custodian also provided the native export, the proprietary player file or an earlier copy, add it as the reference. The workbench hashes the supplied bytes, reads the container and track records, scans every encoded packet in the file for its type, size and timing, decodes a contiguous frame window where you point it and crops the clock region you mark from every window frame. Nothing is uploaded; the parser and the page are the only things that download.
Zero Upload Local Browser Processing
Supported containersMP4, M4V, MOV, WebM, MKV, TS, MTS and M2TS, plus Dahua DAV exports and raw H.264 and H.265 streams decoded by GDF readers in your browser; Hanwha SEC, Genetec G64x and Avigilon AVE identified but not decoded
Size limit2 GiB per clip, whole clip packet scan, 60 seconds and up to 120 frames per examined window
EngineMediabunny container reader or GDF DAV and raw stream readers, browser WebCodecs decoding, GDF frame and motion tests, and ExifTool 13.59 on a header copy
The container is identified from the file bytes, not the extension. Frame decoding depends on the codec and your browser; HEVC varies by device and proprietary wrappers have no browser decoder, so those files return the container identity, the file hash, the vendor named for verification and the string scan, with frame work marked unavailable.
Start with what the export can prove
A cut that was reencoded with new, evenly spaced time stamps leaves no gap in the frame timing, so the check also follows how things move from one frame to the next across the tested window. It reduces each frame to about 160 pixels wide, matches small blocks of the picture against the frame before, and removes the camera’s own pans, tilts and zooms so that only movement inside the scene remains. When a person or vehicle jumps off the path it was following between two frames, or part of the scene changes at once while the frames on either side move normally, the check lists a break in motion with both time stamps, a Show me button that opens the frame after the break beside its difference from the frame before, and a point on the clip timeline. A break in motion is a place to look, not a conclusion: sharp pans, recordings that start on motion, dropped frames and reencoded cuts all disturb motion, so a break is raised to high interest only when the frame timing or the burned in clock breaks on the same pair of frames, and its thresholds were set on synthetic test footage rather than measured on real recordings.
Every clip also passes through ExifTool, the same metadata engine behind our Free Metadata Analyzer, once the main check has finished. ExifTool never receives your whole file: the tool builds a header copy in your browser with the encoded frames and sound replaced by small placeholders, keeps every structure record ExifTool reads for metadata, lists what was removed and records the SHA 256 of the copy beside that of your original. The container dates are compared across the movie, track and media headers; a difference of whole hours and a date left at zero are explained as ordinary, while a modification time earlier than its creation time, a track date days from the movie date, two creation records that disagree or a writer name that belongs to editing software are listed as leads to compare with the recorder’s log.
The stream layer also reads every track’s edit list, the instructions in an MP4 or MOV file that tell a player which parts of the encoded stream to show. Software can trim or cut a clip through an edit list without reencoding a single frame, so the check reports a trim at the start or end, an empty stretch after the footage begins, a clip assembled from several pieces and any change of playback rate, each with times in seconds and a Show me button; the skipped footage stays in the file, and a start offset of a frame or so is treated as ordinary.
Dahua DAV exports are decoded on your device by a reader GDF wrote from the published description of the DHAV frame format, so the packet scan, the frame tests and the clock layer run on them as they do on an MP4. The check also reads the date and time the recorder wrote into every frame header and lists any place where that clock jumps ahead, runs backwards or falls behind the frame timestamps, and sets those moments beside the burned in clock when you mark it. Decoding a DAV file is not verifying it, so the export protection card still names Dahua SmartPlayer as the place to check the recorder’s watermark. Raw H.264 and H.265 streams with no container are decoded the same way; because they carry no timestamps, the tool numbers their frames at the declared frame rate, or at 25 frames per second when none is declared, and treats every timing result on such a file as frame order that cannot show a gap.
Every flagged time in the stream structure, the frame tests and the clock reading has a Show me button, and the clip timeline works the same way: select a marked point, or move between points with the arrow keys and press Enter, to open that frame in the view that fits. When a flagged time falls outside the frames you tested, the tool offers to move the window there and runs only the frame tests and the clock reading again. The sample is a training clip with planted edits, including a clock jump at 3.5 seconds.
Every surveillance manufacturer protects footage somewhere, and almost none of them protect the convenience export. Axis signs each frame inside the video stream itself and publishes the method, ONVIF defines a signed export format and a signed stream, Ring now embeds content credentials in cloud downloads and Avigilon Alta ships a signed hash set beside its clips. Those the check can find and report. Hikvision, Dahua, Hanwha, Bosch, Milestone, Genetec, Avigilon ACC and Exacq protect footage only in their native containers and verify it only in their own players, and in every documented case the MP4 or AVI they export for convenience carries none of it.
When your clip is one of those, the export protection card says so plainly and names the native format and player to request from the custodian, which is also the position of the Scientific Working Group on Digital Evidence: the proprietary export is most likely the best evidence and the open format a secondary copy. A missing signature is not an edit. It is a reason to ask for the original before anyone argues about the copy. When the answer to that question matters to a deadline, a senior examiner can tell you on a free first call exactly what to demand and how to preserve it.
Read the stream before the pictures
An encoder writes a rhythm into a recording. Keyframes arrive on a schedule, the frames between them are smaller and roughly alike in size, and presentation timestamps step forward at the recorder's cadence. The check reads that rhythm across every packet in the file without decoding a single frame: keyframe spacing and where the group of pictures length changes, the packet size profile and where it steps, presentation intervals and gaps, repeated and missing timestamps, and parameter sets that change mid stream.
A keyframe that lands exactly on a cadence break is reported as a coincidence worth examining, in those words, because that is where a cut joined to a re encode tends to leave its seam. Surveillance recorders often run at a variable frame rate and interrupt recording on motion, so an irregular interval is a question for the custodian first and an indicator second. The timeline chart shows the whole clip so you can see whether the irregularity is everywhere, which points to the recorder, or in one place, which points to the place to look next.
Test the frames where the timeline points
Lossy compression leaves a fingerprint in every block of every frame, and an edit disturbs it. Choose a window on the timeline and the check decodes the frames in it and runs the tests examiners run by hand. The discrete cosine transform map shows the compression energy in every 8 by 8 block, so a region that was blurred, painted over or pasted in shows as quiet against a busy scene; flat walls, dark skies and the privacy masks recorders add are quiet too. Video error level analysis recompresses the decoded frame at a fixed quality and amplifies the difference; a region that responds unlike its surroundings is a lead for an examiner to test, not a sign that it was edited, because edges, text and the encoder's own blocks respond strongly too.
Noise extraction, the pseudo color palette and the clipping map support those two, and for a fixed camera the temporal tests show every pixel that never changes across the window and every pixel that departs from its own average, which is how a static patch laid over moving footage gives itself away. Each view carries its exact parameters into the report. These are the tests Doug Carner built into VideoCleaner and the research behind them is cited below; the implementation here is GDF's own. Compression and a careful editor can both defeat them, so a quiet view is not a finding that nothing was edited. When a region matters to a matter, media authentication by an examiner is the next step.
Treat the on screen clock as evidence
The burned in timestamp is the one record on the frame that the recorder wrote at the moment of capture. Mark it once and the check crops it from every window frame into a strip, measures how much the region changes from frame to frame and compares that against the presentation timestamps. A clock that holds still while the scene moves, or changes more or less often than the stream clock says it should, is reported with the frames where it happens. The clock check also measures how much of the marked clock changes at each tick. A normal tick redraws the last digit or two, so a change that redraws far more of the clock at once is listed as a larger than usual clock change. The digits are still not read, so a roll over at the ten minute or hour mark can do the same thing and a jump that changes only the last digits is not detected; look at the frames on either side and read the clock yourself. Some recorders write the clock only on keyframes, so the strip is read beside the structure table rather than alone.
Compare against the native export when you have it
When the custodian provided the native export or an earlier copy, the check aligns the two on reduced frame descriptors and reports the relative playback rate, the matched runs and the regions in either file that find no match. Unmatched content can be an addition, a removal, a crop, a re encode or a different camera view, and the report says which of those it cannot distinguish. The comparison does not make the reference authentic; it tells you where the two recordings disagree so the examination can start there.
Your files and reports remain local
The selected clips, file names, hashes, decoded frames, the clock region, notes and report data never reach a server. Optional usage measurement stays off unless you allow Analytics. With permission it sends GDF only the tool name and fixed action labels, such as analysis completed or report prepared, never an input, result, filename or visitor identifier. Google and advertising scripts do not load on this page. Use Cookie settings below to change your choice. Program files, the parser and fonts download from this website; nothing about your footage travels with them.
Clear cancels active work and removes the displayed records without deleting your original or any report you saved. Saved reports can contain private file names, hashes and notes; review them before sharing.
Try it with AI, offered in beta under the results, runs a small language model on your own graphics processor after you confirm a one time download from this website of about half a gigabyte. The model receives only the numbered observations and the methods text of your check, is instructed to restate them in plain English without adding a fact, and answers questions about them. Every sentence it writes is shown in a labelled box as generated text, is excluded from the findings table, the triage and the PDF, HTML and CSV reports, and is never a finding that footage is authentic or edited. Current Chrome or Edge on a desktop with WebGPU is required, and the check and its reports stand without it.
Save the report
Download the PDF or HTML report in the Global Digital Forensics four section layout: the executive triage and file identity with the full SHA 256, the plain English interpretation guide, the structured findings inventory with every observation located by timestamp and layer and your notes, and the evidentiary scope advisory with the beta notice. The Excel ready CSV gives one column per field and the JSON is the lossless record of hashes, container and track observations, the packet scan, the export protection result, frame test parameters, the clock region and its readings, reference alignment and coverage. The PDF and HTML reports carry reduced copies of the frames, the applied view and the clock strip as figures; no report contains the video itself.
Formats and resource requirements
Containers, codecs and proprietary wrappers
MP4 and M4V belong to the same container family, MOV holds QuickTime video whose codec decides whether frames can be decoded, and MKV and transport stream frames can often be inspected even when a player refuses them. Dahua DAV, Hanwha SEC, Genetec G64x, Avigilon AVE and AVK, Exacq PS and Milestone XProtect exports are identified from their bytes or extension, named with the vendor player that verifies them, and otherwise returned with the file hash and the string scan only. Raw H.264 and H.265 streams without a container are recognized; frame decoding of a raw stream is outside this reader.
ProRes has no browser decoder, HEVC depends on the device, and WMV and FLV are outside the reader. Keep original footage unchanged: renaming an extension cannot add a decoder, and converting a working copy changes its bytes and its SHA 256.
AVI files open locally. Motion JPEG and uncompressed 24-bit or 32-bit RGB video support frame analysis. For other encodings, you can see the stream information and the SHA-256 of the original file. AVI playback times come from frame order and the declared rate.
Each clip is limited to 2 GiB and four million coded and displayed pixels; the clip is hashed in 8 MiB parts and the container is read in place, so a large export never has to fit in memory. The packet scan covers the whole clip up to 200,000 packets, and NAL unit scanning for signed video markers covers the first 20,000 packets of an H.264 or H.265 track. Each examined window is at most 60 seconds and 120 frames, the clock strip follows the window frames, and the operation time limit is 120 seconds per stage, with up to 128 more seconds for each GiB while the clip is hashed. Limits stop work with an explanation rather than a shortened result. When the page opens it tests for hardware graphics acceleration and, once a clip is read, for a hardware decoder for its codec; when either is missing the workbench says so, because the check still runs in software but frame tests and views take longer and a long window can reach the time limit.
Coverage is recorded, not assumed
Every result states what it examined. The packet scan records how many packets it read and whether it reached the end of the file, the frame window records its decoded frames and where it stopped, the export protection card records which markers it searched for and that none is validated in this version, and the clock strip records the region and the frames it was read from. Detection accuracy on real world surveillance footage has not been measured by GDF, so an unavailable, cancelled or quiet result is unknown rather than a finding that nothing was edited.
Metadata and structure are never relied on in isolation. Keep the original and its collection context, work on copies, and bring the observations that matter to a case to an examiner who can test them against the recorder itself. Tell us about a problem with the tool; the link attaches no selected file or report.
Related tools and methods
Video Forensics gives the manual frame workbench with fifteen inspection views and Video Analyzer the guided workflow with optional local models; reselect your clip there, because inputs are never placed in links. Photo Forensics applies error level and noise analysis to still images, and Metadata Analyzer reads the properties of a wider range of files. When a matter turns on the footage, expert witness services begin with a full examination.
Versions and methods
Local container parsing uses Mediabunny and browser decoding is described in WebCodecs. The export checks follow the ONVIF export file format, the ONVIF media signing specification, the Axis signed video framework and the C2PA specification. The frame tests implement the analysis described in the VideoCleaner user guide and the research it cites, with the SWGDE video authentication practice as the frame for every result. These references describe the methods; they do not certify this tool. Version 1.3.0 beta. All free tools. © 2026 Global Digital Forensics, Inc. All rights reserved.
Free consultation
Does a surveillance clip need a full examination
When the structure breaks in one place, the clock holds still while the scene moves or a frame test lights a region that matters, a senior examiner can tell you on the first call what the observations mean, which native export and recorder records to preserve and how to transfer them securely. Global Digital Forensics has supported counsel, auditors and security teams since 1992, and our examiners have testified in federal and state courts on video evidence. Your clip and report are never attached.
Beta tool and owner notice. Surveillance Video Tamper Check is in beta and is not a replacement for an expert's analysis. Its results are observations from automated checks and must not be presented in any filing, proceeding or report as evidence without review by a qualified forensic examiner. Global Digital Forensics makes no warranty as to the accuracy or completeness of these results and will not testify to them unless formally engaged to conduct a full examination.
We want to hear what worked and what did not. Send feedback on the beta; the link attaches no file or report.
Reviewed by Joseph Caruso, Founder, CEO and CTO, CISSP. Last reviewed .