A CSV export can contain thousands of rows and still hide its most useful information in one column of numbers. Values such as 1700000000 may mark when an order was created, a form was submitted, or an event occurred. An epoch time converter helps turn a sample into a readable date before you transform the entire file.
The key is to establish what the column means. A convincing date from a converter does not prove that every row uses the same unit or time zone. A short check at the beginning can save a large cleanup later.
Read the column name and any export documentation. Labels such as created_at, event_time, and updated_ms offer clues, but they are not guarantees. A unix timestamp usually counts seconds since January 1, 1970, at 00:00:00 UTC; some systems instead provide milliseconds. Both are common descriptions of epoch time in everyday documentation.
Check a few values from the beginning, middle, and end of the file. Contemporary seconds values are often about ten digits, while millisecond values are often about thirteen. This is a useful hint, not a rule for all dates. A negative number may represent a date before 1970. An empty cell may simply mean the event never happened.
Keep the original column intact. If a spreadsheet changes a long numeric value into scientific notation or rounds it, copy from the original CSV text before testing. The raw value is your reference if the converted dates look odd.
Choose a value linked to an event you already know, such as an order with a visible confirmation date. Enter it in a timestamp converter and check whether the resulting year, month, and time are plausible. If the output lands close to 1970 when you expect a recent event, a seconds value may have been interpreted as milliseconds. If the value appears out of range, the opposite error may be involved.
Use Epochly's free timestamp converter to check one or two source values before applying a formula to the whole column. Record the unit you confirmed and the display zone you used. That way, someone else can reproduce your result.
Once you have confirmed seconds or milliseconds, add a separate column for the displayed date. A spreadsheet's date functions typically expect a calendar date serial value rather than a Unix count, so the conversion formula must account for the Unix starting date and the input unit. Test the formula on your verified sample before filling it down.
Give the new column a clear name, such as created_utc or created_local. Formatting a cell to look like a date does not automatically determine its time zone. If your report is for a team in several locations, UTC is a useful shared reference, and you can add local views where needed.
Filter for blanks, unusually old dates, and implausibly distant future dates after the conversion. A file can mix units if data came from several services. It can also include placeholders such as 0; zero corresponds to the Unix epoch, but a source system might use it to mean "unknown." Check the data definition before assigning meaning.
Include the original timestamp, its unit, the readable date, and the zone used for display in your working file. This makes a unix timestamp converter check easy to repeat and prevents a later reader from mistaking a local clock time for UTC.
The practical sequence is simple: preserve the raw column, verify representative entries, convert into a new column, and review exceptions. If one value still looks wrong, try it in Epochly's epoch converter before changing your spreadsheet formula. A careful sample check makes a large export much easier to trust.
