Weeks to Milliseconds Converter
Convert weeks to milliseconds instantly. Enter any value — the result updates as you type. 1 week = exactly 604,800,000 milliseconds. Unlike months and years, the week is perfectly uniform: 7 days, always. Use the swap button to convert milliseconds back to weeks.
| Weeks | Milliseconds |
|---|---|
| 0.5 | 302,400,000 |
| 1 | 604,800,000 |
| 2 | 1,209,600,000 |
| 4 | 2,419,200,000 |
| 8 | 4,838,400,000 |
| 12 | 7,257,600,000 |
| 16 | 9,676,800,000 |
| 26 | 15,724,800,000 |
| 40 | 24,192,000,000 |
| 52 | 31,449,600,000 |
| 104 | 62,899,200,000 |
| 520 | 314,496,000,000 |
How to Convert Weeks to Milliseconds
The week is the only calendar unit that is perfectly uniform in milliseconds: 1 week = 7 days × 86,400 s/day × 1,000 ms/s = 604,800,000 milliseconds, always. No leap years, no variable month lengths, no calendar drift. This makes the week uniquely useful in software: any two dates that are exactly n weeks apart will differ by exactly n × 604,800,000 milliseconds, regardless of calendar month or year boundaries. Compare this to months (28–31 days, varies) or years (365–366 days, varies). The week's uniformity is why it dominates in scheduling systems, payroll, sports seasons, and clinical trial protocols. One interesting anomaly: 52 weeks = 364 days = 31,449,600,000 ms, which is less than 1 year (31,556,952,000 ms) by 107,352,000 ms ≈ 29.82 hours. This 1-day-and-6-hour gap is why calendars occasionally need a 53rd week in a year (ISO 8601 years can have 52 or 53 weeks).
Conversion: Weeks × 604,800,000 = Milliseconds
The Week's Unique Mathematical Property
1 week = 604,800,000 ms (exact — 7 × 86,400,000)
1 month = 2,629,746,000 ms (mean Gregorian, not exact days)
1 year = 31,556,952,000 ms (mean Gregorian, not exact days)
52 wk = 31,449,600,000 ms (364 days — short by 107,352,000 ms)Because 604,800,000 = 7 × 86,400,000 = 7 × 24 × 3,600,000 = 7 × 24 × 60 × 60,000, every week converts to an exact, round multiple of every smaller time unit (days, hours, minutes, seconds, milliseconds). This makes weeks uniquely predictable: dateA - dateB mod 604,800,000 === 0 if and only if A and B are on the same weekday. This modular property underpins recurring calendar events, weekly cron jobs, and 7-day rolling windows in analytics.
Weeks to Milliseconds: Pregnancy and Medicine
The week is the dominant unit of clinical time, especially in obstetrics. Human full-term gestation is defined as exactly 40 weeks — which in milliseconds is a perfect calculation:
Weeks to Milliseconds: Sports Seasons and Training Cycles
Professional sports organise entire seasons, training blocks, and competitions in weeks. Every one of these has an exact millisecond duration:
Weeks to Milliseconds: History's Great Durations
Weeks to Milliseconds: Software Engineering and Scheduling
The week's mathematical uniformity makes it the preferred scheduling unit in software. Here are the most practically important values for developers:
- Agile sprint (2 weeks): 2 × 604,800,000 = 1,209,600,000 ms. A sprint timer:
const sprintEnd = sprintStart + 1209600000; - Weekly cron job modular check:
if (Date.now() % 604800000 < tolerance) runWeeklyJob();— works because the week is an exact multiple of ms - 7-day rolling analytics window:
const weekAgo = Date.now() - 604800000;— always exactly 7 days ago in ms - Cookie / session expiry in 1 week:
maxAge: 604800(seconds in Node.js/Express) or604800000(ms in browser). Exact, no rounding needed - ISO 8601 week number: A year has 52 or 53 ISO weeks. 52-week year = 31,449,600,000 ms (364 days). 53-week year = 32,054,400,000 ms (371 days). Neither equals a Gregorian year
- setTimeout maximum ≈ 24.855 days = 3.55 weeks: 2,147,483,647 ms ÷ 604,800,000 = 3.5503 weeks. For timers longer than ~3.5 weeks, use date comparison, not setTimeout
- UNIX timestamp week parity: Week 0 started on Thursday, January 1, 1970 (Unix epoch). Current week number since epoch:
Math.floor(Date.now() / 604800000)
Weeks to Milliseconds: Nature, Science and Space
- Lunar quarter (7.38 days): 7.38 × 86,400,000 = 637,632,000 ms ≈ 1.054 weeks. The lunar month ÷ 4 is slightly longer than 1 week, which is why "week" may etymologically link to the Moon's cycle being divided into quarters
- Earth's rotation rate drift: The day lengthens ~1.4 ms/century = 0.0002 ms/week. Over 52 weeks, today's week is 0.0104 ms longer than a week 100 years ago — negligible for all practical purposes
- ISS orbital period (92.68 minutes): The ISS completes 1 orbit in 5,560,800 ms. In 1 week (604,800,000 ms) it completes 604,800,000 ÷ 5,560,800 ≈ 108.76 orbits
- Plant growth (average ~1 cm/week for fast growers): 1 cm of growth per 604,800,000 ms = ~1.65 nm per second = 1,650 pm per second
- Human hair growth (~1 cm/month ≈ 0.23 cm/week): 1 week = 0.23 cm = 2,333 µm. Per millisecond: 0.00000385 µm/ms
- Light travel in 1 week: 299,792,458 m/s × 604,800 s = 1.813 × 1014 m = 0.01916 light-years. In 52 weeks: 0.9963 light-years ≈ 1 light-year
Tips and Recommendations
- Formula: Milliseconds = Weeks × 604,800,000. Inverse: Weeks = Milliseconds ÷ 604,800,000. Because the week is exact, this formula produces zero rounding error for any integer number of weeks.
- In JavaScript:
const ms = weeks * 604800000;. 7 days ago:Date.now() - 604800000. Weeks since event:(Date.now() - eventMs) / 604800000. Week number since Unix epoch:Math.floor(Date.now() / 604800000). - In Python:
ms = weeks * 604800000. 7 days ago:datetime.now() - timedelta(weeks=n). Weeks between dates:(date_b - date_a).days / 7(exact if both dates are known). - In Excel:
=A1*604800000. 7 days from date:=A1+7(Excel date arithmetic). Weeks between two dates:=INT((B1-A1)/7). - 52 ≠ year: Never assume 52 weeks = 1 year. 52 × 604,800,000 = 31,449,600,000 ms ≠ 31,556,952,000 ms. The gap is 107,352,000 ms ≈ 29.82 hours. Use 52.1775 weeks/year for mean Gregorian year.
- Quick mental check: 1 week = 604.8 million ms. 4 weeks ≈ 2.42 billion ms. 52 weeks ≈ 31.45 billion ms. 1 day = 86.4 million ms. 1 hour = 3.6 million ms.
Weeks to Milliseconds — Frequently Asked Questions
How many milliseconds are in 1 week?
1 week = exactly 604,800,000 milliseconds. Derivation: 7 days × 86,400 s/day × 1,000 ms/s = 604,800,000 ms. This is a perfect integer with no approximation, unlike months or years.
How many milliseconds are in 2 weeks?
2 × 604,800,000 = 1,209,600,000 milliseconds = 14 days exactly. This is the standard Agile sprint duration in ms: sprintEnd = sprintStart + 1209600000.
How many milliseconds are in 4 weeks?
4 × 604,800,000 = 2,419,200,000 milliseconds = 28 days exactly. Note: this is NOT 1 month (a mean Gregorian month = 2,629,746,000 ms).
How many milliseconds are in 52 weeks?
52 × 604,800,000 = 31,449,600,000 milliseconds = 364 days. This is NOT equal to 1 year (31,556,952,000 ms). The gap is 107,352,000 ms ≈ 29.82 hours — why some years have 53 ISO weeks.
How many weeks is 1 billion milliseconds?
1,000,000,000 ÷ 604,800,000 = 1.6534 weeks ≈ 11.57 days.
How many weeks is 1 trillion milliseconds?
1,000,000,000,000 ÷ 604,800,000 = 1,653.44 weeks ≈ 31.69 years.
How many milliseconds is a full-term pregnancy?
Full-term pregnancy = exactly 40 weeks = 40 × 604,800,000 = 24,192,000,000 milliseconds = 280 days. This is one of the rare cases where weeks give a cleaner number than months (9 mean months = 23,667,714,000 ms ≠ 280 days).
Why doesn't 52 weeks equal exactly 1 year in milliseconds?
52 × 604,800,000 = 31,449,600,000 ms (364 days). A Gregorian year = 31,556,952,000 ms (365.2425 days). Difference: 107,352,000 ms ≈ 29.82 hours. This is why some years have 53 ISO weeks and why weekly schedules "drift" through the calendar.
How do I calculate weeks between two dates in JavaScript?
const weeks = (new Date(dateB) - new Date(dateA)) / 604800000; Returns a decimal if the dates aren't exactly a whole number of weeks apart.
How do I convert weeks to milliseconds in Excel?
=A1*604800000. Inverse: =A1/604800000. Days from weeks: =A1*7. Add N weeks to a date: =A1+(B1*7).
How do I convert weeks to milliseconds in Python?
ms = weeks * 604800000. Using timedelta: from datetime import timedelta; delta = timedelta(weeks=n); ms = int(delta.total_seconds() * 1000).
What is the maximum setTimeout delay in weeks?
2,147,483,647 ms ÷ 604,800,000 = 3.5503 weeks ≈ 24.855 days. For timers longer than ~3.5 weeks, use date comparison or repeated intervals instead of a single setTimeout.