Initializing... drag & drop files here
Supports: 3GP, 3G2
A .3g2 file is video recorded to the 3GPP2 file format — the CDMA2000 counterpart to 3GP, specified in 3GPP2 C.S0050-B. It is what Verizon, Sprint and other CDMA-network handsets wrote when you pressed record, and those networks are gone: Verizon turned off the last of its 3G CDMA network on 31 December 2022. What survives is the footage, sitting on old memory cards and in backups, at frame sizes that were designed for a two-inch screen.
A .jfif is a JPEG — the same encoded image data in the same wrapper as a .jpg, under a different name. This page decodes one frame out of the 3G2 and writes it as a JFIF still. It accepts .3gp files as well as .3g2, because the two are close cousins and the decode path is the same.
.3g2 onto the page or click "Add Files" to browse. .3gp files are accepted here too, and several clips can be queued with the same settings.0; type the moment you want, decimals allowed. Multiple Screenshots samples the whole clip at a Capture Rate ranging from one frame every 0.1 second to one every 10 seconds, opening at one per second..jfif. Files are uploaded over an encrypted connection, decoded on our servers, and deleted automatically after a few hours — no sign-up, no watermark.This is the one thing worth understanding before you touch a setting. 3G2 exists because CDMA data was slow and handset screens were tiny, so the frame sizes are small by design. The common ones you will find in real files:
| Frame size | Name | Where it came from |
|---|---|---|
| 128 x 96 | SQCIF | The smallest legal H.263 frame; MMS-era clips |
| 176 x 144 | QCIF | The workhorse size for camera phones through roughly 2007 |
| 320 x 240 | QVGA | Later CDMA smartphones, often with H.264 |
| 352 x 288 | CIF | Better handsets and some camcorder-style recordings |
| 640 x 480 | VGA | The upper end of what a 3G2 file usually contains |
Image resolution opens on Keep original, so a 176 x 144 clip gives you a 176 x 144 still. You can select a Preset Resolution such as 720p and get a 720p file — but every pixel above the source is interpolated, and interpolating a QCIF frame produces a large, soft picture rather than a detailed one. If you need a bigger image for printing or a slide, upscale deliberately in an editor where you can control the algorithm and sharpening, not as a side effect of a dropdown.
The other honest caveat: these clips were often encoded with H.263 at a few hundred kilobits per second, so the frame you extract already carries visible blocking. The JPEG stage adds a second lossy generation on top. Nothing on this page recovers detail the phone never recorded.
Each preset maps to a fixed JPEG quality number handed to the encoder:
| Quality Preset | JPEG quality value | What it is for |
|---|---|---|
| Highest | 100 | Maximum fidelity to the decoded frame; the largest file |
| Very High (Recommended) | 95 | The shipped default; visually close to the source frame |
| High | 90 | A good balance for anything going on the web |
| Medium | 80 | Smaller, with mild softening on fine detail |
| Low | 70 | Compression begins to show on edges |
| Very Low | 60 | Visible blocking in flat areas |
| Lowest | 50 | Thumbnails only |
On a small, already-compressed phone frame the practical range is narrow. At 176 x 144 there are only about 25,000 pixels to encode, so even the Highest preset produces a file measured in tens of kilobytes, and dropping to Medium saves so little that it is rarely worth the extra artefacts. Stay at Very High or Highest here; the size argument that makes lower presets attractive on a 4K photo simply does not apply.
.jfif Extension3G2 and 3GP are siblings rather than the same format. 3GP was defined by 3GPP for GSM and UMTS networks in ETSI 3GPP TS 26.244; 3G2 was defined by 3GPP2 for CDMA2000 in C.S0050-B. Both allow MPEG-4 Part 2, H.263 and H.264/AVC video. The audio lists diverge: 3G2 adds the CDMA speech codecs — EVRC, EVRC-B, EVRC-WB, 13K (QCELP), SMV and VMR-WB — while excluding HE-AAC v2 and AMR-WB+ that 3GP allows. None of that reaches a JFIF, because a still image has no audio track, but it explains why a .3g2 from a Verizon handset sometimes refuses to open in software that handles .3gp fine.
On the output side, .jfif, .jpg and .jpeg are three names for one thing. The image data is byte-for-byte the same kind of file; only the extension differs, and some older applications filter their file pickers on .jpg alone and therefore never show a .jfif. If that happens, rename the file — or use 3G2 to JPG, which writes the conventional extension directly, or JFIF to JPG to convert one you already have.
Yes. JFIF is the interchange format that defines how JPEG-compressed data is packaged — the marker segments, the pixel-density fields and the colour conventions decoders expect. It appeared as JFIF 1.02 in 1992 and was later formalised as ITU-T T.871 in 2011 and ISO/IEC 10918-5 in 2013. A .jfif and a .jpg written at the same quality are the same picture in the same wrapper; renaming one to the other changes nothing inside the file.
Because the video is. 3G2 was built for CDMA data rates and handset screens, so recordings are typically 176 x 144, 320 x 240 or 352 x 288 — a few tens of thousands of pixels, against the several million in a modern phone photo. The still comes out at the source frame's dimensions unless you change Image resolution, and enlarging it there interpolates rather than adds detail. The small size is the source, not a settings mistake.
Yes. This page accepts both .3g2 and .3gp, since the two formats share a container lineage and the same video codec families, and the decode path is identical. The output extension is .jfif either way. If you have a .3gp and would rather use a page named for it, the equivalent 3GP conversions exist too, but nothing about the result changes.
Usually because of the audio codec, not the video. 3G2 files from CDMA handsets frequently carry EVRC or QCELP speech audio, which Windows, macOS and most editors have no decoder for, so the file is rejected before the picture is ever shown. VLC, mpv and anything built on ffmpeg handle it, which is how this converter reads the file. Extracting a still sidesteps the problem entirely, since a JFIF has no audio track.
Switch Frame Selection to Multiple Screenshots and pick a Capture Rate. The list runs from one frame every 0.1 second to one every 10 seconds and opens at one per second, and you get a separate .jfif for each sample. Phone clips are usually short, so the default rate is manageable here in a way it is not on a feature-length source — a 30-second recording at one frame per second gives you 30 images to choose from.
No. The blocking came from the phone's encoder, which was working at a few hundred kilobits per second with H.263 or early H.264, and it is baked into the decoded frame before the JPEG stage ever sees it. Raising the preset stops the JPEG encoder adding new damage, which is worth doing, but it cannot remove what is already there. Picking a moment where the camera is not moving helps more than any setting on this page.
No. JPEG has no alpha channel, and there is nothing to preserve anyway — video frames are fully opaque and none of the codecs a 3G2 can carry store transparency. If you need a cut-out, extract the frame as 3G2 to JPG or a PNG and remove the background in an editor afterwards.
It is discarded. A JFIF stores one still picture and has nowhere to put sound, so whatever the file carried — AMR-NB, AAC, or one of the CDMA speech codecs — is dropped during frame extraction. If you want the audio as a separate file, run the same clip through 3G2 to MP3.
Your clip is uploaded over an encrypted connection, decoded on our servers, and both the upload and the stills it produced are deleted automatically after a few hours. Files are never shared or made public, and there is no sign-up, no watermark and no account required.