Cook fire, 26 July 2025 Cook
The fire started on 26 July 2025 in Cook, Australia, and satellites saw it burning for 24 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 14,856 hectares from heat detections, spread across a single municipality.
It is the 460th largest in Queensland since 2016 (of 1737 with a page). Number 302 in Australia in 2025, of 1124.
Compare with…
Suggestions: Cook · 2023Cook · 2020Cook · 2022Cook · 2018
- Burnt area
- 14,856ha
- GWIS perimeter (Copernicus)
- Duration
- 24days
- 26 Jul 2025 – 18 Aug 2025
- Municipalities hit
- 1
- local government areas
- Started on
- 26 Jul
- 2025
- Heat detections
- 480
- in a single hotspot: 111 MW
- Danger at start
- 23
- High · FWI index
- Average daily power
- 85MW
- detected power per day, on average
Where it burned
How it evolved, day by day
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone 8 days without rain (1 mm or more) when it started.
This area had burned before
99% of the perimeter overlaps earlier fires recorded since 2016: 5,121 ha in 2016, 4,076 ha in 2017, 5,072 ha in 2018, 1,037 ha in 2019, 10,505 ha in 2020, 499 ha in 2021, 8,900 ha in 2022, 11,501 ha in 2023. Part of it burned more than once, so the yearly figures add up to more than the 14,670 ha that had burned before.
- 11,501 ha Cook fire, October 2023 113,118 ha in total; the hectares shown are those it shares with this fire
- 9,106 ha Cook fire, July 2020 14,918 ha in total; the hectares shown are those it shares with this fire
- 6,305 ha Cook fire, July 2022 25,681 ha in total; the hectares shown are those it shares with this fire
- 3,820 ha Cook fire, July 2018 12,804 ha in total; the hectares shown are those it shares with this fire
- 96 ha Cook fire, July 2019 7,192 ha in total; the hectares shown are those it shares with this fire
- 6 ha Cook fire, September 2017 9,599 ha in total; the hectares shown are those it shares with this fire
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Cook where it started14,924 ha reached on 22 Jul0.1 %
Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance runs from the point marking the centre of each area to the nearest fire: staying a kilometre away does not mean it reached the houses.
People and buildings inside the perimeter
GHSL 2025Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2025, satellite-based estimate).
This is an estimate on 100 m cells, made from satellite imagery and census data: it does not mean that homes burned or that anyone was harmed. The perimeter also contains land that never burned. The GHSL 2025 epoch is a projection made from 2020 and earlier data.
Source: Global Human Settlement Layer (GHS-BUILT-S and GHS-POP R2023A), European Commission Joint Research Centre (JRC), © European Union, CC BY 4.0. Sum inside the perimeter computed by WorldFires. human-settlement.emergency.copernicus.eu
The weather day by day
ECMWF ERA5 reanalysis at the fire location, the standard reference for past weather, and the Canadian Fire Weather Index (the same system Copernicus uses), computed by WorldFires from that data. Days after the fire run until the first rain.
Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 19 Jul | 30.9 °C | 54 % | 28 km/h | 0.4 mm | High 23 |
| 20 Jul | 31.4 °C | 49 % | 23 km/h | 0.0 mm | Moderate 21 |
| 21 Jul | 31.8 °C | 53 % | 30 km/h | 0.7 mm | Moderate 20 |
| 22 Jul | 32.0 °C | 55 % | 31 km/h | 1.6 mm | Moderate 12 |
| 23 Jul | 31.8 °C | 55 % | 32 km/h | 0.7 mm | Moderate 17 |
| 24 Jul | 31.8 °C | 51 % | 42 km/h | 0.0 mm | High 24 |
| 25 Jul | 32.5 °C | 45 % | 52 km/h | 0.0 mm | High 32 |
| 26 Jul | 33.2 °C | 44 % | 44 km/h | 0.0 mm | High 29 |
| 27 Jul | 32.6 °C | 45 % | 34 km/h | 0.0 mm | High 26 |
| 28 Jul | 32.6 °C | 45 % | 32 km/h | 0.0 mm | High 26 |
| 29 Jul | 33.4 °C | 43 % | 38 km/h | 0.0 mm | High 30 |
| 30 Jul | 33.0 °C | 44 % | 31 km/h | 0.0 mm | High 27 |
| 31 Jul | 33.1 °C | 43 % | 32 km/h | 0.0 mm | High 28 |
| 1 Aug | 31.9 °C | 47 % | 29 km/h | 0.0 mm | High 26 |
| 2 Aug | 30.4 °C | 39 % | 37 km/h | 0.0 mm | High 29 |
| 3 Aug | 29.5 °C | 47 % | 36 km/h | 0.0 mm | High 29 |
| 4 Aug | 30.6 °C | 40 % | 35 km/h | 0.0 mm | High 30 |
| 5 Aug | 31.7 °C | 36 % | 34 km/h | 0.0 mm | High 32 |
| 6 Aug | 31.5 °C | 41 % | 39 km/h | 0.0 mm | High 32 |
| 7 Aug | 31.3 °C | 45 % | 46 km/h | 0.1 mm | High 35 |
| 8 Aug | 31.1 °C | 42 % | 45 km/h | 0.0 mm | High 35 |
| 9 Aug | 31.5 °C | 42 % | 33 km/h | 0.0 mm | High 28 |
| 10 Aug | 31.1 °C | 41 % | 22 km/h | 0.0 mm | High 26 |
| 11 Aug | 32.0 °C | 41 % | 42 km/h | 0.0 mm | High 34 |
| 12 Aug | 31.3 °C | 39 % | 46 km/h | 0.0 mm | High 36 |
| 13 Aug | 28.7 °C | 57 % | 48 km/h | 0.4 mm | High 30 |
| 14 Aug | 31.0 °C | 44 % | 53 km/h | 0.0 mm | High 33 |
| 15 Aug | 30.8 °C | 34 % | 41 km/h | 0.0 mm | High 34 |
| 16 Aug | 30.7 °C | 35 % | 39 km/h | 0.0 mm | High 34 |
| 17 Aug | 30.9 °C | 30 % | 38 km/h | 0.0 mm | High 37 |
| 18 Aug | 31.8 °C | 33 % | 40 km/h | 0.0 mm | Very high 39 |
| 19 Aug after | 31.1 °C | 36 % | 40 km/h | 0.0 mm | High 36 |
| 20 Aug after | 32.1 °C | 44 % | 40 km/h | 0.0 mm | High 34 |
| 21 Aug after | 30.3 °C | 55 % | 52 km/h | 0.4 mm | High 32 |
| 22 Aug after | 31.4 °C | 49 % | 51 km/h | 0.0 mm | High 34 |
| 23 Aug after | 33.8 °C | 33 % | 48 km/h | 0.0 mm | Very high 38 |
| 24 Aug after | 34.6 °C | 25 % | 43 km/h | 0.0 mm | Very high 42 |
| 25 Aug after | 32.5 °C | 42 % | 46 km/h | 0.0 mm | Very high 38 |
| 26 Aug after | 32.7 °C | 33 % | 42 km/h | 0.0 mm | High 37 |
| 27 Aug after | 33.4 °C | 35 % | 33 km/h | 0.0 mm | High 36 |
| 28 Aug after | 33.5 °C | 37 % | 28 km/h | 0.0 mm | High 33 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.
The smoke
CAMS · CopernicusOn 28 July 2025 the air beside the fire reached 24 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).
Particles from the Copernicus CAMS model at the centre of the perimeter; these are not measurements in each town. The pale bar is the worst hour, the solid one the daily average.
Open-Meteo.com (CC BY 4.0) · Copernicus Atmosphere Monitoring Service (CAMS)
Detections table · 480Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Cook fire last?
- GWIS (Copernicus) dates it between 26 July 2025 and 18 August 2025: 24 days between the first and last heat detection of the perimeter.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 14,856 hectares (148.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Cook (14,924 ha, 0.1 %).
- What was the weather like?
- During the fire the temperature reached 33.4 °C, humidity dropped to 30 % and gusts hit 53 km/h. The fire danger index (FWI) reached 39, class Very high.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Australia (geoBoundaries). It is not an official report.
Where to verify it
A satellite detection is not an official report. Final figures and the fire’s status are published by each country’s emergency service.
Emergency number: 000 · Emergency number and official warnings ›
Satellite cross-check
History of this page Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
No changes since 24 October 2026.
Does something look wrong on this page?
This page is built from satellite data and official records, and it sometimes gets things wrong: the wrong dates, the wrong town, two fires merged into one, or something that was not a wildfire at all. If you know this fire first-hand (you live nearby, saw it, fought it or reported on it), tell us what really happened and we will check it.
Report an error
How we know this
- Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery; 2 polygons grouped in this page.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 480 Suomi-NPP VIIRS detections on those dates.
- We have not matched this page with any official record.
- Weather: Copernicus ERA5 reanalysis at the fire location, in cells of about 25 km.
- Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2025, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.
Where this data comes from
The perimeter comes from the Copernicus Global Wildfire Information System (GWIS), which rebuilds it from MODIS and VIIRS heat detections and publishes it under CC BY 4.0. It is not measured on imagery as in Europe, so it is an estimate. Heat detections come from the VIIRS sensors aboard Suomi-NPP and NOAA-20, distributed by NASA FIRMS at 375 m resolution. Municipal boundaries come from geoBoundaries ADM2 (Creative Commons Attribution 4.0 International (CC BY 4.0)). The area per municipality is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ from each country’s official figure.