How many seconds are in a week?

There are exactly 604,800 seconds in one week: 7 × 24 × 60 × 60 = 604,800. This is a commonly memorised constant in web development, where it represents the standard 7-day session or token lifetime in seconds.

How do I convert weeks to seconds?

Multiply the number of weeks by 604,800. For example, 3 weeks × 604,800 = 1,814,400 seconds. For 0.5 weeks, the result is 302,400 seconds. For 52 weeks, the result is 31,449,600 seconds.

How do I set a 2-week cookie or session expiry in code?

Multiply 2 weeks by 604,800 to get 1,209,600 seconds. In JavaScript, set document.cookie with max-age=1209600. In Python/Flask, set the session lifetime to timedelta(seconds=1209600). In most frameworks, you either pass the second count directly or use a helper that accepts days (14) or weeks (2) and performs this multiplication internally.

Weeks to Seconds (wk to s) Converter

1 wk = 604,800 s

1 Week equals 604,800 Seconds (1 wk = 604,800 s). Convert Weeks to Seconds with formula, table, and examples.

One week equals exactly 604,800 seconds. To convert weeks to seconds, multiply by 604,800. This is the direction most used in software development, where human-readable week-based durations must be translated into the second-level values that systems, APIs, and databases actually work with. The most common use case is token and session expiry. When a developer wants a session to last 2 weeks, they compute 2 × 604,800 = 1,209,600 and pass that value to the token generator. When a CDN cache should last 4 weeks, they configure a TTL of 4 × 604,800 = 2,419,200 seconds. The week is the human unit; the second is the machine unit; 604,800 is the bridge. In science, week-scale experimental durations must be expressed in seconds for use in physics formulas and data analysis. If a chemical equilibration process takes 3 weeks, the time variable in kinetic rate equations is 3 × 604,800 = 1,814,400 seconds. If a radioactive tracer has a biological half-life of 2 weeks, its decay constant λ = ln(2) / 1,209,600 per second. In operations and DevOps, maintenance windows, deployment freezes, and SLA review periods specified in weeks are converted to seconds for comparison against uptime and incident duration counters. A 6-week deployment freeze encompasses 3,628,800 seconds during which no changes may be made to production systems.

How to Convert Weeks to Seconds

s = wk × 604,800

Multiply the value in Weeks by 604,800

Take your value in Weeks
Multiply by 604,800
Read the result in Seconds

Common Weeks to Seconds Conversions

Weeks (wk)	Seconds (s)	Status
0.5 wk	302,400 s
1 wk	604,800 s
2 wk	1,209,600 s
3 wk	1,814,400 s
4 wk	2,419,200 s
6 wk	3,628,800 s
8 wk	4,838,400 s
10 wk	6,048,000 s
12 wk	7,257,600 s
13 wk	7,862,400 s
16 wk	9,676,800 s
26 wk	15,724,800 s
40 wk	24,192,000 s
52 wk	31,449,600 s

Good to Know About Weeks to Seconds Conversion

The programmer's set of memorised second-constants — 86,400, 604,800, 2,592,000, 31,536,000 — forms an informal vocabulary that appears in code comments and configuration files worldwide. Of these, 604,800 is perhaps the most specifically useful, because 'one week' is the most common human-facing expiry period for tokens, trials, and subscriptions — making weeks-to-seconds the most frequently performed manual calculation in this set.

Weeks to Seconds: What You Need to Know

The weeks-to-seconds conversion is standard practice in backend development whenever time-based business logic uses human-friendly week units in configuration but second-level precision in execution. Rate limiting rules, subscription renewal windows, trial period calculations, and data retention policies all follow this pattern. In cryptography and PKI (Public Key Infrastructure), certificate validity periods are specified in weeks or days by certificate authorities but stored and validated in seconds by TLS implementations. A certificate valid for 13 weeks (approximately 3 months) has a validity of 13 × 604,800 = 7,862,400 seconds from the notBefore timestamp. In ecology and field biology, migration and breeding season durations are described in weeks by ecologists but modelled in seconds by computational simulation tools. A 6-week salmon spawning run is 3,628,800 seconds of active migration behaviour in the model. Converting weeks to seconds is the interface between biological observation and mathematical modelling. In satellite operations, observation campaigns, data collection windows, and orbital manoeuvre sequences are planned in weeks for mission scheduling but executed with second-level timing precision by onboard computers. A 4-week Earth observation campaign is 2,419,200 seconds of planned data acquisition time.

What is a Week? wk

Exactly seven days or 604,800 seconds. The universal unit of work and rest cycles, rooted in ancient Mesopotamian and biblical tradition.

Metric SI Imperial US customary work scheduling project planning subscription billing cycles

Learn more about Week →

What is a Second? s

The SI base unit of time, defined by the radiation frequency of the caesium-133 atom. Used universally in science, engineering, and everyday timekeeping.

Metric SI Imperial US customary scientific measurement sports timing computing and networking

Learn more about Second →

Going the other way? Use our Seconds to Weeks converter.

Weeks to Seconds FAQ

There are exactly 604,800 seconds in one week: 7 × 24 × 60 × 60 = 604,800. This is a commonly memorised constant in web development, where it represents the standard 7-day session or token lifetime in seconds.
Multiply the number of weeks by 604,800. For example, 3 weeks × 604,800 = 1,814,400 seconds. For 0.5 weeks, the result is 302,400 seconds. For 52 weeks, the result is 31,449,600 seconds.
Multiply 2 weeks by 604,800 to get 1,209,600 seconds. In JavaScript, set document.cookie with max-age=1209600. In Python/Flask, set the session lifetime to timedelta(seconds=1209600). In most frameworks, you either pass the second count directly or use a helper that accepts days (14) or weeks (2) and performs this multiplication internally.

Non-Frequently Asked Questions About Weeks to Seconds

Questions nobody should ask - but someone did.

0.03 mph × 604,800 seconds ÷ 3,600 seconds per hour = 0.03 × 168 hours = 5.04 miles per week. A snail travelling at 0.03 mph for all 604,800 seconds of a week would cover approximately 5 miles — provided it never sleeps, which snails actually do for extended periods. A fully committed, non-sleeping snail can cover the length of a marathon in about 8 weeks. This is not a recommended racing strategy.
Surprisingly, yes. The human sleep cycle of 90 minutes fits almost exactly 2,016 times into 1,209,600 seconds. The influenza virus incubation period (1 to 4 days) means a 2-week quarantine (1,209,600 seconds) spans several complete incubation cycles. Bamboo shoots grow approximately 3 to 4 centimetres per day, making 1,209,600 seconds (2 weeks) enough time to grow 42 to 56 cm of bamboo. Nature has several processes that align neatly with this number.
1,000,000,000,000 seconds ÷ 604,800 = approximately 1,653,439 weeks, or about 31,710 years. One trillion seconds takes us from today back to approximately 29,700 BCE — deep into the Upper Palaeolithic, when modern humans were creating cave paintings in what is now France and Spain, and Neanderthals had just become extinct. All of recorded human history fits comfortably within the last 600,000 weeks, or about 385 billion seconds.