ForHosting KIT · Audio & Voice

Silence detection threshold calculator for audio

A -60 dB noise floor with a 12 dB margin gives a -48 dB silence threshold and a 550 ms minimum gap. Use the pair to set up trimming, splitting or transcription tools from your own recording instead of a generic preset. Free in your browser.

  • Free
  • Runs in your browser
  • No sign-up
  • Your data stays on your device
Use it from WebAPIEmailTelegramApp soon
If you enter
Noise floor db
-60
Margin db
12
You get
Threshold db
-48
Minimum duration ms
550

Silence detection works best when its cutoff reflects the recording instead of relying on a universal preset. This calculator turns a measured noise floor and a chosen safety margin into two ready-to-use settings: a decibel threshold and a minimum duration. The threshold identifies samples quiet enough to be silence, while the duration prevents very brief dips from being treated as meaningful gaps. Results are deterministic, easy to reproduce, and suitable for configuring trimming, segmentation, transcription, and quality-control workflows.

Start with a representative noise-floor measurement

Measure the noise floor in a portion of the recording where nobody is speaking and no intended sound is present. A representative sample matters more than an artificially quiet instant: room ventilation, microphone preamp hiss, electrical hum, distant traffic, and compression artifacts all contribute to the practical floor. Enter that level as a negative decibel value, such as -60 dB.

The calculator accepts values from -120 through 0 dB and rejects missing, nonnumeric, or non-finite input. If a production contains several environments, measure each environment separately or use the loudest stable background as the conservative input. Do not confuse the noise floor with the peak level or average program loudness.

Peaks describe the strongest signal; the floor describes the baseline that remains when the wanted content stops. A clean studio track may have a much lower floor than a field recording, so copying a threshold from another file can either miss genuine pauses or erase quiet material. This first measurement anchors every later decision in the actual recording.

Choose the margin and understand the calculation

The margin says how far above the measured background the silence cutoff should sit. This capability adds the non-negative margin directly to the noise floor: a -60 dB floor with a 12 dB margin produces a -48 dB threshold. Audio at or below that threshold is a silence candidate; the consuming audio tool still decides exactly how it measures windows, channels, and loudness.

A larger margin creates a higher, more permissive cutoff, which can recognize pauses despite a changing background but can also include quiet speech or fades. A smaller margin stays closer to the observed floor and protects low-level detail, although it may fail to detect pauses when the background fluctuates. Negative margins are rejected because they would place the cutoff beneath the measured floor and contradict the purpose of a silence margin.

Margins above 60 dB are also rejected as impractical.

Apply the minimum duration without clipping natural audio

A threshold alone would label every tiny downward fluctuation as silence. To provide a safer starting point, the calculator pairs it with a minimum duration computed as 250 milliseconds plus 25 milliseconds for every decibel of margin, rounded to the nearest millisecond. The baseline preserves short consonant gaps and waveform crossings, while the increasing duration compensates for the greater chance of false detection when a larger margin raises the threshold.

For example, a 12 dB margin yields 550 milliseconds. Configure your editor, transcoder, voice activity detector, or segmentation pipeline to require the signal to remain at or below the returned threshold for at least this long. Treat the result as a consistent operational preset, then audition representative files before destructive trimming.

Speech with dramatic pauses, soft music, reverberant rooms, and multichannel recordings may need a longer value or channel-specific analysis. The calculator does not inspect audio and does not claim to replace listening tests; it converts two explicit engineering choices into reproducible settings that teams can store, compare, review, and apply across automated jobs.

Configure podcast trimming

Derive repeatable silence settings from each recording room before removing long pauses.

Prepare transcription segments

Choose a documented pause cutoff for splitting speech into manageable transcription chunks.

Standardize media pipelines

Store calculated thresholds with job presets so operators use the same policy across batches.

How is the threshold calculated?

The margin in dB is added to the noise floor in dB, and the result is rounded to three decimal places.

How is the minimum duration calculated?

It is 250 milliseconds plus 25 milliseconds per dB of margin, rounded to the nearest millisecond.

Why are negative margins rejected?

A negative margin places the threshold below the measured background and does not represent a useful safety margin above the noise floor.

Does this service analyze or upload my audio?

No. It receives only numeric settings and performs deterministic arithmetic; it does not receive or inspect an audio file.

How do I measure the noise floor of a recording?

Pick a stretch where nobody speaks and no intended sound plays, and read its level, for example -60 dB. Ventilation, preamp hiss and hum all count. If the recording mixes rooms, measure each one or use the loudest steady background.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/audio/silence-detect-thresholds

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/audio/silence-detect-thresholds \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"noise_floor_db":-60,"margin_db":12}'
{
  "noise_floor_db": -60,
  "margin_db": 12
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "audio.silence_detect_thresholds",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

max_mb200
max_minutes180
HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.
What does an API calculation cost?

Each API request costs $0.002. The calculator can also run in the browser.

Read the full KIT documentation →