TFT

GPS Timestamp Converter

Convert between GPS time (used in satellites and precise navigation) and standard Unix timestamps or UTC. Essential for geospatial and timing applications.

GPS Timestamp Converter

Convert between GPS time and Unix timestamps

About GPS Time

GPS time is measured in weeks and seconds since the GPS epoch (January 6, 1980). GPS time does not include leap seconds, so it currently runs 18 seconds ahead of UTC.

How it works

Enter a GPS timestamp (seconds since January 6, 1980) or a Unix timestamp. The converter transforms between GPS time and Unix time, accounting for the different epoch start dates.

GPS time doesn't include leap seconds, while Unix time is based on UTC which does. The converter applies the current leap second offset (currently 18 seconds as of 2024) for accurate conversion.

Results display in multiple formats: GPS seconds, GPS week number + seconds of week, Unix timestamp, and human-readable UTC date. Copy any format with a single click.

When You'd Actually Use This

GNSS Data Processing

Convert GPS timestamps from receivers to Unix time for database storage and analysis.

Navigation Systems

Translate between GPS time used in navigation messages and Unix time for application logic.

Surveying Equipment

Process GPS survey data timestamps for integration with GIS and mapping systems.

Telemetry Analysis

Convert vehicle tracking data from GPS time to standard timestamps for reporting.

Scientific Research

Synchronize GPS-timed observations with other data sources using Unix timestamps.

Aviation Systems

Convert ADS-B and other aviation data timestamps between GPS and UTC-based systems.

What to Know Before Using

GPS epoch: GPS time started January 6, 1980 00:00:00 UTC. Unix time started January 1, 1970. The offset is 315964800 seconds.

Leap seconds: GPS time doesn't observe leap seconds. UTC does. The offset between them increases with each leap second (18 seconds as of 2024).

GPS week rollover: GPS week number is 10 bits, rolling over every 1024 weeks (~19.7 years). Rollovers occurred in 1999, 2019, and will in 2038.

Week + seconds format: GPS often uses week number + seconds into week (0-604799). This tool converts both continuous seconds and week formats.

UTC vs TAI: GPS time is aligned with TAI (International Atomic Time) minus 19 seconds. UTC = TAI - leap seconds.

Common Questions

What is GPS time?

GPS time is a continuous time scale used by GPS satellites. It started January 6, 1980 and doesn't include leap seconds.

How do I convert GPS to Unix time?

Add 315964800 seconds (GPS epoch offset) and subtract current leap seconds (18). GPS_time + 315964800 - 18 = Unix_time.

What is GPS week rollover?

GPS week number is 10 bits (0-1023). Every 1024 weeks (~19.7 years), it resets to 0. This happened in 1999, 2019, and will in 2038.

Why are GPS and Unix time different?

Different epochs (start dates) and leap second handling. GPS ignores leap seconds for continuous counting, UTC includes them.

What's the current leap second offset?

As of 2024, the offset is 18 seconds. The last leap second was added December 31, 2016. Future leap seconds are announced by IERS.

How do I read GPS week + seconds?

GPS week is weeks since January 6, 1980. Seconds of week is 0-604799 (7 days × 24 hours × 3600 seconds).

Is GPS time the same as UTC?

No. GPS time is ahead of UTC by the leap second offset (18 seconds). GPS time = UTC + 18 seconds (as of 2024).