online clock local time
This clock reads the operating system time and formats it with `Intl.DateTimeFormat`, but the browser is not a trustworthy time source: if the computer clock is wrong, the time shown here is wrong too.
The browser infers this identifier from the operating system settings, not from GPS or IP-based geolocation.
The `pt-BR` locale picks colon separators and 24-hour format by regional convention, with no manual user configuration needed.
Since the page only reads the local clock, any drift in the system clock shows up directly in the displayed time, with no correction against a trustworthy time server.
No. It comes from your device's local clock; the page only formats and displays that value with the browser's Intl API.
Not directly: this clock reads the local operating system time; what keeps that clock close to accurate is the NTP protocol running in the background on the device, not the page in the browser.
By calling `Intl.DateTimeFormat().resolvedOptions().timeZone`, which returns the IANA identifier configured in the operating system, for example `America/Sao_Paulo` or `Europe/Lisbon`, with no geolocation involved.
No: daylight saving time was discontinued in Brazil starting in 2019, when the government did not decree the clock shift that year, and the IANA time zone database reflects that change for dates from that point onward.
Because a fixed offset has no idea whether that region observed daylight saving in a different year; an IANA identifier like `America/Sao_Paulo` carries the full history of rules, so converting a date from before 2019 already applies the correct saving offset for that period.
The clock only uses your device local time in this tab.