Convert Weeks to Seconds

 

Convert weeks to seconds instantly with our accurate time converter.

See formulas, worked examples, and precise calculations.

—
WeeksSeconds

How to Convert Weeks to Seconds

Converting weeks to seconds bridges the human-scale unit we use for planning (the week) with the fundamental SI unit of time (the second). Unlike month-based conversions that require averaging, the week-to-second conversion is exact, because a week is always precisely 7 days:

1 week = 604,800 seconds

This value is a clean, constant integer — no rounding, no averaging, no leap-week complications. Six hundred four thousand eight hundred, every week, every time.

Weeks to Seconds Conversion Formula

Seconds = Weeks × 604,800

Multiply any number of weeks by 604,800 to get the exact equivalent in seconds.

How the Conversion Factor Is Derived

The factor 604,800 is built from four clean multiplications:

  • Step 1: 1 week = 7 days
  • Step 2: 7 days × 24 hours = 168 hours
  • Step 3: 168 hours × 60 minutes = 10,080 minutes
  • Step 4: 10,080 minutes × 60 seconds = 604,800 seconds

Or in a single expression: 7 × 24 × 60 × 60 = 7 × 86,400 = 604,800. Since every factor is an integer, the result is exact and will never change.

Why This Conversion Is Exact

Unlike months (which vary from 28 to 31 days) or years (which alternate between 365 and 366 days), a week has a fixed, invariable definition:

  • A week is always exactly 7 days — no exceptions
  • A day is always exactly 86,400 SI seconds (by definition of the SI second)
  • Therefore 1 week = 7 × 86,400 = 604,800 seconds exactly
  • No leap weeks, no short weeks, no calendar complications

Note on leap seconds: UTC occasionally inserts a leap second (about once every 18 months historically), which would make a specific calendar week 604,801 seconds long. However, for all practical purposes — engineering, finance, scheduling — the standard 604,800 is used, and most modern systems (including GPS and Unix timestamps) ignore or smooth out leap seconds.

Worked Examples

Example 1: How many seconds are in 1 week?

1 × 604,800 = 604,800 seconds

Example 2: How many seconds are in 2 weeks?

2 × 604,800 = 1,209,600 seconds

Example 3: How many seconds are in 4 weeks?

4 × 604,800 = 2,419,200 seconds

Example 4: How many seconds are in 8 weeks?

8 × 604,800 = 4,838,400 seconds

Example 5: How many seconds are in 12 weeks (one quarter)?

12 × 604,800 = 7,257,600 seconds

Example 6: How many seconds are in 26 weeks (half a year)?

26 × 604,800 = 15,724,800 seconds

Example 7: How many seconds are in 52 weeks (~1 year)?

52 × 604,800 = 31,449,600 seconds

Putting 604,800 in Perspective

Over half a million seconds sounds enormous, but a week passes in a flash. Here is a sense-of-scale breakdown of what happens in 604,800 seconds:

Heartbeats: ~604,800 (at 60 bpm — your heart beats roughly once per second, so the number of heartbeats in a week ≈ seconds in a week)

Breaths: ~120,960 (at ~12 breaths/min = 1 every 5 sec)

Blinks: ~120,960 (at ~12 blinks/min while awake, ~16 waking hours/day)

Steps: ~70,000 (at ~10,000 steps/day)

Words spoken: ~112,000 (at ~16,000/day)

Emails sent worldwide: ~2.3 trillion (~333 billion/day × 7)

Google searches: ~61.6 billion (~8.8 billion/day × 7)

Weeks to Seconds in Computing

In software engineering, the 604,800-second week is a fundamental constant used across many systems:

  • Unix/POSIX timestamps — time is measured in seconds since epoch (Jan 1, 1970); adding 604,800 to a timestamp advances it exactly 1 week
  • TTL (Time to Live) — DNS records, cache entries, and tokens are often set in seconds; a 1-week TTL = 604,800; a 2-week TTL = 1,209,600
  • Cron jobs — weekly tasks in systems that use second-based intervals (e.g., Kubernetes CronJobs) reference 604,800
  • JWT expiration — JSON Web Tokens commonly expire after 1 week (604,800 seconds) or 2 weeks (1,209,600 seconds)
  • Rate limiting — API rate limits expressed as “X requests per week” use a 604,800-second sliding window
  • Session timeouts — “Remember me for 1 week” = cookie maxAge of 604,800 seconds

Common TTL and timeout values in seconds:

1 day = 86,400  •  3 days = 259,200

1 week = 604,800  •  2 weeks = 1,209,600

4 weeks = 2,419,200  •  8 weeks = 4,838,400

Weeks to Seconds in Science and Engineering

The second is the base SI unit of time, so scientific calculations always work in seconds. Converting weekly measurements to seconds is routine in several fields:

  • Radioactive decay — half-lives are expressed in seconds for calculation; Iodine-131 (thyroid therapy) has a half-life of ~8.02 days = ~1.15 weeks = 693,000 seconds
  • Orbital mechanics — the ISS orbits Earth every ~92 minutes (5,520 seconds); in 1 week it completes ~109.6 orbits
  • Seismology — earthquake monitoring stations record data in seconds; a 1-week recording session = 604,800 data points at 1 Hz
  • Signal processing — sampling audio at 44,100 Hz for 1 week produces 44,100 × 604,800 = ~26.7 billion samples
  • Pharmacology — drug half-lives and dosing intervals calculated in seconds for precision; a “once-weekly” injection is every 604,800 seconds

Weeks to Seconds in Sports and Performance

In sports, seconds define performance while weeks define training cycles. Bridging the two provides useful context:

  • Marathon world record: ~2:00:35 = 7,235 seconds. A week of training (604,800 sec) is 83.6× longer than the race itself
  • 100m sprint record: 9.58 seconds. There are 63,131 of those sprints in a week
  • Weekly training volume: a serious runner logging 60 miles/week at 8:00/mile pace runs for ~28,800 seconds (8 hours) — only 4.8% of the week’s total seconds
  • NBA game: 48 minutes = 2,880 seconds; a player averaging 36 min/game plays ~2,160 seconds. Over a 3-games-per-week schedule: ~6,480 seconds of game time = 1.07% of the week
  • Swimming 1,500m: world record 14:06.88 = 846.88 seconds. A week has 714 × this duration

The Weekly Time Budget in Seconds

Breaking a week into second-level categories reveals how granular our time allocation really is:

Total week: 604,800 seconds

Sleep (8 hr/day × 7): 201,600 sec (33.3%)

Work (8 hr/day × 5): 144,000 sec (23.8%)

Commute (52 min/day × 5): 15,600 sec (2.6%)

Meals (1.5 hr/day × 7): 37,800 sec (6.3%)

Personal care (1 hr/day × 7): 25,200 sec (4.2%)

Screen time (3 hr/day × 7): 75,600 sec (12.5%)

Chores (1 hr/day × 7): 25,200 sec (4.2%)

Remaining discretionary: ~79,800 sec (13.2% ≈ 22.2 hr)

Those ~79,800 discretionary seconds translate to about 22 hours per week — roughly 3.2 hours per day — for exercise, hobbies, socializing, and personal projects.

Weeks to Seconds in Agile Sprints

Sprint duration is a core Agile parameter. Here are common sprint lengths expressed in seconds — useful for automated scheduling, burndown calculations, and time-box enforcement:

1-week sprint: 604,800 sec (working time: 144,000 sec = 40 hr)

2-week sprint: 1,209,600 sec (working: 288,000 sec = 80 hr)

3-week sprint: 1,814,400 sec (working: 432,000 sec = 120 hr)

4-week sprint: 2,419,200 sec (working: 576,000 sec = 160 hr)

For a 5-person team on 2-week sprints: total available team-seconds = 5 × 288,000 = 1,440,000 seconds (400 person-hours) per sprint. At ~70% utilization: ~1,008,000 productive seconds (~280 person-hours).

Weeks to Seconds: Large-Scale Perspective

To appreciate what longer periods look like in seconds:

1 week: 604,800 (~6 × 105)

1 month (~4.35 wk): ~2,629,746 (~2.6 × 106)

1 quarter (~13 wk): ~7,889,238 (~7.9 × 106)

1 year (~52.18 wk): ~31,556,952 (~3.16 × 107)

1 decade (~521.8 wk): ~315,569,520 (~3.16 × 108)

Average lifetime (~4,000 wk): ~2.4 × 109 (~2.4 billion seconds)

An average human lifespan is approximately 2.4 billion seconds — or about 4,000 weeks. Every week that passes is 604,800 seconds you will never get back.

Tips and Recommendations

  • Memorize 604,800. It is the second most useful time constant after 86,400 (seconds in a day). Together they cover most practical needs
  • For computing: Use 604,800 for TTLs, cache durations, session timeouts, and token expirations. It is an exact integer with no floating-point surprises
  • For quick mental math: 1 week ≈ 600,000 seconds (off by only 0.8%). For 2 weeks, use 1.2 million; for 4 weeks, 2.4 million
  • For scientific calculations: Always use the exact value 604,800. Since it factors cleanly (604,800 = 26 × 33 × 52 × 7), it divides evenly into many useful intervals
  • For Unix timestamps: Adding or subtracting 604,800 from any epoch timestamp gives exactly 1 week forward or backward
  • Leap second caveat: If your system requires UTC accuracy to the second, be aware that a specific calendar week may contain a leap second (604,801 s). For all other purposes, 604,800 is correct

Weeks to Seconds — Frequently Asked Questions

How many seconds are in 1 week?

Exactly 604,800 seconds (7 days × 24 hours × 60 minutes × 60 seconds). This is an exact, constant value.

How many seconds are in 2 weeks?

Exactly 1,209,600 seconds (2 × 604,800). This is a common token expiration and TTL value.

How many seconds are in 4 weeks?

Exactly 2,419,200 seconds (4 × 604,800). Note: 4 weeks = 28 days, which is shorter than most calendar months.

How many seconds are in 52 weeks?

31,449,600 seconds (52 × 604,800). This is close to but not exactly 1 year: a Gregorian year has 31,556,952 seconds (52.1775 weeks), which is 107,352 seconds (~1.24 days) more.

How do I convert weeks to seconds?

Multiply by 604,800. Example: 3 weeks = 3 × 604,800 = 1,814,400 seconds. The result is always exact.

Is this conversion exact?

Yes. A week is defined as exactly 7 days, and a day as exactly 86,400 seconds. Therefore 1 week = 604,800 seconds with zero approximation. The only caveat is UTC leap seconds, which are irrelevant for virtually all practical applications.

What is the common TTL for a 1-week cache?

604,800 seconds. For a 2-week cache: 1,209,600 seconds. These are standard values for DNS records, CDN caches, and browser cookies.

How many heartbeats occur in 1 week?

At an average resting rate of 60–80 bpm: approximately 604,800 to 806,400 heartbeats. At exactly 60 bpm, your heart beats once per second, making heartbeats ≈ seconds.

How many seconds of work are in a 40-hour week?

40 hours × 3,600 = 144,000 seconds. This is 23.8% of the total 604,800 seconds in the week.

How do leap seconds affect this conversion?

Leap seconds are inserted into UTC roughly once every 18 months. If a leap second falls within a given week, that specific week has 604,801 seconds. However, this is ignored by nearly all computing systems (Unix time, GPS, etc.) and for all practical purposes 604,800 is the correct value.

How many seconds of free time do I have per week?

After sleep, work, commuting, meals, personal care, and chores, approximately 79,800 seconds (~22 hours) remain per week for discretionary activities.

What is the prime factorization of 604,800?

604,800 = 26 × 33 × 52 × 7. This rich factorization means 604,800 divides evenly by many common intervals (1, 2, 3, 4, 5, 6, 7, 8, 10, 12, 14, 15, 16, 20, 21, 24, 25, 28, 30, etc.).