Checking the weather is a two-second question that costs a tab, a page full of advertising and about forty seconds of your attention. Having it already on screen removes the whole round trip.

Four things, each of which can be switched off. An icon, the temperature, a one-word condition (Clear, Clouds, Rain) and the city name.
That’s a deliberate floor, not a limitation. Humidity, pressure, wind and sunset are all in the same reading and none of them change what you do next. The jacket question needs a number and a word. Six more numbers only make the answer slower to find.
Leave the icon and the temperature and the widget shrinks to something you park in a corner and read without looking directly at it.
Type a city, pick it from the list. The widget never asks the browser where you are. Which is why it needs no location permission at all.
The reading comes from the weather service directly rather than through our servers, so the city you’re watching isn’t something we can see.
City is stored per widget, so a second one can show somewhere else: where family lives, or where you’re going next week.
Reference information, not the point of the page, corner, modest size. The exception is a travel page, where a big weather block for the destination next to a countdown to the trip is the entire idea.
The weather widget is part of New Tab Studio — free to install, no account needed to start.
Add to ChromeNo. You type the city yourself, and the browser is never asked where you are.
No, current conditions only. For a full forecast, an iframe widget can embed a weather page on the same tab.
It shows the last reading it managed to fetch and updates when you’re back online. The clock, countdowns, tasks and notes on the same page carry on regardless.
See the full widget catalogue or browse themes other people have built.