Settings

The number

A decimal count, a hex blob with or without separators, or a version 1 UUID. Hex is tried most significant byte first and least significant byte first, because a disk image and a document give you opposite answers and remembering to reverse it is how mistakes happen.

What it could be

The other way round

An instant, and what every format would write for it. Read as UTC, because every epoch below is a UTC instant.

A whole column at once

One value per line, all read in the same format, which is the case once you know what the column is.

How it works

A timestamp in a file or log is just a number, and the number does not say what format it is. EPOCH tries every format it knows, including Unix time, Windows FILETIME, .NET ticks, GPS time and hex read both ways, and ranks the results by which give a date that could be real. It converts a whole column at once and shows local time and UTC. Nothing leaves this tab.

The guide: What is this timestamp?

Questions people ask about EPOCH

Which formats does it cover?

Unix in seconds, milliseconds, microseconds and nanoseconds; Windows FILETIME; Chrome, WebKit and Edge; Apple Cocoa absolute time in seconds and in nanoseconds; HFS and HFS+; .NET ticks; NTP and Bluetooth; OLE automation dates as used by Excel and COM; packed MS-DOS and FAT date-time; the time field of a version 1 UUID; GPS seconds; and Twitter and Discord snowflakes. Seventeen in all, each with its epoch and tick size printed beside the answer.

How does it tell a FILETIME from a .NET tick?

It does not, and nor can anything else: both count 100-nanosecond intervals, so a given moment is a valid value in both and the numbers differ only by the constant between their epochs. What it does is show you both readings with their dates, and you decide from where the number came: a value out of an NTFS record is a FILETIME, a value out of a .NET application’s database is probably ticks. Presenting one and hiding the other would be the tool deciding something it has no basis to decide.

Why does the GPS offset matter?

GPS time does not take leap seconds, so it runs ahead of UTC by a whole number of seconds that has grown over the years. The current offset is set on the page and applied to both directions. If you are decoding something from an earlier period the offset was smaller, so change it, and it is on the page rather than buried precisely so that the assumption is visible and adjustable rather than baked in.

Does it handle a whole column?

Yes. Once you know what the format is, which is usually the case after decoding one value, paste the column, pick the format, and every line is read at once, with anything that will not read marked rather than silently dropped. It comes out as a CSV with the original value beside the UTC and local readings, so it can go straight into a schedule or an exhibit.

What about local time versus UTC?

Every format here except two counts from a UTC instant, and both readings are shown: the UTC one, and the same moment in this browser’s own time zone. The two exceptions are called out where they appear: classic HFS wrote local time while HFS+ writes UTC and the number alone does not say which, and packed DOS and FAT timestamps are always local with no record of the zone. Those are properties of the formats, not of this tool, and pretending otherwise would be the sort of quiet assumption that gets an exhibit challenged.

Is anything sent anywhere?

No. It is a page of arithmetic. Nothing is uploaded, there is no account, and once the page has loaded it works with the network off, which matters, because forensic workstations frequently have none.

Doing this often? OBSCURA Umbra edits a folder of code where it is and runs JavaScript, TypeScript and Python over it in a sandbox. Everything is US$5 a month or US$48 a year.