SpeechRecognition­Result.audio­EndTime

syntax

readonly attribute DOMHighResTimeStamp? audioEndTime;

Proposed spec text (PR #192, quoted verbatim): “A nullable DOMHighResTimeStamp representing the end of the audio segment corresponding to this recognition result, in milliseconds relative to the time origin. Returns null if the underlying recognition engine does not support audio segment end timestamps.”

The shipping Chromium IDL gates the same member on the runtime feature (speech_recognition_result.idl):

[RuntimeEnabled=WebSpeechTimestamps] readonly attribute DOMHighResTimeStamp? audioEndTime;

value

inputs

None. This is a read-only attribute: no setter, no parameters, no options. What the engine supplies is what the getter returns (after quantization); script cannot influence the value other than by choosing a recognition engine/backend that supports segment timestamps.

errors

No error surface. The getter never throws: unsupported engines yield null, not an exception. Reading the attribute on a browser without the runtime flag fails earlier — the member does not exist on the prototype at all — so feature-detection ('audioEndTime' in SpeechRecognitionResult.prototype) is the correct guard, not try/catch.

context and exposure

• Exposed on every SpeechRecognitionResult — the objects in SpeechRecognitionEvent.results delivered to result event handlers — when the WebSpeechTimestamps runtime feature is enabled.
• The host Web Speech API requires a secure context and microphone permission (or a MediaStreamTrack source); these attributes add no new requirements of their own.
• Both interim (isFinal === false) and final results can carry the value: Chromium's aggregation path constructs provisional and final results from the same engine struct (speech_recognition.cc). Latency monitoring therefore works on interim hypotheses, not only on final segments.

lifecycle

1. The recognition engine emits a result with timing information (TimingInformation.audio_end_time in the mojom struct).
2. Blink stores it on the result object at construction (SpeechRecognitionResult::Create).
3. Each getter call returns the stored value floored to 2 ms, or null if unset. The value for a given result object does not change afterwards.
4. Because Event.timeStamp is captured when the result event is created, the latency figure event.timeStamp - result.audioEndTime is most accurate when read promptly inside the handler; heavy handler work before reading it inflates the apparent lag.

examples

recognition.onresult = (event) => {
  const result = event.results[event.resultIndex];
  if (result.audioEndTime === null) return;  // engine without segment timing

  const lagMs = event.timeStamp - result.audioEndTime;
  latencySamples.push(lagMs);

  // Sustained lag over a sliding window → fail over to the cloud backend.
  if (median(latencySamples.slice(-20)) > 1500) {
    switchToCloudBackend();
  }
};

browser compatibility

Interim table. No BCD key exists for this member (verified 2026-07-29); rows compiled from primary sources.

security and privacy

• High-precision timing is a hardware-fingerprinting vector; the spec PR requires fuzzing/precision reduction before script exposure (“e.g. by rounding to 2ms precision”) and Chromium floors values to 2 ms multiples in the getter — so derived latency figures are likewise 2 ms-quantized.
• The attribute reveals nothing beyond timing metadata about audio the page already submitted for recognition under the existing permission model — no new audio, device, or engine access. Engine load is indirectly observable through latency trends; the 2 ms floor plus event-delivery noise keeps that signal coarse.
• A null result distinguishes “engine cannot time segments” from “segment ends at 0”, preventing fabricated-zero latency misreads (a null guard must precede any subtraction — event.timeStamp - null would silently compute a bogus value).

see also

• SpeechRecognitionResult Timestamps — overview (feature page, incl. the latency walkthrough)
• audioStartTime — the segment start
• Chrome Platform Status — feature 5811907077472256
• MDN — Event.timeStamp (the latency formula's other operand)
• Showcase — latency monitor demo (HEAD-checked 200, 2026-07-29)