ITHMB File Documentation
Summary
An .ithmb file is an Apple iPod/iPhone/iPad thumbnail cache, a proprietary database that older Apple devices built to preview synced photos quickly. Its MIME type is application/octet-stream. It is not a normal image: it packs many small thumbnails back-to-back as raw pixel data with no per-image header, so ordinary viewers cannot open it. To get pictures out, run it through an extractor such as iThmb Converter (Windows) or File Juicer (Mac), which export the frames to JPG or PNG. The output is low-resolution thumbnails only, not full-quality originals.
Technical details
| Feature | Value |
|---|---|
| Full name | Apple iPod/iPhone/iPad thumbnail cache |
| File extension | .ithmb |
| MIME type | application/octet-stream |
| Format type | Proprietary binary thumbnail database (many images in one file) |
| Developer | Apple |
| Introduced | circa 2004 (photo-capable iPod) |
| Open standard | No — undocumented, proprietary |
| Created by | iTunes, when syncing photos to the device |
| Pixel storage | Raw, uncompressed; commonly 16-bit RGB565 (some UYVY variants) |
| Magic number | None — no per-image or file signature |
| Geometry source | Implied by the numbered filename (e.g. F1019_1.ithmb) |
| Contents | Low-resolution preview thumbnails only, not originals |
| Typical location | Hidden Photos/Thumbs folder on the device or backup |
| Extract with | iThmb Converter, File Juicer, GraphicConverter |
| Related extensions | .jpg, .png, .bmp, .heic, .db |
What is an ITHMB file?
An .ithmb file (from “iThumb”) is Apple’s internal thumbnail cache, used from around 2004 on iPods that could display photos and later on early iPhones and iPads. When you synced photos to the device through iTunes, the device pre-rendered small preview versions of each picture and stored them together in .ithmb files inside a hidden photo-cache folder. Showing these caches let the photo grid scroll instantly, without re-decoding a full-size image every time you flicked the wheel or swiped.
The key thing to understand is that ITHMB is a cache, not a photo. It contains only downsized thumbnails, often a few hundred pixels on a side, and it has no documented public specification. That combination, low resolution plus a proprietary undocumented layout, is why the file both refuses to open in a normal viewer and disappoints anyone hoping to recover full-quality originals from it.
How the file packs many thumbnails into one blob
An ITHMB file is a flat container: many fixed-size thumbnails stored one directly after another as raw, uncompressed pixel data, with nothing between them. There is no per-image header, no length field, no offset table, and no file signature at the start. Reading it is less like opening an image and more like reading a strip of film where every frame is exactly the same size and you must already know that size to cut them apart.
The pixels are typically stored as 16-bit RGB565: two bytes per pixel, with 5 bits for red, 6 for green and 5 for blue. Some device and size variants use a UYVY-style layout instead. Because the data is uncompressed and headerless, the file’s total size is simply the number of thumbnails times the bytes-per-thumbnail, and a reader can only locate frame boundaries if it knows the exact width, height and pixel format in advance.
Why the filename, not the file, defines the geometry
Since the bytes carry no dimensions, the geometry lives in the filename. Different numbered .ithmb files (for example F1019_1.ithmb, 1009.ithmb) correspond to the different thumbnail sizes the iPod or iOS photo interface used, one file per size class. An extractor recognises the naming pattern, looks up the width, height and pixel format that Apple paired with that number, and uses those to slice the raw stream into individual pictures. This is exactly the metadata an ordinary image viewer expects to find inside a file and cannot find here, which is the concrete reason Windows Photos or macOS Preview show an error or a screen of noise: there is no header to parse and no way to guess the frame size from the bytes alone.
Extracting the thumbnails with a dedicated tool
To get usable pictures out you need a tool that knows the ITHMB geometry and can carve the stream into frames. On Windows, iThmb Converter opens the file (or points at a whole device or backup folder), slices the cache, and exports each thumbnail to JPG, PNG or BMP. On macOS, File Juicer carves the embedded images when you drag the file onto it, and GraphicConverter can read the raw thumbnail data if you supply the pixel geometry. These are the maintained extractors; be wary of “free ITHMB viewer” download sites, which frequently bundle adware because the format genuinely confuses people and draws that kind of traffic. PNG output is the safest target, since it is lossless and preserves the already low-resolution pixels exactly.
Where ITHMB files come from, and their limits
Almost everyone who meets an ITHMB file is doing data recovery: pulling photos off an old iPod Classic, Photo, nano or touch; finding these files in an old iTunes backup or a recovered folder; or trying to salvage pictures from a dead older iPhone where only the thumbnail cache survived. In every case the important limit is the same. ITHMB holds previews the device generated for speed, not the master images. The full-resolution originals live elsewhere, in the device’s photo library or on the computer that synced it. If those are gone, the thumbnails are a last resort, worth extracting for a small usable copy but never a source of full-quality photos. Modern iPhones and iPads do not expose photos this way at all; they use a Photos library of HEIC and JPEG images with on-device caches you never see, so ITHMB is effectively a legacy artifact you only encounter with old hardware or old backups.
References
- iThmb Converter — what the ITHMB format is
- File Juicer (Echo One) — extract images from .ithmb
- MajorGeeks — how to view and convert ITHMB files
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.