What is MJPEG?
MJPEG, or Motion JPEG, is a video format that compresses each frame independently as a complete JPEG image, with no prediction between frames. The transposed spelling MPJEG is a common misspelling and does not name a separate video compression standard.
How MJPEG works
Motion JPEG compresses every frame as an individual JPEG picture, so decoding does not depend on neighboring frames. That independence makes random access and frame extraction straightforward, while repeated full images consume more bandwidth than interframe coding. The spelling MPJEG usually appears when MJPEG has been mistyped in a filename, option name, inventory record, or user interface. A media pipeline should canonicalize that label but still inspect the bitstream and container before assigning a decoder.
Key facts
- 1Because each MJPEG frame is independently coded, damage to one frame normally does not create the multi-frame error propagation seen with predictive codecs.
- 2There is no registered codec family created by transposing the letters to “MPJEG”; parsers should map that spelling only as an explicit alias for MJPEG.
- 3MJPEG streams occur in AVI, QuickTime, cameras, and multipart HTTP delivery, but those wrappers use different framing and metadata conventions.
When MJPEG matters
Choose MJPEG when frame-independent decoding matters more than bandwidth efficiency, as in camera capture, inspection, and frame-extraction workflows. Normalize the misspelling MPJEG in filenames, configuration, or documentation before codec lookup so valid MJPEG media is not rejected as an unknown format.
Common use cases for video
These examples cover video broadly, not specifically MJPEG.
- Preparing uploaded video for web, mobile, connected-TV, social, or editorial playback.
- Creating clips, thumbnails, captions, alternate aspect ratios, and adaptive renditions.
- Normalizing camera, screen-recording, and user-generated files into predictable outputs.
Working with video
This guidance covers video broadly, not just MJPEG.
A demuxer separates tracks from the container, decoders turn compressed streams into frames or samples, and filters apply spatial or temporal changes. Encoders compress the transformed tracks before a muxer writes the chosen output container.
Video compatibility is the product of codec, container, profile, level, frame rate, color, audio, and subtitles. Validate the complete output on target devices because a playable file on one decoder may fail or look different on another.
What you gain
- Standardized derivatives make diverse source files playable on target devices.
- A retained master can feed many resolutions, aspect ratios, codecs, and channels.
- Automated inspection and transformation make large upload volumes consistent.
What it costs
- More efficient codecs can lower bitrate at similar quality but usually cost more compute and may have narrower support.
- Higher resolutions and frame rates preserve more detail and motion while increasing processing and delivery requirements.
- Fast encoding settings improve throughput but can produce larger files or lower quality than slower analysis.
Before production
- 1Inspect codec, container, dimensions, frame rate, color, audio, and subtitle tracks.
- 2Test visual quality and playback support across the slowest and oldest target devices.
- 3Preserve a suitable master before applying lossy, destructive, or delivery-specific changes.