Can I schedule a recording for a specific time of day?

No. The control is a delay of up to sixty seconds before the take begins, not a clock. For a session at a known hour you arm it at that hour rather than setting a start time, and the automatic stop then handles the other end of the take.

Why does the panel say to keep the tab visible?

Because browsers throttle background tabs to save power, and a throttled page can interrupt a long media capture. The timer driving the auto-stop also lives in the page, so a frozen tab would fail to stop. Keeping the window in front avoids both problems.

What happens if the countdown finishes but the microphone is blocked?

The arm fails and reports the permission problem in plain language, the same way the manual recorder does. Nothing is written, so there is no empty file to clean up. Grant microphone access before arming to avoid the wasted countdown.

Yes. While the take is running the arm control has become a stop control, and pressing it ends the recording immediately and builds the file. The pending automatic stop is cancelled along with it, so the two timers cannot conflict.

How long can an armed recording run?

Up to one hour, in fifteen second increments, with five minutes as the default. That ceiling is a practical one rather than a hard technical limit, since a very long capture in a single browser tab is fragile, and the recording is much more reliable when the tab stays in front.

Scheduled Recorder

You Might Also Need

Voice Recorder

Record your voice in browser

Interview Recorder

Record interviews in high quality

Microphone Recorder

Record from any microphone

Voice Memo

Quick voice memo recording

Scheduled Recorder arms a microphone recording with a countdown before it starts and an automatic stop when it has run long enough. It is built for the take you cannot be watching: a call, a session or a timed block.

What is Scheduled Recorder?

Set a start delay and a duration, press arm, and the tool waits, counts down, then records for exactly as long as you asked before stopping itself and building the file.

The two controls and the lifecycle:

A start delay from 3 to 60 seconds in single second steps, defaulting to 10.
An auto-stop duration from 15 seconds to 3600 seconds in steps of 15, defaulting to 300, displayed in seconds or minutes depending on how long it is.
An arm control whose label counts down while it waits, then switches to a live indicator once recording begins.
The familiar preview and download panel once the take completes.
A hint stating the countdown length, the stop time and the reminder to keep the tab visible.

The reason this exists is that starting a recording by hand and then leaving it is unreliable, and so is remembering to stop it. The countdown gives you time to move away from the machine and to settle the room, and the automatic stop means a session that overruns cannot fill the file with hours of nothing. Both behaviours live in the shared recorder and are simply configured by the two sliders here. Once the countdown finishes, the capture path is the usual one: the microphone stream into a media recorder, a decode on stop, and a 16-bit WAV written to disk. If the microphone request is denied the arm fails with a clear message rather than recording nothing, and the timer that drives the auto-stop is cleared properly when you stop early. Keeping the tab visible matters because browsers throttle background tabs, which can interrupt a long take.

What scheduling does not give you:

It is a delay, not a clock: you cannot set it to begin at a specific time of day.
Closing the tab, sleeping the machine or switching off cancels everything, because the timer lives in the page.
Background tab throttling can affect a long take even when the tab is technically open, which is why the panel asks you to keep it visible.
Only one take is armed at a time, with no queue of recordings.
There is no level metering, so an armed recording cannot be monitored while it runs.
The maximum duration is one hour, so longer sessions need either a second take or a different approach.

Use it when you know a session is about to start and want it captured without staying at the keyboard, or when you want a fixed length block such as ten minutes of dictation. Set the delay long enough to step away, set the duration to the length you actually need rather than a very generous figure, and leave the tab open and in front. It is also worth testing the setup once with a short delay and a short duration, because a failed capture discovered after a long session is an expensive way to find out; that test costs a minute and proves the input, the permission and the timer all work together.

How to use Scheduled Recorder

Set the start delay between 3 and 60 seconds, choosing long enough to leave the machine.
Set the auto-stop duration, from 15 seconds up to an hour, in fifteen second steps.
Press arm; the control counts down and recording begins automatically when it reaches zero.
Let the take stop itself at the set duration, then download the WAV from the completed panel.

When to use Scheduled Recorder vs related tools

Scheduled Recorder is for captures you cannot babysit, which makes it the right answer for a session with a known start time and length. Voice Recorder is the manual version of the same capture, and Interview Recorder is the high quality variant with a long safety stop built in. When the two sides of the conversation may end up at different levels, Multi-Guest Leveler is the follow up step.

Privacy & Security

This tool runs entirely in your browser — no data ever leaves your device. There is no server round-trip, no upload, no logging, and no account required. Your input is processed locally using client-side JavaScript and is never stored, transmitted, or accessible to anyone else. When you close the tab, everything disappears.