Step 1: Drop your MPEG files using the button above or by deposit and leave.
Step 2: Click the 'Convert' button to start the conversion.
Step 3: Receive your converted TIFF files.
MPEG to TIFF Conversion FAQ
How do I convert an MPEG file to TIFF?
+
Upload your MPEG file using the picker above and the converter detects the source type and runs the MPEG → TIFF pipeline. The result downloads automatically when conversion completes; no account needed for one-off conversions.
Why do my extracted frames have horizontal lines through them?
+
Because the source is interlaced. MPEG content from the broadcast and DVD era stores two half-height fields per frame, captured a fiftieth of a second apart, and a still pulled straight out shows both woven together as combing on anything that moved. Enable deinterlacing before extraction and each still is built from a single reconstructed progressive frame. MPEG here means an MPEG-1 or MPEG-2 program stream, the format standardised for Video CD and then for DVD and broadcast television.
Which frame of the MPEG do I actually get as a TIFF?
+
The one you point at, not just the first. A timestamp picks a single moment out of the MPEG; an interval setting walks the whole video and returns one TIFF per step, delivered as a ZIP. The default grabs a frame a few seconds in rather than at 00:00, because the opening frame of a video is very often black.
Does the TIFF output support transparency?
+
The format does, but the source has no alpha to give it — video frames and rendered pages are fully opaque by nature, so every pixel arrives solid. The alpha channel is still useful afterwards: it means you can cut a subject out of the TIFF later without changing format again. TIFF handles CMYK, 16-bit depth, embedded ICC profiles and multi-page documents, which is exactly what print and archival workflows require.
How big will the TIFF files be?
+
Larger than you might expect, because TIFF keeps every pixel exactly rather than approximating. A 1080p still lands around 2-5 MB and a 4K still around 6-15 MB, so a long extraction run adds up quickly. That is the right trade when the images feed further processing, and the wrong one when they are going straight onto a web page. TIFF is a container more than a codec: it can hold uncompressed, LZW, ZIP or even JPEG data, at up to 32 bits per channel, with multiple pages in one file.
Is the MPEG to TIFF converter free?
+
Yes — basic MPEG → TIFF conversion is free with no registration. Premium adds higher per-file size limits, more parallel batch workers, and removes ads.
How big an MPEG file can I convert to TIFF?
+
Free accounts: up to 100 MB per MPEG file. Premium: typically 1 GB per file, depending on the MPEG source type. Very large files are split into chunks server-side when the TIFF format allows.
Will conversion change the content of my MPEG?
+
Conversion preserves all information that both MPEG and TIFF can represent. Format-specific features that the TIFF format doesn't support (e.g. vector data in raster output, formulas in plain-text output) are rasterized or stripped — see the format-specific notes on the result page.
Can I convert many MPEG files to TIFF at once?
+
Yes — drop multiple MPEG files into the upload zone and they are queued in parallel. Premium has more parallel workers; on a 50-file batch this is the difference between minutes and seconds.
Does the MPEG to TIFF converter work on phones and tablets?
+
Yes — the UI is responsive and the conversion pipeline runs server-side, so mobile devices upload-then-download just like desktops. iOS and Android browser file pickers (camera roll, Files app) work end-to-end.
Which browsers does the MPEG to TIFF converter support?
+
Chrome, Firefox, Safari (15+), Edge, and Opera. The converter uses standard `<input type="file">` upload — no WebAssembly or PWA dependencies — so even older browsers work.
Are my MPEG files kept private?
+
Yes — uploaded MPEG files are processed in isolated workers and deleted within minutes. We never view, retain, or share content. See /privacy/ for the data-retention window.
