Sea Temperature by Satellite, 5 km Grid
The sea temperature at your place, read by satellite on a 5 km grid, with the date of the measurement and how far the sampled point sits.
Related tools
All Weather & environment tools →Pick a place on a coast and this page gives you one number: what a satellite analysis says the sea surface was, on a five-kilometre grid, on the day the product was last published. It also tells you two things most sea-temperature pages leave out — the date that number belongs to, and how far from your place the sampled pixel actually sits. Both matter more than they sound. The product runs a day behind and its cut-over slides through the afternoon, so a page that writes "today" is guessing. And a beach coordinate read off a map falls on sand, not water: the nearest pixel carrying sea can be two kilometres away, occasionally five. On a coarser grid it was eleven, and the number still looked perfectly reasonable.
How to use it
- Choose your place — a coastal town from the list, or the button that uses your position. Coordinates are rounded to about a kilometre before anything leaves your browser.
- Read the temperature, then read the date under it. The two belong together: the analysis is published once a day and runs a day behind, so the figure is yesterday's sea, not this morning's.
- Check how far the sampled pixel is. Under half a kilometre it covers your place; at two or three kilometres it is the nearest water the satellite could see, which for a sheltered bay is not quite the same sea.
- Glance at the spread line. When the sea around your point varies by more than a couple of tenths, the page says so — near a river mouth, a lagoon or a headland, eleven kilometres can hold two different seas.
- If the page says there is no sea nearby, it means exactly that — no water within about eleven kilometres — and not that the service failed. The two are written differently, on purpose.
Where the number comes from
The source is NOAA's Geo-polar Blended analysis: several satellites, geostationary and polar-orbiting, merged into one daily field on a 0.05° grid — about five kilometres. Our server asks for a small box around your place rather than a single point, and then keeps the nearest cell that actually carries sea. That box costs roughly 1.1 kilobytes and four tenths of a second, and it is the whole difference between a page that answers and a page that shrugs.
Why a box at all? Because a coordinate taken from a map sits on land. Tested on twenty European bathing beaches, asking for the exact point on a twenty-five-kilometre grid returned nothing at all nine times out of twenty — Brighton and Faro among them — and when it did answer, the pixel was 8.1 kilometres away in the median case. The five-kilometre grid with a box answered twenty times out of twenty, at 2.2 kilometres in the median. Raising the resolution never removes the problem on its own: even on a one-kilometre product, the exact pixel at Biarritz is empty.
What it answers well, and what it does not
- You are choosing between two stretches of coast for a holiday and want the real difference, not the brochure's: eighteen degrees in the Channel against twenty-six in the Balearics is the kind of gap this answers straight away.
- You swim or dive through the year at the same spot and want to see the season turn — the water lags the air by weeks, and a page that shows the date lets you follow that lag honestly.
- What it cannot do is tell you the temperature of the water at the end of the pier this afternoon. It is a satellite analysis of the surface, a day old, averaged over twenty-five square kilometres. For an actual swim, the only honest instrument is a thermometer.
Three readings, taken the same afternoon
- Nice, 18 September 2026: 25.8 °C. Fourteen of the twenty-five pixels in the box carried sea; the other eleven were the Alpes-Maritimes. On the coarser twenty-five-kilometre product the same request gave 25.84 °C — indistinguishable, and taken 11.6 kilometres out to sea.
- Lisbon, the same day: 16.4 °C — nine degrees colder than Nice, at almost the same latitude. That is the Atlantic upwelling, and it is the single most useful thing this page tells a traveller who assumes southern means warm.
- Palma, on the same product: twenty-three of the thirty pixels in the window were masked, and the two nearest valid ones gave 26.73 and 26.39 °C. A third of a degree hangs on which pixel is picked, which is why the choice is made by distance and settled the same way every time rather than by whichever line the file happens to list first.
What this page is not
- It is not today's temperature. The analysis is published once a day and runs a day behind, and the cut-over slides through the afternoon. The page shows the date the service itself stamps on the data, and never writes "today".
- It is the surface, and only the surface. A metre down the water can be a degree colder; in a thermocline, several. The product describes the skin the satellite sees, not the column you swim through.
- The swimming bands are ours, not the agency's. NOAA publishes a temperature; it does not say at what point water becomes pleasant. Those thresholds are an editorial guide, and the page labels them as such rather than lending them an authority they do not have.
- Inland, there is nothing to read, and the page says so rather than reaching for the nearest coast. Measured from Paris, finding any sea at all means widening the search to about two hundred kilometres — which would be an answer, but not the right one.
Privacy
Processed on a serverThe place you pick is rounded to about a kilometre in your browser, then sent to our server, which asks NOAA's CoastWatch ERDDAP service for a small box of sea-surface values around it. NOAA sees our server, never your address, and nothing you type reaches it. The last town you chose stays in your browser's local storage under the allin_tools key; a position you share is used for the request and never stored. No lookup is logged or written to any table.
Frequently asked questions
Is this the temperature at the beach right now?
No, on two counts. It is a satellite analysis published once a day and running a day behind, so the page shows the date the data belongs to. And it describes a five-kilometre cell of open surface, not the shallow water at the shore, which warms and cools far faster. The page gives you the date and the distance precisely so you can judge how close the two are.
Why does it say there is no sea near my town?
Because the search box around your place is about eleven kilometres across, and every cell in it is land. That is a real answer, not a failure — and it is written differently from a service outage on purpose. Widening the search would eventually find water, but from an inland city that water is two hundred kilometres away and tells you nothing about where you are.
Why show how far away the pixel is?
Because without it the number cannot be judged. On a twenty-five-kilometre grid, Nice returned a perfectly believable 25.84 °C taken 11.6 kilometres out to sea — nothing on screen would have hinted at the gap. Showing the distance turns an unverifiable figure into one you can weigh: under half a kilometre it covers you, at four it is the nearest water there was.
Does the sea really differ within a few kilometres?
Often enough to matter. At Palma the two nearest valid cells differed by a third of a degree; near a river mouth, a lagoon or a headland the gap is wider still. That is why the page prints the range across the measured cells of the box when it is more than a couple of tenths, and stays quiet about it when the water is even.
Which product is this, and may it be reused?
It is NOAA's Geo-polar Blended day-and-night analysis, and its own licence attribute says data use is free and open under the GHRSST protocol — no clause restricting commercial use, no wording imposed. A second product of identical resolution was rejected on purpose: its licence text carries a clause restricting part of its record to pure academic research, which would bite the day a history view were added.
How fresh is the figure, and how often does it change?
Once a day, and the page keeps a reading for six hours before asking again. Six rather than twenty-four because the service's notion of the latest available day shifts during the afternoon: a longer cache would keep showing the day before last for hours after the new field went up. The source sends no cache headers at all, so the whole schedule is ours to set and ours to state.