How to transcribe audio without uploading it
Use a tool that decodes the file and runs its speech model on the current device. Whisper Web keeps the selected media in browser memory; only the site and model files are downloaded.
Read the guideChoose where to process audio and how to export the transcript
Compare local and cloud processing, browser compute options and subtitle formats before selecting a recording.
What these pages cover
Use these guides to choose where the audio is processed, whether WebAssembly or WebGPU fits the device, and whether the next tool needs SRT or VTT. Each guide includes the limits that affect that choice.
Local vs cloud transcription: choose based on the data path
Choose local transcription when avoiding a media upload is the first requirement and the file fits your device and browser limits. Choose a cloud workflow when long files, centralized collaboration or provider-managed compute matter more than keeping the recording on one device.
Read the guideWebGPU vs WebAssembly for local Whisper transcription
Start with WebAssembly when you want the broadest browser compatibility. Try WebGPU on a supported desktop browser and GPU when local processing is too slow, then switch back if model loading or inference fails.
Read the guideSRT vs VTT: choose the subtitle file your destination expects
Export SRT when a video editor or upload form asks for SRT or when broad subtitle compatibility is the priority. Export VTT for HTML video and web players that expect WebVTT. Always review the text and timing in the destination player.
Read the guideTranscribe on this device
Choose a file