Initializing... drag & drop files here
Supports: XCF
.tif (3-letter, used by older Windows and DOS-era pipelines) or .tiff — both contain the same TIFF 6.0 bytestream.XCF is GIMP's native project format — short for eXperimental Computing Facility, the UC Berkeley lab where GIMP was born. It stores layers, paths, channels, selections, transparency, guides, and (since GIMP 2.10) zlib-compressed pixel data. The trade-off: only GIMP and a small handful of tools (Krita, ImageMagick) can open it. TIFF, first published by Aldus in 1986 and now maintained by Adobe under the TIFF 6.0 spec (June 1992), is the universal lossless container for print, scanning, and archival workflows. The .tif extension is the same format with a 3-letter suffix preferred by legacy Windows pipelines and many prepress RIPs.
.tif rather than .tiff. The bytes are identical, only the extension differs.| Property | XCF | TIF |
|---|---|---|
| Developer | GIMP (Spencer Kimball, Peter Mattis) | Aldus 1986; maintained by Adobe since 1994 |
| First released | December 15, 1997 | Autumn 1986 (current spec: TIFF 6.0, 1992) |
| Native compression | RLE; zlib since GIMP 2.10 | None, LZW, PackBits, Deflate, JPEG, CCITT G3/G4 |
| Layers | Native (each layer + mask, blend mode, opacity) | Only via Adobe layer extension or as multi-page IFDs |
| Color depth | 8/16/32-bit per channel; gray, RGB, indexed | 1, 8, 16, 32-bit; gray, RGB, CMYK, Lab, indexed |
| Color profile (ICC) | Stored | Stored |
| Max file size | Limited by host filesystem | ~4 GB (32-bit offsets); 18 EB with BigTIFF |
| Print industry use | Not supported | Industry standard (PDF/X workflows accept TIFF) |
| Software support | GIMP, Krita, ImageMagick, a few viewers | Universal: Photoshop, InDesign, Capture One, scanners, RIPs |
| Compression | Lossless? | When to use |
|---|---|---|
| LZW | Yes | Default for general TIFF; best compatibility across prepress and Photoshop |
| Deflate (zip) | Yes | Smaller than LZW for photographic images; sometimes blocked by old RIPs |
| PackBits | Yes | Fast, simple run-length; fine for screenshots and flat art |
| None (uncompressed) | Yes | Largest files; choose for forensic / scientific archives where any encoder is suspect |
| JPEG-in-TIFF | No | Only when small file size matters more than fidelity; avoid for print |
| CCITT Group 4 | Yes | 1-bit black-and-white only — fax, signed documents, line art |
Yes. They are byte-for-byte identical — both store TIFF 6.0 data per the 1992 Adobe specification. The only difference is the file extension. .tif is the 3-letter form preferred by older Windows, DOS, and some prepress systems that truncate to 8.3 filenames; .tiff is the 4-letter form used by macOS and Linux. Renaming .tiff to .tif (or vice versa) is non-destructive.
No. This converter flattens the XCF to a single composited image before writing the TIF. If you need each layer kept as a separate page inside the TIFF (TIFF supports multi-IFD pages), that has to be done from GIMP's "Export As..." dialog with the "Save layers" checkbox enabled — most third-party readers (Photoshop, browsers, scanners) will only see the first page anyway, so flattening is the safer default for sharing. Keep your .xcf as the editable master.
XCF compresses pixel data with zlib (since GIMP 2.10) and stores layers as their own bounding boxes. A flattened TIF with LZW or Deflate is typically larger because every pixel of the image is stored once at full resolution, including transparent areas the layered XCF could skip. Switch to Deflate compression or accept JPEG-in-TIFF if you need smaller output and the TIF isn't going to print.
LZW is the safer default — it's been part of TIFF since 1988 and every prepress RIP, scanner, and image library supports it. Deflate (zlib) usually produces 5-15% smaller files for photographic content but is technically a TIFF extension and can be rejected by very old equipment. For modern Photoshop, InDesign, or web archives, either is fine.
Both are lossless, but they target different audiences. Use TIF for print (CMYK support, ICC profiles, 16-bit channels, multi-page archive), scientific imaging, and long-term preservation. Use XCF to PNG for web, screen previews, and anywhere browsers will display the file directly — PNG has no CMYK and caps at 8 or 16-bit RGB.
The output here is RGB. For a true CMYK separation suited to offset press, do the soft-proof and Image → Mode → CMYK conversion inside GIMP (with a plugin) or Photoshop using the printer's ICC profile, then export the CMYK TIFF directly. Most modern presses now accept RGB TIF and convert in their RIP, but ask your print provider before assuming.
They're rasterized into the flattened pixels. TIFF does not store editable vector paths or live text. If you need those preserved, keep the XCF, or export to XCF to PDF where text and paths can survive as vector content.
Yes — it's the default in nearly every scanner and document-management system. Multi-page TIFF (one IFD per page) using CCITT Group 4 compression is the long-time standard for black-and-white scanned text; LZW or Deflate works for color scans. It's also the format Tesseract OCR prefers for accuracy.
Standard TIFF uses 32-bit offsets, capping a single file at roughly 4 GB. BigTIFF (a backwards-compatible variant with 64-bit offsets) extends that to 18 exabytes and is supported by ImageMagick, libtiff, and Photoshop, but not all consumer software opens BigTIFF. For a typical XCF flattened to TIF, you'll be well under the 4 GB limit.
It's identical. XCF to TIFF produces the same TIFF 6.0 bytestream — only the output extension differs. Pick this .tif page if your downstream system expects 3-letter extensions; otherwise either works.