Add Album Cover to M4A Online
Embed artwork in a common M4A audio container without uploading the song. The editor replaces or creates the Apple-style cover atom, keeps media payload bytes intact, and corrects chunk offsets if a larger metadata box moves the audio data.
Complete the task in three clear steps
- 1
Locate the M4A metadata
The page scans top-level MPEG-4 boxes and reads the moov box without loading the entire audio file into an ArrayBuffer.
- 2
Prepare a compatible cover
Upload JPG, PNG, or WebP. It is converted to a compact JPEG before being placed in a covr data atom.
- 3
Rebuild and verify the container
Ancestor box sizes and affected stco or co64 chunk offsets are updated, then the new cover atom is read back.
What the browser changes—and what it leaves alone
M4A is based on the ISO Base Media File Format. Unlike MP3 and FLAC, its metadata and audio are arranged in nested boxes with absolute chunk tables. Adding bytes before media can invalidate playback unless those offsets are adjusted, so this tool rebuilds the relevant hierarchy rather than performing a blind byte replacement.
The editor targets common non-fragmented M4A files with a readable moov box. Unusually large or malformed metadata is rejected. The output is always a new file, leaving the original available if a particular player uses uncommon vendor metadata.
When this tool is a practical fit
- Personal AAC or ALAC files stored in an M4A container
- Replacing artwork used by common desktop and mobile music players
- Adding a cover when the M4A already has ordinary MPEG-4 metadata or no cover atom
Supported behavior and honest limits
- Common non-fragmented .m4a containers
- Creates the udta/meta/ilst/covr path when it is missing
- Patches 32-bit and 64-bit chunk tables whose media offsets move
Frequently asked questions
Is AAC or ALAC audio converted?
No. The media payload remains byte-for-byte in the original file slice.
Why is M4A editing more complex than MP3?
MPEG-4 stores data in nested boxes and may use absolute media offsets. Metadata size changes can require offset corrections to keep playback valid.
Does this support every MP4 variant?
It targets common M4A audio files. Fragmented, encrypted, malformed, or unusually structured containers may be rejected rather than changed unsafely.