Initializing... drag & drop files here
Supports: 3GPP
This tool pulls one still frame out of a .3gpp mobile video and saves that single frame as a TIFF — a lossless, archival image format. It does not turn the clip into a "TIFF video" (TIFF is a still picture, not a moving format); you choose one moment and get one image. This walk-through is for anyone with an old 3G-era phone clip who wants a clean, print-and-archive-grade copy of a specific frame — a face, a sign, a moment worth keeping — and wants to know exactly which settings to touch and what to realistically expect from a tiny, heavily-compressed source.
.3gpp (or .3gp) file onto the page, or click "+ Add Files" to browse. You can queue several clips and they all process with the same settings.2.1 lands on the frame at 2 seconds and 100 milliseconds. That one frame becomes your TIFF.The two settings that matter for this job are Frame Selection and Compression Type — everything else can stay on its default. Here is how to think about each.
Choosing the frame. With Specific Frame selected, the Time (seconds) field decides exactly which instant you capture. Decimals are allowed, so you can nudge in by hundredths of a second to skip past a blink or a blurred pan. If you are not sure which moment you want, switch to Multiple Screenshots instead: it samples frames across the whole clip and returns them as a set, so you can pick the best one afterward from a contact sheet rather than guessing a timestamp up front.
Keeping it lossless. TIFF is prized because it stores pixels without throwing any away — but only if you pick a lossless Compression Type. The practical choices:
For a tiny 3GPP frame the absolute file sizes are small either way, so most people can leave a lossless type selected and not think about it again.
TIFF is unusual among image formats in that "TIFF" does not name one encoding — the tag-based container can hold pixels compressed several different ways, which is why the Compression Type dropdown exists and why one .tiff can open everywhere while another chokes an old tool. Here is what each choice actually does:
| Compression Type | Lossless? | Relative file size | Compatibility | Use it when |
|---|---|---|---|---|
| LZW | Yes | Small | The broadest of the compressed schemes; opens essentially everywhere | Default choice — the page flags it as the standard for TIFF |
| Deflate (ZIP) | Yes | Usually slightly smaller than LZW on photos | Very good in modern tools, weaker in pre-2000s software | You want the smallest lossless file and control the destination |
| PackBits | Yes | Larger — simple run-length coding only | Very old and very wide, including legacy Mac tooling | An ancient tool rejects LZW and Deflate |
| None | Yes (uncompressed) | Largest | Maximum — nothing to decode | A legacy tool refuses any compressed TIFF |
| JPEG | No | Smallest | Good, but the pixels are permanently altered | Almost never for an archival still; it re-introduces lossy compression |
| CCITT Group 4 | Yes | Tiny | Fax and document tooling | Only for bilevel (pure black-and-white) images, not a colour video frame |
Every lossless row produces pixel-identical output — the differences are purely size and how old a program can still read the result.
TIFF is the right answer for print and editing, but it is the wrong answer for anything on a screen. If you are not sure which you need, compare the three targets before converting:
| Property | TIFF | JPG | PNG |
|---|---|---|---|
| Lossless | Yes (with LZW, Deflate, PackBits, or None) | No — always re-compresses | Yes |
| Colour depth | 8-bit and higher, plus CMYK and alpha | 8-bit RGB, no alpha | 8-bit and 16-bit RGB, with alpha |
| Displays in browsers | Safari only; other browsers need an add-on | Every browser | Every browser |
| Typical file size for a QCIF-class frame | Small in absolute terms, largest of the three | Smallest | Between the two |
| Re-editable without further loss | Yes | No — each save loses more | Yes |
| Best for | Print, archival, precision editing | Posting, messaging, email | Web use where you still want lossless pixels |
For a frame pulled out of a 3G-era phone clip, the source is so small that all three land in the tens-of-kilobytes range — so pick on where the image is going, not on size.
.tiff inside an <img> tag without an add-on, and MDN lists it among image types to avoid for web content. TIFF is for downloadable print and editing files. For on-screen or web use, extract the frame as Convert 3GPP to JPG instead..3gpp and .3gp are two interchangeable extensions for the same 3GPP container; upload it as-is.A few clips resist clean frame extraction. A corrupted or partially-downloaded .3gpp may decode with gray blocks or stop short of your chosen timestamp — re-export or re-download the original first. A clip shorter than your Time (seconds) value has no frame to grab there, so lower the number. And remember the hard ceiling: this is a rescue tool for getting a memorable frame out of an old phone clip into an archival-stable format, not an enhancer — it will not restore resolution or sharpness the original never captured. If you simply want the whole clip playable on a modern device, convert the video itself with Convert 3GPP to MP4 rather than pulling a single still.
Yes. .3gpp and .3gp are two interchangeable extensions for the same 3GPP container format, built on the ISO base media file format (MPEG-4 Part 12), so the file uploads and decodes identically here. The longer .3gpp spelling turns up most often on certain Android camera exports and MMS-handled clips, but it is not a separate or lossier format and needs no renaming before upload. The matching tool for the short spelling lives at Convert 3GP to TIFF.
No — and this is the honest catch. TIFF is lossless, so it preserves whatever the decoder produced without adding a second round of compression. But the frame you start with is whatever the 3GPP already held — commonly QCIF-class, around 176×144, and heavily compressed for an early mobile network. TIFF cannot add detail or resolution the original never captured; you get a pristine, re-editable copy of an existing low-resolution still, not an upscaled one. Enlarging it past its native size only stretches the existing pixels. The value here is archival stability and editability, not enhancement.
Use LZW or Deflate — both are lossless, so neither changes image quality, and the choice is purely size versus compatibility. LZW is the most broadly supported compressed-TIFF scheme and the page's recommended default; Deflate/ZIP is usually a hair smaller on photographic content. Pick None only if a legacy tool refuses compressed TIFFs, accepting a larger file. Avoid the JPEG compression type for archival stills, since it layers lossy compression back into the TIFF. For a tiny 3GPP frame the sizes are small whichever lossless option you choose.
You can grab several, but they arrive as separate files, not one multi-page TIFF. Choose Multiple Screenshots under Frame Selection instead of Specific Frame: it samples frames across the whole video and returns each as its own TIFF, delivered together in a ZIP. That keeps every still independently usable. It is handy when you are unsure which exact moment you want and would rather choose from a set afterward.
Because TIFF was never built for web display. Other than Safari, no major browser renders a .tiff inside an <img> tag without an add-on or a JavaScript decoder, and MDN explicitly lists TIFF among image types to avoid for web content. TIFF is meant for downloadable print, archival, and precision-editing files. If your goal is posting or on-screen viewing, extract the frame as a web-friendly format with Convert 3GPP to JPG instead. In our testing, a frame pulled from a QCIF-class 3GPP clip and saved as an uncompressed 8-bit TIFF came out to only a few tens of kilobytes, because the source resolution is so small.
Exactly the resolution of the video frame it came from — the extraction copies the decoded frame, it does not resample it. 3GPP clips recorded on 3G-era handsets are commonly QCIF-class at around 176×144, with somewhat better devices reaching QVGA (320×240) or CIF (352×288), so that is the pixel count you will see in the TIFF's properties. This is the honest ceiling of the whole operation: TIFF stores those pixels without adding a second round of compression, but there is no setting anywhere on the page that manufactures resolution the phone never captured. If you need the still physically larger for print, enlarge it afterwards in an editor and accept that you are stretching existing pixels rather than revealing new ones.
Both are lossless, so neither one damages the image — pick on where the file is going. TIFF is the format print shops, scanning workflows, and archival systems expect, and it can carry higher bit depths, CMYK, and multiple compression schemes, which is why it remains the default for long-term storage. PNG is the lossless format the web actually understands: it renders in every browser, drops straight into a document or a chat message, and is generally a little smaller for an 8-bit image. For a QCIF-class 3GPP frame the size difference is trivial, so the practical rule is TIFF for archiving and printing, PNG for anything that will be viewed on a screen, and JPG only when you need the smallest possible file and can accept lossy compression.
Your 3GPP file is uploaded over an encrypted (TLS) connection, processed on our servers, and the files are deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public. Most 3GPP clips are only a few megabytes, so uploads are quick; if a longer recording stalls, the practical limit is upload size and time, so trim the section you need first with the Video Cutter, then grab a frame. The same single-frame extraction is available with the three-letter spelling at Convert 3GPP to TIF.