3GPP to PNG Converter

Extract a PNG Frame from a 3GPP Video: What This Tutorial Covers

A .3gpp file is the mobile video container specified by the 3rd Generation Partnership Project in TS 26.244 ("3GPP file format (3GP)"), an instance of the ISO base media file format that also underpins MP4. This tutorial covers pulling one still frame — or a whole timed sequence of frames — out of that clip and saving it as PNG, the lossless raster format whose specification reached W3C Recommendation status as a Third Edition on 24 June 2025. You will learn how to hit an exact timestamp, how many images each capture rate produces, and what to do when the still comes out soft.

How to Convert 3GPP to PNG

1. Upload Your 3GPP File: Drag and drop the .3gpp clip onto the page or click "+ Add Files" to browse. Files with the .3gp extension hold the same container and behave identically; several clips can be queued and they all run with the same settings.
2. Choose Specific Frame or Multiple Screenshots: Under Frame Selection, keep Specific Frame and type a moment into Time (seconds) — 2.100 grabs the frame at 2 seconds and 100 milliseconds — or switch to Multiple Screenshots and set a Capture Rate to sample the clip at a fixed interval.
3. Set Image Resolution and Compression Level: Leave Image resolution on "Keep original" to match the source pixel-for-pixel, or use Preset Resolutions, Width x Height, or Resolution Percentage to scale; Compression level trades encode time for a smaller file without altering a single pixel, because PNG is lossless.
4. Convert and Download: Click Convert and save the PNG. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared.

Walk-through: Landing on the Frame You Actually Want

We ship the Time (seconds) box pre-filled with 0, which grabs the very first frame of the clip. On phone footage that first frame is frequently the worst one on the reel — the sensor is still adjusting exposure, or the hand is still moving off the record button. Getting a usable still is almost always a matter of typing a better number into that box.

• One clean still: scrub the clip in any player, note the time, and enter it in Time (seconds). The field takes decimals, so 3.4 means 3 seconds plus 400 milliseconds.
• A frame that is not blurred by motion: nudge the timestamp a few tenths of a second either way. Feature-phone clips are often recorded at 10-15 fps, so consecutive frames sit roughly 0.067-0.1 seconds apart and one nudge can be the difference between a smear and a sharp subject.
• Every distinct moment: switch to Multiple Screenshots. The Capture Rate defaults to "1 second per frame", which yields roughly one PNG per second of runtime.
• Dense sampling for analysis: the Capture Rate list goes down to "0.1s seconds (single frame at 10fps)", which is as fine as most 3GPP recordings were ever shot.
• A smaller, shareable still instead of a lossless one: export the same frame through 3GPP to JPG or 3GPP to WebP rather than shrinking the PNG afterwards.

How Many PNGs Each Capture Rate Produces

The count is simply clip duration divided by the interval, so a dense rate on a long recording produces a lot of files. Start coarse, find the second you care about, then re-run Specific Frame on that timestamp.

PNG vs JPG vs WebP for the Same 3GPP Frame

Common Errors and How to Fix Them

• "The PNG looks soft or blocky." That is the source. 3GPP was designed for 2G/3G bandwidth, so clips are commonly QCIF (176x144), QVGA (320x240), or CIF (352x288) and already lossily compressed. PNG stores those pixels perfectly but cannot invent detail the phone never recorded.
• "I got a black or empty image." The timestamp fell before the first decodable frame or past the end of the clip. Re-enter a time inside the actual runtime; 0 on some recordings lands on a black lead-in.
• "Upscaling made it worse." Raising Image resolution above the native size stretches existing pixels and enlarges the blur along with them. Keep "Keep original" unless a downstream tool requires a specific canvas.
• "Multiple Screenshots returned far more files than I expected." Frame count equals duration divided by the Capture Rate — check the table above before running a fine rate on a long clip.
• "The PNG is bigger than I assumed a tiny frame would be." PNG never throws pixels away. Raise Compression level for a smaller file at identical quality, or export the frame as JPG or WebP if size matters more than fidelity.

When This Doesn't Work

Frame extraction needs a decodable video stream. A .3gpp that was partially downloaded, truncated by a dying handset, or delivered as DRM-protected operator content can fail or decode into garbage — open it end to end in a desktop player such as VLC first to confirm it plays, and re-save it from there if it does not. If what you actually want is the moving clip rather than a still, re-encode it with 3GPP to MP4. To grab frames from other video types — MP4, MOV, AVI, WebM and more — use the general Video to PNG tool instead.

Frequently Asked Questions

Is a .3gpp file different from a .3gp file?

No. Both name the same container defined in 3GPP TS 26.244 and both use the video/3gpp MIME type; .3gp is simply the shorter and more common spelling. The video inside is typically H.263, MPEG-4 Part 2, or H.264, and the extracted PNG is identical whichever extension the file carries. The related .3g2 extension is the 3GPP2 variant used on CDMA networks — a near-identical container with a different voice-codec list.

Which frame do I get if I leave every setting alone?

The very first one. Our Frame Selection default is Specific Frame with Time (seconds) set to 0, so an untouched conversion returns frame zero of the clip. That is deliberate — it always produces something — but it is rarely the frame you want from handheld phone footage, so type a real timestamp before converting.

Will the PNG look sharper than the 3GPP video?

No. PNG is lossless, which means it faithfully preserves the frame as the video decoder produced it and adds no new JPEG-style artifacts on top. It cannot restore resolution or detail that the original low-bitrate mobile encode discarded. The gain from PNG is fidelity to the source, not an improvement on it.

How large is a PNG frame from a small 3GPP clip?

Small, and you can bound it with arithmetic: an uncompressed 176x144 RGB frame is 176 x 144 x 3 = 76,032 bytes, about 76 KB, and a 320x240 frame is about 230 KB. PNG's lossless compression then squeezes that down further, so stills from typical feature-phone clips usually land well under those ceilings. Photographic frames compress less than flat, graphic ones.

Should I export a phone-video frame as PNG or JPG?

Pick PNG when the frame will be edited, archived, or contains text and hard edges that JPEG's blocking would smear. Pick JPG when the file is going into an email, a chat thread, or an old photo app that predates newer formats — the same frame is typically several times smaller as JPG. WebP sits in between and beats both on size, with the caveat that some desktop viewers still cannot open it.

Can I extract every single frame of the clip?

Effectively, yes — set Multiple Screenshots with the Capture Rate at "0.1s seconds (single frame at 10fps)", which matches or exceeds the frame rate of most 3GPP recordings. Bear in mind what that means for volume: a three-minute clip at that rate is roughly 1,800 separate PNG files. For anything longer than a few seconds, sample coarsely first and then pull the exact frames you need.

Does the PNG keep transparency or the video's camera metadata?

Neither, and both for structural reasons. A decoded video frame has no alpha channel, so the PNG is fully opaque even though the format supports transparency. Camera and capture metadata in a 3GPP file lives in container-level atoms rather than inside the picture data, so it does not survive as EXIF on the extracted still — the PNG carries the pixels, not the recording's provenance.

How is my uploaded 3GPP file handled?

It is uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours. There is no sign-up and no watermark on the output, and files are never shared or made public. The practical limit on a big upload is transfer size and time rather than clip length, which is rarely an issue since 3GPP recordings were built to be tiny.