What command line utilities does GDAL provide?

Updated

GDAL ships with a set of command line utilities for data translation and processing, and the documentation groups them under Programs, split into a gdal application and the "Traditional" applications. If you want to know what a specific tool does or how to call it, the fastest route is the Programs section of the GDAL documentation, where each program has its own page describing its parameters and usage. The utilities exist because GDAL is, at its core, a translator library for raster and vector geospatial data formats released under an MIT style Open Source License by the Open Source Geospatial Foundation — the command line tools are the packaged way to reach that library's translation and processing capabilities without writing code.

How the programs are organized

The documentation's Programs area is divided into two groups:

  • The gdal application — the newer, unified command line entry point.
  • "Traditional" applications — the long-standing individual utilities that predate the unified application.

Both groups are listed in the same Programs section, so you can browse either style depending on what you already have in your scripts or habits.

What the utilities are for

The stated purpose of the bundled utilities is data translation and processing. That covers the two data models GDAL exposes:

Data model What the library presents
Raster A single raster abstract data model to the calling application for all supported formats
Vector A single vector abstract data model to the calling application for all supported formats

Because the library abstracts formats behind one model, the command line utilities can operate across the many raster and vector drivers GDAL supports rather than being tied to one file type. The driver list in the documentation is long and varied — raster drivers alone include entries such as AAIGrid, ADRG, AIG, COG, DTED, ECW, ENVI, and FITS, among many others.

Finding the right tool for a task

  1. Go to the Programs section of the GDAL documentation.
  2. Decide whether you want the gdal application or a "Traditional" application.
  3. Open the page for the specific program — each one documents its own parameters and usage.
  4. Match the tool to your task: translation (moving data between formats) or processing.

The expected result is that you end up on a single program page that tells you exactly which arguments to pass, rather than guessing from the library-level description.

Practical notes

  • The documentation is also available as a PDF for offline browsing, which is useful if you need to look up program usage without network access.
  • GDAL can be quoted in publications using its Digital Object Identifier, and the site maintains a NEWS page describing releases — the excerpt references the August 2026 GDAL/OGR 3.13.3 release.
  • Download options listed include source code, binaries, and containers, so the utilities can be obtained in whichever form fits your environment.

Common sticking point

The main confusion is assuming there is one single command. There isn't — the documentation deliberately separates the gdal application from the traditional applications, and each program has its own page. If a command you remember doesn't appear where you expect, check the other group before concluding it doesn't exist.