Audio Splitter runs the audio editing and conversion job locally inside your browser. 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. 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.
Internally the tool runs on standard browser APIs — the same processing stack used by professional desktop pipelines, just compiled for the browser. MP3, WAV, M4A, AAC, OGG, Opus, FLAC, AIFF, and WMA files are accepted natively. 200 MB is the practical ceiling, set so the tool stays responsive on phones and older laptops.
Most people land on Audio Splitter via a search at the moment they actually need the tool. That shapes the design: the page is a single screen with the input on one side, the controls in the middle, and the result on the other, so a first-time visitor can complete the job without reading documentation.
The architecture is local-first by design. Once the page is loaded, you can disconnect from the network and the tool still completes the job. The processing stack — standard browser APIs and the small UI shell wrapping it — ships with the page itself, so the tool keeps working in offline conditions, on a captive-portal Wi-Fi, or behind a corporate proxy that limits what the tab can reach.
The only practical limit is the 200 MB per-file ceiling, which keeps the tool responsive across a wide range of devices. Run the tool ten times in a row, run it ten thousand times — it behaves the same way and produces the same quality of result.
Audio Splitter fits naturally next to several adjacent tools. Common companions include Audio Merger, Audio Trimmer, Audio Segment Remover, and Audio Compressor — combine them when the job needs more than one transformation. After running Audio Splitter, many users move on to Audio Merger and Audio Trimmer. Each tool is a separate page so you can compose the exact pipeline you need.
Audio Splitter fits naturally into the workflow of language learners reviewing speech and voice-over artists exporting takes, both of whom typically need a fast result inside the browser. There is no learning curve to budget for: anyone who has used a typical web upload form can complete a run on the first try.
Output handling is intentionally boring: Audio Splitter produces `{name}-edited.{ext}` and triggers your browser's standard "save" behaviour. If you have a default download folder configured, that is where it will land. There is no Favtoo-side history of jobs you have run.
Audio Splitter 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.
From a product perspective, Audio Splitter is one of the simplest possible expressions of "do one thing well." The catalog contains dozens of related tools that each handle a slightly different audio editing and conversion task, and every one is a separate page rather than a tab inside a larger app. That separation keeps each tool fast to load and easy to bookmark.
If you want to get the most out of Audio Splitter, three small habits help. Drag-and-drop is faster than the file picker once you get used to it. The keyboard shortcut for downloading the result is whatever your browser uses for "save link as," because the result is a normal download. And if you are working on a sensitive file, processing in an Incognito or Private window is a good extra layer — it leaves no trace in browser history when the tab closes.
Audio Splitter fits the gap where opening a desktop app feels heavy and writing a script feels overkill. The page handles the common audio editing and conversion task with sensible defaults so a single visit usually completes the job; for highly specialised work, a dedicated desktop application can offer more knobs to turn.
If Audio Splitter appears to hang, the engine is almost certainly still working — large inputs simply take longer to process inside a browser than they would on a server with multi-core scheduling. For inputs near the 200 MB cap, give it up to a minute on a typical laptop before assuming something is stuck.
That is the whole tool. Use Audio Splitter for as long as it stays useful to you, and if it does, the catalog has many more tools built the same way. Each applies the same single-purpose discipline, so the way you used this page transfers to the next one you try.
You set the number of parts. The tool reads your file's duration, divides it equally, then runs FFmpeg with `-c copy` for each segment. The resulting files are bundled into a ZIP archive in your browser using JSZip and offered for download. Stream-copy means no quality loss and very fast processing.
Up to 50 parts. Each part is roughly equal in duration. For more granular control over individual cut points, use the Audio Trimmer tool repeatedly, or chain the splits manually.
Each part keeps the same format as the original file — split an MP3 and you get MP3 parts; split a FLAC and you get FLAC parts. This is because we use stream-copy: the container is just resealed without decoding. To change format, run the parts through Audio Converter afterward.
Up to 200MB. Splitting is very memory-efficient because FFmpeg processes each segment independently and writes it to disk before moving on. Even 3-hour audiobooks process in well under a minute.
For lossless formats (WAV, FLAC) the cuts are sample-accurate. For lossy formats (MP3, AAC, OGG) the cuts snap to the nearest keyframe, typically within 20ms. This is invisible to the ear and is the same behavior as professional tools like a desktop audio editor's "split without re-encoding."
Two reasons: it's instant (no install), and it's private (your audio never leaves the browser). Desktop audio editors are powerful but require installation and have a learning curve. For a quick split, this tool is faster end-to-end.
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.
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.
Once the page is loaded, Audio Splitter can complete jobs without an active internet connection — the engine is bundled with the page, so there is no per-job network call. The initial page load does require a connection (to fetch the static assets), but after that you can disconnect entirely and the tool will still work. This is a side-effect of the local-first architecture, not a deliberate "offline mode" feature.
Audio Splitter runs in any modern mobile browser — Safari, Chrome, Firefox and the in-app browsers in most messaging apps all support the underlying APIs. Performance depends on the device: a recent phone handles typical inputs nearly as fast as a laptop, while older devices may take a few seconds longer near the 200 MB ceiling. The interface lays out cleanly on small screens, so you do not need to pinch-zoom to see the controls.
Audio Splitter 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 Splitter 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.
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 Splitter 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 Splitter 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.
Favtoo keeps no copy of your file because Favtoo never receives your file. Audio Splitter runs entirely in your browser, the input is held only in your tab's memory, and closing the tab discards it. There is no opt-in cloud history, no "recent jobs" panel synced to an account, and no server-side retention to configure — the architecture simply has nowhere for your file to be stored.
Audio Splitter works in any modern browser released in the last few years — Chrome, Edge, Firefox, Safari, Brave, Arc and the major Chromium derivatives are all supported. The underlying engine relies on widely-supported web APIs, so there is nothing exotic to install. If you are on a very old browser version and the tool fails to load, updating to the latest release of your preferred browser is the only fix needed.
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 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.