How this instrument works
A second is the base unit every other measure of time is built from, and counting a life in seconds is really just counting days and rescaling the answer: this tool takes the whole calendar days between a birth date and a chosen reference date, then multiplies by 86,400 (24 hours x 60 minutes x 60 seconds) to get a number large enough to feel genuinely surprising even for a fairly young person.
The day count itself comes from the same civil-calendar engine that already powers this site's age-in-days, age-in-weeks, and age-in-years pages, so the figures agree with each other rather than drifting apart from separate logic. That engine only tracks whole dates, not a time of day, so 'today' and 'the day you were born' are each treated as a single unit regardless of what hour either actually happened at.
That day-granularity choice is a deliberate, disclosed limitation rather than an oversight: without a birth *time* on record, no calculator can honestly claim second-level precision anyway, and rounding to whole days keeps the output consistent with the site's other age tools instead of inventing false precision from a time field nobody actually filled in accurately.
- Enter Date of birth using the date picker.
- Enter Age on this date — it defaults to today, but you can pick any reference date instead.
- Read Age — total seconds lived, the whole-day count between the two dates scaled by 86,400.
- Compare it against a friend's figure by changing only the birth date — the reference date stays fixed so the comparison is apples-to-apples.
- Remember the count updates only at day boundaries, not in real time — refresh the page tomorrow for tomorrow's total, it won't tick upward while you watch.
Worked example — someone born May 20, 1990
Someone born on 1990-05-20, checking their total as of 2026-07-29, has lived exactly 13,219 whole days on this site's shared civil-calendar count (the same figure the age-in-days calculator would show for those two dates). Scaled to seconds: 13,219 x 86,400 = 1,142,121,600 seconds.
That is over 1.1 billion seconds, a number that reliably surprises people the first time they see their own age expressed this way, even though it describes exactly the same span of time as '36 years and change' — just measured in a much smaller unit.
Questions
Why does this calculator ignore the exact time I was born?
Because the underlying engine only tracks whole calendar dates, not a time of day, matching this site's age-in-days, age-in-weeks, and age-in-years calculators. Most people don't have a precisely recorded birth minute handy anyway, and mixing a real day count with a guessed time of day would produce a false sense of precision rather than a genuinely more accurate number.
Where does the number 86,400 come from?
It's the number of seconds in one full day under the everyday civil clock: 24 hours x 60 minutes per hour x 60 seconds per minute = 86,400. Multiplying a whole-day age by 86,400 converts the same span of time into seconds without changing what it represents.
Does this figure account for leap seconds?
No, and essentially no everyday calculator does. Leap seconds are occasional one-second adjustments added to Coordinated Universal Time to keep it aligned with Earth's slightly irregular rotation — a few dozen have been added since the practice began in 1972. Against a lifetime measured in the billions of seconds, that handful of leap seconds is a rounding error too small to matter for a curiosity number like this one.
Will this number change if I refresh the page later today?
No — it only changes at midnight, when the whole-day count between your birth date and the reference date increases by one. This tool reports a snapshot based on calendar dates, not a live ticking counter, so watching the page won't show the total climbing second by second.
How is this different from a 'live seconds since birth' countdown widget?
A live countdown widget usually assumes a birth time (often midnight, if none was given) and increments continuously as you watch it. This calculator instead reports a fixed total based only on whole calendar days, which is more honest about what's actually known — a date, not a timestamp — even though it means the number won't visibly move in real time.