Clean up messy lyrics text

No. The whole tool is a JavaScript function running in your browser — there is no request to our servers, no account, and no limit on how much text you run through it.

Word order, capitalisation and ordinary punctuation are all preserved. The one exception is brackets: the bracket rule removes each bracketed span and its contents, so backing vocals written as '(oh, oh)' go with it. Switch that rule off if your lyrics use parentheses for words you want to keep.

Not by default — the 'Drop blank lines' rule is on, which is what most people want before importing into an LRC editor. Turn it off and your verse spacing is preserved, with only leading and trailing blank lines trimmed.

No, and it never will. Removing '(x2)' is markup cleanup; deleting a repeated line is deleting lyric content. If you want the chorus four times, paste it four times — the tool will not collapse it.

Text copied from lyrics sites routinely carries non-breaking and zero-width spaces that look identical to normal spaces. They defeat the double-space rule and break word splitting in anything downstream. The rule is off by default so the output matches what this tool has always produced; turn it on if spacing looks right but behaves oddly.

Because everything on it was inside brackets or was a music symbol — '[Instrumental]' or '♪♪♪' leave nothing behind. Those lines are listed under the result so you can see exactly which ones went, rather than discovering it later in an editor.

No. The line-number rule only fires when the dot is followed by a space or the end of the line, so an ordinal like '1. Hello' is stripped and a lyric that starts with a decimal is left alone.

Yes — .srt, .vtt and .lrc are read directly, with timestamps and cue numbers removed, leaving only the spoken or sung lines. Drop an audio file and you'll get told it isn't text rather than nothing happening.