No. Processing happens locally in the browser using the Web Audio API.
WAV, MP3, M4A, and OGG containers. Other formats may fail to decode depending on browser codec support.
We do not store your audio, and there is no account or contact form data kept on a server. The site does use analytics and advertising cookies served through Google, which set identifiers in your browser. See the Privacy Policy for the full detail, including how to opt out of personalised ads.
Yes, provided you hold rights to the original audio and usage does not infringe third-party rights.
Stadium systems intentionally limit certain frequency ranges; adjust High Cut / Low Cut sliders for a fuller spectrum.
Seven ship today: Ballpark, Arena, Vintage, Modern, Classic, Outdoor, and Megaphone. Every slider stays adjustable after you pick one, so a preset is a starting point rather than a fixed sound. More may be added over time.
Both WAV and MP3 downloads are offered once your audio has been processed. The MP3 encoder is loaded on demand the first time you ask for one, so it never weighs down the initial page load; expect a brief pause on that first MP3 export.
There is no hard limit. Because every step runs in your browser, longer files simply consume more memory, and a very long clip may be slow or fail on a low-memory device. Short announcement-length clips are what the tool is tuned for.
Yes, after your first visit. A service worker caches the whole tool, not just a shell, so you can return with no connection and still process audio. Ads and analytics simply do not load while you are offline.