Frequently Asked Questions (FAQ)

The time on screen is your device's own system time as read by the browser, so it matches your computer clock exactly. What the page adds is a check: it compares your device against our server and shows the gap to a tenth of a second, reporting a match when the difference is under 0.3 seconds. When second-level accuracy matters — a ticket sale or course registration — use the Server Time page instead.

Yes. Search 70 cities by city or country name and add the ones you need. Each card shows the current time plus the offset from your main city, whether it is still today or already tomorrow there, the time zone abbreviation, and a DST badge when daylight saving is in effect. Drag a card to reorder it or tap it to promote it to the main clock; your layout is saved in the browser for the next visit.

The − and + buttons under the clock scale the digits from 20px to 140px in 5px steps, and the fullscreen button in the header hides the menu entirely. The settings menu at the top right switches between digital and analog faces and between 24-hour and 12-hour time, and those choices are saved as well. It works well left running on a classroom projector or a shop display.

Yes. The export button under the lap list saves a CSV file named stopwatch_laps_<date>.csv with four columns: lap number, split time, total time, and the wall-clock timestamp. It is written with a UTF-8 BOM, so non-ASCII labels open correctly in Excel, and Google Sheets reads it as is.

With a keyboard, Space starts and stops, L records a lap, and R resets. Every lap also plays a short beep and, on touch devices, a vibration pulse, so you know the lap registered without watching the display. The beep and the vibration each have their own on/off button right below the time.

Laps are stored in your browser, so they survive a reload or closing and reopening the tab, and the display resumes from the last lap's total time. The measurement itself comes back paused, so press start again to keep timing. With two or more laps the fastest and slowest splits are color-coded and the average, best and worst splits appear below the list; deleting a single lap with its ✕ button renumbers the rest automatically.

The basic Timer counts down once from any duration up to 23 hours 59 minutes 59 seconds. Pomodoro alternates focus and break automatically and logs every completed focus session. Interval repeats a work/rest pair for the number of rounds you set. Multi-Timer runs up to 10 separately named timers of different lengths side by side.

Yes. The timer tracks its end time instead of counting ticks, so leaving the tab or reloading the page does not make the remaining time drift. While it runs, the remaining time appears in the browser tab title, and if you grant notification permission you also get a browser notification when it finishes. Closing the tab entirely ends the page, though, so no alarm will sound.

The +1s, +5s, +1m, +5m, +1h and +5h buttons add to whatever is already entered, so a duration like 7:30 takes a couple of clicks. The share button copies a link that carries the duration in the address (for example ?h=0&m=7&s=30), so whoever opens it lands with the same time filled in and only has to press start.

A regular timer counts down once; Pomodoro chains 'focus → break → focus' automatically and records every completed focus session. The defaults are 25 minutes of focus and a 5-minute break, with a 15-minute long break after the fourth focus block. A timeline above the clock shows which block you are in and what comes next.

Yes. Focus can be set from 1 to 90 minutes, and the short and long breaks from 1 to 30 minutes each, using the − / + buttons or by typing a value. With 'auto start' on, each block rolls straight into the next; turn it off and an alarm sounds at the end of every block and waits for you to start the next one. Your settings are saved in the browser.

Yes. Only focus sessions completed while the page is open are counted — breaks are not — and the panel below shows today's, this week's and the last 90 days' session counts, your day streak, the sum of configured focus minutes, and a bar chart by weekday. Older records are dropped automatically. Records are stored in this browser, so they will not appear on another device or in a private window, and a reset button clears them.

Tabata is 20 seconds of work / 10 seconds of rest / 8 rounds — four minutes in total. HIIT is 40 seconds of work / 20 seconds of rest / 6 rounds. Choose Custom and you can set work and rest anywhere from 5 to 99 seconds each, with 1 to 20 rounds; your values are saved in the browser for next time.

No tapping is needed: work, rest, and the next round's work switch automatically. Each phase change plays the selected sound briefly. A supported device also vibrates briefly when vibration is enabled, and a separate completion alarm sounds after the final round. Browser or device settings may limit sound or vibration, so check the remaining time and round number on screen too.

The remaining time is recomputed from the phase's end time, so the countdown does not drift when the screen goes dark and comes back. While the interval runs the timer requests a screen wake lock, but not every browser supports it, and browsers slow scripts down while the screen really is off, so a round change alert can be delayed. If the round boundaries matter, extend your device's screen timeout and keep the display on.

Up to 10, each with its own name and color so you can tell which one finished. With two or more timers you also get start-all, stop-all and reset-all buttons, and on a keyboard the number keys 1-9 start or stop that timer, Shift + a number resets it, and A, S and R start, stop or reset everything.

Yes. Three built-in templates are included — cooking (pasta + sauce), laundry (wash + dry) and workout (sets + rest) — and you can name and save the current set — up to 10 of your own — then reload it in one click. The share button copies a link that encodes the whole set in the address (for example ?timers=10m:pasta,20m:sauce), so you can move the same setup to another device or send it to someone else.

No. The 15 alarm sounds, the volume slider and the vibration setting apply to every timer at once. You tell them apart by the name and color on screen and by the name shown in the browser notification. The alarm stops on its own after 30 seconds, so it will not keep ringing while you are away.

Each alarm gets one of 15 sounds, and the ▶ button previews it before you save. Vibration is stored per alarm, and the vibration button only appears on touch devices that support it. There is no silent option, so for a soundless alarm turn your device volume down and leave vibration on.

No. An alarm rings once at the time you set, and dismissing it switches that alarm off in the list. To use it again the next day, flip its switch back on; choosing snooze instead moves it 5 minutes later. You can keep up to 10 alarms, each with a label of up to 30 characters.

No. The alarm only works while the alarm page is open. It will ring while you are on another tab — the tab title flashes and the favicon turns into a bell — and if you allow notifications, a browser notification appears as well. While any alarm is switched on, the page also requests a screen wake lock so the display does not sleep, where the browser supports it.

Enter the target hour, minute and second and start it: the countdown runs to the millisecond, a beep sounds at 3, 2 and 1 seconds, and at zero the screen flashes with a GO alert. The speaker icon mutes the beeps, your target time is saved in the browser, and preset buttons jump to the next full hour or to 1, 5 or 10 minutes from now.

On load the page requests the Date.now() timestamp from Clock-Tani's server three times, sorts the samples by round-trip delay, and uses the middle one to calculate the offset from your device clock. It then applies that offset to the display. A badge such as 'synced +12ms' is the calculated offset, and failed requests fall back through external time APIs. The page does not poll on a fixed schedule; it re-syncs after events such as a device-clock jump or return to a long-hidden tab.

A per-site address such as /server-time/interpark asks that site for its own clock and counts down against the time in its HTTP response header. That header carries whole seconds only, so it cannot give millisecond precision, and if the lookup fails the page falls back to standard time. Interpark Ticket, Yes24 Ticket and Melon Ticket are supported; the course-registration page runs on standard time.

Yes. Each event exports an ICS file you can import into Google Calendar, Apple Calendar or any other calendar app to get reminders there, and you can export every saved event at once as a single dday-events.ics file. Events marked 'repeat yearly' carry a yearly recurrence rule into the ICS as well.

Yes. Select the lunar option when creating an event and the date is converted to the solar calendar for the countdown. Seollal (lunar 1/1) and Chuseok (lunar 8/15) come as presets, alongside presets for the Korean college entrance exam, New Year, Christmas and Children's Day. You can distinguish a regular month from a leap month, and the form checks that the selected leap month actually exists in that lunar year.

Yes. The tabs at the top add a milestone calculator (100, 200, 300, 365, 500 and 1,000 days and beyond, plus 1-10 year anniversaries), a couple view (the same day milestones from your start date, plus the upcoming monthly 14th anniversaries), and a date calculator (a date plus or minus N days, and the number of days between two dates). You can store up to 20 events with one of six categories and a memo, and giving an event a start date adds a progress bar.