Initializing... drag & drop files here
Supports: TIFF, TIF
.tiff / .tif images. Multi-page TIFFs and batches are supported — each page or file becomes a frame in the output video..3g2 file. Files process on our servers, are auto-deleted after the session, and there's no watermark or sign-up.TIFF (Tagged Image File Format) is a flexible raster container favored by scanners, prepress, archival imaging, and microscopy — single files can hold multiple pages or layers at full bit depth, often uncompressed or losslessly compressed with LZW or ZIP. 3G2 (defined by 3GPP2 in spec C.S0050, initial release January 2004) is a CDMA2000-targeted multimedia container that wraps a small H.263, MPEG-4 Part 2, or H.264 video stream with low-bitrate audio for legacy mobile playback. Turning a TIFF stack into 3G2 is how you make a still-image sequence playable on older CDMA handsets, kiosks, MMS pipelines, or any device that only speaks the 3GPP2 ISO base media file format.
| Property | TIFF | 3G2 |
|---|---|---|
| Type | Raster image container | Multimedia (video + audio) container |
| Standards body | Adobe (originated at Aldus, 1986) | 3GPP2 (spec C.S0050-B, latest Sept 2024) |
| Typical use | Scanning, prepress, archival, microscopy | CDMA2000 mobile, MMS, legacy feature phones |
| Compression | None, LZW, ZIP, PackBits, JPEG (lossy) | H.263, MPEG-4 Part 2, or H.264 video + AMR/AAC audio |
| Multi-frame | Multi-page support | Yes — video stream over time |
| Bit depth | 1, 8, 16, 32-bit per channel | 8-bit per channel (H.264 baseline) |
| Color spaces | Grayscale, RGB, CMYK, Lab, more | YUV 4:2:0 (video-standard) |
| Audio support | No | EVRC, EVRC-B, QCELP, AMR-NB, AMR-WB, AAC-LC |
| Typical bitrate | N/A (file size driven by pixels/bit depth) | 64-384 kbps video, 5.3-23.85 kbps AMR audio |
| MIME type | image/tiff |
video/3gpp2 |
| Modern relevance | Active in prepress and archival workflows | Legacy — superseded by MP4 on LTE/5G handsets |
| Video Codec | When to use | Trade-off |
|---|---|---|
| H.264 (default) | Newest 3G2-capable handsets (post-2010), best quality-per-bit | Some early CDMA feature phones reject it |
| MPEG-4 Part 2 | Mid-era CDMA devices, broad mid-2000s support | Larger files than H.264 at the same quality |
| H.263 | Oldest handsets, kiosks, low-resolution thumbnails (≤352×288 CIF) | Lowest visual quality; only useful for legacy targets |
| Xvid | MPEG-4 ASP variants on certain feature phones | Niche; check the target device first |
For the audio track xconvert defaults to AMR Narrow Band (8 kHz, 4.75-12.2 kbps) since image-to-video conversions normally produce a silent slideshow — the AMR stream is effectively empty filler that satisfies the 3G2 container requirement for many players. If you want stereo audio, use TIFF to MP4 and merge an audio track separately.
You'd only pick 3G2 if your target device is a CDMA2000 feature phone, an older kiosk, or an MMS gateway that requires 3GPP2 framing. For anything modern (smartphones, tablets, desktop browsers, social media) MP4 plays everywhere and produces smaller files. If you're not sure your destination needs 3G2 specifically, try TIFF to MP4 or TIFF to MOV instead.
Yes. When "Merge images" is selected, each page of a multi-page TIFF becomes one frame in the 3G2 video, in document order. Set Image Duration to control how long each page is held — 5 seconds per frame is the default. Single-page TIFFs become single-frame videos of the chosen duration.
3G2 is a low-resolution container by design — most CDMA handsets cap decode at QCIF (176×144), CIF (352×288), or QVGA (320×240). xconvert defaults to 768p, which works on modern 3G2-capable software players (VLC, MX Player) but may be rejected by older hardware. For genuine feature-phone targets, drop to 320×240 or 176×144 in the Video Resolution preset.
No. 3G2 video uses YUV 4:2:0 with no alpha plane. Any transparent pixels in your TIFF are composited against the Background Color (Black by default; pick White, Gray, or any of 24 named colors in Advanced Options). If you need transparency in the output, you need an image-output format with alpha like TIFF to PNG or TIFF to WebP.
The most common cause is codec choice — pre-2010 CDMA handsets often only decoded H.263 or MPEG-4 Part 2 inside 3G2, not H.264. In Advanced Options, change Video Codec to H.263, drop the resolution to 176×144 (QCIF) or 320×240 (QVGA), and try again. The other common cause is bitrate ceilings — some handsets reject anything above 384 kbps video.
Yes, going from TIFF to 3G2 always re-encodes pixels with a lossy video codec (H.264, MPEG-4 Part 2, or H.263). There's no lossless mode for 3G2. If preserving every pixel matters, keep a TIFF master and only generate 3G2 as a delivery copy. The Quality Preset dropdown (Very High → Very Low) trades file size against visible artifacts on the re-encode.
Not in this tool — xconvert's image-to-3G2 path produces a silent video (with a placeholder AMR audio stream for container compliance). To attach real audio, first convert your TIFFs to MP4 with TIFF to MP4, then use a video editor to merge an audio track. 3G2's AMR-NB audio is narrowband (8 kHz sample rate, mono) and not suited to music anyway — for spoken narration on CDMA targets it works fine, but you'll need to mux the AMR stream in externally.
3G2 with H.264 is efficient for motion video but inefficient for slideshows of static frames — every frame is encoded against the previous, and abrupt full-frame changes (slide-to-slide cuts) generate large keyframes. Lowering the Quality Preset, dropping resolution, and increasing frame duration (so fewer keyframes per minute) all reduce file size. For a single static image, TIFF to JPG at a tenth the bytes is almost always the better answer.
Image-to-video conversions run server-side because they need FFmpeg with the H.263/H.264/AMR encoders. Your TIFFs are uploaded over HTTPS, converted, served back as a download, and deleted from our servers after the session ends. No account is required and there's no watermark.