Catch Genius formatting problems before you submit.

What it looks like

Verse 1:
i has counted every streetlight on the way
you said we'd drive until the radio gave out, yeah
and the "quiet" part was never really quiet

That transcription has a written-out section header, a lowercase line start, a subject and verb that disagree, a stray comma, and an ad-lib nobody parenthesised.

Apply the fixes it offers and you are left with the document you meant to submit — the same plain text and literal Genius markup you would have typed by hand:

[Verse 1]
I have counted every streetlight on the way
You said we'd drive until the radio gave out (Yeah)
And the "quiet" part was never really quiet

Grammar checking that stays on your device

Harper catches I has above and suggests I have. The open-source English grammar and spelling engine runs inside the page, so your lyrics are not sent to Harper or to a LyricLint server.

Lyrics are not ordinary prose, so Harper stays advisory: its fixes are always shown for review. Performer names and reviewed Genius spellings such as ayy are added to its dictionary, and LyricLint's sourced Genius rules take precedence wherever the two disagree.

Performer tagging without hand-writing the HTML

Marking up who sings what is the part of a Genius transcription that costs the most and goes wrong the most. The markup is literal HTML, it has to be balanced, the style slots have to be used in a consistent order, and the section header's legend has to agree with every span underneath it — all of it typed by hand, in a plain textarea, one <i> at a time.

LyricLint does it as a selection. Select the words, choose the voice, and the wrapper, the slot, and the header legend are written together as one edit you can undo in one press. Every performer keeps a color, so you can see who is singing each passage at a glance — and the color is display only. It never reaches the markup you copy out, which stays exactly what Genius expects.

The demo above has two performers on its roster already. Select any part of a line and hand it to one of them — after you've fixed the header!

Every warning carries its source

A linter that cannot say why it is complaining is just an opinion with a red underline. Every rule here required an exact Genius URL or annotation ID, a written interpretation, a human review, and a last-verified date before it was allowed to ship — and each finding links to the guideline it came from, so you can check the ruling rather than take it.

Where a convention is genuinely contextual — an ad-lib that may or may not want parentheses, a spelling that changes the meaning — the finding says so and its fix is previewed for you to confirm instead of applied. Judgement is labelled as judgement.

Read the full rule reference, including the sources behind each one.

Your lyrics stay in your browser

There is no account, no server, and no upload. Your 'scribes autosave to local storage in your own browser, so closing the tab does not lose work and a crash does not either. Once the page has loaded it keeps working offline, which matters when the rules you are checking against live on a site that is not always reachable.

There is one exception, and you choose it 'scribe by 'scribe: you can play the song you are transcribing alongside the lyrics. That could be an audio file off your own disk, which is never uploaded and never copied into the browser, a YouTube video, which loads Google's player into the page and lets Google see which video it is, or an Apple Music track. A 'scribe using the online options stops working offline.

What it is not

• Not a way to edit Genius directly. You copy the finished markup out and paste it in.
• Not an automated transcriber, and not a chat assistant.
• Not a live scraper. The rules are a reviewed, versioned snapshot bundled with the app, so what it checks today is what it checked yesterday.
• Not a rewriter. Nothing changes in your document unless you press the control that changes it.