Audio Loop is the kind of utility you bookmark and reach for when you need it. Loop any audio file 2 to 50 times into a longer continuous file. Great for extending short ambient tracks, creating long versions of jingles, or producing background loops for videos. Files are processed entirely in your browser with FFmpeg WebAssembly. It loads quickly, works on any modern browser, and produces a result you can download or copy in a single click.
Reach for Audio Loop when you need a predictable result on a single file. The page works on the first visit, the controls are visible without a menu, and the output is delivered the moment the engine finishes.
Audio Loop runs the entire transformation inside your browser. The file is read by JavaScript running in the page, processed in-memory by standard browser APIs, and written back as a download. The browser is the runtime; the page is the interface. You can confirm what the tool does by opening the developer-tools Network tab during a run — the only requests are for the page's own static assets.
From a technical standpoint, Audio Loop is JavaScript and standard browser APIs running in your tab. The browser is the runtime; the page is the interface. Inputs accepted: MP3, WAV, M4A, AAC, OGG, Opus, FLAC, AIFF, and WMA. Maximum input size: 200 MB per run.
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.
If you fit any of these descriptions, Audio Loop should slot cleanly into your workflow: language learners reviewing speech; teachers recording lessons; sound designers prototyping cues. The tool keeps the controls focused on what matters for each of these use cases.
Audio Loop returns the result as `{name}-edited.{ext}`. If you are running multiple jobs, the output names will not collide as long as the input names differ. You can re-run with different settings as many times as you like; each run produces a fresh file with no caching trickery in between.
Audio Loop sits in a small group of related tools. Useful neighbours include Metronome, Audio Clip Maker, Audio Crossfade, and Audio Trimmer. They are designed to compose: the output of one is a sensible input to the next, so a multi-step task is usually a sequence of single-click operations.
Audio Loop 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 context on why Audio Loop 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 Loop is built on top of that capability, which is why a single page can host the full pipeline.
As a single-page tool, Audio Loop stays focused on one audio editing and conversion step. Multi-step workflows are composed by chaining adjacent tools — each tool produces a standard file the next one can read directly, so a longer pipeline is just a sequence of short tab-and-tab visits.
Useful patterns when working with Audio Loop: 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).
Open the workspace above to start using Audio Loop. 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.
A WebAssembly build of FFmpeg loads in the page and uses the `-stream_loop` flag to repeat your input file the chosen number of times. The looped output is then re-encoded to your target format. Because we are not decoding and re-encoding the same audio multiple times, this is much faster than a manual concat.
50 repeats. A 1-minute song looped 50 times produces a 50-minute file. The total output duration is limited mostly by file size — at 320 kbps MP3, 50 minutes is about 120MB.
Maybe — if the audio does not start and end at zero crossings, you'll hear a small click each time it restarts. To make seamless loops, trim your source so the start and end waveforms match (or apply a brief fade with the Audio Fade tool first). Many "loop ready" sound effects are designed this way.
Trim the section you want with Audio Trimmer first, then run that trimmed file through this loop tool. This two-step workflow gives you looped sections of any length from any source.
Up to 200MB. Be aware the output is many times larger than the input (50× looping makes the output 50× the input size). If you exceed the browser's memory budget, try a higher MP3 compression or a shorter loop count.
Background music for videos and live streams, sleep aids (loop a 1-hour track to play all night), meditation backings, ambient soundscapes for game maps, on-hold music files, and extending royalty-free music to fit longer projects.
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 Loop 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.
Audio Loop 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.
Audio Loop only needs the standard web platform — file picker access for the inputs you choose to load, and optionally clipboard access if you copy the result rather than downloading it. There is no microphone, camera, geolocation or background-permission request, because none of those are needed for the work the tool does.
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 Loop 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 Loop 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 Loop is a static page running an open-source engine in your browser, so a typical corporate firewall does not get in the way as long as it allows JavaScript to load from Favtoo. For teams that need to host it themselves on an internal network, the underlying engine (standard browser APIs) is open-source and can be packaged into a private build with the same behaviour. Reach out via the Contact page if that is something you are exploring.
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
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.