Recovering original time zone from DateTimeOffset after conversion

Answer to the Exact Question

There is no supported .NET API that preserves or recovers the original time‑zone identifier when a DateTime is converted to a DateTimeOffset. The DateTimeOffset type only contains the local time value and the UTC offset; it has no field for the time‑zone ID or the TimeZoneInfo instance that performed the conversion. Consequently, an application must store the zone identifier (for example, the Windows or IANA ID) separately if it later needs to know the source zone.

Why the Offset Is Insufficient

• The same offset can belong to multiple zones (e.g., UTC‑05:00 is used in Eastern Time, Central Standard Time, and many others).
• During daylight‑saving transitions the offset changes, so an offset value alone cannot determine whether a local time was ambiguous or invalid.
• Time‑zone rules can change over time; relying on the current rules on the host machine can produce different results for the same historical timestamp.

Recommended Pattern

1. Capture the zone ID. When converting a local DateTime to a DateTimeOffset, also record the zone identifier that you used (e.g., "Pacific Standard Time" or "America/Los_Angeles").
2. Persist the pair. Store the DateTimeOffset and the zone ID together – in a DTO, a database column, or a JSON field. Example:

3. public record ZonedDateTime
   {
       public DateTimeOffset Offset { get; init; }
       public string ZoneId   { get; init; }
   }
   

4. Re‑apply the rules when needed. Later, retrieve both values and reconstruct the original zone:

   var tz = TimeZoneInfo.FindSystemTimeZoneById(zoned.ZoneId);
   var originalLocal = TimeZoneInfo.ConvertTimeFromUtc(zoned.Offset.UtcDateTime, tz);
   

Practical Verification

On any .NET runtime (e.g., .NET 8 on Windows or Linux), the following minimal code demonstrates that the zone ID is not part of DateTimeOffset:

var local = new DateTime(2026, 10, 18, 18, 0, 0, DateTimeKind.Unspecified);
var tz = TimeZoneInfo.FindSystemTimeZoneById("Pacific Standard Time");
var offset = tz.GetUtcOffset(local);
var dto = new DateTimeOffset(local, offset);
Console.WriteLine(dto);            // 2026-10-18T18:00:00-07:00
Console.WriteLine(dto.Offset);       // -07:00
// No property for "Pacific Standard Time" is exposed.

Conclusion

Because the offset alone cannot uniquely identify the original time zone, the only reliable way to recover that information is to store the zone identifier explicitly alongside the DateTimeOffset. This approach works across platforms, survives daylight‑saving changes, and allows you to re‑apply the exact rules that were used during the original conversion.