PicaJet
Search Build shortlist

Reference Formats

GeoTIFF

GeoTIFF is a public-domain extension of the TIFF raster image format that embeds georeferencing metadata directly in the image file as TIFF tags.

Extension

.tif

Full name

GeoTIFF (Geographic Tagged Image File Format)

Introduced

GeoTIFF 1.0 specification released November 1995; adopted as OGC Standard (version 1.1) in September 2019

Vendor

GeoTIFF Working Group (community-developed); formalized by the Open Geospatial Consortium

What is inside the container

A GeoTIFF is a single self-contained file: standard TIFF image data plus a defined set of TIFF tags that record coordinate reference system, pixel scale, and the transform mapping pixels to real-world coordinates. Because everything lives inside one .tif file, there is no companion .tfw world file or separate projection file to lose, unlike older raster georeferencing workarounds. GeoTIFFs can hold anything from a single satellite band to multi-band imagery or elevation data, and the same TIFF compression options (LZW, DEFLATE) apply.

How to open it

Desktop GIS QGIS opens GeoTIFFs directly as raster layers and reads the embedded CRS
Desktop GIS Esri ArcGIS Pro imports GeoTIFFs natively for raster analysis and mapping
Image viewers Most standard image viewers (Preview, IrfanView) display the pixel data but ignore the georeferencing tags
Command line GDAL's gdalinfo and gdal_translate read metadata and convert GeoTIFFs from scripts or pipelines

For archives

Store GeoTIFFs as-is since the format is already a single self-describing file with no companion-file risk; preserve the original bit depth and compression rather than re-encoding to a lossy format. For DAM preview generation, extract the embedded CRS and extent tags to render a thumbnail and map footprint without needing the original GIS software.

GeoTIFF grew out of an informal effort in the early 1990s to add coordinate information to the widely used TIFF image format; SPOT Image Corporation proposed an early version limited to Universal Transverse Mercator in 1994, and the community-run GeoTIFF Working Group published the GeoTIFF 1.0 specification in November 1995. It remained a de facto, community-maintained standard for over two decades before the Open Geospatial Consortium formally adopted GeoTIFF 1.1 as an OGC Standard in September 2019, keeping it backward compatible with the original 1995 specification.

Technically, a GeoTIFF is ordinary TIFF raster data carrying an additional set of defined tags that record the coordinate reference system, the pixel-to-map transform, and other georeferencing parameters directly inside the file. That single-file design is what sets it apart from older raster georeferencing methods that relied on a separate .tfw world file sitting next to a plain image — lose the world file and the image loses its location.

  • Satellite and aerial imagery, single- or multi-band
  • Digital elevation models (DEM) storing height rather than color per pixel
  • Classified land-cover or other scientific raster data
  • Cloud Optimized GeoTIFF (COG) variants, tiled and internally indexed for fast partial reads over HTTP

For a DAM, GeoTIFF is comparatively easy to manage precisely because it is self-contained: there’s one file to version, one file to preview, and the georeferencing metadata can be read straight out of the TIFF tags to populate searchable fields like coordinate system and geographic extent without opening a GIS application. A DAM that supports GIS assets can generate a map-footprint thumbnail from those embedded tags, which is not possible for formats where the spatial reference lives in a separate file.

The tradeoff is file size: GeoTIFFs holding high-resolution satellite or aerial imagery can run into gigabytes, so DAM storage and preview pipelines built for photography assets often need adjusted thumbnail-generation and streaming logic (or Cloud Optimized GeoTIFF handling) to deal with these files efficiently.

Frequently asked

What makes GeoTIFF different from a regular TIFF image in a DAM?

A GeoTIFF carries embedded coordinate reference system and geolocation tags inside the same file, so a DAM can read real-world extent and projection metadata without any companion file.

Does a GeoTIFF need a separate world file like older georeferenced images?

No. Unlike a plain image paired with a .tfw world file, a GeoTIFF's georeferencing tags are embedded in the TIFF structure itself, which is why the format needs no companion file to stay geolocated.

Can a standard image viewer display a GeoTIFF?

Yes, most image viewers will render the pixel data, but they generally ignore the georeferencing tags, so the file looks like an ordinary photo without map context.

Why do GeoTIFF files get so large in a DAM archive?

They often store high-resolution satellite or aerial raster data at full bit depth across multiple bands, which produces much larger files than typical photography assets of similar pixel dimensions.

When was GeoTIFF standardized by the OGC?

The Open Geospatial Consortium approved GeoTIFF version 1.1 as an official OGC Standard in September 2019, after the format had already been a widely used community specification since 1995.

Should a DAM convert GeoTIFF to another format for previews?

Not necessarily for storage, but many DAMs generate a lightweight rendered thumbnail or Cloud Optimized GeoTIFF variant for fast web preview while keeping the original file untouched.

What metadata should a DAM extract from a GeoTIFF on ingest?

Coordinate reference system, pixel resolution, and geographic bounding box read from the embedded TIFF tags, all of which can be pulled with tools like GDAL's gdalinfo.

Is GeoTIFF a good archival format for a DAM?

Yes; because it's a single self-describing file with a long-standing OGC standard behind it, it archives cleanly without the companion-file risk that affects formats like Shapefile.

Sources