SoundSlicr FAQ

SoundSlicr is designed around browser-first processing. In the current version, working tool pages use browser APIs and FFmpeg WASM where needed instead of an intentional backend upload step for audio processing. There are no accounts, billing screens, saved cloud projects, or user libraries.

You should still use judgment with private files. Browser-first does not make every device private. Avoid editing sensitive recordings on shared computers, keep originals in a safe place, and do not send private audio through the contact path unless specifically requested.

The current file size limit is 100MB. Common inputs include MP3, WAV, M4A, AAC, OGG, WebM, and FLAC where browser and FFmpeg WASM support are available. Video extraction workflows focus on MP4, MOV, M4V, WebM, and similar containers when the audio stream can be decoded.

Downloads are created by your browser. If a download does not appear, check download permissions, popup/download blocking, browser storage settings, and whether the file finished processing. Keep the source file until you have verified the result in the destination app or platform.

Use /audio-trimmer for general trimming, /mp3-cutter for MP3 cuts, /audio-converter for broad format conversion, /merge-audio for joining clips, /voice-recorder for microphone capture, and /extract-audio-from-video for video sources. Spoken-word workflows often use /silence-remover, /audio-normalizer, and /audio-compressor after timing edits are finished.

A reliable order is extract first if the source is video, trim before converting when you only need a shorter section, normalize after timing is correct, and merge only after each clip has been prepared. This reduces processing time and makes mistakes easier to find.

SoundSlicr can be used on modern browsers, but behavior varies across Chrome, Edge, Safari, Firefox, iOS, Android, and desktop systems. Mobile browsers may have tighter memory limits and stricter download behavior. Long files that work on a desktop may fail on a phone.

The site includes a web app manifest so supported browsers may offer install behavior. Installing the web app does not create a cloud account or offline guarantee for every tool. Media processing still depends on browser support, local memory, and the selected file.

Only process audio and video you own, created, licensed, or otherwise have permission to use. SoundSlicr makes file handling more convenient, but it does not change copyright, workplace, classroom, platform, or privacy obligations.

If a file fails, try a shorter clip, a more common export, another modern browser, or a desktop editor. If you contact support through /contact, include the route, browser, device, approximate file size, format, duration, and the exact error message. Do not send private files unless asked.

SoundSlicr does not currently transcribe audio to text, generate captions, host podcasts, save cloud projects, run billing, or provide user accounts. Searches for audio to text converter, podcast hosting, AI mastering, or collaboration features should be handled by products built for those tasks. SoundSlicr focuses on downloadable file utilities.

That boundary keeps the site easier to evaluate. If you need an online audio editor for a quick MP3 edit, trim, conversion, merge, recording, or level adjustment, a focused route may be enough. If you need a production timeline, multiple tracks, detailed repair, or exact delivery standards, a desktop editor remains the safer option.

Use clean source files when possible. Record in a quiet room, keep microphones close enough for clear speech, avoid clipping, and export standard formats from recording apps. Browser tools can help with timing and simple loudness, but they cannot fully repair audio that was captured poorly.

Work in copies and name each export clearly. For example, keep interview-original.wav, create interview-trimmed.mp3, then create interview-normalized.mp3. Clear names make it easy to return to the previous step if a later result is too compressed, too quiet, too loud, or cut too tightly.