Guide
Audio Lab FAQ
These answers cover the practical questions people usually have before editing audio in the browser: what happens to files, which formats work, why export options differ, and how each tool behaves.
Using the editor
Audio Lab is organized around separate tools rather than a complex multitrack project. Choose Trim Audio, Change Volume, Change Speed, or Reverse Audio, then load a file for that tool. Keeping workspaces separate avoids surprises: changing speed in one tool does not accidentally affect a file you loaded in the trim tool.
The editor is best for focused one-step jobs. If you need chained processing, export the result of one tool and load that exported file into another. This adds an extra step, but it keeps each operation clear and makes the final download easier to understand.
File privacy
The audio editing workflow is designed to happen locally in your browser. Your selected audio file is decoded and processed in the browser session for preview and export. Audio Lab is not designed around uploading source files to a server-side processing queue.
Website activity can still include normal network requests, such as loading the app itself, analytics if enabled, or advertising scripts on eligible editorial pages if enabled. See the browser privacy guide and Privacy Policy for more detail.
Formats and exports
Input support comes from the browser. If your browser can decode the file, Audio Lab can usually work with it. WAV, MP3, M4A, OGG, FLAC, and WebM are common, but support differs by browser and operating system.
WAV and AIFF are reliable export choices for editing quality. Compressed export options appear only when the browser exposes a compatible encoder. MP3 export is not currently built into Audio Lab.
Troubleshooting common issues
If the waveform does not appear, try a smaller file, a different browser, or a WAV copy of the source. Very large files require more memory because the browser has to decode audio before drawing and processing it.
If playback works but export fails, try WAV first. Compressed exports depend on browser encoders, while WAV export is handled directly by the app. If a speed preview is slow, wait for processing to finish before clicking export again.
FAQ
Frequently asked questions
Do I need an account?
No. Audio Lab can be used without signing in or creating a project account.
Does Audio Lab upload my audio file?
The editor is designed to process selected audio locally in the browser for preview and export.
Why does my file fail to open?
The browser may not support that codec, the file may be damaged, or the file may be too large for the available memory.
Can I combine multiple tools at once?
Not in a single chain. Export from one tool, then load the exported file into another tool if you need a second operation.
Does the speed tool preserve pitch?
Yes. It is designed for pitch-preserving tempo changes rather than simple playback-rate changes.
Why are some export formats missing?
Compressed export depends on browser MediaRecorder support. Not every browser exposes the same encoders.
Can I use Audio Lab on mobile?
The site is responsive, but large files and long processing tasks work better on devices with more memory and CPU headroom.
Where should I start?
Open the tool that matches the result you need, or start with the guide index if you want help choosing settings.
Why does Audio Lab keep tools separate?
Separate workspaces make each operation predictable. A trim setting will not silently affect a speed edit, and each tool can hold its own file.
Should I keep my original file?
Yes. Always keep the original recording. Audio Lab exports edited copies and does not replace your source file.