TECHNICAL OVERVIEW

How Studio Capture works

A browser-native audio workstation designed to capture, encode and export tab audio without sending the signal to a server.

Application version—LOCAL AUDIO

01

Audio pipeline

The complete signal path stays inside the browser.
01

1 · Capture

The Screen Capture API requests a browser tab and its audio track.

02

2 · Process

Web Audio routes the signal through an AudioWorklet and analyser.

03

3 · Encode

WAV, Opus or LAME encode the captured signal locally.

04

4 · Export

The browser creates a local Blob and temporary download URL.

02

Formats and execution

Real-time behavior depends on the selected format and normalization.
FormatEngineProcessingTechnical profile
WAVPCM encoderAssembled after stop16-bit, 24-bit or IEEE 32-bit float
WEBMMediaRecorder · OpusReal time64–320 kb/s
OPUS PROlibopus 1.6.1 · WASM WorkerReal timeWebM or Ogg Opus · advanced deterministic controls
MP3LAME 3.100 · WASM WorkerReal time without normalization64–320 kb/s CBR

03

Modular architecture

A small client-side microkernel starts independent services.
KERNEL

Microkernel

Registers services and resolves dependencies.

AUDIO

AudioWorklet

Collects PCM blocks on the audio rendering thread.

ENCODER

Web Worker

Runs MP3 encoding away from the interface thread.

SERVER

Server boundary

The server provides application files but never receives captured audio.

04

Privacy and security

Audio remains device-local from capture to download.
  • No audio upload or cloud conversion
  • Explicit browser permission for every source
  • Restricted Content Security Policy
  • Temporary URLs are revoked

05

Performance and memory

Streaming path

WebM and MP3 encode during capture.

Deferred path

WAV and normalized MP3 retain PCM until stop.

Prudent memory estimate

Pro mode estimates browser headroom and recording time with large safety margins. This indication is approximate and provided without guarantee because browser and operating-system limits can be lower.

06

Browser limits