Ghost Frames in Your Video: How Converters Invent Footage That Was Never There

Ghost Frames in Your Video: How Converters Invent Footage That Were Never There

You did everything right. You shot clean footage, ran it through your converter, and exported what should have been a polished final file. But something looks... off. There's a weird blur between cuts. A motion sequence looks slightly smeared. Objects seem to ghost across the screen in a way that wasn't there when you first reviewed your raw clips.

Welcome to the phantom frame problem — one of the sneakier issues in video conversion, and one that a lot of creators don't even realize is happening until they're staring at it on a big screen.

What Are Phantom Frames, Exactly?

At its core, a phantom frame is any frame in your converted video that didn't exist in your original source. The converter didn't pull it from your footage — it made it up.

This usually happens through a process called frame interpolation, where the software synthesizes new frames to fill in gaps between existing ones. Sometimes that's intentional — like when you're deliberately converting 24fps footage to 60fps for a smoother look. But often, it happens without you asking for it, as a side effect of how your converter handles timing mismatches between your source and your target format.

The result? Frames that blend two moments in time into one artificial image. Motion gets smeared. Edges look doubled. Fast cuts produce a weird visual echo that no amount of color grading is going to fix.

Variable Frame Rate Is Usually the Culprit

If you've ever recorded video on a smartphone — and statistically, most of us have — there's a good chance your footage is variable frame rate (VFR). Unlike constant frame rate (CFR) video, which delivers a locked number of frames every second, VFR footage speeds up and slows down its frame delivery based on what's happening in the scene. Low motion? Fewer frames. Fast action? More frames.

This is totally fine for playback on your phone. But when you hand that footage to a video converter and ask it to spit out a clean CFR file, you've created a math problem. The converter has to figure out where all those unevenly spaced frames go in a perfectly timed timeline. And when it can't find a real frame to put in a particular time slot, it interpolates — it invents one.

This is where phantom frames are born.

How Converters "Hallucinate" Footage

The technical term for what's happening is temporal interpolation, and different converters handle it in wildly different ways.

Basic converters use simple blending: they average two nearby frames together to create an in-between image. The result is often a semi-transparent smear — two moments in time layered on top of each other like a double exposure. You'll notice this most in scenes with fast movement or hard cuts.

More advanced converters use optical flow algorithms, which try to analyze the motion vectors in your footage and predict where pixels should be at a given moment. This sounds smarter, and it usually is — but it's also where things can go spectacularly wrong. Optical flow is essentially guesswork at scale. When the algorithm misreads motion (which happens constantly near edges, complex backgrounds, or rapid camera movement), it generates frames that look like something out of a fever dream. Limbs stretch. Faces warp. Objects duplicate themselves across the screen.

Some people actually pay for this effect in post-production tools. When it shows up uninvited in a conversion you were expecting to be clean, it's a different story.

How to Tell If Your Converter Is Doing This

The easiest way to check is to run a frame-by-frame inspection on your converted file using a tool like VLC (just step through frames manually with the E key) or import it into a video editor and scrub slowly through sections with fast motion or hard cuts.

Watch for:

• Ghosting on moving subjects — especially hands, faces, or any fast-moving object
• Edge doubling — where the outline of a subject appears in two slightly offset positions
• Smearing between cuts — where two different scenes seem to bleed into each other for a single frame
• Weird stillness — sometimes converters duplicate a frame instead of interpolating, leaving a brief freeze that looks like a dropped frame but isn't

If you're seeing any of these, your converter is generating frames it shouldn't be.

Fixing the Problem Before It Starts

The most reliable fix is to convert your VFR source to CFR before doing anything else. Tools like HandBrake and FFmpeg both handle this well. In FFmpeg, you can force a constant frame rate output with the -r flag and let it handle the timing normalization cleanly, without blending frames together.

In HandBrake, look for the Peak Framerate vs. Constant Framerate option in the Video tab. Switching from Peak to Constant forces the encoder to commit to a fixed rate, which eliminates most of the timing ambiguity that causes phantom frames in the first place.

If you're working with footage that genuinely needs frame rate conversion (say, you're going from 24fps to 30fps for broadcast delivery), be deliberate about how you handle it. Avoid converters that apply interpolation automatically without telling you. Look for settings that let you choose between frame duplication (less pretty, but honest) and blending or optical flow (smoother, but risky). Frame duplication won't win any awards, but at least it's not inventing information that wasn't there.

When Interpolation Is Actually What You Want

It's worth saying: frame interpolation isn't inherently bad. When you're intentionally creating slow-motion sequences or trying to smooth out choppy footage for a specific creative effect, controlled interpolation is a legitimate tool. Apps like Topaz Video AI and DaVinci Resolve's optical flow engine do this with a lot more precision than a basic converter.

The problem is when interpolation happens by default, without your knowledge, on footage where you expected a clean 1:1 conversion. That's when phantom frames become a real headache.

The Bottom Line

Your video converter is only as smart as the assumptions it makes about your footage — and when those assumptions are wrong, it fills in the gaps by making stuff up. Understanding that this is happening, knowing what to look for, and taking a few extra steps at the start of your workflow can save you from discovering the problem after you've already delivered the final file.

Check your source frame rate before you convert. Force CFR output when you need consistency. And always do a quick frame-level review before you call a project done. A few minutes of checking now beats a re-render later.