repair.video

Video file shows 0 bytes — what that actually means, and what to do next

Windows, macOS or your phone shows the video sitting at 0 bytes — no size, no thumbnail, nothing to open. This is a different problem from every other "won't play" case on this site, and it deserves a straight answer before you upload anything: here's what a 0-byte file actually is, and what to do about it.

What actually happened to the file

A 0-byte file is a filesystem entry — a name, a folder location, a "this exists" flag — with zero bytes of data attached to it. The camera or phone created that entry when you pressed record, then crashed, lost power, or hit a full or failing card before a single frame was written into it. Or, on a card recovered after deletion, the filesystem could only recover the empty entry and lost track of where the actual data lives.

The file was never a video at all. There is no mdat, no frame data, no index — nothing inside it to walk or rebuild, because nothing was ever written.

What we can rebuild

Nothing, from the 0-byte file itself — that's the one honest "there's nothing here" on this site, and the engine says so immediately, before any strategy runs. But the recording itself may not be gone:

• The footage may still be on the card as unallocated sectors. If the camera wrote frames before the directory entry failed to finalize, a card-level undelete tool (PhotoRec-class software — not a video repair service) can scan raw sectors and carve out whatever survived.
• If that tool hands you back a file with a real size that won't play, that's where we come in — see recovered video won't play for exactly that handoff.

What we honestly cannot fix — and the look-alikes that aren't 0 bytes

We can't rebuild frames that were never written. That's true of a real 0-byte file, and of two related shapes worth telling apart — both measured directly rather than guessed at:

• A file with a real size but almost nothing behind it. A real case we saw: a 1.54 GB file where the camera pre-allocated the full size up front and only ever wrote the first 1 MiB before failing — the rest was all zeros. It looks like a normal-sized file at a glance; it isn't one.
• A file that's card-level erasure, not video. Another real case: 1.87 GB made up of a small set of fixed 512-byte patterns repeating across every sector — the signature of erased or overwritten flash storage. There was no video structure in it anywhere, and no reference file could have changed that.

Both of those get an honest "no" too — the free analysis tells you which one your file actually is before you pay anything.

Do this first

• Stop writing to the card. Every new photo, clip, or even the camera powering back on can overwrite the sectors your video used to occupy.
• Don't format the card — formatting can erase what an undelete tool would otherwise still find.
• Copy an image of the whole card before running any recovery tool on it, so you have an untouched original to fall back to.
• Keep the camera's other clips. A healthy clip from the same device and recording mode is exactly what we'd need as a reference, if the undelete step returns something for us to work with.

Free while in beta — no account, no card. If your file is genuinely 0 bytes, the analysis says so immediately, for free — no wasted upload, no false hope.

Frequently asked questions

Can you recover a 0 KB video file?

No — not from the 0-byte file itself. It has no data behind it at all, so there's nothing to rebuild. What might still be recoverable is the footage on the card as unallocated sectors, using a card-level undelete tool rather than a video repair service. If that tool hands you back a file with a real size that won't play, that's something we can look at.

Why does Windows (or my phone) show my video as 0 bytes?

It means the filesystem created an entry for the file — a name and a location — but no video data was ever written into it, usually because the camera or app crashed, lost power, or ran out of storage right at the start of recording. It isn't a display glitch; there's genuinely nothing in the file.

The undelete tool gave me a file with a size now — what next?

Upload it to us. A file that comes back from card-level recovery with an actual size, but won't play, is a different and often fixable problem — the frames may be there with the index lost or misaligned. Our recovered-video-wont-play page covers this case in detail.

Phone says the video is 0 bytes — is that different from a camera?

Same failure, same first step: the recording never made it to storage before something interrupted it — an app crash, storage full, or a restart mid-save. Card-level (or phone-storage-level) recovery is the right next move, not video repair.

Is the footage gone for good?

Honestly, we don't know until a card-level recovery tool has looked — and neither does anyone who tells you otherwise before checking. Some 0-byte cases recover real footage from unallocated sectors; some genuinely don't, because the sectors were already overwritten. Once you have whatever the undelete step returns, our free analysis can give you a real answer on that file.