Audio Recorder runs the audio editing and conversion job locally inside your browser. Record from your microphone directly in the browser. Pick quality (high, medium, low), toggle echo cancellation, noise suppression and auto-gain, then save to WebM/Opus or M4A/AAC. Audio is captured locally — nothing is uploaded. The work happens on your machine, the result is generated on your machine, and the page exposes the controls you need to drive it without burying them in menus.
The right moment to reach for Audio Recorder is when you have a focused audio editing and conversion job that fits inside a browser tab. Open the page, drop in the file or paste your input, choose the options that matter, and the tool returns the result.
The execution path is auditable from the page itself: open developer tools, switch to the Network tab, run a job. The requests you see are static-asset GETs for the engine and the page resources. The actual work is JavaScript code running against the bytes already in your tab's memory.
Audio Recorder is implemented on top of standard browser APIs. Inputs are read from the file picker or drop zone, decoded in the browser, processed, and re-encoded into the output format. Files up to 0 MB are well within the comfort zone of any modern browser.
The hard constraints are easy to remember. Maximum input: 0 MB. Multiple files per run: no — one input at a time, by design, to keep results predictable. The same controls apply on every run.
If you fit any of these descriptions, Audio Recorder should slot cleanly into your workflow: streamers cleaning microphone tracks; podcasters preparing episodes; sound designers prototyping cues. The tool keeps the controls focused on what matters for each of these use cases.
The output handed back by Audio Recorder is the output file. If you would prefer to keep the result in the browser instead of downloading it, you can copy it from the result panel and paste it directly into another tab — useful when the next tool in your workflow expects pasted text rather than a file.
Audio Recorder fits naturally next to several adjacent tools. Common companions include Text to Speech, Tone Generator, Add Audio to Video, and Silence Generator — combine them when the job needs more than one transformation. After running Audio Recorder, many users move on to Add Audio to Video and Replace Video Audio. Each tool is a separate page so you can compose the exact pipeline you need.
Audio Recorder keeps the control set focused. Every option on the page is there because a real workflow needs it, and the defaults aim at the most common case so a first-time user can get the right output without changing any settings.
Some background on the design choices behind Audio Recorder: every option you see on the page is there because a real workflow needs it, and every option that is not shown has been deliberately omitted to keep the common case fast. The bias is toward minimal-but-complete.
Audio Recorder produces deterministic output: the same input plus the same options always produces the same result. That predictability matters when the result has to match an upstream specification or be reproducible later.
Useful patterns when working with Audio Recorder: keep the input file open in another tab so you can compare against the result; give the output file a descriptive name when saving so you can find it later (the default name is sensible but generic); and treat each run as independent — the tool has no concept of "history", which means you cannot accidentally pollute one job with leftovers from another.
For most failure modes, refreshing the page and re-running the job is enough — the engine has no persistent state to corrupt. If the same input fails twice in a row, the input itself is most likely the problem (a truncated file, an unexpected variant of the format, or a stream the engine does not recognise).
Audio Recorder is one of many single-purpose tools in the catalog. Each is built around the same single-page model. Use this one, close the tab, and come back the next time you need the same job done. None of the tools require prior knowledge of the others — each page is self-contained.
The tool calls the browser's MediaRecorder API after asking your permission to use the microphone. Audio is captured into RAM in the format your browser supports best (WebM/Opus on Chrome and Firefox, M4A/AAC on Safari) and offered as a direct download when you stop. Nothing is uploaded — the file lives only in this tab.
No. The recording exists only in the browser tab's memory while you are recording. The moment you close the tab or refresh, it's erased. Unlike SaaS recorders we do not write to a server, an analytics pipeline, or a third party.
High (256 kbps, broadcast-grade), Medium (128 kbps, the YouTube/Spotify default), and Low (64 kbps, voice-memo grade for tiny files). All three are compressed using your browser's native encoder.
These are browser-level filters built into the WebRTC audio pipeline. Noise suppression removes steady background hiss (fans, AC). Echo cancellation removes the speaker output from your mic capture — essential when recording while playing reference audio. Auto Gain Control evens out level differences between loud and quiet talkers.
Safari does not support WebM recording — it uses MP4 (M4A audio) as its native container with the AAC codec. Both are universally supported, so the file plays everywhere; only the extension differs. We pick whichever your browser supports automatically.
Yes — recordings run as long as the tab is open and you have enough RAM. A typical compressed recording uses 1MB per minute at medium quality, so 60 minutes is about 60MB. For multi-hour recordings consider stopping and saving in chunks.
Server-side tools use multi-threaded native FFmpeg running on dedicated CPUs with fast disks and parallel pipelines. Our engine is FFmpeg compiled to WebAssembly, which runs single-threaded inside your browser tab and has no access to native hardware acceleration. That makes browser-based jobs typically 3–8× slower than a server. The trade-off is total privacy: your audio file is never uploaded, never logged, and never stored — closing the tab erases everything from memory immediately. For most clips up to a few minutes the wait is small, and for sensitive recordings (voice memos, drafts, confidential meetings) the privacy gain is well worth it.
No. Everything runs entirely inside your browser tab using FFmpeg compiled to WebAssembly. The file is read into local memory only, processed in the same tab, and the result is offered as a direct download. Nothing is transmitted to any server, no account is required, no analytics are tied to your file, and closing the tab discards every byte from memory.
The file picker accepts audio inputs up to about 1 GB, which is well above what mainstream "free tier" online converters allow. The real ceiling is your device — everything runs inside your browser tab, which shares memory with the rest of the page. Most podcasts, songs, and voice memos sit comfortably under that limit even on a phone. If a very large lossless WAV or FLAC ever fails, trim it first or transcode to MP3 / Opus to bring the size down before re-running the tool.
MP3, WAV, OGG (Vorbis and Opus), FLAC, M4A (AAC), AAC, Opus, AIFF, and WMA all decode reliably via FFmpeg WASM. Output formats depend on the specific tool — most editing tools default to MP3 (universal) or WAV (lossless) but expose a format picker so you can pick the one that fits your downstream player or DAW.
Recent Chrome, Edge, Firefox, Safari, and other Chromium-based browsers all work. The tool relies on WebAssembly and SharedArrayBuffer, which require the page to be served over HTTPS with the right cross-origin headers — this site is configured correctly by default. On phones the same code runs but is slower than on a desktop because mobile CPUs are weaker.
No. The tool is completely free, requires no account, attaches no watermark, applies no usage caps, and shows no popup ads on your output. Because the work happens on your own device, there is no per-user quota for us to enforce — your hardware and browser memory are the only limits. The download is the file you would get from running FFmpeg locally, nothing more, nothing less.
No installation is needed. Audio Recorder runs as a normal web page, with no browser extension, no native helper, and no separate desktop client to download. That is partly a privacy choice — extensions can request broad permissions, while a regular page is sandboxed by default — and partly a convenience one: you can use Audio Recorder on any computer you have temporary access to without leaving anything installed on it.
Audio Recorder uses native HTML controls wherever possible, which means keyboard navigation, focus rings, and screen-reader labels work the way the platform expects. The drop zone accepts files via the keyboard-accessible file picker as well as drag-and-drop, and result downloads use standard browser download flows. If you spot an accessibility gap, Favtoo treats it as a bug worth fixing.
Audio Recorder is a browser-only tool by design and does not expose a hosted API. The reason is the same as the privacy story: there is no Favtoo backend doing the work, so there is no service to call. If you need to script the same transformation, the underlying engine (standard browser APIs) is open-source and can be used directly from your own code.
Desktop apps usually have more advanced features but require installation, maintenance and (often) a licence. Paid online tools are convenient but route your file through their servers and gate downloads behind accounts. Audio Recorder sits in between: free, instant, and private, but intentionally narrow in scope. For one-off jobs and the common audio editing and conversion operations, it is usually the lowest-friction choice; for highly specialised work, a dedicated app is still the right answer.
Audio Recorder is built on standard browser APIs, which is the same class of engine used by professional audio editing and conversion pipelines. For deterministic operations, the output is byte-identical to what an equivalent CLI run would produce; for operations involving a codec or a model, the result is well within the range of what comparable tools generate. If you have a specific reference output you need to match, run a small test job first to confirm the configuration produces what you expect.
Your file is processed inside your browser by standard browser APIs. The engine reads the file's bytes from your tab's memory, computes the result, and writes the result back into the tab. You can confirm what the page does by opening developer tools and watching the Network tab during a run — the requests you see are for the tool's static assets only.
Audio Recorder can be used for personal and commercial work alike — there is no separate "business" licence to purchase. The output you generate is yours to use however you want, including in client deliverables, internal documents, or commercial products. Favtoo's only ask is fair, individual use; the tool is not designed to be embedded as a backend service or wrapped behind an API for resale.
Text to Speech
Type or paste text, pick a system voice, and listen instantly. Adjust speaking rate (0.5×–2×), pitch, and volume in real time. Uses your browser's built-in Web Speech API — no cloud TTS, no API keys, no costs.
Tone Generator
Generate a pure tone at any frequency from 20 Hz to 20 kHz. Pick a sine, square, triangle, or sawtooth waveform, choose duration, amplitude, and mono/stereo. Exports a 16-bit PCM WAV file at 44.1 kHz with built-in click-preventing fades.
Silence Generator
Generate a perfectly silent WAV file of any length from 1 second up to 1 hour. Pick mono or stereo, get a 16-bit PCM WAV at 44.1 kHz. Useful as padding between clips, intro silence, leader audio for video timing, or test material.
White Noise Generator
Generate white, pink, or brown noise as a 16-bit PCM WAV file. Pick noise type, duration up to 1 hour, amplitude, and mono/stereo. Useful for sleep, focus, masking distractions, audio testing, and as a backing layer for ambient music.
Metronome
A precise browser-based metronome powered by the Web Audio API. Set BPM from 30 to 300, choose a time signature, accent the first beat, and use tap-tempo to sync. Click timing is sample-accurate using lookahead scheduling — much steadier than typical JavaScript setInterval beats.
Audio Trimmer
Trim any audio file to a precise start and end time. Outputs a lossless stream-copy by default (no quality loss, very fast) or re-encodes to MP3, WAV, OGG, or M4A. Files are processed entirely in your browser with FFmpeg WebAssembly.
Audio Splitter
Split a long audio file into N equal-length parts and download them as a ZIP. Each part is named sequentially. Great for chapterizing audiobooks, podcasts, or long DJ mixes. Runs entirely in your browser with FFmpeg WebAssembly.
Audio Merger
Merge up to 12 audio files into one continuous track. Supports MP3, WAV, OGG, M4A, AAC, FLAC, Opus, AIFF and more. Optional loudness normalization to even out clip levels. Files are processed entirely in your browser with FFmpeg WebAssembly.