By Lucas, founder of FixMyVideos · Updated

Green Screen or Glitched Playback in a Recovered Video

The file opens and the timeline runs, but the picture is wrong. The lower half might be bright green, the first second could be a vertical smear, or the whole thing looks blocky and over-contrasted with a different colour cast above and below some line across the frame. On a Mac you may even get solid green striped with horizontal bands while the same file looks fine in another player.

These symptoms have different causes, and most can be told apart on screen. Every case below is a file we opened and measured while working on our own recovery engine.

What the green actually is

A video decoder writes each picture into a buffer that starts out as zeros. Video is stored as one brightness channel (Y) and two colour-difference channels (U and V), and "no colour" in those channels is the value 128, not 0. So a region where the decoder never wrote anything sits at Y=0, U=0, V=0, and converted to RGB that combination comes out as saturated green.

Green therefore means nothing was decoded there. Real black footage keeps its chroma at 128, and a chroma-key green screen in your shot has bright luma, so neither produces the exact all-zero triple. That triple is what our engine counts as unwritten pixels.

Decoders differ in what they do when data runs out:

  • H.264 usually conceals. It copies neighbouring content over the hole, which you see as a smear or blocks dragged across the frame, and it prints a line such as concealing 19694 DC, 19694 AC, 19694 MV errors in I frame in ffmpeg's log.
  • HEVC (H.265) neither conceals nor announces. It stops writing and leaves the rest of the buffer at zero. On the file we measured, ffmpeg printed a header warning but no concealment line and no corrupt-frame line, while more than half the frame was green.
  • Field-coded (interlaced) H.264 can do the same silent stop. On a 14.6 GB Premiere export, one keyframe decoded with an empty log at the normal verbosity and 62 % of the picture had never been written.

So "ffmpeg reports no errors" proves little about a glitched file.

Four ways a file ends up green or glitched

The bytes inside a picture were destroyed

This is what we found in files that recovery software had stitched back together. We worked through six files belonging to one person that appear to come from the same recovery tool. Five were 4K H.264 and one was HEVC, and in every one a block of random data (393,216 bytes on most of them) sat inside or right after the first keyframe. On one of the H.264 files the decoder had to conceal 19,694 of the keyframe's 32,400 macroblocks, 61 % of the picture, and the smear lasted 45 frames until the next keyframe arrived. On the HEVC file 55.4 % of the keyframe was unwritten, and the preview was bright green from the horizon down for the whole first group of pictures. Past the next keyframe, the pictures were clean.

Nothing can bring those bytes back, because they are not in the file. What we changed is how the engine treats them. On files that lost their index, the preview now decode-checks its starting keyframe and moves forward to the first one that decodes clean, so you judge your footage on real pictures. The full recovery keeps the damaged frames, because they are still your recording and silently cutting them would be worse.

The decoder was given the wrong description of the stream

When a file loses its index (the moov box), it usually loses the small parameter sets that tell a decoder the frame size and how the picture was compressed. A repair tool then has to borrow them from another recording. If the borrowed size is wrong, the stream can decode without a single error (a size guessed too wide is the exception, the decoder does complain about that one), and what you see depends on which way it is wrong:

  • A different shape. The decoder fills the top of the frame and leaves the rest green. A moov-less 1280x720 HEVC phone recording previewed about 85 % flat green because a 480x854 profile had been picked for it, with zero error lines. Since that file, every candidate gets decoded and looked at, and one that leaves more than half the frame unpainted is thrown out.
  • Too small. No green at all, just the top part of every frame. Android screen recordings at 1080x2400 came out as their own top 45 % this way, until we started measuring the true height from the stream itself and correcting the borrowed size.
  • Right size, wrong quantiser. On a 2013 Android 720p recording the borrowed pic_init_qp was 26 where the camera had used 20. That value is never checked during decoding, so the file decoded cleanly while every coefficient came out six quantiser steps too coarse. The picture came out blocky, clipped to pure black and pure white at once, with a different colour cast above and below the line where the two slices of each frame meet. We now detect that signature (a share of the picture pinned at both 0 and 255 at the same time) and step the value down until the clipping stops.

If the glitches cover the whole file rather than a moment, suspect this family.

The pixels are fine but the container misleads the player

This one was our own bug. We recovered a 4K all-intra 4:2:2 10-bit Canon file, about 8.5 GB, that had come back as a .DAT after card recovery. It decoded correctly here, and on a Mac it played green with eight horizontal coloured lines. Eight was the number of slices in each picture. ffmpeg had written the track under the aivx tag with no decoder configuration box, so the Mac had nothing to configure its decoder with. Re-muxing to avc1 with its avcC box fixed it, and we confirmed on a Mac that it plays.

A file that looks right in one player and green in another may well have intact data, as that Canon file did.

Damage scattered through the recording

Failing cards and copy errors can hit the middle of a file, not only its start. A 3.37 GB wedding video carved off a card, 1280x720 at 50 fps, had no container left at all, and 4096-byte blocks stamped by the card tool sat in place of video data all through it. Every picture in a group is predicted from the one before it, so one damaged picture spoils the rest of its group until the next keyframe.

A different file kept its index intact and had noise only in the media. There the engine checks each group against the index, leaves out the pictures the noise reached, and holds the last clean picture on screen instead of showing the smear. Audio frames that cannot be read become silence. The picture freezes where bytes were lost, and when the damage is dense those freezes can be long.

What you can check yourself first

Was the file fine before a repair tool touched it? If the glitches appeared after running a repair or recovery program, keep that output aside and work from the original copy. A tool that re-encoded with the wrong size or quantiser has baked the damage into the pixels, and nothing undoes that.

Try a second player. VLC and QuickTime use different decoders. If the file is green in QuickTime and normal in VLC, suspect the container, as in the Canon case above, and not the footage.

Count concealment in H.264 files. At ffmpeg's default log level:

ffmpeg -i broken.mp4 -f null - 2>&1 | grep -c concealing

A handful of hits on a long file points to local damage, and hits all the way through to damage throughout. A wrong stream description, as described above, often prints nothing. For HEVC, and for interlaced (field-coded) H.264, a count of zero proves nothing, because neither prints the line.

Look at actual frames. Pull stills at a few points and open them:

ffmpeg -ss 30 -i broken.mp4 -frames:v 1 still_30s.png

If green appears only up to the next keyframe and then clears, it is destroyed bytes in that group. If every frame is green below the same row, it is a frame-size mismatch. A thin green strip along the bottom edge only can be a padding band written as zeros, left visible after a repair borrowed or rebuilt the stream description.

When a file cannot be saved

Some files have nothing left to decode, and no tool can change that. Three we have measured:

  • Every byte is zero. A 30 MB DJI file arrived as nothing but 0x00 from start to end. There was no video, audio or structure at any offset.
  • Only a header. A 24-byte upload held a single ftyp box and nothing after it.
  • A few sectors repeated. A 20 MB file turned out to contain 12,288 bytes of distinct data, the same sectors read over and over. The only move left there is to copy the original again through different hardware.

The diagnosis now names each of these cases.

Getting a recovery preview

If your file is green or glitched and none of the checks above solved it, upload it here. The analysis reports what it found in the file, and the free 5-second preview is made by the same recovery pipeline, so you see your own footage before paying anything. A full recovery costs €6 below 2 GB, €18 from 2 to 20 GB, €35 from 20 to 50 GB and €59 above that, VAT included. Uploads go up to 150 GB and are deleted automatically after 48 hours.

FAQ

Why is the broken part green and not black? Because green is what an untouched decoder buffer looks like. The buffer starts at zero in all three channels, and zero colour difference converts to saturated green. Real black keeps its colour channels at the neutral value, so it never looks like this.

Why is my video glitched only for the first second? That fits a destroyed first keyframe. Everything up to the next keyframe depends on it, so the damage lasts one group of pictures and then clears. Those frames cannot be rebuilt, but the rest of the file can still be fine.

Why does it play fine in VLC but green on my Mac? Then the pixels may well be fine and the container is describing them wrongly. In the case we fixed, a remux with the correct sample entry and decoder configuration was enough, and it changed no picture data because the frames were already right.

Is a thin green strip along the bottom edge a sign of damage? Not necessarily. An encoder pads the frame out to whole coding blocks, and the stream header normally crops that band away. When a repair has borrowed or rebuilt that header, the crop can be off, and a band written as zeros then shows as green. Check the rest of the frame before you decide.

Can you fix glitches from bad sectors in the middle of a file? When the index survives, we hold the last good picture where noise hit instead of showing the smear. The overwritten pictures themselves cannot be recreated.

Is my footage safe if I upload it? Files are deleted automatically after 48 hours. See the privacy policy for the details.

Related

Free preview · No commitment

Ready to recover your video?

Upload your file and get a free 5-second preview in about a minute. Pay only if the preview looks right.

Upload your file →