GeoTIFF Metadata Reader

Inspect GeoTIFF CRS, extent, pixel size, band count, nodata values, compression, and raster statistics directly in your browser.

Browser-based No upload GDAL-style metadata
Share this tool

-

Dimensions

pixels

Pixel Size

native units

Nodata

GDAL_NODATA

Data Type

sample format

Raster Footprint

CRS and Georeferencing

CRS

EPSG

Units

Origin

Pixel Size X

Pixel Size Y

Band Statistics

Raw TIFF Tags and GeoKeys

GeoTIFF Pixel Grid and Map Extent

A GeoTIFF stores normal TIFF image pixels plus georeferencing tags. The tiepoint anchors a raster pixel to map coordinates, pixel size defines ground resolution, and the coordinate reference system explains whether values are decimal degrees, metres, or feet. This reader exposes those fields in a GIS-friendly format.

GeoTIFF raster georeferencing diagramRaster grid with tiepoint, pixel size, bounding box labels, and CRS label. Top-left tiepoint north east pixel size X pixel size Y CRS / EPSG embedded Raster bands extent, resolution, nodata, stats

What Is GeoTIFF Metadata?

GeoTIFF metadata is the set of embedded tags that turns a TIFF image into a geospatial raster. A plain TIFF can store pixels, compression, bit depth, and color interpretation. A GeoTIFF adds map-aware fields such as coordinate reference system, affine transform, tiepoints, pixel scale, bounding box, band count, and nodata values. Those details tell QGIS, ArcGIS Pro, GDAL, rasterio, and web mapping pipelines where the raster belongs on the earth.

This browser-based GeoTIFF metadata reader is built for quick inspection. Drop a DEM, satellite scene, drone orthomosaic, land cover raster, scanned map, or Cloud Optimized GeoTIFF and see the fields analysts usually check with gdalinfo. The file is opened locally in your browser, so sensitive imagery and survey data are not uploaded.

How to Read GeoTIFF CRS and EPSG Codes

The CRS section shows the embedded GeoKeys that identify the raster's coordinate system. A projected raster may report a key such as EPSG:32632 for WGS 84 / UTM zone 32N, while a geographic raster may report EPSG:4326. If the file contains only a citation string, the reader displays that text rather than guessing a code. If CRS tags are missing, the tool says so clearly because coordinate values alone are not enough to identify a reliable projection.

FieldMeaning
ProjectedCSTypeGeoKeyEPSG code for a projected CRS, often UTM or a national grid.
GeographicTypeGeoKeyEPSG code for a latitude/longitude CRS such as WGS 84.
ModelPixelScaleGround size of each raster pixel in native CRS units.
ModelTiepointAnchor connecting raster row/column space to map coordinates.
GDAL_NODATAPixel value treated as empty or invalid during analysis.

Understanding GeoTIFF Extent and Pixel Size

Extent describes the raster footprint: west, south, east, and north in the file's native coordinate reference system. Pixel size describes raster resolution. A 10 metre Sentinel-2 band has a very different analytical meaning than a 30 metre Landsat band or a 0.05 metre drone orthomosaic. This reader keeps those values in native units rather than converting them automatically, which avoids mixing metres, feet, and degrees.

When georeferencing tags are present, the footprint diagram in the reader places the bounding coordinates around a raster grid. When those tags are absent, the raster may still be a valid TIFF, but GIS software will need a sidecar file, manual georeferencing, or external metadata before it can be mapped accurately.

Band Count, Nodata Values, and Raster Statistics

Band metadata is essential when checking elevation models, multispectral imagery, thermal rasters, or classified land cover. The reader reports band count, bit depth, sample format, compression, and nodata value, then calculates min, max, mean, standard deviation, valid pixel count, and nodata pixel count. It starts with sampled statistics so large rasters remain responsive. A full statistics button is available when you need exact values and your browser has enough memory.

Why Browser-Based GeoTIFF Inspection Is Safer

Raster files often contain private project locations, client imagery, mining prospects, utility corridors, crop health data, or restricted environmental observations. Uploading those files to a generic converter is unnecessary when the task is only metadata inspection. This tool uses your browser's file API and geotiff.js to parse the selected file locally. The server renders the page; it does not receive your raster bytes.

GeoTIFF Metadata in QGIS, GDAL, and ArcGIS

This reader is designed for quick checks before opening heavier desktop software. In QGIS, the same information appears under Layer Properties and the Information tab. In ArcGIS Pro, raster metadata appears in catalog details and raster properties. In GDAL, the closest command-line equivalent is gdalinfo input.tif. Use desktop GIS or GDAL when you need reprojection, overviews, histogram generation, color tables, or edits to the raster itself.

Frequently Asked Questions

Does this GeoTIFF reader upload my file?

No. The file is read with the browser file API and parsed locally. The server never receives the raster bytes.

Can it read Cloud Optimized GeoTIFF files?

Yes. A COG is still a GeoTIFF, so local COG files can be inspected. This tool reads the selected local file rather than making HTTP range requests.

Why does my file say CRS not embedded?

The TIFF may lack GeoKeys, or the CRS may live in external project documentation. The reader does not guess CRS from coordinate ranges because that can produce wrong GIS decisions.

Are the raster statistics exact?

The first result uses a sampled read to stay fast. Click Calculate full statistics when you need exact values across every readable pixel.

Can this reproject a GeoTIFF?

No. It is a metadata reader, not a raster processing engine. Use GDAL, QGIS, rasterio, or ArcGIS Pro to reproject or resample raster data.