It happened me many times that I could end up in corrupted video files:

  • video downloaded from official sources but with torrent and for some reason not all the pieces are there in .mkv, .ts or .mp4
  • records in .ts format where at a certain point the data is missing
  • copied videos from an old hard drive with damaged sectors

When I play this videos with VLC or other players they plays till a certain point and then instantly exits. Sometimes I can try to skip the bad part but I could meet another bad sector and have an insta-quit again.

Question is:

Can I fix this problems (I suppose stream and keyframes related) with ffmpeg and maybe in a -c copy fashion so I haven't to recompress everything?

What I want to achieve is a full lenght video where the missing parts are skipped, I prefer a glitch rather than having my videos crash.


If parts of the file reside on physically bad sectors, or for whatever reason, the OS cannot serve the whole file to FFmpeg, then naturally FFmpeg can't do anything about that. You should get a utility which can ignore those portions and write the salvageable parts to a new file, like ddrescue.

Now, if the file protocol is not the cause of errors, you can try

ffmpeg -err_detect ignore_err -i video.mkv -c copy video_fixed.mkv
  • 1
    This works, but fails without -c copy. Surprising that it doesn't work during recode.
    – intuited
    May 26 '17 at 18:52
  • Even with that, I'm still getting Invalid data found when processing input -- and ffmpeg gives up.
    – Mikhail T.
    Apr 13 '19 at 18:16
  • Nice solution... if the moov atom (on a MP4 file) is still present somewhere. What if it's not even there? Oct 22 '19 at 16:52
  • It works at my end with surprising goodness :)
    – shirish
    Jan 6 '20 at 23:26

In the search of a better answer a possible way could be:

ffmpeg -i video.mkv -c copy video_fixed.mkv

However I'm pretty sure there are some extra options that can make the result even better..

  • 1
    Works for me every time I have some kind of issue with the meta data, timestamps, or container info. And it's very fast, usually faster than 400x playspeed.
    – user24601
    Jun 16 '18 at 0:03
  • This command saved my butt, to be frankly.
    – neverMind9
    Aug 3 '18 at 19:52

I've tested lot of solutions and software. I love cli commands, so using ffmpeg you can fix your video file with no hassle. Try the next command if you came here searching some useful fix:

ffmpeg -vcodec mpeg4 -b:v 7561k -qscale:v 2 -acodec aac -ac 2 -async 1 -strict experimental ./video_fixed.mp4 -threads 0 -i damage_file.mp4

Good luck 😃!

  • This will probably work, but the file will be HUGE! Better so just use H264 again, like: ffmpeg.exe -i "input.mp4" -c:v libx264 -crf 22 -preset slow output.mp4
    – kett
    Sep 27 '20 at 22:40

Not the answer you're looking for? Browse other questions tagged or ask your own question.