Initializing... drag & drop files here
Supports: MPEG2
If you are pulling a still out of an MPEG-2 source — a ripped DVD, a broadcast or cable capture, a camcorder tape — the real question is which format to land it in. TIFF if the frame is headed for an archive, a print shop, or precision color work; JPG or PNG if it is headed for a screen, an email, or the web. This tool decodes one frame from your MPEG-2 clip and saves it as a lossless TIFF; the table below shows exactly when that is the right call and when it is not.
| Property | TIFF (this tool) | JPG | PNG |
|---|---|---|---|
| Compression | Lossless: None, LZW, Deflate, PackBits (lossy JPEG also defined) 1 | Lossy (DCT) — discards detail | Lossless (Deflate) |
| Re-saves without quality loss | Yes — edit and re-save repeatedly | No — each save degrades | Yes |
| Bit depth per channel | Up to 16-bit 1 | 8-bit only | 8 or 16-bit |
| Color models | RGB, CMYK, grayscale, LAB | YCbCr (RGB on export) | RGB / grayscale + alpha |
| Typical size, SD frame | ≈ 1 MB uncompressed (720×480×3) | Smallest (tens of KB) | Medium |
| Browser preview | No — Safari only 2 | Yes, universal | Yes, universal |
| Metadata / tags | Extensive (TIFF tags) | EXIF | Limited (text chunks) |
| Standard archival raster | Yes — libraries, museums, print | No | Web-oriented |
| Best for | Archive, print, precision editing | Sharing, email, social | Web/UI, sharp text, alpha |
.mpeg2, .mpg, or .mpeg file onto the page, or click "+ Add Files" to browse. You can queue several files and process them with the same settings.2.100 grabs the frame at 2.1 seconds. (Switching to Multiple Screenshots returns each sampled frame as its own TIFF in a ZIP — not one multi-page TIFF.)For an archival master, yes. JPG is lossy — it discards detail on every save, so it is a poor choice for a file you intend to keep or re-edit. TIFF stores the decoded frame without adding any further loss and survives repeated edit-and-save cycles intact, which is why libraries and museums standardize on it for preservation. The catch worth stating plainly: TIFF does not make an SD MPEG-2 frame look better than JPG would — both start from the same decoded pixels. TIFF's advantage is that it stops the quality clock there, while a JPG keeps degrading. For a frame you will only ever post or email, that advantage does not matter and a JPG is the lighter, more practical choice.
No. MPEG-2 is a lossy, motion-compensated codec, and the still you extract is whatever the decoder reconstructs — typically standard definition (about 720×480 for NTSC DVD, 720×576 for PAL) with TV-range color. TIFF wraps those exact pixels losslessly; it cannot recover information the original encode discarded, upscale the resolution, or sharpen a soft frame. Think of TIFF as a faithful, re-editable container for the frame MPEG-2 already produced, not a way to undo the compression that produced it.
Both are lossless, so neither degrades the pixels. The difference is reach versus depth. PNG is lossless and opens in every browser, which makes it a fine archive if you also want the frame viewable on a screen — but it tops out at RGB and does not carry CMYK or the extensive metadata tags a print or preservation workflow leans on. TIFF carries CMYK, up to 16 bits per channel, and rich tags, at the cost of not previewing outside Safari. Use TIFF when the destination is print, color-managed editing, or a formal archive; use PNG when you want lossless and web-friendly in one file.
Both are lossless — their decoded pixels are identical to uncompressed — so the choice is size versus compatibility, not quality. Deflate/ZIP usually packs a little tighter; LZW is the most broadly supported compressed-TIFF scheme and opens in older software (the tool itself notes LZW is the standard for TIFF). Pick None only when a legacy application chokes on any compressed TIFF and you want the absolute-safest archival master, accepting a larger file. For a standard-definition MPEG-2 frame the absolute sizes are small either way.
Because TIFF was never a web display format. MDN states that other than Safari, browsers do not natively render TIFF in an <img> tag without an add-on, and recommends it only for downloadable print and precision-editing files. 2 That is by design — TIFF is the archival and print target, not the on-screen one. If you need the frame to show in a browser, an email, or a slide deck, extract it as a JPG (universal) or a PNG (lossless, web-friendly) instead.
No — that is interlacing in the source, not anything TIFF does. Older MPEG-2 from DVD, camcorders, and broadcast is frequently interlaced: each frame is built from two fields captured a fraction of a second apart, so on a moving subject they land out of register and you see comb artifacts. Nudge Time (seconds) by a few hundredths to land on a still moment, or pick a frame where the subject is stationary. For footage that is interlaced throughout, deinterlace the clip first and extract from the progressive result. JPG and PNG would record the exact same combing — the fix is a clean source frame, whichever format you target.
In our testing, a 720×480 DVD-era MPEG-2 frame saved as uncompressed 8-bit RGB TIFF landed near 1 MB, matching the raw pixel math (720 × 480 × 3 bytes ≈ 1.04 MB); turning on LZW or Deflate trims that further on natural-image content with zero quality loss. The same frame as a JPG is typically a small fraction of that — tens of kilobytes — which is exactly the archival-versus-sharing trade-off this page is about. If your downstream tools expect the three-letter spelling, there is a dedicated MPEG-2 to TIF converter; .tif and .tiff are the same format, just the legacy DOS/Windows 8.3 name. The MPG to TIFF converter handles the equivalent .mpg/.mpeg spellings of the same MPEG family.
Your MPEG-2 file is uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public.