Audio Fade is built for audio editing and conversion jobs that fit cleanly into a browser tab. Apply a smooth fade-in to the start and/or fade-out to the end of any audio file. Pick the fade duration in seconds. Perfect for polishing intros and outros, smoothing over hard cuts, and creating gentle transitions for podcasts and music. The processing runs in the page itself, which is why the controls update instantly when you change settings and why a freshly loaded page is ready to do real work the moment it becomes interactive.
If you fit any of these descriptions, Audio Fade should slot cleanly into your workflow: sound designers prototyping cues; podcasters preparing episodes; musicians sharing demos. The tool keeps the controls focused on what matters for each of these use cases.
Audio Fade performs the transformation entirely inside the JavaScript runtime. Your file lives in the tab's memory while the engine works on it; the result lives in the tab's memory until the browser triggers the download. Both are released when the tab closes, the way every browser tab releases its memory.
Behind the controls you see, standard browser APIs is doing the actual audio editing and conversion. MP3, WAV, M4A, AAC, OGG, Opus, FLAC, AIFF, and WMA are first-class formats and the engine produces a deterministic output for any given input + options combination — useful when you need to re-run a job and expect identical results.
Audio Fade is shaped for the gap between "I'll do it by hand" and "I'll script it." When the job is small enough that automating it would take longer than doing it, but annoying enough to want a focused tool — that is the situation this page is built for.
Even on its own, Audio Fade composes well with the rest of your toolkit. The output is a standard MP3 file that opens in any program that handles the format, so the result of one run can become the input to whatever step you use next.
The download is delivered as `{name}-edited.{ext}` the moment processing completes — no email link, no "your result will be ready in 5 minutes" queue, no expiry timer. The file is generated in your browser and saved by your browser's normal download flow.
Constraints worth knowing about: inputs are capped at 200 MB to keep memory usage in a sensible range, one input is processed per run, and the tool must be loaded over HTTPS for the in-browser engine to work. These are properties of the architecture.
Audio Fade is built around steady iteration on a small set of options rather than feature creep. Every additional setting attracts a slightly different audience, but a long settings panel makes the common case slower for everyone. The current controls reflect what users of the tool actually use.
Some context on why Audio Fade exists in this form: modern File APIs, high-performance JavaScript engines, and well-maintained open-source libraries now make it possible to perform audio editing and conversion work entirely in the browser. Audio Fade is built on top of that capability, which is why a single page can host the full pipeline.
A few practical tips that experienced users of Audio Fade pick up over time. First, keep your default browser updated — the engine relies on standard web APIs and newer browser versions are noticeably faster than ones from a few years ago. Second, close other heavy tabs before processing a large input; the engine shares CPU and memory with whatever else is open. Third, if you re-run the same kind of job often, your last-used settings are remembered for the rest of the tab session, so subsequent runs are essentially one click.
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 Fade 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.
Open the workspace above to start using Audio Fade. The engine loads on the first interaction so the page itself stays light, and once the tool is warm it processes subsequent jobs quickly. The moment the page is interactive, the tool is ready to do real work on your file.
FFmpeg's `afade` filter applies a linear amplitude ramp at the start (silence → full volume) and/or end (full volume → silence) of your file. The fade duration in seconds is configurable independently for in and out. The result is re-encoded to your target format.
For songs and music: 2–6 seconds is typical for a polished outro. For podcasts: 0.5–1.5 seconds is enough to soften an intro. For sound effects: 50–200ms removes clicks. Setting either to 0 disables that side of the fade.
That's the fade-in working — the audio is fading up from silence over the duration you specified. If you don't want a fade-in, set its duration to 0. Many people only want the fade-out for songs.
This tool applies a linear amplitude fade. For most uses linear is perceptually fine. True equal-power crossfades are used in the Audio Crossfade tool where two sources overlap and you need constant total energy. Linear fades to/from silence sound natural.
Up to 200MB. The fade itself is fast — most of the time is the file decode and re-encode. Lossless formats process faster than lossy because the encoder is lighter.
Not with this tool — afade only fades at the start or end. For ducking music under voiceover or other middle-of-file fades, use a desktop DAW or our future audio editor tool.
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.
Audio Fade is updated whenever the underlying engine releases an improvement or a bug fix. Because the tool is delivered as a static page, every visit fetches the latest version automatically — there is no "version" to manage on your end. If a particular release ever changes default behaviour, the change is documented on Favtoo's changelog so you can confirm what shifted.
Audio Fade 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.
Audio Fade accepts MP3, WAV, M4A, AAC, OGG, Opus, FLAC, AIFF, and WMA. If your input is in a format that is not directly supported, convert it first using one of Favtoo's converter tools — every Favtoo converter outputs a file that is a clean input to the next tool in the chain.
Audio Fade is built to preserve quality wherever the underlying audio format allows it. Operations that are mathematically lossless (e.g. structural transformations, lossless re-encoding) round-trip with no perceptible change. Operations that involve a lossy codec inevitably introduce small artefacts at the byte level, but the defaults aim at the sweet spot where output looks or sounds the same to a normal viewer or listener while still being meaningfully smaller or faster than the input.
Audio Fade is free to use. The processing runs in your browser, which keeps the per-user cost low enough that the tool can be offered openly. The download is the same file the engine produced — you can use it for as many runs as you need.
Failures usually fall into one of three buckets: the input is in an unsupported format, the input is over the size cap, or the input is structurally malformed (a truncated download, a partial export, or a stream the engine does not recognise). The first two are easy to confirm — check that your file is one of MP3, WAV, M4A, AAC, OGG, Opus, FLAC, AIFF, and WMA and that it is below 200 MB. For the third, opening the file in its native viewer first is the fastest way to confirm the source is intact.
Audio Fade 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.
Audio Recorder
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.
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.