Convert Weeks to Timestamp

This tool converts numeric values representing weeks into full UTC timestamps, using the Unix epoch (1970-01-01 00:00:00 UTC) as the starting point. If you enter 1, you’ll get 1970-01-08 00:00:00, which is exactly one week later. Entering 1.5 returns 1970-01-11 12:00:00.

Whether you’re working with analytics data, offset-based logs, or timestamps from tools that store durations in weeks, the Convert Weeks to Timestamp tool handles it instantly. You can paste values directly, import from a file, or type manually the results update live.

Everything happens right in your browser. Nothing is sent to a server. It’s fast, accurate, and designed for batch use.

Paste your input above or import a file below.
No file chosen
Supported file types: .txt, .csv, .tsv, .log, .json, .xml, .md, .ini, .yaml, .yml, .html, .htm, .css
Total items: 0
Options
Trim input lines
Ignore invalid values
Maximize output

How to Use:

  • Paste or type your values into the Input Weeks Since Epoch box one per line.
  • Each number represents weeks since 1970-01-01 00:00:00 UTC.
  • Use the Trim input lines toggle to automatically clean whitespace.
  • Enable Ignore invalid values to skip negative or non-numeric entries.
  • Use Maximize output to expand the results panel.
  • Output updates live, or click Convert to trigger it manually.
  • Click Copy Output to copy the results (the button flashes “Copied!”).
  • Use Export to File to download your results as .txt.
  • Click Choose File to import from .txt, .csv, .log, .json, or similar formats.
  • Click Clear All to reset input, output, toggles, filename, and count.

What Convert Weeks to Timestamp can do:

This tool helps you convert week offsets into real-world UTC timestamps. Each line of input is multiplied by 7 days and then added to the epoch start. If you enter 260.5, for example, the output is 1975-01-01 12:00:00, which is 260 full weeks and 3.5 days from epoch.

It supports fractional weeks, handles large values easily, and formats everything in clean YYYY-MM-DD HH:MM:SS UTC format. Bad input like not-a-number or -5 shows as Invalid, unless you enable the toggle to skip them silently.

Use this when analyzing time offset systems, converting data exports, decoding backend logs, or even prepping timestamps for charts or visualization.

Example:

Here’s a list of input values showing different week offsets and how they convert to UTC timestamps.

Input:

0
1
1.5
4.25
52
260.5
520
1040
-2
not-a-number

Output:

1970-01-01 00:00:00
1970-01-08 00:00:00
1970-01-11 12:00:00
1970-01-30 12:00:00
1971-01-01 00:00:00
1975-01-01 12:00:00
1980-01-01 00:00:00
1990-01-01 00:00:00
Invalid
Invalid

Convert Weeks to Timestamp Table:

This table includes 10 real-world examples showing how many weeks since epoch translate to full UTC timestamps.

WeeksUTC TimestampDescription
01970-01-01 00:00:00Epoch start
11970-01-08 00:00:001 full week
1.51970-01-11 12:00:001.5 weeks
4.251970-01-30 18:00:004.25 weeks = 29.75 days
521970-12-31 00:00:0052 weeks = 364 days
260.51975-01-02 12:00:00260.5 weeks = 1823.5 days
5201980-01-01 00:00:0010 years (approx)
10401990-01-01 00:00:0020 years (approx)
15602000-01-01 00:00:0030 years (approx)
2604.28572020-01-02 06:51:2550 years + fractional week

Common Use Cases:

Use this tool when you’re converting log durations, system metrics, counters, or archive values stored in weeks. It’s perfect for offset-based systems, timeline reconstruction, or simplifying week-based tracking into readable timestamps.

Related Tools