Initializing... drag & drop files here
Supports: 3GP, 3G2
This tool decodes one frame from a .3gp or .3g2 mobile clip and writes it as a JFIF still. The thing worth knowing before you start: JFIF is not a rival of JPG — it is the interchange wrapper that ordinary JPEG files have used since 1992, so .jfif and .jpg hold the same kind of lossy JPEG data and the same image/jpeg MIME type. Choose this page when something in your workflow specifically wants the .jfif extension; choose a different output when you need lossless pixels or wide app compatibility.
| Property | JFIF | JPG | PNG |
|---|---|---|---|
| Underlying coding | JPEG (lossy DCT) | JPEG (lossy DCT) | Deflate (lossless) |
| MIME type | image/jpeg |
image/jpeg |
image/png |
| Standard | ITU-T T.871 (2011), ISO/IEC 10918-5 (2013) | Same JPEG coding; usually an Exif or JFIF wrapper | ISO/IEC 15948 |
| Header segment | JFIF APP0, carrying pixel-density units and an optional thumbnail |
JFIF APP0 or Exif APP1 |
Typed chunks (IHDR, pHYs, …) |
| Transparency | No | No | Yes, 8-bit alpha |
| Re-saving cost | Recompresses each save | Recompresses each save | No generation loss |
| Recognised by apps | Widely, but some editors and uploaders reject the extension | Universally | Universally |
| Best for a 3GP frame | A pipeline that explicitly asks for .jfif |
Sharing, uploading, archiving the still | Frames with text, logos or sharp edges |
The formats in the first two columns are so close that renaming the file usually settles any disagreement: our output is standard JPEG data with a JFIF APP0 header, so changing .jfif to .jpg alters the name and nothing else about the bytes.
.jfif specifically and rejects other extensions..jfif naming and want consistency..jpg and .png and will simply not see a .jfif. Use 3GP to JPG instead..3gp (3GPP) and .3g2 (3GPP2, from CDMA handsets) are accepted, and several files can share one job.2.100 is 2.1 seconds in — or choose Multiple Screenshots with a Capture Rate to grab a spread of stills across the clip..jfif. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours. No sign-up, no watermark.| Property | 3GP (source) | JFIF (output) |
|---|---|---|
| Type | Video container | Still image |
| Standard | 3GPP TS 26.244, built on ISO/IEC 14496-12 | ITU-T T.871 / ISO/IEC 10918-5 |
| First published | 3GPP release in the early 2000s | JFIF 1.02 on 1 September 1992 |
| Codec / payload | H.263, MPEG-4 Part 2 or H.264 video; AMR or AAC audio | JPEG lossy DCT coding |
| MIME type | video/3gpp |
image/jpeg |
| Close relative | .3g2, the 3GPP2 variant for CDMA phones |
.jpg and .jpeg, byte-compatible in practice |
| Designed for | Low-bandwidth mobile capture and playback | Interchange of a single JPEG picture between programs |
For practical purposes, yes. JFIF — the JPEG File Interchange Format, published as ITU-T T.871 in 2011 and ISO/IEC 10918-5 in 2013 — is the original wrapper that says how JPEG-compressed data is written into a file. It registers under the same image/jpeg MIME type as a .jpg. If a program refuses a .jfif, renaming it to .jpg almost always opens it, because the data inside is identical.
Usually because of a naming rule on the machine that saved it, not because of anything unusual in the image. On Windows the MIME database can map image/jpeg to the .jfif extension, so browsers saving a perfectly ordinary JPEG write it out with that name. Renaming the file is harmless. This page is here for the opposite case: when you deliberately need that extension.
A mandatory APP0 segment immediately after the start-of-image marker. It records the JFIF version, the pixel-density units — pixels per inch or per centimetre — the horizontal and vertical density values, and optionally a small uncompressed RGB thumbnail. That density field is why a JFIF can declare a print size even though the pixel data itself has no physical dimensions.
No, and there is a structural reason as well as a practical one. JFIF and Exif both require their application segment to sit immediately after the start-of-image marker, which makes the two headers formally incompatible even though many programs write both anyway. The practical reason matters more here: a video's metadata describes the whole recording, not one frame, so there is nothing frame-specific to carry across. The output is a new image with its own creation time.
Because the source was built for a 3G network. 3GP clips are usually recorded at small frame sizes — QCIF 176×144, QVGA 320×240 or CIF 352×288 on older handsets — with H.263 or early MPEG-4 coding at low bitrates. The frame you pull out already contains that blocking and smearing; raising the Quality Preset preserves it faithfully but cannot invent detail that was never captured.
Use the JPEG family, including JFIF, for ordinary photographic content: it produces a much smaller file and the artefacts are hard to see in a scene. Use 3GP to PNG when the frame holds text, a logo, a user interface or anything with hard edges, and whenever you intend to edit the still afterwards — PNG is lossless, so repeated saves cost nothing in quality.
Yes. Set Frame Selection to Multiple Screenshots and pick a Capture Rate; the choices run from one frame every 10 seconds down to one every 0.1 seconds, which is ten frames per second. Each output is a separate image, not an animation. Start at one frame per second unless you are chasing a very specific moment, because dense rates produce a lot of files quickly.
It is uploaded over an encrypted connection, decoded and re-encoded on our servers, and deleted automatically after a few hours. There is no sign-up, no watermark, and files are never shared or made public. If you only need a frame from early in a long clip, Trim 3GP first — a shorter upload finishes noticeably sooner than a long one.