Generate subtitles
from any audio or video
Upload your file, enter your Groq API key, pick a language — download a ready-to-use .srt in seconds. Nothing is stored on any server.
File is sent directly from your device to Groq. This page never receives it.
✅ Subtitles generated successfully
Download .srtPaste your Groq key into the top field. You can keep it on this device only if you want faster repeat use. If you skip saving, nothing is remembered after you leave the page.
Select an audio or video file from your phone or PC. MP3, MP4, WAV, M4A, OGG, FLAC, WEBM, MKV, AAC, and OPUS are supported here.
Use auto-detect for mixed or unknown speech, or pick a language manually when the audio is clearly in one language. Manual selection can improve accuracy on clean recordings.
Tap Generate SRT, wait for the upload and transcription step, then download the subtitle file. The browser will save the final .srt file automatically.
Best results usually come from clear speech, low background noise, and audio that is not too clipped or distorted. Longer files are fine as long as they stay within the size limit and your connection is stable.
Does this tool store my audio or API key on a server?
No. The file is uploaded directly from your browser to the transcription endpoint, and the key is only sent in the request needed to run the transcription. If you choose to remember the key, it stays in this browser’s local storage on this device.
Why do I need my own Groq API key?
Because the transcription service is being called through your own API access. That keeps the tool flexible, simple, and fast, while letting you control your usage through your own account.
What file size works best?
This page is set up for files up to 25MB. Smaller files usually finish faster, especially on mobile data. If the file is huge, trim it or compress it first for a smoother experience.
Why did the download not start automatically?
Some browsers block automatic downloads or ask for permission first. In that case, just tap the download button that appears after processing completes.
Can I use Urdu subtitles?
Yes. You can choose Urdu from the language list, or use auto-detect if the speech switches between languages. That is useful for mixed-content videos and casual recordings.
What if the transcription is empty or weak?
Usually that means the file has very low speech content, heavy music, noise, or a broken upload. Try a cleaner source, a better mic recording, or a smaller clip with clearer talking.
This page is built to stay lightweight. The file goes from your browser to the transcription service, and the interface is mainly there to collect your inputs and show progress. That keeps the workflow simple and avoids unnecessary storage on this site.
If you enable key remembering, the key is saved only in local storage on this device and this browser profile. That means it is convenient for repeat use, but it is still under your control. You can remove it any time with the Forget button.
For extra safety, avoid using public devices for saved keys. On shared phones or shared computers, always clear the key after use. Also make sure the site is opened from the correct domain before you paste anything sensitive.
The page does not need account creation, passwords, or profile setup. That reduces friction and also reduces the amount of personal data involved. Less data collected usually means less data exposed.
In simple terms: your content is handled for one job only — generating subtitles — and the page is designed to stay out of the way while doing that job well.
A lot of modern websites include helpful bottom sections so users can understand the tool quickly, trust the workflow, and find answers without leaving the page. That is not just cosmetic. It makes the page easier to use, easier to scan, and more helpful for first-time visitors.
Long-form support content can also be useful when someone is in a hurry and just wants one clear place to check how the tool works, what the limits are, and how the data is handled. That is why this page includes the practical details without changing the generator itself.
Use clean speech when possible
Clear voice recordings, interviews, podcasts, lectures, and tutorial narrations usually produce much better subtitles than noisy background audio or overlapping speakers.
Trim out dead space before upload
If your file contains long silent parts, intros, or outro music, trimming those sections can make the final subtitle file cleaner and faster to process.
Keep the output filename simple
Short filenames like lesson1, podcast-clip, or lecture-urdu are easier to manage later when you are saving several subtitle files.
The Generate button is disabled
That usually means one of the required inputs is missing. Add a valid Groq key and select a file. Once both are in place, the button should become active.
The upload is slow
Large files, poor connection, or mobile data can slow things down. Try a smaller file, a stronger network, or a shorter clip if you need quicker results.
The subtitles look off
That can happen when the audio is unclear or when the wrong language is selected. Try auto-detect first, then test the most likely language for the content.
🔒 Your API key and file(s) are never sent to Our servers. The request goes directly from your browser to Groq via a CloudFlare proxy. Nothing is logged or stored. If you choose "Remember this key," it stays only in this browser's local storage on this device — clear it anytime with the Forget button.