A voice recording stopped when the app crashed or the device lost power. Now the M4A file is there, but the player cannot open it. Keep that file untouched while you check for another copy and a working recording from the same app. The interruption may have affected the file’s structure, the recorded audio, or both.
Save the original and look for another copy
Copy the M4A to a different location and work on the copy under a new name. Check the recording app’s own list, its recently deleted folder, any cloud backup, and the original device before running a converter. If the file was copied from a recorder or memory card, try copying it again without deleting the source.
Check the size as a clue, not a diagnosis. A zero-byte file contains no recorded audio to recover. A larger file may contain audio data, but its size alone cannot show how much will play. Do not record over the source or reformat the card while you are looking for another copy.
Separate a playback problem from a damaged file
Try the copy in the recording app and one other player that supports M4A. If one opens it, listen beyond the beginning and export a separate copy through that app. If neither opens it, save any error message. A file extension tells you the intended format; it does not confirm that the contents are intact.
An error such as moov atom not found points to a missing or unreadable piece of MP4-family container metadata. It does not by itself reveal whether the sound data is present or recoverable. M4A audio uses the same container family as MP4 video; our guide to a missing moov atom explains the container issue in more detail.
Find a working reference from the same app
For some unreadable M4A files, a repair attempt may require a separate playable recording as a reference. Look for one made by the same app, on the same device, using the same audio settings as the damaged recording. If you make a new sample, use those settings and stop the recording normally. Keep both files: the sample supplies structural clues, not the missing words from your original. Even a close match does not guarantee a usable result.
If you already have FFmpeg’s ffprobe installed, the following command inspects a file named reference.m4a in the current folder. Substitute the actual path if needed; keep the quotes around paths containing spaces.
ffprobe -v error -show_entries format=duration:stream=codec_name,codec_type,sample_rate,channels -of default=noprint_wrappers=1 "reference.m4a"Look for the audio stream’s codec, sample rate and channel count. If a readable copy of the damaged file can also be inspected, compare its reported settings. Matching values are useful clues, not proof that two recordings are compatible. The command may fail on the damaged file if its structure is unreadable. An M4A can contain more than one audio stream; MendVid currently does not support multi-audio-track M4A repair.
Decide whether to try repair
MendVid’s audio repair can attempt some damaged M4A recordings. Depending on the file, it may need a matching reference. It cannot restore audio that was never written or has been overwritten, and a repair is not guaranteed. It is not an audio enhancement service.
The price is US$9.99 per file. Payment is confirmed before upload and repair; there is no result preview before payment. The fee is not refunded if the attempt fails or yields only a partial result, subject to any non-waivable rights and applicable payment processor rules. Check the current pricing and repair terms before starting.
Listen to the result before relying on it
Open any recovered file separately and listen at the beginning, around the middle and near the end. Compare its duration with your best estimate of the session, and check for missing sections, silence or abrupt changes. A file that opens may still contain only part of the recording. Save the original, the reference and the result separately until you have checked the content you need.