Reference Formats
MIDI
MIDI is a 1983 protocol and file format for encoding musical performance instructions — note-on/off, timing, control changes — rather than recorded audio, letting any compliant synthesizer reproduce the performance.
Extension
.mid
Full name
Musical Instrument Digital Interface
Introduced
1983
Vendor
MIDI Manufacturers Association (originally Sequential Circuits, Roland, Yamaha, Korg, Kawai)
What is inside the container
A Standard MIDI File contains no actual sound at all — it's a sequence of timed events describing which notes to play, how hard, and with what instrument, control changes and tempo, so playback quality depends entirely on the synthesizer or sound bank rendering it, which is why the same MIDI file can sound completely different on two systems. It supports meta-events for track names, lyrics, and copyright text, but nothing resembling ID3-style descriptive tagging for cataloging purposes.
How to open it
For archives
MIDI files are tiny (often a few kilobytes for a full song) because they store instructions, not audio, so archiving them is cheap, but the tradeoff is that a stored MIDI file preserves the composition, not a specific sonic performance — playback fidelity depends on whatever synth renders it later. A DAM handling MIDI assets (game audio, sample libraries, sheet-music-adjacent workflows) should treat it as a distinct asset class from recorded audio: keep the MIDI file itself for editability, and if a specific reference sound matters, also archive a rendered audio bounce (WAV or FLAC) captured from the exact synth/sound bank used, since that combination can't be reliably reproduced later.
MIDI is the oldest format on this list by a wide margin, and unlike every other entry here, it was never designed to encode sound at all. A consortium of synthesizer manufacturers — including Sequential Circuits, Roland, Yamaha, Korg and Kawai — published the MIDI 1.0 Specification in August 1983, giving different manufacturers’ keyboards and synthesizers a shared electrical and data protocol for the first time. The famous first public demonstration paired a Sequential Circuits Prophet 600 with a Roland Jupiter 6 over a simple 5-pin cable, playing one keyboard and hearing both respond.
What a MIDI file actually stores is a timed sequence of performance instructions — note on, note off, velocity, pitch bend, control changes, instrument selection — rather than any recorded waveform. That’s the source of both its enduring usefulness and its central limitation: a MIDI file is minuscule compared to any recorded audio format and endlessly editable (transpose the key, swap the instrument, fix a wrong note), but the actual sound it produces on playback depends entirely on whatever synthesizer or sound bank renders it, meaning the same file can sound dramatically different across two systems.
A MIDI file doesn’t store a single second of recorded sound — only the instructions for a synthesizer to perform it, which is why the same file can sound completely different from one system to the next.
Inside a DAM, MIDI occupies a genuinely different category from every other audio format here — it’s closer to a structured document than a media file, in the same sense that a vector illustration differs from a rasterized image. Game-audio libraries, music-education content, and sample/instrument libraries often need MIDI files kept alongside their rendered audio counterparts, since the MIDI preserves editability while a paired WAV or FLAC bounce preserves the specific, referenceable sound of a given performance.
Frequently asked
Does a MIDI file actually contain recorded audio?
No — a MIDI file stores performance instructions (which notes to play, when, how loud, with what instrument) rather than a recorded waveform. The actual sound only exists when a synthesizer or sound bank renders those instructions, which is fundamentally different from every other format in this collection.
Why do the same MIDI file sound different on two different computers?
Because playback quality and timbre depend entirely on the synthesizer or sound bank interpreting the file's instructions, and different systems use different default synths. This is the core tradeoff of MIDI's tiny file size — it trades sonic consistency for editability and portability.
Should a DAM archive MIDI files or convert them to audio first?
Both, if the specific sound matters — keep the MIDI file itself for editability (transposing, reassigning instruments, fixing notes) and also archive a rendered WAV or FLAC bounce from the exact synth setup used, since that particular sound can't be reliably reproduced from the MIDI file alone later.
Can MIDI files carry metadata like song title or composer credits?
To a limited degree — Standard MIDI Files support meta-events for track names, tempo markers, lyrics, and copyright text, but nothing approaching the structured descriptive tagging that ID3v2 or Vorbis comments offer for recorded audio.
How large is a typical MIDI file compared to a recorded audio file of the same song?
Dramatically smaller — a full multi-track MIDI arrangement is often just a few kilobytes, versus tens of megabytes for the equivalent uncompressed WAV, because MIDI stores instructions rather than sampled audio data.
Is MIDI still relevant for a modern DAM, or is it a legacy format?
Still actively used — game audio, film scoring workflows, sample-library production, and music education content regularly rely on MIDI for its editability, even though final delivery to end listeners is almost always a rendered audio format like WAV, MP3 or AAC.
Does MIDI require any licensing to support playback or editing in DAM software?
No — the MIDI 1.0 Specification has been openly published and freely implementable since 1983, maintained now by the MIDI Manufacturers Association, with no patent licensing barrier to building MIDI-compatible tools.
What is General MIDI and why does it matter for consistent playback?
General MIDI (GM) is a standardized mapping of instrument numbers to specific sounds (program 1 is always acoustic grand piano, for example), adopted to make playback more consistent across different synthesizers. A DAM previewing MIDI files benefits from GM-compliant playback, though even GM only standardizes which instrument plays, not exactly how it sounds.
Sources
- The MIDI 1.0 Specification was published in August 1983 by a group of synthesizer manufacturers including Sequential Circuits, Roland, Yamaha, Korg and Kawai, with the first public demonstration pairing a Sequential Circuits Prophet 600 and a Roland Jupiter 6. checked 2026-08-07 — MIDI.org — MIDI History Chapter 7: MIDI Associations (1983–1985)