Written by Jackson Cooper | Last updated: June 2026
Who Writes the Content on This Site
All content published on SoundLatencyTest.com is written by Jackson Cooper, audio systems engineer and web audio latency researcher, and founder of this site. There are no guest contributors, no outsourced writers, and no AI-generated articles published without full review, fact-checking, and rewriting by Jackson personally.
Every page — whether a technical explanation, a tool guide, an FAQ answer, or a legal disclosure — is the direct product of Jackson’s research into browser audio architecture, operating system audio pipelines, and the practical measurement of audio latency for musicians, engineers, and developers.
Editorial Standard
The single test every piece of content on this site must pass before publication:
Would a professional audio engineer, DAW user, or web audio developer reading this page find it technically accurate, practically useful, and honest about its limitations — or would they find something missing, vague, or wrong?
If the answer is anything other than “technically accurate, practically useful, and honest,” the content is not ready to publish. This standard applies equally to a 200-word FAQ answer and a 1,800-word technical explainer. Filler language, vague generalisations, and unsupported accuracy claims are not acceptable on any page of this site.
How Tool Pages Are Written
The tool page for the Sound Latency Test is written to document three things with equal rigour:
1. What the tool measures and how Every tool page names the specific Web Audio API methods, signal processing steps, and mathematical operations involved. The measurement pipeline — AudioContext creation, tone burst generation via OscillatorNode, microphone capture via MediaStream, cross-correlation analysis, and latency calculation in milliseconds — is documented in full on the How It Works page. The tool page itself summarises this pipeline in user-facing language without sacrificing technical accuracy.
2. What the result means A latency figure in milliseconds is only useful if the reader understands what range is normal for their hardware type, what threshold matters for their use case, and what variables might cause their result to differ from another user’s result on the same tool. Every result explanation on this site includes this contextual layer.
3. What the tool cannot determine No browser-based latency measurement tool can isolate hardware-only latency from software latency, cannot measure one-way latency (output or input separately), and cannot account for hardware-level zero-latency monitoring that bypasses the software stack entirely. These limitations are stated explicitly on every relevant page — not buried in footnotes, but presented as a normal and important part of understanding the measurement. See the FAQ for the most common questions about result interpretation and tool limitations.
How Technical Articles Are Researched
Browser and Web Audio API Content Articles covering Web Audio API behaviour, AudioContext latency properties, and browser-specific audio scheduling are researched against the W3C Web Audio API specification, MDN Web Docs, and browser DevTools documentation. Where browser behaviour differs from the specification or differs between browsers, this is documented and attributed. Claims about specific latency values are cross-referenced against measured figures, not taken from secondary sources.
Operating System and Driver Content Articles covering Windows (WASAPI, WDM, ASIO), macOS (Core Audio), and Linux (ALSA, PipeWire) audio pipelines are researched against official platform documentation and verified against real-world measurement ranges. Driver architecture explanations distinguish between what is documented in platform specifications and what is observed in practice.
Hardware and Interface Content Articles covering audio interface latency, Bluetooth codec overhead, and consumer versus professional hardware are based on published specifications from hardware manufacturers, codec technical documentation (SBC, AAC, aptX, LDAC), and independent measurement data from the audio engineering community. Where specific latency ranges are cited (e.g. Bluetooth adds 40–200 ms of round-trip overhead), the source basis for that range is traceable to published technical documentation.
AI Content Policy
Jackson uses AI writing tools as a research aid and first-draft accelerator. No AI-generated content is published on this site without the following process:
- Fact-check every technical claim — any claim about a specific algorithm, API method, formula, latency value, or hardware behaviour is verified against the primary source before it appears on the page
- Rewrite for accuracy and voice — AI drafts are rewritten to reflect Jackson’s technical knowledge and the specific accuracy standards this site maintains; vague or hedged language is replaced with precise, verifiable statements
- Add site-specific context — generic explanations are replaced with examples and figures relevant to the specific tool and audience of SoundLatencyTest.com
- Final review before publication — every page is read in full by Jackson before it goes live
AI is a tool for efficiency, not a substitute for expertise. The expertise behind every published page is Jackson’s.
Corrections Policy
If a technical error is identified on any page of this site — an incorrect formula, a misattributed API property, an outdated browser behaviour, or an inaccurate latency range — it will be corrected as a priority. Corrections are made to the live page, and the “Last updated” date is revised. Significant corrections are noted at the top of the relevant page.
To report a correction, use the Contact page with the subject line “Content Correction” and the specific page URL and error. Jackson reviews all correction submissions personally. Response time for content correction reports: 48–72 hours.
What This Site Does Not Publish
- Content that implies browser-based latency measurement is equivalent to certified professional acoustic measurement
- Latency benchmarks presented without disclosure of the hardware and software environment in which they were measured
- Tool comparison claims that cannot be verified independently
- Health, medical, or hearing safety advice — for hearing protection guidance, consult a qualified audiologist
- Link exchange requests, sponsored content, or paid product placements of any kind
- Content written by contributors who have not verified their claims against primary technical sources
Related Pages
- About SoundLatencyTest.com — what this site is, who runs it, and who it is for
- How It Works — full technical documentation of the latency measurement pipeline
- Data Security — how microphone audio is handled and why it never leaves your device
- Contact — to report errors, ask technical questions, or submit data requests
These guidelines were written by Jackson Cooper and apply to all content published on SoundLatencyTest.com. Last updated: June 2026.