Skip to main content
Upgrade to Pro
English
简体中文
繁體中文
繁體中文(香港)
English
日本語
العربية
Deutsch
Español
Français
हिन्दी
Italiano
한국어
Português
Português (Brasil)
Русский

YouTube Subtitle 429 Errors

When YouTube temporarily rejects subtitle requests, subtitles may fail to load and a 429 error may appear.

This error comes from YouTube's subtitle endpoint, not from Immersive Translate's translation service. The most common case is that YouTube's machine-translated subtitles have been temporarily rate-limited.

Immersive Translate tries to recover automatically

When a request for YouTube's machine-translated subtitles returns 429, Immersive Translate automatically tries to fetch the original-language version of the same subtitle track, then translates it with your selected subtitle translation service.

If the original-language subtitles are available, bilingual subtitles continue normally and you do not need to switch tracks manually. This recovery path no longer relies on YouTube's machine-translated subtitles.

The extension shows an error only if automatic recovery fails. At that point, selecting the original-language subtitles manually is mainly a diagnostic step to check whether YouTube itself can provide them. It usually cannot bypass the same original-subtitle request that has already failed.

Why does a 429 error occur?

429 means that YouTube has temporarily rejected the current subtitle request. YouTube has not published the specific rules for its subtitle endpoint. Common situations include:

YouTube has limited machine-translated subtitles

The video's original-language subtitles work, but subtitles fail to load after you select a language under “Auto-translate”.

This is the most common situation. Immersive Translate automatically removes the target translation language and fetches the original-language subtitles instead. This usually avoids the request path that is more likely to be rate-limited.

Too many subtitle requests in a short time

Switching between several subtitle languages, opening multiple videos quickly, repeatedly refreshing the page, or retrying continuously can generate many subtitle requests in a short period.

Stop repeated actions, wait for a while, and then try again. Repeatedly retrying immediately may cause the limit to last longer.

A VPN, proxy, or shared network has been limited

YouTube may limit subtitle requests from the current network exit. With a VPN, proxy, company network, campus network, or another shared network, many users may share the same exit.

If the original-language subtitles also fail to appear, try:

  • Switching to a different VPN or proxy node;
  • Temporarily disabling the VPN or proxy;
  • Changing networks and reopening the video;
  • Waiting for a while before trying again.

The current YouTube session has been limited

Some limits may be related to the current YouTube session, account status, or browser environment. Open YouTube directly, check whether it asks you to sign in or complete a security verification, and then reopen the video.

YouTube's subtitle service is temporarily unavailable

If many videos suddenly have the same problem and the issue persists after changing the network, video, and subtitle language, YouTube's subtitle service or related policies may have changed temporarily. In this case, you usually need to wait for YouTube to recover.

How does Immersive Translate reduce these problems?

In the default subtitle flow, Immersive Translate tries to reuse the original-language subtitles already fetched by the YouTube player, avoiding extra subtitle requests whenever possible.

Immersive Translate then uses your selected subtitle translation service to generate the translation. It does not need to call YouTube's machine-translation subtitle endpoint. This mainly reduces two risks:

  • Extra requests caused by fetching the same subtitles again;
  • The 429 limit that is more likely when calling YouTube's machine-translated subtitle endpoint.

If a request for YouTube's machine-translated subtitles returns 429, Immersive Translate also makes one automatic attempt to fetch the corresponding original-language subtitles. If that request is also limited or does not return usable subtitles, there is no source text to translate and automatic recovery cannot continue.

If it still does not work

Start with the message shown by the extension:

“YouTube subtitle requests are temporarily limited (429)”

This means that the original-language subtitle request also returned 429. Repeatedly switching subtitle tracks usually will not help. Try the following:

  1. Stop refreshing or switching subtitles repeatedly, wait for a while, and try again.
  2. If you use a VPN or proxy, switch nodes or temporarily disable it.
  3. Change networks and reopen the video.
  4. Open YouTube directly and check for sign-in or security-verification prompts.

“Couldn’t automatically load the video’s original-language subtitles”

Automatic recovery did not receive usable original subtitles, but this does not necessarily mean that the second request also returned 429. Select the original-language subtitles in the YouTube player to check whether YouTube itself can display them:

  • If YouTube also cannot display them, wait for a while, change networks, or check whether your account requires verification.
  • If YouTube can display them, refresh the page and try Immersive Translate again. If the problem persists, report the video URL and the error message to us.

For a complete check, follow these steps:

  1. Confirm that the video provides original-language subtitles.
  2. Confirm that YouTube can display the original-language subtitles.
  3. Stop refreshing or switching subtitles repeatedly, wait for a while, and try again.
  4. If you use a VPN or proxy, switch nodes or temporarily disable it.
  5. Change networks and check whether the original-language subtitles work.
  6. Open YouTube directly and check for sign-in or security-verification prompts.

If the original-language subtitles never appear on YouTube, the problem occurs before Immersive Translate can begin translating. Wait for YouTube to recover and try again later.