FAQ

Your website seems to be broken?

We update our website from time to time. Your browser may have cached older versions and may not be able to find the files that have been replaced. You can hard refresh the page and that should fix the problem. Let us know if that doesn't solve the problem, as it could be a bug we're not aware of.

Which browser works best?

Most modern browsers should work, including mobile browsers. We mainly use Firefox during development and include Chrome and Safari when carrying out testing. Previously, Firefox had the best performance of all browsers we tested. However, we recently optimized Chrome's performance and achieved a significant improvement, making Chrome the fastest browser for subpicture conversions.

Why am I getting a "Multiple Tabs Found" message?

The message means another tab or window of this site is still open and running — it is easy to forget one from an earlier visit, or one sitting in another browser window or on another monitor. Only one tab can run at a time.

Close every other tab and window of the site and reload this page. Or simply keep this tab open: it starts working automatically as soon as the other one is closed. If you are certain that no other tab or window is open and the message still appears, let us know.

Why am I getting a "Failed site verification check" error?

We use Google reCAPTCHA to prevent abuse, and it often blocks IP addresses from popular VPN servers. Try disabling your VPN and see how it goes. If the problem persists, you may want to try a different browser.

Does subtitle translation send text to Google?

Yes. Subtitle files are parsed in your browser, and subtitle text is sent to Google Translate only after you explicitly start a translation. The Google Translate language widget may load third-party assets before then. Review Google's privacy information before sending content you are not permitted to share.

Why does my CPU usage go so high during subpicture conversion?

Subtitle conversion runs entirely in your browser, using your own computer's CPU, and converting subpicture files is CPU-intensive. Once conversion starts, the cue pictures within the file are extracted and prepared for OCR (Optical Character Recognition). Recognizing a single picture does not take too long, but a single subpicture subtitle file can contain thousands of cue pictures, each of which needs to be extracted, processed and recognized by the OCR engine.

Why are subpicture conversions taking so long?

As mentioned above, conversion runs entirely in your browser using your own computer's CPU. The faster your processor, the faster the conversion.

Which languages does two-step OCR support?

Subpicture conversion can run on either engine. Two-step OCR is a deep-learning pipeline that first detects text regions in each subtitle image, then recognizes the characters in them. It is generally the more accurate of the two but it is slower, and it has a model for 41 of the 59 languages we offer, listed below. Any other language still converts normally, using the default engine.

Albanian, Azerbaijani, Bosnian, Catalan; Valencian, Chinese - Simplified, Chinese - Traditional, Croatian, Czech, Danish, Dutch; Flemish, English, Estonian, Finnish, French, German, Hungarian, Icelandic, Indonesian, Irish, Italian, Japanese, Latvian, Lithuanian, Malay, Maltese, Norwegian, Norwegian (Bokmal), Norwegian (Nynorsk), Polish, Portuguese, Romanian; Moldavian; Moldovan, Serbian, Slovak, Slovenian, Spanish; Castilian, Swahili, Swedish, Tagalog, Turkish, Uzbek, Vietnamese.

How do I convert SUP/PGS or VobSub subtitles to SRT?

For Blu-ray image subtitles, use the SUP / PGS to SRT converter. For VobSub, choose both matching .sub and .idx files in the VobSub SUB/IDX to SRT converter.

Can I convert text subtitles (SRT, ASS, VTT) to PGS (Blu-ray SUP)?

Yes. Text-based subtitles such as SRT, ASS and VTT can be converted into Blu-ray PGS (SUP) picture subtitles. Each cue is rendered into a bitmap and encoded as a SUP stream locally in your browser — no files are ever sent to our server. Simply upload your text subtitle files, choose "Blu-ray PGS (SUP)" as the output format, and click Convert.

When converting ASS to PGS, are positions and styles preserved?

Static ASS layout is preserved: inline \pos and \an/\a alignment tags are honored, along with the script header — PlayResX/PlayResY scaling, per-style fonts, colors, outline, shadow, margins and default alignment. Cues that don't use \pos are anchored at their style-defined position instead of the usual bottom-center.

PGS is a static picture format, so effects that PGS cannot represent are simplified: karaoke (\k), animated transitions (\t), fades (\fad/\fade) and rotation are dropped, and \move uses its starting position. Per-cue inline styling tags (such as \c, \fs, \fn, \b, \i) are also not applied — each cue renders in its resolved style.