Video corrupted after transfer or copying: what happened and how to fix it
If a video played fine on your phone or camera but is broken after copying it to a computer, USB drive or cloud, the copy is usually incomplete or the new device lacks the codec; the original is normally fine. Compare the file size of the copy with the original, test the copy in VLC, and copy again with a reliable method. Only if the original is gone and the copy is truncated do you need to repair it.
Step 1: compare sizes
Check the size in bytes (not MB, which is rounded) on both sides: on Windows, right-click > Properties; on macOS, Get Info; on the phone, a file manager's details view.
- Same size: the copy is complete. If it does not play, the new device lacks the codec. Test in VLC. iPhone videos are typically HEVC; see play MOV files on Windows.
- Copy is smaller: the transfer stopped early. Copy again.
- Copy is 0 bytes: the transfer failed at the start, or a cloud placeholder was copied instead of the file; see MP4 is 0 bytes.
- Exactly 4,294,967,295 bytes (or the transfer failed at 4 GB): the destination is FAT32.
Common causes and fixes
Phone over USB (MTP). Windows' MTP connection to Android and iPhone is known to stall or drop on large files and large batches without a clear error. Copy fewer files at a time, use a different cable or port, keep the phone unlocked during the transfer (iPhones stop transferring when locked on some setups), or use the Photos app import.
iPhone conversion. With Settings > Photos > Transfer to Mac or PC = Automatic, the iPhone converts HEVC videos during a cable transfer. Conversion of long videos can fail silently and produce a short or broken file. Switch to Keep Originals and copy again.
FAT32 USB sticks and cards. FAT32 cannot store files of 4 GB or more. Some tools stop with an error; others leave a truncated file. Reformat the stick as exFAT (back up first) or use NTFS for Windows-only use.
Removing the drive too early. Windows and macOS cache writes. Pulling a USB drive before "Safely remove" or Eject can leave the end of the file (sometimes the index) unwritten.
Cloud sync. OneDrive, iCloud Drive, Google Drive and Dropbox can show files that are not fully downloaded or uploaded yet. Wait until sync completes; make the file available offline before copying it elsewhere. Some apps (WhatsApp, Telegram, email) also recompress or limit video size, so the received file may be a different, smaller file rather than a broken one.
Failing card or cable. If copies of the same file differ each time, or copying produces read errors, the source card or reader may be failing. Copy once with a different reader, then stop using the card.
Browser downloads. An interrupted download leaves a .crdownload or .part file, or a truncated file if the server did not report the size. Download again.
Step 2: copy again, reliably
- Windows: Robocopy retries on errors and reports what it copied:
robocopy D:\DCIM\100GOPRO C:\Videos *.MP4 /Z /R:3. - macOS / Linux:
rsync -av --progress /Volumes/CARD/DCIM/ ~/Videos/. Re-running rsync resumes and verifies. - Phones: the Photos app import (Windows), Image Capture (macOS), or a cloud upload with the original quality setting.
Step 3: verify
Compare checksums to be sure the copy is identical:
`` certutil -hashfile video.mp4 SHA256 ``
on Windows, or shasum -a 256 video.mp4 on macOS and Linux. Run it on the source and the copy; the hashes must match.
Step 4: when the original is gone
If the original was moved, deleted or the card was formatted, work with what you have:
- Run the copy through the free MP4 file checker. A truncated copy typically shows a box that extends past the end of the file, or a missing index.
- Most MP4 and MOV recordings from cameras and phones write the index at the end. A truncated copy therefore lacks the index, but the copied part of the video and audio data is intact. Rebuilding the index recovers the part that was copied. Use the repair tool with a healthy clip from the same device as a reference.
- If the card was formatted or files deleted, try data recovery first; see recover videos from an SD card.
Prevent it
Copy rather than move, and delete from the source only after you have verified the copy plays and matches in size. Use exFAT for portable drives. Eject before unplugging. For important footage, keep two copies on different devices before formatting the camera card.
Quick diagnosis table
| What you see | Likely cause | Fix |
|---|---|---|
| Copy smaller than original | Interrupted copy | Copy again |
| Fails at 4 GB | FAT32 destination | exFAT/NTFS |
| Same size, will not play | Missing codec | VLC, HEVC extension |
| Plays on PC, broken on the phone after copying back | Format not supported by phone | Convert |
| Copies differ each time | Failing card or reader | New reader; back up immediately |
| Short, lower quality file | App recompressed it | Send as file/document, or original-quality upload |
FixMP4 compared with other options
| Feature | FixMP4 | Desktop repair suites | untrunc (CLI) | VLC |
|---|---|---|---|---|
| Runs where | Browser, on your device | Desktop app | Command line | Desktop player |
| Keeps your file on your device | ✓ | ✓ | ✓ | ✓ |
| Nothing to install | ✓ | ✕ | ✕ | ✕ |
| Rebuilds a missing MP4/MOV index | ✓ | ✓ | ✓ | ✕ |
| Preview of your own repaired file before paying | ✓ | Trial (varies) | Free tool | n/a |
| Voice Memos / AAC without a reference | Usually | Varies | ✕ | ✕ |
| Formats beyond MP4/MOV/M4A | ✕ | ✓ | Many (FFmpeg) | Plays many |
Frequently asked questions
Why does my video play on the phone but not on the PC?
Either the copy is incomplete, or the PC lacks the codec (often HEVC). Compare file sizes and test in VLC.
Can copying damage the original video?
Normally no. Copying reads the original. Moving (cut and paste) and a failed transfer can leave you with only a broken copy, though.
Why are my videos cut at exactly 4 GB?
The destination is formatted FAT32, which cannot hold files of 4 GB or more. Use exFAT or NTFS.
Can a truncated copy be repaired?
If the original is gone, the part that was copied can often be repaired by rebuilding its index.