DateTime.ToString()

wassupy.com

shorthand format strings

dates

d 11/19/2026
D Thursday, November 19, 2026
m November 19
M November 19
y November 2026
Y November 2026

times

t 3:35 PM
T 3:35:48 PM

combos

f Thursday, November 19, 2026 3:35 PM
F Thursday, November 19, 2026 3:35:48 PM
g 11/19/2026 3:35 PM
G 11/19/2026 3:35:48 PM
o 2026-11-19T15:35:48.9485178
r Thu, 19 Nov 2026 15:35:48 GMT
s 2026-11-19T15:35:48
u 2026-11-19 15:35:48Z
U Thursday, November 19, 2026 3:35:48 PM

custom date bits

era

%g AD
gg AD

year

yyyyy 02026
yyyy 2026
yyyy 2026
yy 26
y November 2026

month

MMMM November
MMM Nov
MM 11
%M 11

day

dddd Thursday
ddd Thu
dd 19
%d 19

custom time bits

hour

HH 15
%H 15
hh 03
%h 3

minute

mm 35
%m 35

second

ss 48
%s 48

subsecond

%f 9
ff 94
fff 948
ffff 9482
fffff 94822
ffffff 948225
fffffff 9482255

miscellaneous bits

date separator

%/ /

time separator

%: :

AM/PM

%t P
tt PM

time zone1

%K
%z +0
zz +00
zzz +00:00

Pitfalls and traps

General advice

Dates, times, and time zones are tricky. In .NET, there are subtle differences that can be challenging to spot. My general advice is:

Other gotchas

TimeZoneInfo.ConvertTime(...) returns a DateTime with Kind = Unspecified. For example:

DateTime dt = DateTime.UtcNow;
// dt.ToString("o") -> 2026-11-19T20:35:48.9489112Z
// dt.Kind -> Utc

TimeZoneInfo tz = TimeZoneInfo.FindSystemTimeZoneById("America/Chicago");
var sf = TimeZoneInfo.ConvertTime(d, tz);
// sf.ToString("o") -> 2026-11-19T14:35:48.9489112
// sf.Kind -> Unspecified

Note that the Unspecified time lacks a time zone offset in the output. You might be tempted to set its Kind to Local, but this is usually not a good idea:

// don't do this
var sfLocal = DateTime.SpecifyKind(sf, DateTimeKind.Local);
sfLocal.ToString("o") -> 2026-11-19T14:35:48.9489112+00:00

The time is correct, but the time zone offset is not. Chicago is -06:00, not +00:00. "Local" in this context is the server's time zone (-00:00).

1That undesired time zone also shows up in the related format strings %K, %z, zz, and zzz above. Again, these show the time zone of the server, not the time zone the value was converted to. Luckily, DateTimeOffset handles this better:

var dto = DateTimeOffset.UtcNow;
var chicagoDto = TimeZoneInfo.ConvertTime(dto, tz);
// dto.ToString("zzz")        --> +00:00
// chicagoDto.ToString("zzz") --> -06:00

Other surprising things

The Ticks property is not agnostic of time zones/kind:

DateTime utc = DateTime.UtcNow;
DateTime local = utc.ToLocalTime(); // don't do this
DateTime unspecified = TimeZoneInfo.ConvertTime(utc, tz);

// utc.Ticks         --> 639307173489489490
// local.Ticks       --> 639307173489489490
// unspecified.Ticks --> 639306957489489490

I guess it makes sense that Ticks would vary here, but I personally would have guessed that it was always in UTC, sort of like Javascript's getTime.

And DateTimeOffset works in the same spirit by factoring in the offset:

// these are the same for DateTimeOffset, but not DateTime
// dto.Ticks        --> 639307173489489470
// chicagoDto.Ticks --> 639306957489489470
//
// and the difference is the same as the time zone offset ✔️:
// (chicagoDto.Ticks - dto.Ticks) / TimeSpan.TicksPerHour --> -6