How to Read a Surf Forecast: Why Period Matters More Than Height

OwlPlot was built for photographers standing on coastlines, which meant it already needed tides and wind. Adding swell was a small step, and then something unexpected happened: surfers started using it. So we finished the job properly — swell, period, wind and tide for the same ten-day window as everything else, and a way for people to correct it.

If you have only ever looked at the wave height number, most of the value in a forecast is passing you by.

Height is the headline. Period is the story.

Every forecast leads with wave height, and it is the least informative number on the page in isolation.

The one to look at next is period — the seconds between passing wave crests. It tells you what kind of swell you are getting:

• Under 8 seconds. Wind swell. Generated locally by recent wind, disorganised, weak, and often closing out. The sea is choppy rather than lined up.
• 8 to 12 seconds. Mixed. Workable, and most ordinary days live here.
• 12 to 16 seconds and above. Groundswell. Generated by a distant storm and sorted by the journey, arriving in clean, evenly spaced lines with far more energy behind each one.

The reason period matters so much is that it does not simply add energy, it multiplies it. A long-period wave carries its energy much deeper in the water column, so it feels the seabed sooner, stands up harder and breaks with much more push. A 1-metre swell at 14 seconds will produce a bigger, better wave at the beach than a 1.5-metre swell at 6 seconds — and it will be a rideable shape rather than a mess.

So the habit worth building is to read the two numbers together. Height without period tells you almost nothing.

Wind decides whether it is worth the drive

Swell decides whether there are waves. Wind decides what the surface of them looks like.

Offshore wind blows from the land out to sea. It holds the face of the wave up, smooths the surface and grooms it. Light offshore is the condition everyone is chasing, and it is why dawn sessions have their reputation — offshore breezes are common in the early morning before the land heats up.

Onshore wind blows from the sea in. It gets under the wave and pushes it over early, and the surface turns to chop. A good swell can be ruined completely by a strong onshore.

OwlPlot works this out for the specific beach rather than making you do the geometry: it knows which way the shore faces, compares that with the wind direction for each hour, and shows you whether that hour is offshore or onshore. Strength matters as well as direction — a 30 km/h offshore can be too much of a good thing, holding waves up until they break too late.

The hour is the unit, not the day

Conditions turn over within a day, often sharply. Wind swings as the land warms. Tide moves through its cycle. A day that is unsurfable at noon can be clean at seven in the morning.

This is why the forecast is hourly, and why picking a different day keeps the hour you were already looking at. If you are checking Thursday at 3pm because that is when you can actually get to the beach, jumping to Friday should show you Friday at 3pm — not throw you back to 9am and make you scroll again.

Tide is the third variable. Which state suits a break is local knowledge that no model has, but knowing whether the water will be pushing or dropping while you are there is half of it.

Why the number never quite matches the beach

Here is the part that explains a lot of frustration with forecasts generally.

Marine models give you significant wave height — an average of the highest third of waves — in open water, offshore. What you care about is the face of the wave breaking in front of you, after the swell has crossed a particular seabed, refracted around a particular headland and squeezed into a particular bay.

The relationship between those two numbers is different at every single spot, and it is not a constant you can look up. Some beaches reliably produce a face twice the offshore figure. Others eat swell and hand you half. It is why the regulars at your local know to mentally translate the forecast, and why a newcomer reading the same number gets it wrong.

So the app asks people what they actually saw

Rather than pretend the model is the truth, OwlPlot lets you report what was really there — bigger than forecast, about right, smaller than forecast — and uses those reports to build a correction for that specific spot. Once enough people have reported the same pattern, the spot gets a calibration, and the forecast shown there is adjusted toward what people genuinely find.

Two things about how that works are worth stating plainly, because "community data" usually means something less pleasant:

There is no account, and reports are stored with nothing that identifies who filed them. The app does not attach a device identifier to what it saves, and coordinates are rounded to about 110 metres. What is kept describes the sea, not a person — which also means there is nothing to leak and nothing to delete.

And a spot only gets a calibration once several independent reports agree. One person having an unusual day does not move it.

Getting to it

Surf sits behind its own tab. If you do not see it, open Settings and use the tab bar editor — you can swap a tab you never open for it, so a coastal shooter can put Surf where AR Sky was.

Heights follow your unit setting, in metres or feet. Where a NOAA buoy nearby is reporting water temperature, that shows too, which in some months is the number that actually decides the session.

One thing to be clear about: this is a planning tool built for photographers, and the marine data is a model forecast, not an observation. Conditions at the water change faster than any forecast updates. Check local conditions, check the warnings, and make your own call before you go in.