Kitchen Timer Online: 12 Recipe Presets in One URL

Your phone runs one timer. The rice needs eighteen minutes, the eggs need eight, and the oven needs forty-five — so you end up shouting at a smart speaker with wet hands. A kitchen timer online solves this badly if it makes you retype the duration every time, and well if each duration is just a link you can bookmark, pin, or stick on the fridge as a QR code.

#TL;DR

• One URL per dish: ?t=8m on iKit's timer opens with eight minutes loaded.
• Two tabs equal two independent countdowns — no phone timer required.
• Screen Wake Lock stops your phone dimming mid-recipe; it's Baseline since 2025.
• Hidden tabs throttle timer callbacks, so deadline math beats tick counting.
• Time tells you when to check; a thermometer tells you when it's done.

#How to set a kitchen timer online without an app

The fastest kitchen timer isn't the one with the biggest buttons. It's the one where the duration is already in the address bar before the page finishes painting.

#The one-parameter preset

iKit's Stopwatch & Timer reads a t query parameter on load:

https://timer.ikit.app/?t=8m

That opens countdown mode with 480,000 ms on the display. The parser also accepts 90s, 1h, combinations like 1h+30m, colon form like 18:00, and a bare number read as minutes. The string never leaves your machine — it's parsed in the tab, like every other tool on iKit.

#Why the browser beats a phone timer for cooking

A phone timer is a single global resource, and it lives behind a lock screen you have to unlock with greasy fingers. A browser tab is cheap: open six of them and you have six timers, each with its own name in the tab strip.

• Each preset is a real URL — bookmark it, pin the tab, drop it in a family group chat.
• The laptop or tablet already propped on the counter is bigger than a phone screen.
• No app install, no account, no notification permission required for the tab you're looking at.
• Generating a QR code for a preset link with iKit's QR Code Generator turns a printed recipe card into a one-scan timer.

#Running two timers at once

Open ?t=8m in one tab and ?t=18m in another. They're separate documents with separate JavaScript contexts, so they count independently. Pin both tabs so an accidental close doesn't lose your rice. The only caveat is the one covered further down: keep the tab you actually care about visible, because hidden tabs get their callbacks slowed.

#12 recipe presets mapped to one-click timer links

These are starting points, not guarantees — pan thickness, altitude, and how cold the food was all move the number. The roast and poultry figures come from the FoodSafety.gov meat and poultry roasting charts; the rest are conventional stovetop timings you can adjust once and re-bookmark.

#Eggs, pasta, and rice

The green-grey ring on an overcooked yolk isn't a safety problem — USDA's egg guidance describes it as sulfur and iron compounds reacting at the yolk's surface, and it's safe to eat. It is, however, a very good visual signal that your egg timer is running two minutes long. Also worth knowing: hard-cooked eggs should be back in the fridge within two hours of cooking.

#Bread, roasting, and resting

That last row is not filler. Per USDA guidance, whole cuts of beef, pork, veal, and lamb need to reach 145°F and then rest at least three minutes — the rest is part of the safe minimum, not a serving-suggestion nicety, because the temperature holds or climbs while the meat sits.

#Building your own preset row

If you keep a recipe site or a personal wiki, generate the links instead of typing them:

const presets = {
  "Soft egg": "6m",
  "Al dente pasta": "9m",
  "Rice": "18m",
};

const link = (d) => {
  const u = new URL("https://timer.ikit.app/");
  u.searchParams.set("t", d);
  return u.href;
};

Object.entries(presets).forEach(([name, d]) =>
  console.log(name, "→", link(d))
);

URLSearchParams handles the encoding, so a value like 1h 20m becomes 1h+20m without you thinking about it. If you'd rather understand exactly what it does to spaces and plus signs, that's a rabbit hole we've already been down.

#Why does my phone screen turn off during a recipe

Because the platform is doing its job. Phones dim and lock on an idle timer to save battery, and "user is staring at a countdown" looks exactly like "user has walked away."

#The Screen Wake Lock API, in one call

The web platform has a fix. Per MDN, the Screen Wake Lock API lets a visible document ask the system to keep the screen on, and it reached Baseline "newly available" status in March 2025 — meaning it works across current versions of the major browsers. Following a recipe is one of the use cases MDN lists by name.

let lock = null;

try {
  lock = await navigator.wakeLock.request("screen");
} catch (err) {
  // Denied: low battery, power saving, or hidden doc.
  console.warn(err.name, err.message);
}

It requires a secure context (HTTPS) and it can be refused — low battery and power-saving modes are both legitimate reasons for the promise to reject. Always feature-detect with "wakeLock" in navigator before wiring a button to it.

#What releases the lock

A wake lock is not fire-and-forget. The system releases it when the document stops being visible, so switching to another tab silently drops it. Re-acquire on the way back:

document.addEventListener("visibilitychange", async () => {
  if (lock && document.visibilityState === "visible") {
    lock = await navigator.wakeLock.request("screen");
  }
});

Release it yourself when the countdown ends. Holding a screen awake after the pasta is drained is just battery theft.

#Does a browser timer keep running in a background tab

It keeps running. It does not necessarily keep good time — and the difference matters when the thing at stake is a tray of cookies.

#What throttling actually does to setTimeout

Browsers deliberately slow timer callbacks in hidden tabs to save CPU and battery. MDN's Page Visibility API documentation describes the budget model both Firefox and Chrome use: execution time is deducted from a per-window timeout budget that regenerates at roughly 10 ms per second. Tabs playing audio are treated as foreground and are exempt, as are tabs holding real-time connections such as WebSockets or WebRTC.

The practical consequence: a timer implemented as "add one second every time the interval fires" will finish late, sometimes by minutes, if you tabbed away to read a recipe.

#Deadline math beats tick counting

Store the absolute finish time once, then derive the remaining time from the clock on every frame. Throttling changes how often you repaint; it doesn't change what time it is.

const endsAt = performance.now() + 8 * 60 * 1000;

function tick() {
  const left = Math.max(0, endsAt - performance.now());
  render(left);
  if (left > 0) requestAnimationFrame(tick);
  else ring();
}

Come back to the tab after ten minutes in another window and the display is instantly correct, because nothing was ever accumulated.

#Getting an alarm you can hear from the next room

Three layers, in order of reliability:

1. Audio. A synthesised beep needs no file and no permission beyond the initial user gesture — and as a bonus, an audio-playing tab is exempt from throttling.
2. A system notification. Useful when the tab is buried, subject to permission and to whatever Focus mode your OS is in.
3. The title bar. Writing the remaining time into document.title costs nothing and is visible in a pinned tab.

Browsers block audio until the user has interacted with the page, which is precisely why a preset URL loads the duration but doesn't auto-start. A timer that started itself from a link would very often finish in silence.

#Timers don't replace a thermometer

A kitchen timer answers "when should I check?" It cannot answer "is this safe to eat?" Those are different questions and only one of them has a number you can measure.

#Time is a proxy; temperature is the fact

USDA's safe minimum internal temperature guidance is the actual finish line: 165°F for all poultry, 145°F plus a 3-minute rest for whole cuts of beef, pork, veal and lamb, and 160°F for ground beef. Roasting charts exist to tell you when to open the oven with a probe in hand, not to tell you dinner is ready.

#Where a countdown to a date fits instead

Timers are for minutes. If you're counting down to Thanksgiving dinner or a bake sale rather than to the moment the eggs come out, iKit's Countdown Timer targets a calendar date and produces a shareable link — the same URL-as-state idea, scaled up from minutes to months.

#References

• Meat and Poultry Roasting Charts — FoodSafety.gov; source for the oven temperatures and roasting times in the second preset table.
• Safe Minimum Internal Temperatures — the 165°F / 145°F + 3-minute rest / 160°F figures cited in the thermometer section.
• Shell Eggs from Farm to Table — USDA FSIS; used for the green-ring explanation and the 2-hour refrigeration window for hard-cooked eggs.
• Screen Wake Lock API — MDN; Baseline status, the request/release lifecycle, and the visibility re-acquire pattern.
• Page Visibility API — MDN; background-tab timeout budget, the 10 ms-per-second regeneration rate, and the audio/WebSocket exemptions.

#Related on iKit

• 5-minute timer, 10, 25: one URL trick for all — the full parameter syntax behind every preset link in this article, including browser keyword shortcuts.
• Online timer: how to run an accurate countdown — how much error a browser countdown actually accumulates, and where that leaves a 3-minute rest.
• Why background tabs pause your JavaScript timer — the throttling rules in detail, for when your oven timer fires ninety seconds late.
• How setInterval drifts and performance.now() doesn't — the deadline-based scheduling the code sample above relies on.
• Build a browser alarm sound with the Web Audio API — synthesising a beep loud enough to hear from the next room, with no audio file.
• Notification API: reminders that survive a tab switch — the second alarm layer, for when the timer tab is buried behind a recipe.
• Online stopwatch with lap times — the count-up half of the same tool, useful for timing folds and turns during a long proof.