Convertitore Ora: Fusi Orari Online Gratuito

Enter the time in the Time field (supports HH:MM, HH:MM:SS and ISO 8601 like 2026-07-10T14:30Z) under the 'From' panel, select the source zone by typing a city or choosing from the dropdown, pick the date with the Date picker to account for DST, then click the "Convert" button. The result appears in the 'To' panel with the converted time, numeric UTC offset and a short IANA name (for example, America/New_York). Use the "Copy" button to copy RFC3339 output (YYYY-MM-DDTHH:MM:SS±HH:MM) or "Swap" to flip zones without retyping.

Time Converter accepts HH:MM, HH:MM:SS, full ISO 8601 timestamps (YYYY-MM-DDTHH:MM:SSZ or with offset), Unix epoch seconds and milliseconds, and free-text city names tied to IANA zones. Date range covers years 1900–2100 and UTC offsets up to ±14:00; when uploading CSV the limit is 2 MB or 500 rows per file. For best results use ISO 8601 or epoch milliseconds to avoid browser parsing quirks (Safari on older macOS/iOS parses some nonstandard formats inconsistently).

Yes — click 'Add Location' to add up to 10 locations on desktop (mobile is limited to 5 to conserve memory). After adding locations, use the 'Show 24-hour grid' toggle to see a side-by-side hourly view and the 'Highlight working hours' checkbox to mark 09:00–17:00 in each locale. You can then click 'Download CSV' to export the table as a .csv file (UTF-8, comma separated) or 'Copy table' to paste into Slack or a calendar invite; large tables may slow older phones, so export on desktop when possible.

Time Converter uses the IANA time zone database (tzdata) for DST and historical rules; the UI shows the tzdb version at the bottom and updates it periodically. When you pick a specific date in the Date picker the conversion applies the DST rules that were valid on that date (useful for historical scheduling). Note the trade-off: the tool caches tzdb locally for seven days to avoid repeated downloads, so very recent tzdb patches might require a refresh (click 'Reload tzdb' in the footer).

Click the 'Now' button — the tool reads your browser clock and timezone and populates the 'From' time; then choose the destination city and click 'Convert' to see the current time in X with the UTC offset and IANA name. If your device clock is wrong, results will be offset, so verify system time first; the UI displays the detected browser time and a 'Sync with NTP' suggestion if it differs by more than 2 minutes. Live second updates are throttled in background tabs (browsers pause timers), so click 'Refresh' when you return to avoid stale displays.

Select 'UTC' or enter +00:00 in the 'From' zone, input the UTC time (ISO 8601 recommended) or click 'Now', then press 'Convert' or use the quick 'To My Timezone' button to map it to the browser-detected local zone. UTC has no DST, so conversions only depend on the target zone's historical and current DST rules; if your local timezone recently changed rules the cached tzdb might be out-of-date until you click 'Reload tzdb'. For batch conversions of timestamps use the CSV upload and set the source zone to UTC to avoid ambiguous local parsing.

Conversions are performed client-side in your browser using JavaScript so you don't upload your input times to our servers during normal use; the app only fetches the tzdb file (and will cache it locally for seven days). Optional actions like 'Download CSV' generate files in-browser; if you click 'Share' it creates a short URL that is stored on the server — the UI warns you before creating any share links. We also collect anonymized usage metrics only if you opt in; there is no account required and no watermark on exports.

Typical issues are ambiguous abbreviations (CST), malformed timestamps, or browser clock drift. If you see an 'Ambiguous zone' warning, click the zone name to pick the correct IANA region (for example, choose America/Chicago instead of Asia/Shanghai). For parsing errors, reformat inputs to ISO 8601 or epoch milliseconds, ensure CSVs are UTF-8 with commas and include a header row; if live results seem off, click 'Reload tzdb' and verify your device time.

On desktop Chrome and Firefox provide the most consistent behavior: real-time updates, fast CSV downloads, and smooth 10-location tables. Safari on iOS/macOS can parse nonstandard date strings differently and background tab timers are paused by the OS, causing live clocks to stop updating; on low-memory Android devices large multi-location tables may stutter, so limit to five locations. For heavy planning use a desktop browser, upload CSVs there, and export the .csv for import into calendar software.

Use the 'Add Location' and 'Show 24-hour grid' to quickly visualize overlaps and working-hour windows without opening Outlook/Google Calendar. The tool exports the result table as a UTF-8 .csv you can import into Excel (columns: original_time, original_zone, converted_time, converted_zone, utc_offset), or copy RFC3339 strings to paste into calendar event start/end fields. The trade-off is you won't get calendar integration like availability checks or invitations — for that, export and then use your calendar client.

Yes — click 'Upload CSV', select a .csv (UTF-8) file up to 2 MB or 500 rows, then use the 'Preview' step to map columns: timestamp (ISO 8601 / Unix seconds / Unix milliseconds), source_zone (IANA name or UTC offset) and an optional label. After mapping, press 'Convert All' to produce a converted CSV you can 'Download CSV' (comma-delimited) or 'Copy' to clipboard. Common pitfalls include using semicolons as delimiters or non-UTF-8 encodings; if parsing fails, re-save the file from Excel with UTF-8 encoding and commas.

Abbreviations are inherently ambiguous (CST can mean America/Chicago or Asia/Shanghai), so Time Converter shows an 'Ambiguous abbreviation' dialog and lists matching IANA zones; choose the correct one from that list (for example, pick America/Los_Angeles for PST/PDT). For scripts or CSVs, prefer full IANA names (America/New_York) or numeric offsets (UTC-05:00) to avoid warnings. The UI also displays the resolved offset and whether DST/policy is currently applied so you can confirm the intended zone before exporting.