Life in Weeks
Your whole life as one square per week: weeks lived, weeks left and the share already used, from any birth date and any life expectancy.
About this tool
Four thousand weeks is the standard way to describe a life, and it is close to right: 80 years comes to 4174 weeks, and 30 years to 1565. The number is small enough to look at in one screen and large enough that each square is a real week with a Monday and a Sunday in it. That is the whole idea of the chart. A calendar tells you what is happening this month; this shows how much of the paper is left.
The counting is done in days rather than in years for a reason. A year is 365.2425 days, which is 52.18 weeks, so a grid built at 52 squares per year quietly falls behind by about a fifth of a week every year. That sounds like nothing until it accumulates: at 80 years the shortcut is 14 squares short, almost three months. Here every square is seven days measured from the birth date, so a row holds 52 or 53 squares depending on where the leap years fall, and the last row of a plan can stop partway through.
The life expectancy you type in is a deliberate choice, not a measurement. Life expectancy at birth is an average over a whole population, and it says nothing about any one person: it moves with where you live, and for an adult it is usually higher than the at-birth figure because you have already survived the early years. The chart is therefore a planning tool with a chosen horizon. Change the number and the same life looks more or less crowded, which is the honest way to use it.
Why the grid is counted in days, not in years
A year is 52.18 weeks. Drawing 52 squares per year looks right and is wrong by about one square every five years.
The error is easy to underestimate because it is invisible on a single row. Fifty-two squares cover 364 days, so each row ends one and a quarter days before the anniversary it is supposed to represent. After ten years the grid is 12 days ahead of the calendar, after forty years it is 50 days ahead, and at eighty years it is 100 days ahead, which is 14 squares. The picture still looks plausible; the dates it implies are simply wrong.
Counting seven days at a time avoids the problem entirely, at the cost of an uneven grid. A row is the set of squares whose start dates fall inside one year of age, and that set has 52 members most years and 53 when the accumulated extra days cross a boundary. The last row of a plan can be short, because the plan ends on an anniversary rather than on a week boundary. None of that needs explaining to the reader, but all of it changes the numbers.
The same arithmetic explains why the totals look slightly off at first glance. Forty years is 2087 weeks, not 2080; a hundred years is 5217, not 5200. If a chart built on 52-week years shows a different total, the difference is not rounding, it is the drift.
What the chart is good for, and what it is not
It is a picture of a chosen horizon. It is not a forecast, and the number of squares is not a measurement of anyone.
The useful part is proportion. Seeing that a third of the grid is behind you, or that a child starting school has more than four thousand squares ahead, changes how a long project feels in a way that a number in a sentence does not. That is a legitimate use: it is a scale model of time, and scale models are for getting a sense of size.
The unuseful part is prediction. Life expectancy figures are averages built from mortality tables, and an average over a population cannot locate an individual within it. The number also carries a silent assumption that nothing changes: no illness, no accident, no medical advance. A grid that treats an 80 year horizon as a fact will be wrong for almost everyone, in both directions.
There is also a subtler trap in the format itself. Squares are identical, so a week at 6 years old and a week at 60 look the same, and the chart cannot show that time is experienced at different densities. Treat the grid as a ruler, not as a record of a life. It measures how much room there is, and says nothing about what has been done with it.
Eighty years is 4,174 cells, not 4,160
Fifty-two weeks times eighty years gives 4,160 cells, but eighty years is 29,220 days, and that divided by seven is 4,174. The fourteen-cell gap is most of an extra row on this chart.
The cell count comes from days divided by seven, not from years times 52. A year is not exactly 52 weeks: 365 days is 52 weeks and one day, and a leap year adds one more.
Eighty years span about twenty leap years, reaching 29,220 days, which is exactly 4,174 weeks. Missing fourteen cells sounds small, but the entire point of the page is seeing a life at a glance, so the error gets magnified visually — one extra division is worth it.
A related decision: Date.parse is not used. It interprets 03/04/2020 according to the runtime, so the same string is 4 March in one environment and 3 April in another. Dates are therefore parsed as YYYY-MM-DD and checked for existence, so 30 February is rejected rather than silently rolled to 2 March.
One more boundary: elapsed weeks are clamped inside the total. A birth date in the future gives zero elapsed weeks, and going past the lifespan gives zero remaining — the grid never draws a negative cell.
Eighty years is a default, not a forecast
The lifespan is an input that accepts 1 to 120 and starts at 80. It is never read from a life-expectancy table.
Born 1990-06-15 and viewed on 2026-10-27, the grid holds 4,174 cells at 80 years, 4,696 at 90 and 5,217 at 100. The steps are 522 then 521 rather than equal, because leap days land unevenly across the range and the count comes from days divided by seven.
A table would have to know the country, the sex and the birth cohort, and it would still be a population average applied to one person. Life expectancy at birth and remaining expectancy at 36 are different numbers, and the gap between them is large enough to move the grid by hundreds of cells.
So the assumption is exposed instead of hidden. Changing it leaves the filled part untouched at 1,897 cells for this birth date, because the past is fixed; only the total moves, and with it the remaining count. Anyone looking at the picture can see which denominator produced it, which matters because the chart is persuasive in a way a table of numbers is not.
Frequently asked questions
Why is a year not 52 squares?
Because it is 52 weeks and a day, and 52 weeks and two days in a leap year. Fifty-two squares of seven days cover 364 days, so a grid laid out that way loses 1.25 days per year against the calendar. Over a lifetime that is visible: an 80 year plan drawn at 52 squares per year is 4160 squares, while 80 real years are 4174 weeks. This tool measures every square from the birth date, so the squares never drift away from the dates they represent.
Why do the rows have 52 squares sometimes and 53 other times?
Because a row is one year of age, and a year of age is 52 weeks plus a day or so. When the extra days add up past a week boundary inside that year, a 53rd square falls into the row. The alternative, forcing every row to 52, would push the leftover into the next row and slowly move every birthday to the wrong place on the grid.
What does the life expectancy number actually mean?
Nothing predictive. It is the horizon you choose to draw. Average life expectancy is a population statistic, and the figure at birth includes infant mortality, so an adult who is already 40 usually has a higher remaining expectancy than the at-birth number suggests. Use a number you find useful for planning, and remember that the grid is a drawing of an assumption, not an estimate of an individual.
Why does the current week get its own marker?
Because the difference between 1878 and 1879 weeks lived is invisible in a mass of squares, and the square you are in right now is the only one that is actually moving. Marking it also makes the grid honest about rounding: the weeks already used are counted whole, and the week in progress is shown separately rather than being counted as finished.
Does this work with a birth date in the future, or a plan that has already run out?
Both are allowed and neither is treated as an error, because both are legitimate questions. A future birth date means no squares are used yet. If the date you are counting up to is past the end of the plan, every square is used and the chart says so. Errors are reserved for input that cannot be read at all, such as a date that does not exist or a fractional number of years.
Related tools
Convert between Gregorian and Chinese lunar dates, including leap months, the zodiac animal and the sexagenary year name, for any date from 1900 to 2099.
Convert between Unix timestamps and readable dates in any time zone. Seconds or milliseconds are detected for you — and nothing you type leaves your browser.
Convert a date and time across time zones, with correct daylight-saving handling — including wall-clock times that do not exist on that date.
Paste any cron expression to see what it means in plain English and exactly when it will run next — in your own time zone, DST included.