How many seconds are in a week?

There are exactly 604,800 seconds in one week: 7 days × 24 hours × 60 minutes × 60 seconds = 604,800. This is the most common token expiry value in web development, where a 7-day session timeout is configured as 604,800 seconds.

How do I convert seconds to weeks?

Divide the number of seconds by 604,800. For example, 1,209,600 seconds ÷ 604,800 = 2 weeks. For 302,400 seconds, the result is 0.5 weeks (3.5 days). For 3,024,000 seconds, the result is exactly 5 weeks.

Why is 604,800 important in web development?

604,800 seconds equals exactly 7 days, making it the standard value for 1-week session timeouts, JWT expiry times, and cookie max-age settings. Many web frameworks and API documentation use 604,800 as a default or example value for week-long authentication tokens. Knowing this constant saves repeated calculation.

Seconds to Weeks (s to wk) Converter

1 s = 0.000002 wk

1 Second equals 0.000002 Weeks (1 s = 0.000002 wk). Convert Seconds to Weeks with formula, table, and examples.

One week equals exactly 604,800 seconds, so to convert seconds to weeks you divide by 604,800. This conversion spans the widest gap between two commonly used time units — from the machine-precision second to the human-scale week — and is most useful in computing and data engineering, where second-level Unix timestamps or duration counters need to be expressed in weeks for reporting, scheduling, or compliance checking. The number 604,800 is 7 × 24 × 60 × 60. It appears in programming whenever a week-long token expiry or cache duration must be expressed in seconds: a JWT with a 1-week validity is set to expire 604,800 seconds from now. A CDN cache TTL of 2 weeks is 1,209,600 seconds. Converting in the other direction — from a raw second count back to weeks — is needed whenever a monitoring tool, database query, or analytics pipeline returns durations in seconds that need to be summarised in weeks. In system uptime monitoring, servers that have been running for millions of seconds are summarised in weeks for operations dashboards. A server uptime of 3,628,800 seconds is exactly 6 weeks. A service that experienced 1,209,600 seconds of cumulative downtime had 2 weeks of outages — a figure that reads very differently in a board presentation than '1,209,600 seconds'. In scientific experiments, long-running measurements recorded in seconds are compared against week-based schedules. A particle physics detector run lasting 1,814,400 seconds ran for exactly 3 weeks of continuous data collection.

How to Convert Seconds to Weeks

wk = s ÷ 604,800

Divide the value in Seconds by 604,800

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

Common Seconds to Weeks Conversions

Seconds (s)	Weeks (wk)	Status
86,400 s	0.1429 wk
259,200 s	0.4286 wk
604,800 s	1 wk
1,209,600 s	2 wk
1,814,400 s	3 wk
2,419,200 s	4 wk
3,024,000 s	5 wk
3,628,800 s	6 wk
4,838,400 s	8 wk
7,257,600 s	12 wk
15,724,800 s	26 wk
31,449,600 s	52 wk

Good to Know About Seconds to Weeks Conversion

604,800 is one of the small set of second-derived constants that practising programmers simply memorise: 86,400 for a day, 604,800 for a week, 2,592,000 for a 30-day month, 31,536,000 for a year. These numbers appear in configuration files, API documentation, and code comments across millions of software projects. Knowing 604,800 is a week is as fundamental to a web developer as knowing that an HTTP status code of 200 means success.

Seconds to Weeks: What You Need to Know

The seconds-to-weeks conversion is embedded in authentication and security infrastructure. SSL/TLS certificates commonly have 90-day or 1-year validity periods, but some short-lived certificates are issued for 2 to 4 weeks. A 2-week certificate is valid for 1,209,600 seconds. Password reset tokens, single-use login links, and OAuth access tokens with week-long lifetimes are all implemented as second offsets in databases and token verification systems. In genomics and bioinformatics, sequencing runs and computational analyses that last days to weeks are logged in seconds by pipeline automation tools. A whole-genome sequencing run taking 1,209,600 seconds processed samples for exactly 2 weeks. Converting these second-level job logs to weeks is routine when reporting throughput and capacity utilisation to laboratory management. In logistics and supply chain, shipment tracking systems record timestamps in seconds but carrier transit time commitments and service level agreements are expressed in weeks. A parcel that left the origin depot 1,814,400 seconds ago has been in transit for exactly 3 weeks — a figure that determines whether a service level breach has occurred. In financial markets, certain derivative contracts and regulatory reporting windows are specified in weeks but market data systems timestamp events in seconds. A 4-week T-bill has a term of 2,419,200 seconds. Position reporting windows of 2 weeks correspond to 1,209,600-second periods in trading system configuration.

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 →

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 →

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

Seconds to Weeks FAQ

There are exactly 604,800 seconds in one week: 7 days × 24 hours × 60 minutes × 60 seconds = 604,800. This is the most common token expiry value in web development, where a 7-day session timeout is configured as 604,800 seconds.
Divide the number of seconds by 604,800. For example, 1,209,600 seconds ÷ 604,800 = 2 weeks. For 302,400 seconds, the result is 0.5 weeks (3.5 days). For 3,024,000 seconds, the result is exactly 5 weeks.
604,800 seconds equals exactly 7 days, making it the standard value for 1-week session timeouts, JWT expiry times, and cookie max-age settings. Many web frameworks and API documentation use 604,800 as a default or example value for week-long authentication tokens. Knowing this constant saves repeated calculation.

Non-Frequently Asked Questions About Seconds to Weeks

Questions nobody should ask - but someone did.

Exactly 1 week — 604,800 seconds. If you counted continuously, day and night, one number per second, you would reach 604,800 precisely at the end of 7 days. At a realistic pace of 8 waking hours per day, counting during all waking hours, you would need approximately 3 weeks to count to 604,800. Attempting this is strongly discouraged; hiring a computer to do it instead takes approximately 0.0006 seconds.
604,800 seconds is 1 week. One centimetre per month divided by approximately 4.35 weeks per month gives about 0.23 centimetres of hair growth per week — roughly 2.3 millimetres. In 604,800 seconds, your hair grows a little over 2 mm. This is imperceptible day to day but adds up to a haircut every 6 to 8 weeks, or about every 3,628,800 to 4,838,400 seconds.
A fortnight is exactly 2 weeks or 1,209,600 seconds. It is absolutely a real unit, derived from the Old English 'fēowertīene niht' (fourteen nights). It remains in common use in British English, Australian English, and some official contexts including UK government benefit payment schedules. Employees paid fortnightly receive their salary every 1,209,600 seconds — a figure that their bank would find unwieldy to display.