Initializing... drag & drop files here
Supports: 3GP, 3G2
This tool pulls one still frame out of a .3g2 clip and encodes it as AVIF, the AV1-based image format. The question worth answering before you click convert is whether AVIF is the right container for that frame at all. Short answer: choose AVIF when the still is going onto a modern web page and every kilobyte counts; choose JPG when it has to open in anything, anywhere, including software from the same era as the phone that shot the clip; choose PNG when you need a lossless, pixel-exact grab for editing or evidence. The comparison below is the whole decision.
| Property | AVIF | JPG | PNG |
|---|---|---|---|
| Underlying coding | AV1 intra-frame, stored in a HEIF/ISOBMFF container | DCT, ITU-T T.81 / ISO-IEC 10918 | DEFLATE, lossless |
| Specification status | AOMedia AVIF v1.2.0, Final Deliverable, 16 October 2025 | Published 1992, unchanged and universal | W3C Recommendation (Third Edition), 24 June 2025 |
| Compression | Lossy or lossless | Lossy only | Lossless only |
| Bit depth | 8, 10 or 12-bit, plus HDR and wide gamut | 8-bit | 8 or 16-bit per channel |
| Transparency | Full alpha | None | Full alpha |
| Typical size for one phone-video frame | Smallest of the three | Small | Largest — often several times the AVIF |
| Browser support | ~94.7%: Chrome 85+, Firefox 93+, Edge 121+, Safari 16.4+, iOS Safari 16+ | Universal | Universal |
| Support in desktop viewers and older apps | Patchy — many image viewers and editors still cannot open it | Everything opens it | Everything opens it |
| Best for | Web delivery where bytes matter | Sharing, printing, attaching, maximum compatibility | Editing, archiving, pixel-exact grabs |
.3g2 onto the page or click "From my Computer". .3gp files from GSM-era handsets are accepted here too, and several clips can be queued at once.2.100 means 2 seconds and 100 milliseconds into the clip. Choose "Multiple Screenshots" instead to sample frames across the whole clip at a fixed interval..avif. The file uploads over an encrypted connection, is processed on our servers, and is deleted automatically after a few hours. No sign-up, no watermark.| Your 3G2 source | The AVIF you get back | |
|---|---|---|
| What it is | A short mobile video clip in a 3GPP2 container | One still frame, coded with AV1 |
| Container lineage | ISO base media file format | HEIF, which is also built on the ISO base media file format |
| Frame size | Small — QCIF (176x144) and QVGA (320x240) were typical of the CDMA era | Identical pixel dimensions unless you scale them down |
| Motion | Yes, at a low frame rate | None. A single moment |
| Audio | Usually present, often a CDMA voice codec | None. An image has no audio |
| Detail | Whatever the handset's encoder preserved | The same detail, re-encoded — nothing added |
A single still image. AVIF can hold animation — the specification defines AV1 Image Sequences, and some converters use that to make looping AVIFs — but this page extracts one frame at the timestamp you set and encodes it as a static picture. That is a deliberate difference: animated AVIF support is still uneven, with Firefox carrying an open bug for animated AVIF sequences. If you want the clip to loop, 3G2 to APNG or 3G2 to GIF are the safer animated targets.
No. AVIF is a more efficient way to store a picture, not a way to create detail. The frame you start with is whatever the handset's encoder recorded — often a small, heavily compressed image built for a network with very little bandwidth to spare. AVIF will store that picture in fewer bytes with fewer new artefacts than JPEG would, but it cannot invent resolution. Enlarging the result past its native size only stretches the pixels that are already there.
Use "Specific Frame" and type the time in seconds, with decimals for sub-second precision — 2.100 is two seconds and one hundred milliseconds in. If you are not sure where the moment is, run the clip once with "Multiple Screenshots", which samples frames across the whole video at the interval you choose and gives you a set of stills to pick from, then go back and grab the exact timestamp.
Because the source frame is tiny. Video from CDMA-era handsets was commonly encoded at QCIF (176x144) or QVGA (320x240), so there are only a few tens of thousands of pixels to store, and AV1 intra coding stores them very compactly. A file of a few kilobytes is the correct output for that input, not a truncated conversion. Open it in a current browser to confirm it renders.
Browsers are the reliable path: about 94.7% of global browser usage supports AVIF, covering Chrome 85+, Firefox 93+, Edge 121+, Safari 16.4+ and iOS Safari 16+. Outside the browser it is patchier — plenty of desktop image viewers, older photo editors and office suites still will not open one. If you have to email the still, drop it into a document, or hand it to someone on an unknown machine, convert it as 3G2 to JPG instead.
Do not count on it. A 3GPP2 file carries container-level metadata such as creation time, and a still extracted from a video frame does not inherit a photographic EXIF block the way a camera JPEG would — there was never a shutter event to describe. If the recording date matters, note it from the original file's properties before you convert, and keep the .3g2 itself as the record.
Yes, and that is the common case. .3g2 is the 3GPP2 container that CDMA2000 handsets recorded to, which in the US meant Verizon and Sprint. The network is long gone — Verizon shut down its 3G CDMA network on 31 December 2022, the last major US carrier to do so — but the files themselves are unaffected. The same page accepts .3gp from GSM-era phones; the 3GP to AVIF converter is the equivalent page for those.
Your 3G2 is uploaded over a TLS-encrypted connection, processed on our servers, and deleted automatically after a few hours. There is no sign-up, no watermark on the output, and files are never shared or made public. If you want the clip in another form entirely rather than as a still, the 3G2 converter hub lists the rest of the targets.