Initializing... drag & drop files here
Supports: MJPEG
MJPEG (Motion JPEG) stores video as a sequence of independently compressed JPEG frames. Because there's no inter-frame compression, MJPEG files are large but every frame is a clean still — which is why webcams, IP / security cameras, scientific microscopes, and industrial inspection rigs prefer it. The trade-off is portability: MJPEG plays in VLC and a handful of viewers, but rarely embeds anywhere. GIF embeds in every chat, forum, wiki, and email client made in the last 30 years. Common reasons to convert MJPEG to GIF:
| Property | MJPEG | GIF |
|---|---|---|
| Compression | Per-frame JPEG (intra-frame only) | Per-frame LZW (1987) |
| Color depth | 24-bit (16M colors) | 8-bit (256 colors max) |
| Audio | Optional (often absent in cameras) | No |
| Typical size for 5-sec clip | 5-30 MB (depends on bitrate) | 1-8 MB |
| Universal playback | VLC + media-player apps | Every device, every viewer |
| Looping | Manual | Automatic |
| Frame independence | Yes (good for editing / dropouts) | Yes |
| Best for | Cameras, capture rigs, archival | Embedding, sharing, reactions |
MJPEG and GIF share one trait: every frame stands alone. That makes the conversion clean — no inter-frame artifacts to flatten — but it also means MJPEG files are large by modern video standards. A 30 MB MJPEG webcam clip routinely shrinks to a 2-4 MB GIF once resolution drops to 480 px wide. For audio-bearing footage that needs universal playback, MJPEG to MP4 is the better path.
| Setting | Effect on size | Best for |
|---|---|---|
| 24-30 fps, Highest preset | Largest, smoothest | Microscopy, lab captures, color-rich footage |
| 15 fps, High preset | Balanced | Webcam clips, doorbell-cam highlights |
| 10 fps, Medium preset | Compact | Security-cam reactions, forum embeds |
| 8 fps, Low preset | Smallest | Long surveillance loops that must fit a forum upload |
No. MJPEG is large because every frame is a full JPEG with no inter-frame compression — a 1080p webcam at 30 fps can hit 5-10 Mbps. A 50 MB MJPEG clip converted as a 5-second GIF at 480 px wide and 12 fps typically lands at 1-3 MB. Trim length, resolution, and fps decide the GIF's size, not the source file size — and File Compression → Max file size can pin it to an exact ceiling.
Most webcams capture at 15-30 fps but with uneven timing (USB bandwidth varies). 10-15 fps is the GIF sweet spot — smooth enough to read motion while halving file size compared to 30 fps. For lab time-lapses where the source is already 1-5 fps, match the source frame rate exactly so the GIF plays at intended speed.
GIF has no audio support, so any audio in the MJPEG is dropped. Most MJPEG sources (security cameras, microscopes, machine-vision rigs) don't record audio anyway. If you do need to keep sound from a webcam clip, convert to MJPEG to MP4 or MJPEG to WebM instead.
Not from this page — the GIF output is always an animation of the clip. For stills, use MJPEG to JPG or MJPEG to PNG, which offer "specific frame" mode (one frame at a chosen timestamp) and "multiple frames" mode (a sequence as separate images) — useful for pulling an evidence frame from security footage or a hero frame from a microscopy capture.
The direct route: switch File Compression to Max file size and grab the Discord (10 MB max) preset — the converter lands at or under the cap for you. Tuning by hand instead: drop fps to 10 and set the width to 480 px under File Compression → Custom; a 5-second clip at those settings typically lands at 1-3 MB. For tighter caps, trim to 2-3 seconds first. Security and webcam footage compresses especially well because the source palette is already limited (mostly grays, browns, and skin tones).
The visual timestamp burned into the video frames (most Reolink, Hikvision, Amcrest, and Wyze cameras embed this) carries through to the GIF as part of the image. Make sure the resolution preset is high enough that the timestamp text remains readable — 480P and above usually works, while 240P and below can blur the digits.
Yes. Both extensions point at the same Motion JPEG container. Windows historically used.mjpg, while Unix and many camera vendors prefer.mjpeg. The internal data is identical and this converter accepts both interchangeably.
Two reasons. GIF caps at 256 colors per frame, so the smooth gradients in low-light security or microscopy footage show banding and dithering that aren't visible in the 24-bit MJPEG source. Step the File Compression Quality preset up toward Highest to minimize this — palette choice itself is automatic on video sources. Also, JPEG compression in MJPEG already adds blocky artifacts at low bitrates — converting to GIF preserves them. For grain-heavy or low-light footage, MJPEG to WebM preserves full color and produces a smaller file at the cost of GIF's universal embedding.
Yes — drop in as many.mjpg or.mjpeg files as you want. Each converts in parallel on our servers. Settings can apply to all files or be tuned per-file. Useful for processing a folder of doorbell-camera triggers or a sequence of microscope acquisitions into a shareable GIF set.