Audio Segment Remover is built for audio editing and conversion jobs that fit cleanly into a browser tab. Cut out a middle section of any audio file (e.g. an ad break, a coughing fit, or a mistake) and seamlessly join the remaining halves. Files are processed entirely in your browser with FFmpeg WebAssembly. 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.
Technically, the work is done by standard browser APIs, loaded as part of the page. Inputs in MP3, WAV, M4A, AAC, OGG, Opus, FLAC, AIFF, and WMA format are recognised automatically and validated before the engine begins processing. Files up to 200 MB are supported per run; that ceiling keeps browser memory usage stable on a wide range of devices.
Audio Segment Remover 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.
Typical users of Audio Segment Remover include students preparing oral submissions, streamers cleaning microphone tracks and sound designers prototyping cues. The thread connecting all of them is the same: a focused audio editing and conversion task that fits cleanly into a browser tab and benefits from a tool with sensible defaults and minimal setup.
Audio Segment Remover 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.
A practical note on limits: Audio Segment Remover accepts inputs up to 200 MB per run, and the tool processes one input at a time to keep memory usage predictable. If you ever bump into the ceiling, the cause is the size of the input.
Workflow tip: Audio Segment Remover pairs well with Audio Trimmer and Audio Crossfade. Other adjacent tools you may find useful are Audio Splitter and Audio Merger. Because every tool is a separate page, you can mix and match the steps that match your job. Bookmark the ones you reach for the most.
Audio Segment Remover 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.
The output handed back by Audio Segment Remover is `{name}-edited.{ext}`. 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.
Some context on why Audio Segment Remover 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 Segment Remover is built on top of that capability, which is why a single page can host the full pipeline.
If you also use a command-line tool for audio segment remover, Audio Segment Remover is a convenient alternative for the times you are on a different machine or helping someone who is not comfortable in a terminal. The output is a standard file in the format documented above.
Useful patterns when working with Audio Segment Remover: 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.
Common gotchas worth flagging: Audio Segment Remover only accepts MP3, WAV, M4A, AAC, OGG, Opus, FLAC, AIFF, and WMA, so if your file is in another format you will need to convert it first. The 200 MB ceiling is per-file, not per-session; you can run as many separate jobs as you like, but a single oversized input will be rejected on load.
Open the workspace above to start using Audio Segment Remover. 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 WebAssembly loads in your browser. Two trims are run — one from 0 to the cut start, and another from the cut end to the file end. Both are decoded to PCM and concatenated using the `concat` filter, then re-encoded. The result has the middle removed and the halves seamlessly joined.
Usually no. The concat filter aligns at sample boundaries so there is no gap. If your cut points happen to land mid-syllable or mid-note, the transition may be audible — try snapping the cut to natural pauses (between sentences, between musical phrases) for a clean join.
Removing podcast ad reads, deleting filler words and "ums" from interviews, cutting out coughs or sneezes from voice recordings, removing a controversial section from a meeting recording, and trimming long pauses out of audiobooks. Anywhere you want to shorten audio by removing one specific middle section.
Splitter divides the entire file into N equal parts. This tool removes one specific range (e.g., from 5:00 to 7:30) and keeps everything else as one continuous file. To remove multiple sections, run this tool multiple times sequentially.
For lossless formats (WAV, FLAC) the cut is sample-accurate. For lossy formats (MP3, AAC) the cuts snap to the nearest keyframe (within 20ms). Both are imperceptible in normal listening. To verify, the tool plays a preview of the join after processing.
Use Audio Trimmer instead — it's the simpler tool for cutting one end off. This Segment Remover is for cuts where both halves of the source need to remain.
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.
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 Segment Remover 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 Segment Remover 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 Segment Remover processes one input at a time by design — it keeps memory usage predictable on lower-end devices and makes results easier to verify. To handle a folder, run the tool once per file; the page stays loaded between runs and remembers your last-used settings, so the second run is essentially instant.
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.
Most jobs finish in seconds. Speed scales with input size and with how many CPU cycles your browser tab has available — the engine runs in your browser, so it shares resources with whatever else you have open. For inputs near the 200 MB ceiling, expect anywhere from a few seconds to roughly a minute on a typical laptop. Closing other heavy tabs noticeably speeds things up.
Audio Segment Remover 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 Segment Remover 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.
No installation is needed. Audio Segment Remover 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 Segment Remover on any computer you have temporary access to without leaving anything installed on it.
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.