Naar de inhoud
OneKitly

The Same .ics File Can Mean Five Different Times

Gepubliceerd op 7-9-2026 · 4 min leestijd · Bestandstools

Daniel Okonkwo

Daniel Okonkwo — Front-enddeveloper en techredacteur bij OneKitly

Webprestaties · Bestandsformaten

Getoetst aan 3 bronnen

Profiel bekijken →
Kort gezegd

A DTSTART line comes in three shapes. DTSTART:20260908T080000Z ends in Z and is an instant in UTC — the same moment for everyone, and the only form nothing can misread. DTSTART;TZID=Europe/Paris:20260907T140000 is a wall-clock time plus the name of the zone it belongs to, which is correct only if whatever reads it knows that zone. DTSTART:20260907T140000, with neither Z nor TZID, is a floating time: two o'clock wherever you happen to be, which is what you want for a New Year countdown and almost never for a meeting. The dangerous case is the middle one handled carelessly: strip the TZID, keep the digits, and the wall-clock time gets re-anchored to whichever machine is doing the reading. The viewer here shows you which of the three you are looking at before anything is converted, and the converters carry the zone through untouched rather than guessing.

Advertentie

iCalendar writes a start time in one of three ways, and only one of them is unambiguous. A meeting written with a named zone, converted on machines in Paris, New York and Honolulu, spanned nineteen hours and changed day.

Why the file names a zone instead of an offset

Writing +02:00 would fix the meeting to a number that stops being true twice a year. A weekly appointment at 14:00 in Paris is +02:00 in September and +01:00 in November, and the point of a recurring event is that it stays at two in the afternoon on both sides of the change. Naming Europe/Paris says which rulebook to apply; the offset is then looked up, date by date, in a zone database that gets updated whenever a country moves its clocks.

That is also why converting a TZID time to UTC is not a subtraction you can do in your head, and why a tool that has no zone database should not try. Keeping the name and the wall-clock digits exactly as the file wrote them is lossless; replacing them with an instant computed from the wrong zone is not, and it is the kind of error that looks fine on screen until somebody joins a call an hour late.

The all-day event, which is not a time at all

A birthday, a public holiday or a day off is written DTSTART;VALUE=DATE:20261225 — eight digits, no time, and the parameter that says so. It means the whole of 25 December wherever the reader is, which is exactly right for Christmas and would be wrong as an instant. Rewrite it as a datetime and it becomes midnight UTC, which is still the 25th in Europe and already the 24th anywhere west of Greenwich. The VALUE=DATE marker is carried through here rather than being resolved into an hour.

What to check before you trust an imported calendar

Open the file in the viewer and look at one event you know the real time of. If it is right there, the file is right and any later disagreement comes from the application you imported into. Three habits cover almost everything: prefer the Z form when you publish a calendar other people will subscribe to, keep TZID when you are moving your own calendar between applications, and never edit a start time by hand in a text editor without checking which of the three forms the line is in.

One meeting written TZID=Europe/Paris, re-anchored to the reading machine
Machine reading the fileWhat 14:00 becomesOff by
Europe/Paris20260907T120000Zcorrect
UTC20260907T140000Z+2 h
America/New_York20260907T180000Z+6 h
Asia/Tokyo20260907T050000Z-7 h
Pacific/Honolulu20260908T000000Z+12 h, next day
ICS-lezerOpen een agenda-uitnodiging of -export en lees de gebeurtenissen voordat je iets importeert.Probeer de tool →
Advertentie

Veelgestelde vragen

My imported events are all off by one or two hours. What happened?
A constant shift across every event is the signature of a zone that was dropped and replaced. Open the original .ics in the viewer: if the start times look right there, the file kept its zone and the application you imported into is applying a different one — check its calendar time-zone setting, which is separate from the operating system's. A shift that varies event by event is a different problem, usually a mix of Z and floating times in one file.
Which form should I use when I publish a calendar?
Z for anything with a fixed instant — a webinar, a match, a deadline — because it cannot be misread and needs no zone database at the other end. TZID for a calendar people live by locally, such as a school timetable or an office's opening hours, where the wall-clock time is the thing that must stay put across a daylight-saving change. VALUE=DATE for whole days. Floating times only when you genuinely mean local time everywhere, which in practice is New Year and very little else.
Does the viewer change my file?
No. It reads the file in your browser and shows what is in it; the file on disk is untouched, and nothing is sent anywhere. That is the point of looking before converting — you can settle an argument about a start time without committing to anything.

Artikelen die je misschien interesseren

Alle gidsen →
HandleidingBuilding a Calendar From a Schedule You Already Have in a SpreadsheetCourse timetables, match fixtures, shift rotas and conference programmes all start life as a table. Four columns are enough to turn one into a file every calendar application can import.VergelijkingThe JSON Export Keeps Three Things the CSV Has No Column ForSame file, same parser, two outputs. The spreadsheet gets eight columns; the JSON gets the named time zone, the all-day flag and the recurrence rule as well.UitlegA Recurring Event Is One Line in the CSV, Not TwelveAn .ics file stores a weekly meeting once, with a rule attached. Export it to CSV and you get a single row for the whole series — which is the file being honest, not the converter losing rows.HandleidingYou Do Not Have to Rename Your Columns to EnglishThe header row is matched in six languages, so prénom, apellidos, Vorname and cognome are all understood. One header is genuinely ambiguous — nom — and it is settled by the column next to it.HandleidingMerging Calendars and Address Books Appends — It Does Not DeduplicateThe merge tools put every record from every file into one output, in the order you gave them. That is the right default and the one thing to know before you feed in two exports of the same account.VergelijkingTwo Emails in One Cell, or Two Strings in an ArrayA contact can have several phone numbers and several addresses. The CSV joins them with a middle dot into one cell; the JSON keeps them as a list, which is the difference between a script that works and one that splits on a guess.

Vergelijkbare tools

Bronnen

Een fout in dit artikel gezien?