The same per-file price as a single AI LRC generation, charged as each file starts rather than up front. The live rate is shown on the page. A file that fails is refunded automatically.

What if I don't have enough credits for the whole batch?

You're told how many files your balance covers before anything runs. Those files go through and the rest stay queued, so you can top up and press Process again without re-adding anything.

What if my browser closes mid-batch?

The queue is held in the page, so closing the tab ends it. Files that already finished are unaffected — jobs that completed are in your history — but anything still queued is lost and will need re-adding.

What happens if one file fails?

The rest of the batch keeps going. The failed file is marked with the reason, its credits are refunded, and you can retry just the failures with one button.

Which files can I add?

Audio and video containers up to 100 MB each — MP3, WAV, FLAC, OGG, OPUS, AAC, M4A, plus MP4, MKV, MOV, WebM and AVI, whose audio track is used. Anything else is refused as you drop it.

Can I download everything as one ZIP?

No. Each finished file downloads as its own .lrc; Download all saves them one after another. There is no archive step — the files are small and your browser handles them individually.

Why only two at a time?

Your account has a limit on concurrent jobs. Running two keeps the batch safely under it, so the queue never fails its own files by competing with itself — or with a job you started on another page.

Batch processing

Sync a stack of songs in one queue

Drop in a folder of audio files and get a synced LRC back for each one. Two run at a time, every file reports its own status, and you can retry just the ones that failed.

Input

Your audio or video files

MP3 · WAV · FLAC · OGG · M4A · MP4, 100 MB each

Output

One .lrc per song

Per-file status + retry

Start batch job

Batch queue

1 credit per file

Batch generation spends credits from your account, so it needs a sign-in.

Add audio files

Drop them here or click to browse — MP3, FLAC, WAV, OGG, M4A, MP4. Max 100 MB each.

Nothing queued yet. Add files above — each one becomes its own synced LRC, two at a time so the worker pool stays responsive.

See it in action

A folder in, a synced LRC per song out

Batch input

What you provide

🎵 01_track.mp3
🎵 02_track.mp3
🎵 03_track.mp3
… 12 files queued

Running   : 2 at a time
Cost      : credits per file, as each one starts

Per-file status

What you receive

[01/12] 01_track.mp3   ✓ done · 01_track.lrc
[02/12] 02_track.mp3   ✓ done · 02_track.lrc
[03/12] 03_track.mp3   ✓ done · 03_track.lrc
[04/12] 04_track.mp3   ⚠ failed · credits refunded
[05/12] 05_track.mp3   ● transcribing…
…
11 done, 1 failed — retry just the failure

Step-by-step guide

How to use this tool

01
Drop your files
Pick as many as you like — each one is listed with its name and status. Files that are empty, over 100 MB, or not an audio or video container are rejected as you add them, with the reason shown.
02
Run the queue
Two files transcribe at a time, so the batch never trips the per-account concurrent-job limit and starts failing its own files on quota.
03
Watch each file
Every row shows its own progress and its own error if something goes wrong.
04
Download the LRCs
Save them one at a time, or use Download all to save every finished file in turn.

Key features

Why use this tool

Per-file progress

Each row reports its own stage rather than one bar for the whole batch.

One failure doesn't stop the rest

Failed files are marked with their reason and left in the queue so you can retry only those. Credits for a failed file are refunded.

It tells you the bill first

A large batch, or one that costs more credits than you hold, asks for confirmation before it starts spending — including how many files your balance will actually cover.

Common use cases

Who this tool is for

Album runs

Generate synced lyrics for every track on a record in one sitting.

Back-catalogue cleanup

Work through a folder of older tracks that never got LRC files.

Questions answered

Frequently asked questions

There's no fixed cap on the queue. Two files are processed at a time, and each one spends credits as it starts — so the practical limit is your credit balance.