Why is my server showing the wrong time?

It's a classic. You call date('Y-m-d H:i:s') and you realize your server is sitting in UTC or some random data center in Virginia, while you're sitting in London or Tokyo. By default, PHP looks at the date.timezone setting in your php.ini file, but you usually don't have access to that in shared hosting, or you don't want to mess with global configs.

The quickest fix is date_default_timezone_set(). I usually put this right in my configuration or bootstrap file so it's set once for the entire request. Here is how you do it:

// Set the default timezone for all date/time functions
date_default_timezone_set('America/New_York');

echo date('H:i:s'); // Now this reflects New York time

Just a heads-up: make sure you use the official timezone identifiers (like 'Europe/London' or 'Asia/Kolkata'). If you misspell them, PHP will throw a warning, and you'll be right back where you started.

Should I just store everything in the user's local time?

Absolutely not. Please, for the love of your future sanity, don't do this. If you store "2023-10-01 10:00:00" in your database without a timezone, and you have users in three different countries, that timestamp is meaningless. Then you hit Daylight Savings Time (DST) changes, and suddenly your scheduled posts are appearing an hour early or late.

The industry standard—and the way I build every project—is to store everything in UTC. UTC doesn't have daylight savings. It's the "ground truth." You treat your database as a UTC-only zone. You only convert that time to a local timezone at the very last second, right when you're echoing the string to the user's screen.

How do I actually convert a UTC time to a specific user's timezone?

While the date() function is fine for simple things, once you're dealing with multiple timezones, you need the DateTime and DateTimeZone classes. They are far more powerful and less prone to errors.

Imagine you've pulled a UTC timestamp from your database and you know your user is in Los Angeles. Here is how I'd handle that conversion:

// 1. The time as it exists in your database (UTC)
$utcDate = '2023-12-25 15:00:00'; 

// 2. Create a DateTime object and tell PHP it is currently UTC
$date = new DateTime($utcDate, new DateTimeZone('UTC'));

// 3. Change the timezone to the user's local preference
$date->setTimezone(new DateTimeZone('America/Los_Angeles'));

// 4. Output the formatted local time
echo $date->format('Y-m-d g:i a'); // "2023-12-25 7:00 am"

Notice that we didn't change the actual point in time; we just changed the perspective of the time. The DateTime object handles all the messy math of offsets and DST for you.

What if I need to calculate the difference between two timezones?

This is where the diff()` method comes in. If you have two DateTime objects—even if they are in different timezones—PHP will normalize them to UTC internally to calculate the exact difference.

I've used this often for "Time until event" countdowns. You create one object for "now" (in the server's zone) and one for the "event time" (in the event's local zone), and diff() gives you a DateInterval object. It's much cleaner than trying to subtract Unix timestamps manually and dividing by 86,400 to get days.

📋 Practical Task

Exercise: Build a Global Webinar Time-Converter

You are building a registration page for a global webinar. The webinar is scheduled for 2024-11-15 18:00:00 UTC. Your task is to create a PHP script that allows a user to select their timezone from a list and see exactly when the webinar starts in their local time.

• Create a hardcoded array of 3-4 different timezones (e.g., 'Asia/Tokyo', 'Europe/Paris', 'America/New_York').
• Simulate a user selection (you can use a $_GET variable or a simple variable for testing).
• Use the DateTime and DateTimeZone classes to convert the UTC webinar time into the selected local timezone.
• Print the result in a human-readable format: "The webinar starts at [Time] in [Timezone Name]."