The EPW Weather Converter reads an EnergyPlus Weather (.epw) file — the standard hourly typical-year weather format used by EnergyPlus, OpenStudio, IES-VE, and most building energy simulation software — and turns it into something you can actually look at and work with: a shared-axis temperature chart with daily min/max bands, a searchable hourly data table, and a rolling-window filter for finding extreme periods. It can also fetch real, observed historical weather for a station from Meteostat, so you can compare a "typical year" EPW file against what actually happened in a given year.
An EPW file starts with 8 header lines (location, design conditions, typical/extreme periods, ground temperatures, holidays, two comment lines, and a data-period declaration), followed by one comma-separated row per hour of the year — 8,760 rows in total. Each row carries 35 fields: dry-bulb and dew-point temperature, relative humidity, atmospheric pressure, wind speed and direction, solar radiation and illuminance components, sky cover, precipitation, and more. This tool parses every field, but focuses its charts and exports on the ones most design workflows actually use — dry-bulb, dew-point, wet-bulb (calculated), and relative humidity.
An EPW file is usually a typical meteorological year (TMY) — a synthetic year stitched together from the statistically "most typical" months across a multi-year record, built for consistent simulation, not for representing any single real year. The Meteostat option in the sidebar instead fetches actual recorded hourly observations for a real station and year, pulled from the same open weather-station network Meteostat aggregates from. Switching between the two lets you sanity-check whether a design's typical-year assumptions held up against a specific real year, or investigate an unusually hot, cold, humid, or dry period that an EPW file's averaging would smooth away.
The sidebar links to EPW files organized by WMO region, sourced from the standard public EnergyPlus weather file repositories — pick the region closest to your project location.
That's expected — an EPW file is a synthetic typical year built from long-term averages, while Meteostat gives you one specific real year's actual observations. Differences between them are the whole point of comparing the two.
No — EPW parsing, charting, filtering, and Excel export all happen locally in your browser. The only network request is the Meteostat fetch itself, if you choose to use it, which goes directly to the Meteostat API.
Yes, completely free, with no account and no usage limit.