Converting hours to minutes is different from calculating the difference between São Paulo and Tokyo.
Converting time units (hours, minutes, seconds) is linear and simple: 1 hour = 60 minutes = 3,600 seconds, and 1 minute = 60 seconds. These relationships are fixed and universal, based on the definition of the second in the International System of Units. Converting between them is a direct mathematical operation, without ambiguity — simply multiply or divide by 60 or 3,600. This is the conversion TudoConversor offers in the time category.
Converting between time zones, on the other hand, is fundamentally different: it is not a fixed mathematical relationship, but a political and administrative definition. A time zone is a region of the world that adopts a common official time, usually aligned to a multiple of hours relative to Coordinated Universal Time (UTC). Countries and regions can change their time zone by government decision, and this has happened several times throughout recent history — including in Brazil, which changed its time zone and daylight saving rules several times over the past decades.
The central concept of time zone conversion is the UTC offset: each time zone is defined by a difference relative to UTC, which can be positive or negative. Brasília time, for example, is UTC−3, while Tokyo is UTC+9 — a 12-hour difference between the two. To convert a time from Brasília to Tokyo, add 12 hours to the local time. This calculation seems simple, but is complicated by two factors: daylight saving time and the International Date Line.
Daylight saving time (a temporary clock change, usually moving forward 1 hour during part of the year) complicates calculations: two countries that have the same time zone difference in January may have a different difference in July, if one of the two observes daylight saving time and the other does not, or if the start and end periods of daylight saving time in each country do not align. Brazil abolished daylight saving time in 2019, but many countries in the northern hemisphere still observe it, which means the difference between Brasília and Europe, for example, changes depending on the time of year.
Another often-forgotten factor is the International Date Line: traveling east or west across this imaginary line in the Pacific Ocean can mean gaining or losing an entire day on the calendar, not just adjusting hours. If it is 10am Monday in Brasília, in Auckland (New Zealand, UTC+13) it may be 11pm Monday — but crossing the line in the opposite direction, the same time may correspond to Sunday. This is different from any physical unit conversion, where there is no concept of "skipping" an entire unit.
For these reasons, time zone conversion tools need to consult regularly updated databases, such as the IANA Time Zone Database, used by virtually every modern operating system and programming language. Time zone and daylight saving rules for each region of the world change by political decision, not by a fixed mathematical constant like physical units. An outdated database can produce wrong conversions, especially for dates close to recent rule changes.
TudoConversor treats the two needs clearly and separately: time unit conversion (hours, minutes, seconds) follows fixed mathematical relationships and is available in the time category; time zone conversion, in turn, depends on political rules and updated databases, and should be done with tools that consult reliable sources such as IANA. Understanding this difference avoids the common mistake of treating time zones as if they were just another unit conversion.
The IANA Time Zone Database, maintained by the Internet Assigned Numbers Authority, is updated several times a year to reflect political changes in time zones and daylight saving time worldwide. In 2024, for example, the database recorded adjustments in regions such as Kazakhstan, which unified its time zone to a single UTC+5, and Mexico, which abolished daylight saving time in much of its territory. These frequent updates demonstrate that time zones are a living system, subject to government decisions, and not a mathematical constant like physical units.
The standardization of time zones by named zones (such as "America/Sao_Paulo" or "Europe/London"), rather than fixed numeric offsets, is what allows computer systems to handle daylight saving time correctly. A schedule stored as "2 pm in America/Sao_Paulo" remains correct even if Brazil reintroduces daylight saving time in the future, because the system consults the zone's current rules at display time. A schedule stored as "2 pm UTC−3", however, would become wrong if the offset changed — this is the practical advantage of using named zones in calendar applications.