Data Recovery Case File · Trust, Practice & Honest Limits · A File Without a Header
An Audio File With No Waveform Is One the Player Cannot Decode, Not One That Is Empty
His enquiry describes a symptom precise enough to name the fault. An interview recorded on a tablet which no device will play, where "I can see the file but the sound graphs disappeared." A missing waveform is not silence — it is a player unable to interpret the file well enough to draw one, which points at the file's description of itself rather than at the recording.
| Media | Audio recording created on a tablet — file present with expected size; no waveform displayed and playback unavailable across multiple devices |
| Reported situation | Interview recorded using a tablet application · recording failing to play on any of the owner's devices · file visible and present · waveform display absent in playback software · recording required for a professional project |
| Fault class | Audio container header incomplete or absent — recording written and finalisation not performed; audio stream present and decodable once the container is reconstructed |
| Equipment used | Absent waveform interpreted as a decoding failure rather than as absent audio · file size compared against expected duration to confirm content presence · container structure examined and header reconstructed from stream parameters · audio stream decoded independently of the container · recovered audio validated by playback in full |
The decode: what a waveform requires, and what is missing
What drawing a waveform actually involves: decoding the audio. A player reads the file, works out how the sound is encoded, and computes amplitude over time to draw the display — every step of playback except producing sound.
Why an absent waveform is therefore diagnostic: it means decoding failed at the very beginning. A player that could read the file would draw a line even for silence, so a blank display means it never got that far.
What is at the beginning of an audio file: a header. A short structure describing the encoding, the sample rate, the channel count and the length, without which the rest is an undifferentiated stream of numbers.
Why that header is frequently the missing piece: it is written last. Recording applications write audio as it arrives and complete the header when recording stops, because the length is not known until then.
Why that makes an interrupted recording present and unplayable: the audio was written and the description was not. An application that crashed, ran out of space or was closed during recording leaves exactly this — a large file with nothing at the front to explain it.
Why his file size is the confirming evidence: a substantial file means substantial audio. If the file is roughly the size a recording of that length should be, the content is there.
Why no device will play it: they all check the header first. Every player on every platform reads the description before the content, so trying more devices confirms rather than resolves.
How it is repaired: the parameters are determined from the stream itself and a header reconstructed. Encoding, rate and channel count leave recognisable signatures in the audio data, and once written correctly the file plays normally.
Why the result is usually complete: nothing was lost, only undescribed. A reconstructed header returns the entire recording, including whatever was captured up to the moment it stopped.
What must not happen meanwhile: no attempts to repair the file with conversion tools, and no re-saving it. A converter that cannot read the header may write a valid empty file over it, which would be the actual loss.
On the bench
The absent waveform was interpreted as a decoding failure rather than as absent audio — drawing a waveform requiring the file to be read, the encoding determined and amplitude computed, so a blank display indicates failure at the outset rather than silence. Audio files carry a header describing encoding, sample rate, channels and length, written last because length is unknown until recording stops, so interruption leaves audio written and undescribed. The header was reconstructed from stream parameters.
The outcome
The absent waveform read as a decoding failure, file size compared against expected duration, and the header reconstructed from the stream's own parameters. Free assessment, one fixed written figure including VAT. The decode: a blank waveform means the player could not decode the file at all, because a player that could read it would draw a line even for silence. What is missing is the short description at the front, which is written last — and your audio was written first.
A recording that exists and will not play
Don't run it through a converter or re-save it, since a tool that can't read the header may write a valid empty file over your recording — that would be the actual loss. Check the file size first: if it's roughly what a recording of that length should be, the audio is there. What's missing is the header, a short structure at the front describing the encoding and length, which applications write last because the length isn't known until recording stops. An interruption leaves audio written and undescribed, and no player will touch it.
Don't convert it — call Manchester Data Recovery on 0161 871 0788; absent waveform read as a decoding failure, file size checked against duration, header reconstructed from the stream's own parameters.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.