View metadata and band statistics of raster files
Instant analysis powered by GDAL WASM
Files processed in browser, never uploaded
Complete statistics for each band
Upload a raster file to view its metadata
Driver, size, CRS, resolution
Upload a file to see metadata automatically
Raster Info opens the header of any GDAL-supported raster and reports what is actually inside: the coordinate reference system, the geographic extent, the pixel size, the band count with each band's data type, and the nodata value. It also computes minimum, maximum, mean, and standard deviation for every band - all with GDAL WASM running locally in the browser.
It answers the questions that come before any real work starts: which projection is this file in, why do two layers refuse to line up, is this DEM really 30-meter resolution, and are outlier values skewing the histogram. That makes it a natural QA stop for downloaded data or files from unfamiliar sources.
Upload the raster you want to inspect - everything from GeoTIFF and NetCDF to HDF, GRIB, and SRTM .hgt elevation files is readable.
The file is parsed locally: projection, extent, resolution, band list, and nodata value appear immediately, and per-band statistics are computed automatically.
Read the values straight off the panel - nothing is generated, so there is nothing to download, and the file never leaves your machine.
AThe extent is reported in the file's own coordinate system. A raster projected to UTM shows large easting and northing values in meters, while an EPSG:4326 file shows degrees. Always read the listed CRS first, then interpret the extent in those units.
AYes - compare the CRS and pixel size of both files. If either differs, the layers will not overlay pixel-perfectly, and you should reproject one of them with Raster Reprojection before merging or combining them.
AIt is the sentinel number the format uses for missing pixels, such as -9999 or 255. Operations like raster merge and Fill NoData rely on it to know which pixels to skip or interpolate, so a wrong or missing nodata value is a common hidden cause of strange analysis results.