Are these the same as the tool pages?
No. A tool page documents one feature. A workflow tells you which features to run, in which order, for a concrete result.
Step-by-step recipes that chain several Sound Booster tools into one job — prepare a podcast voice, balance an interview, make a video louder, or get a file ready to publish.
From a raw take to a publish-ready voice: trim edges, check levels, normalize, and export without uploading the file.
Open workflow →Workflow · 7 minOne speaker is loud, the other is soft. Measure both, lift the quiet side carefully, and re-check so the dialogue stays even.
Open workflow →Workflow · 7 minQuiet dialogue in a clip: boost in the browser, extract audio when you need a separate track, and check for clipping before you publish.
Open workflow →Workflow · 8 minA checklist before you upload: loudness, peaks, length, and the format the platform expects — without treating tools as isolated buttons.
Open workflow →Workflow · 6 minUse Vocal Remover as one step in a small pipeline: preview, export, then check levels before karaoke or practice use.
Open workflow →Workflow · 6 minPhone memo to something shareable: trim, find dead air, raise level carefully, and avoid boosting noise into the spotlight.
Open workflow →Tool pages explain one feature. These guides assume you will use two or three features in a fixed order. The goal is a finished outcome (a publishable voice track, a louder video bed, a cleaner memo), not a tour of every button.
LUFS, peaks and clipping are explained in the Audio Knowledge Base. Situations like quiet YouTube are covered under Sound Booster for Every Situation.
No. A tool page documents one feature. A workflow tells you which features to run, in which order, for a concrete result.
Skip steps that do not apply. If the file is already trimmed, start at measurement. If levels are fine, jump to format conversion.
The linked website tools are designed to process audio in the browser. Keep sensitive recordings on your device and use the same care you would with any local editor.
Multi-track interviews, detailed noise reduction, and sample-accurate music edits still belong in a dedicated editor. Use these recipes for fast, single-file jobs.
Use Cases start from a listening problem (“YouTube is quiet”). Workflows start from a production goal (“prepare this voice for the host”).