Are these the same video? Free duplicate file checker

Are these the same video?

Choose two video files and select Compare files. This free tool checks for an exact file duplicate, even when the filenames are different.

Each file can be up to 64 MiB. The comparison runs in your browser; this tool does not upload your files or save them.

A re-encoded, trimmed or otherwise changed copy will count as a different file. This checks file contents, not whether two videos look similar.

No file selected.
No file selected.

MP4, MOV, WebM, M4V, OGV or OGG. Maximum 64 MiB per file.

Choose two files to begin.

How this checker works

When you select Compare files, your browser reads the two files you chose and computes a SHA-256 fingerprint of each with the browser's built-in Web Crypto API. If the two fingerprints are equal, the files are byte-for-byte identical, whatever their names. The page makes no network request with your files, and nothing is saved after you close it. Files are limited to 64 MiB each because the whole file is read into memory.

When it is useful

  • An upload folder holds final.mp4, final2.mp4 and export-copy.mp4, and you want to know which ones are simply renamed copies.
  • You downloaded an export again and want to confirm it is the same file you already checked.
  • You want to record a fingerprint next to the approved filename in your upload note.

What it cannot tell you

A re-encoded, trimmed or metadata-edited copy of the same footage gets a different fingerprint, so this tool will call it a different file. In our test, changing only the title metadata produced a different file even though the decoded video matched. For the loudness, silence and frozen-picture checks we run before uploading, see Before You Upload an AI Song or Video.

Comments

Post a Comment

Popular posts from this blog

FFmpeg Shows −1.5 dBTP. Did You Actually Fix the Audio?

An output_tp of −1.50 in an FFmpeg log does not mean your original audio has been fixed. A command can show that number without saving any corrected audio. Before uploading, measure the file you actually exported. This follow-up to our AI song quality checklist tackles one practical mistake: confusing filter output statistics with a saved deliverable. You need FFmpeg installed and a local audio file. These commands process files on your computer; they do not upload your recording. One recording, two different stages On September 18, 2026, we measured one newly generated, roughly 2-minute-20-second MP3. Its integrated loudness was −11.41 LUFS and its true peak was +0.84 dBTP . The same analysis log showed output_tp: -1.50 . input_i and input_tp describe the file supplied to that command. output_i and output_tp describe the signal after the filter in that execution. They do not establish the measured properties of a separately encoded final file. We then reduced gain by...
Read more

VoxCPM2 vs ElevenLabs for a 30-Second Science Short: We Timed Both on the Same Script

Image
Disclosure: DigitalHarvest (NSST) is an independent affiliate of ElevenLabs. We may earn a commission if you subscribe through the referral link in this article. ElevenLabs has not sponsored, reviewed, or approved this article. This relationship does not change the numbers below, and the free local option wins on cost in our own test. We make 30-second science Shorts from public-domain NOAA ocean footage, and every one needs about six lines of narration. On October 4, 2026 we took one finished script and voiced the same six lines twice: once with VoxCPM2, an open-source model running on our own Apple Silicon Mac, and once with ElevenLabs on the paid Creator plan we already use. Then we ran both outputs through the same Whisper check our pipeline uses before anything is published. Here is what came out. The script we used The episode is "Why doesn't hot water on the seafloor boil?" (a small black smoker vent filmed at 2,947 m by NOAA Ocean Exploration). Six lines, 428...
Read more

Before You Upload an AI Song or Video: The Checks We Run (Free Commands)

The FFmpeg and file-hash commands below run locally. No purchase is needed to follow them. In September 2026 we published a 140-second "music video" for one of our AI songs. It was one still picture with a small moving waveform along the bottom. Our pre-upload checks had measured the length, the resolution and the loudness. Nobody had checked whether the picture actually moved. We deleted it from our channel the next morning. This post shows the checks we run now. Every command below runs on your own computer with ffmpeg , and every number comes from files we measured ourselves. 1. Loudness and true peak (free, one command) ffmpeg -hide_banner -nostats -i song.mp4 -af ebur128=peak=true -f null - Read the Summary block at the end: I: is the integrated loudness in LUFS. Peak: under "True peak" is the true peak. ffmpeg prints the unit as dBFS. A test file we deliberately pushed too loud read I: -8.4 LUFS and Peak: 3.5 . Our own working baseline is ...
Read more