FREE PREMIERE PRO EXTENSION
Turn your Premiere timeline into timed SRT subtitles with one click.
Transcribe speech in 100 selectable languages with local Whisper models, then bring accurately timed captions into your edit. Stay inside Premiere Pro from start to finish.

THE WORKFLOW
Built around the sequence you are editing.
01 / PREPARE
Choose a language and model
Pick one of 100 languages or use automatic detection. Download a model once through Manage Models.
02 / TRANSCRIBE
Run the active timeline
The extension automatically exports the sequence audio and sends it to the local transcription agent. The entire process runs automatically; track progress in the panel.
03 / EDIT
Refine the subtitles
Use the generated SRT in your Premiere project. Review names, spelling and timing before delivery.
LANGUAGE COVERAGE
Find your language.
All 100 language choices in Multilingual Transcriber, compared with the languages explicitly listed in Adobe’s Speech-to-Text documentation. Automatic detection is an additional option in the extension.
| Language | Premiere built-in Speech-to-Text | Multilingual Transcriber |
|---|---|---|
| 1.Afrikaans | × | ✓ |
| 2.Albanian | × | ✓ |
| 3.Amharic | × | ✓ |
| 4.Arabic | × | ✓ |
| 5.Armenian | × | ✓ |
| 6.Assamese | × | ✓ |
| 7.Azerbaijani | × | ✓ |
| 8.Bashkir | × | ✓ |
| 9.Basque | × | ✓ |
| 10.Belarusian | × | ✓ |
| 11.Bengali | × | ✓ |
| 12.Bosnian | × | ✓ |
| 13.Breton | × | ✓ |
| 14.Bulgarian | × | ✓ |
| 15.Cantonese | ✓ | ✓ |
| 16.Catalan | × | ✓ |
| 17.Chinese | ✓ | ✓ |
| 18.Croatian | × | ✓ |
| 19.Czech | × | ✓ |
| 20.Danish | ✓ | ✓ |
| 21.Dutch | ✓ | ✓ |
| 22.English | ✓ | ✓ |
| 23.Estonian | × | ✓ |
| 24.Faroese | × | ✓ |
| 25.Finnish | × | ✓ |
| 26.French | ✓ | ✓ |
| 27.Galician | × | ✓ |
| 28.Georgian | × | ✓ |
| 29.German | ✓ | ✓ |
| 30.Greek | × | ✓ |
| 31.Gujarati | × | ✓ |
| 32.Haitian Creole | × | ✓ |
| 33.Hausa | × | ✓ |
| 34.Hawaiian | × | ✓ |
| 35.Hebrew | × | ✓ |
| 36.Hindi | ✓ | ✓ |
| 37.Hungarian | × | ✓ |
| 38.Icelandic | × | ✓ |
| 39.Indonesian | × | ✓ |
| 40.Italian | ✓ | ✓ |
| 41.Japanese | ✓ | ✓ |
| 42.Javanese | × | ✓ |
| 43.Kannada | × | ✓ |
| 44.Kazakh | × | ✓ |
| 45.Khmer | × | ✓ |
| 46.Korean | ✓ | ✓ |
| 47.Lao | × | ✓ |
| 48.Latin | × | ✓ |
| 49.Latvian | × | ✓ |
| 50.Lingala | × | ✓ |
| 51.Lithuanian | × | ✓ |
| 52.Luxembourgish | × | ✓ |
| 53.Macedonian | × | ✓ |
| 54.Malagasy | × | ✓ |
| 55.Malay | × | ✓ |
| 56.Malayalam | × | ✓ |
| 57.Maltese | × | ✓ |
| 58.Maori | × | ✓ |
| 59.Marathi | × | ✓ |
| 60.Mongolian | × | ✓ |
| 61.Myanmar | × | ✓ |
| 62.Nepali | × | ✓ |
| 63.Norwegian | ✓ | ✓ |
| 64.Nynorsk | × | ✓ |
| 65.Occitan | × | ✓ |
| 66.Pashto | × | ✓ |
| 67.Persian | × | ✓ |
| 68.Polish | × | ✓ |
| 69.Portuguese | ✓ | ✓ |
| 70.Punjabi | × | ✓ |
| 71.Romanian | × | ✓ |
| 72.Russian | ✓ | ✓ |
| 73.Sanskrit | × | ✓ |
| 74.Serbian | × | ✓ |
| 75.Shona | × | ✓ |
| 76.Sindhi | × | ✓ |
| 77.Sinhala | × | ✓ |
| 78.Slovak | × | ✓ |
| 79.Slovenian | × | ✓ |
| 80.Somali | × | ✓ |
| 81.Spanish | ✓ | ✓ |
| 82.Sundanese | × | ✓ |
| 83.Swahili | × | ✓ |
| 84.Swedish | ✓ | ✓ |
| 85.Tagalog | × | ✓ |
| 86.Tajik | × | ✓ |
| 87.Tamil | × | ✓ |
| 88.Tatar | × | ✓ |
| 89.Telugu | × | ✓ |
| 90.Thai | × | ✓ |
| 91.Tibetan | × | ✓ |
| 92.Turkish | × | ✓ |
| 93.Turkmen | × | ✓ |
| 94.Ukrainian | × | ✓ |
| 95.Urdu | × | ✓ |
| 96.Uzbek | × | ✓ |
| 97.Vietnamese | × | ✓ |
| 98.Welsh | × | ✓ |
| 99.Yiddish | × | ✓ |
| 100.Yoruba | × | ✓ |
A red × means the language is not explicitly named in Adobe’s published Speech-to-Text list (last updated August 22, 2025). Adobe lists 18 options across 16 base languages, including regional variants. This comparison concerns transcription, not subtitle translation. Recognition quality varies with language, recording and model.
MADE FOR EDITORS
Control the subtitle output.
Set practical limits for line length, words, reading speed and duration. Keep sequence time or start SRT time from the in point.
To improve transcription accuracy, provide context and manually add important words, such as names or technical terms, that the model might otherwise mishear.
- Model choice from turbo to large-v3
- Word timestamps and sentence splitting
- Subtitle layout and timing controls
- Prompt/context and hotwords for terminology hints
- SRT files stored with the Premiere project
- Local processing after the model is downloaded
WHAT YOU NEED
Premiere Pro 2025 or 2026.
Install the extension, open it from Premiere’s Window menu, start the local agent and download a model before the first transcription.
Before you start
- Allow time and disk space for the first model download.
- A faster GPU can improve performance; CPU speed varies by model and system.
- Save your Premiere project so subtitle files can be kept beside it.
- Check the generated SRT before final export.
COMMON QUESTIONS
Good to know.
Does it translate subtitles?
Does it need an internet connection?
Which operating systems are supported?
Is it free?
DOWNLOAD
Start transcribing your next edit.
Multilingual Transcriber for Premiere Pro v1.0.4 · Premiere Pro 2025/2026
Extract the ZIP first, then run the installer for your system. Open Premiere Pro after installation.
Multilingual Transcriber is an independent extension by Djordje Pivnicki. Adobe and Premiere Pro are trademarks of Adobe Inc. This product is not affiliated with Adobe.

It is interesting thing!
Is there ay tutorial how to use your plug-in?
Thanks for your comment! I haven’t made a tutorial yet, but that’s a good idea. The extension is straightforward to use, so feel free to give it a try in the meantime and let me know if you run into any questions.
Lep pozdrav.
Hello,
First, thank you for developing Multilingual Transcriber for Adobe Premiere Pro. I find your plugin very interesting, particularly because it supports Slovenian speech recognition and local transcription using Whisper.
I would like to use it regularly for educational videos about Traditional Chinese Medicine, anatomy, acupuncture, and Tuina massage.
Before installing version 1.0.4 on my main Windows computer, I had the installation package and its source files reviewed for potential security issues.
The review did not identify obvious malicious code, but it highlighted several areas that may benefit from improvement.
### 1. Local API security – high priority
In `apps/local-agent/src/api/server.py`, the FastAPI server currently uses:
`allow_origins=[“*”]`
The reviewed API routes also appear to lack authentication.
Although the server binds to `127.0.0.1`, allowing requests from arbitrary origins may create unnecessary security risks.
**Suggested improvements:**
– Restrict CORS to explicitly authorized origins.
– Implement authentication, such as a session-specific access token, for sensitive API operations.
– Validate request origins and protect against unauthorized local requests.
– Review and restrict filesystem operations exposed through the API.
– Add automated security tests for unauthorized access attempts.
### 2. Verify downloaded components
The Windows installer downloads several dependencies, including Python, pip, Faster-Whisper-XXL, and potentially 7-Zip.
Some downloads are checked against expected file sizes, but I could not confirm consistent SHA-256 verification for all downloaded components.
**Suggested improvements:**
– Verify downloaded files against trusted SHA-256 checksums or digital signatures.
– Pin dependencies to reviewed versions rather than automatically selecting the latest available release.
– Reject downloads when integrity verification fails.
– Consider digitally signing the Windows installer.
### 3. Minimize administrator privileges
The installer requests administrator permissions and uses PowerShell with `-ExecutionPolicy Bypass`.
I understand that some elevated permissions may be necessary to install the Adobe extension.
However, I would appreciate an installation process that follows the principle of least privilege.
Could you separate operations requiring administrator rights from those that can run under a standard user account?
It would also be helpful to explain why execution-policy bypass is required.
### 4. Avoid forcibly closing Adobe Premiere Pro
The Windows installation scripts contain commands that can terminate Premiere Pro processes using `Stop-Process -Force`.
This could result in the loss of unsaved editing work.
I suggest checking whether Premiere Pro is running and asking the user to save their project and close the application manually before continuing.
### 5. Clear privacy information
One of the most attractive features of your plugin is local speech transcription.
It would be helpful to provide clear documentation explaining:
– Which operations are performed entirely on the user’s computer.
– Whether any audio, video, transcripts, or metadata leave the computer.
– Which internet connections are required for downloads and updates.
– Whether cloud transcription services are completely optional.
### 6. Feature suggestions
I would also like to suggest a few improvements that would make the plugin especially useful for educational video production:
**Professional terminology dictionary**
Allow users to define custom terminology, such as acupuncture-point names, anatomical terminology, and Traditional Chinese Medicine concepts, to improve transcription accuracy.
**English-to-Slovenian translation**
It would be extremely useful to automatically translate English subtitles into Slovenian while preserving their timing.
**Improved subtitle formatting**
Automatic sentence-aware segmentation, adjustable maximum characters per line, and convenient subtitle styling presets would be valuable additions.
### Final question
Could you let me know whether you plan to address these security concerns in an upcoming release?
I would be particularly interested in an updated version with authenticated local API access, verified downloads, and safer installation behavior.
I would be happy to use your plugin once these issues have been addressed.
Thank you for your work and for considering these suggestions.
Best regards,
Adding subtitle translation would require either a local model or a cloud service with ongoing costs. A local option like Qwen3 4B is about 2.5 GB, plus software to run it and preferably 16 GB RAM. It’s a fairly small model, though, and I haven’t tested whether its subtitle translations would be good enough. I don’t want users to have to pay for a cloud service.
I could bundle Faster-Whisper, but its Windows package is about 1.4 GB to download, plus around 1.6 GB for the turbo model. That would make the download from my site too large. Redistribution may be possible, but I’d need to check the licenses of everything included.
You can transcribe audio with Faster-Whisper without Premiere Pro. My extension exports audio from the active timeline and brings the resulting subtitles back into Premiere. That’s how I used to work, but the manual process was slow, which is why I made the extension.
I can’t bypass Premiere Pro’s security restrictions. The extension works well on Windows; I haven’t received feedback from macOS users yet.
Hello,
Thank you for your detailed response. I appreciate your explanation of the technical limitations, download sizes, and your intention to keep the extension free.
I completely understand your decision not to bundle large AI models or require paid cloud services.
My main concern, however, is still the security of the Windows installation and the local API.
I would appreciate clarification on three specific points.
1. Local API security
The reviewed source code appears to configure FastAPI with allow_origins=[“*”], while some local API endpoints do not appear to require authentication.
Could you clarify whether these endpoints are protected against unauthorized requests?
Would it be possible to restrict allowed origins and introduce authentication or session-specific tokens for sensitive operations?
I understand that Premiere Pro has its own security restrictions, but my question concerns the security of the local API implemented by your extension.
2. Installer security
Does the installer verify downloaded dependencies using trusted SHA-256 checksums or digital signatures?
If not, would you consider adding these checks in a future version?
I am particularly interested in ensuring that downloaded components have not been modified or replaced.
3. Administrator privileges and Premiere Pro
Could the installer avoid forcibly terminating Premiere Pro and instead ask the user to save their work and close the application manually?
Could administrator privileges also be limited to operations where they are strictly necessary?
My main question is whether you consider these security concerns valid and whether you plan to address them in a future release.
I am not suggesting that your software is malicious. I simply want to ensure that it can be installed and used safely on my main Windows workstation.
Your plugin is very useful, and I would genuinely like to use it regularly.
Thank you again for your work and your time.
Best regards
Thank you for the careful review. Your security concerns are valid.
1. Local API: It listens on 127.0.0.1, but that alone is not sufficient. I plan to restrict allowed origins, add authentication to sensitive endpoints, and review filesystem access.
2. Downloads: The installer does not consistently verify dependencies against trusted SHA-256 hashes or signatures. It would be possible to pin specific versions and verify each download against a trusted checksum or signature.
3. Installation: I hadn’t encountered the forced-closure issue because I always closed Premiere Pro before testing. Thank you for pointing it out. The installer should ask users to save their work and close Premiere themselves. I’ll also review which steps actually need administrator privileges.
I can’t promise an update release date. In the meantime, you can use Faster Whisper XXL as a standalone tool without my extension.
Thannks.