Initializing... drag & drop files here
Supports: TIFF, TIF
.tif and .tiff are accepted.TIFF (Tagged Image File Format), released by Aldus in 1986 and now maintained by Adobe, is the archival workhorse of scanning, publishing, and GIS — uncompressed or losslessly compressed with LZW or Deflate, often 50–100 MB per page at print resolution. 3GP, defined by the 3rd Generation Partnership Project and first released April 4, 2003, was engineered to shrink video down to what a 2003-era flip phone could stream over 3G — H.263 or MPEG-4 Part 2 video paired with AMR-NB audio, often at QCIF (176×144) or CIF (352×288). Converting a stack of TIFFs into a 3GP slideshow is the right move when your target device is a legacy feature phone, a Symbian/early-Android handset, or an MMS-based delivery channel.
| Property | TIFF | 3GP |
|---|---|---|
| Type | Bitmap image container | Multimedia (video + audio) container |
| Introduced | 1986 (Aldus, now Adobe) | April 4, 2003 (3GPP) |
| Extensions | .tif, .tiff |
.3gp, .3gpp |
| MIME | image/tiff |
video/3gpp, audio/3gpp |
| Compression | None / LZW / Deflate / JPEG / PackBits / CCITT | H.263, MPEG-4 Part 2, or H.264 video; AMR-NB/WB or AAC-LC audio |
| Typical size (per page/frame) | 5–100+ MB (uncompressed); 30–50% smaller with LZW | A few KB per H.263 QCIF frame; KB–MB for the whole clip |
| Native playback | Photo viewers, GIS, Photoshop | Android (native), VLC, QuickTime, Windows Media Player; not iPhone/iOS |
| Best for | Archival print, scanning, GIS, multi-page docs | Legacy feature phones, MMS, low-bandwidth video |
| Lossless? | Yes (default and with LZW/Deflate) | No — all 3GP video codecs are lossy |
| Setting | Best for | Trade-off |
|---|---|---|
| H.263, QCIF 176×144 | Maximum compatibility with the oldest 3G handsets | Very small picture; soft detail |
| H.263, CIF 352×288 | Symbian, early Android, MMS slideshows | Still soft, but legible product/chart TIFFs |
| MPEG-4 Part 2, 320×240 | Mid-2000s feature phones with better decoders | Slightly better quality than H.263 at the same bitrate |
| H.264 Baseline, 480×360 | Newer 3GP-only devices (post-2010 budget phones) | Sharper, but excludes some pre-2008 hardware |
| H.264 Baseline, 640×480 | Modern playback that just happens to need a .3gp extension |
File is larger; loses the "tiny 3GP" advantage |
| Image Duration 5s | Default slideshow pacing — readable text on each TIFF | At 10 TIFFs that's a 50-second clip |
| Image Duration 1/24s | "Cinematic" stop-motion from a TIFF sequence | A 240-frame TIFF stack becomes a 10-second clip |
If you'd rather target a modern container, use TIFF to MP4 for H.264/AAC playback on iPhone and the open web, or JPG to 3GP when your sources are already JPEGs. To shrink the input TIFFs before converting, see Compress TIFF. For the reverse direction, 3GP to MP4 lifts legacy clips into modern playback.
Only one reason: the target device or pipeline can't play MP4. Modern phones, browsers, and streaming services all prefer MP4 H.264/AAC. If you're not specifically targeting a 3G-era handset, an MMS gateway, a legacy kiosk, or 3GP-only firmware, convert TIFF to MP4 instead — it's smaller per quality unit, plays on iPhone, and is supported by every social platform.
Yes. A multi-page TIFF is unpacked into individual frames, then sequenced into 3GP at your chosen Image Duration (default 5 seconds per frame). If you upload one 12-page TIFF with the default duration, the output is a 60-second slideshow. If you upload 12 separate single-page TIFFs with Merge images, the result is identical.
No. iOS does not include a native 3GP decoder — iPhone's video stack supports H.264 in MP4, MOV, and M4V containers only. You can play 3GP on iPhone via a third-party app like VLC for Mobile, but for direct playback in the Photos app or web sharing, convert to MP4.
Two reasons. First, TIFFs are typically uncompressed or losslessly compressed (LZW, Deflate) and carry full bit depth — easily 5–100 MB per page. Second, 3GP uses lossy video codecs (H.263, MPEG-4 Part 2, or H.264) designed for low-bitrate cellular streaming, and was downscaled to mobile resolutions (often 176×144 or 320×240). A 500 MB TIFF stack converting to a 2 MB 3GP slideshow is normal — you're trading archival quality for mobile compatibility.
QCIF is 176×144, CIF is 352×288 — both are the original ITU-T H.263 resolutions baked into the 1996 codec spec for low-bitrate video calls. They're what the oldest 3GP-only devices expect. Choosing 1920×1080 produces a technically valid 3GP file, but defeats the purpose: most legacy decoders that need 3GP will reject HD frames, and modern devices that handle HD prefer MP4 anyway.
Not directly from this page — image-to-video conversion produces a silent 3GP. If you need audio, convert TIFF to MP4 first using TIFF to MP4, then merge an audio track in a separate step, or use a video editor. 3GP audio codecs (AMR-NB, AMR-WB, AAC-LC) are supported by the format, but the slideshow generator outputs a video-only stream.
It's the inverse. "5 seconds per frame" means 0.2 fps; "1/24s per frame" means 24 fps (cinematic). For a readable photo slideshow, 3–5 seconds per frame is typical. For stop-motion or a fast scroll through a TIFF stack, pick 1/24s or 1/30s. The output clip length is simply (number of TIFFs) × (duration per frame).
3GP is a low-bitrate format designed for cellular video calls, not photo reproduction. H.263 in particular smooths fine detail aggressively. If your TIFFs contain small text, sharp line art, or fine charts and you're seeing mush, either (a) bump up the Quality Preset to "Very High", (b) raise the resolution to CIF 352×288 or 480×360, or (c) accept that 3GP isn't the right target and use TIFF to MP4 instead.
No. 3GP video has no alpha channel — transparent regions in a TIFF are flattened against the Background Color you select (default Black). If your TIFF logo or scan has a transparent background, pick a color that matches your downstream context (White for paper docs, a brand color for product imagery) before converting.