How to Switch Immersive Translate to DeepL, OpenAI, or a Custom Engine: API Key and Quota Checks

You can switch the Immersive Translate engine in the extension settings: built-in options cover most browsing; for a DeepL translation engine or OpenAI-style custom engine, pick that entry and paste the vendor API key. Invalid keys, exhausted quota, or blocked API routes show up as timeouts or explicit errors. Treat the engine list on your current settings page as source of truth—not an outdated screenshot. If every page still fails after a switch, fix extension enablement and never-translate rules before re-pasting keys.

People searching for Immersive Translate engines usually already see the floating control. They want a faster path, better wording, or their own DeepL / OpenAI quota. That is a different job from “install failed” or “click Translate, nothing happens”—those belong in the not-working checklist and the not-translating guide. This article covers switching engines, verifying keys, and spotting quota exhaustion. If the install is shaky, start from the download page.

When to switch translation engines

Scene: pages do translate, but the wording is stiff, names mangled, or the spinner never finishes at peak hours.

Check: if the icon looks healthy and a normal news article goes bilingual, you are more likely dealing with engine reachability, quality fit, or key quota—not a corrupted install.

Common reasons to switch:

• The default path times out; another built-in engine recovers immediately.
• You want DeepL for steadier EN↔ZH / European formal prose.
• You already pay for OpenAI or a compatible API and want a custom engine.
• The corporate network blocks one vendor; another still reaches the API.

A trap I hit: blaming the engine on an SPA/iframe page, then burning three keys. Prove the extension on a static English article first, then touch engine settings.

Stop when: the extension will not load, the icon is gray, or every site is dead—fix install and permissions before custom engines.

Where to switch built-in vs custom engines

Scene: you know you want DeepL or OpenAI, but cannot find the control.

Action (labels follow your current settings UI):

1. Open the Immersive Translate icon → Settings / Options.
2. Find Translation Service / Translation Engine (wording varies by version).
3. Pick a built-in engine, or a custom / third-party entry that asks for a key.
4. Save, then translate a short page to confirm the new engine is live.

Note: which engines appear depends on your installed version and what the settings page actually lists. This article will not invent a “complete official catalog.” If a tutorial screenshot names something you do not see, trust your device—do not install unknown modded builds just to chase a label.

Baseline bilingual reading is in the webpage translation guide; style trade-offs are in the AI translation engine comparison.

Configuring DeepL / OpenAI and similar options

Scene: settings show DeepL, OpenAI, or a “custom API” row and you need to attach your account.

Shared steps:

1. Create (or copy) an API key in the vendor console.
2. In Immersive Translate settings, select that engine entry.
3. Paste the key into the field. If Base URL / model / service type fields exist, follow the vendor docs and the on-screen hints—do not invent values for blank optionals.
4. Trial-translate a short paragraph. Keep the setup on success; on failure, read the error text before touching quota.

DeepL translation engine: if the UI separates free vs paid endpoints, picking the wrong type fails auth immediately. Leading/trailing spaces and half-copied keys are the most common human errors.

OpenAI or compatible APIs: wrong model names, missing org access, or pasting a chat-site password instead of an API key all fail. Use the string from the vendor’s API keys page.

Stop when: the vendor console says the account is restricted or unavailable in your region—reinstalling the extension will not unlock that.

API key mistakes and safety

Scene: you created a key, saved it, and translation fails instantly.

Checklist:

• Full paste, no leading/trailing spaces or line breaks.
• Engine row matches the key vendor (do not put vendor A’s key in vendor B’s field).
• Large system-clock drift can break signed auth—sync the clock.
• Confirm the key was not revoked, rotated, or bound to another project.

Safety: do not paste keys into public chats, ticket screenshots, or synced plain-text notes. If leaked, rotate at the vendor and update the extension. For sensitive drafts, know which vendor receives the text—see the translation extension privacy guide.

Quota exhausted and how to read errors

Scene: yesterday worked; today the same engine fails, or you see limit / quota / 402 / 429 style messages.

Rule of thumb: quota exhausted = vendor rejects billable calls; bad key = auth failure; network block = timeouts that recover on a phone hotspot.

Action:

1. Open the vendor usage panel for daily/monthly caps and billing status.
2. In the extension UI or browser network panel, separate 401/403 (key/permission) from 429/quota-class responses.
3. Temporarily switch to a built-in engine that still has allowance to prove the extension path works.
4. After renewing or replacing the key, retest the custom engine on a short page.

Stop when: the console clearly shows an expired plan—reinstall loops will not pay the invoice.

Still no translation after switching engines

Scene: the key works in a vendor test, but the target site still shows no bilingual text.

Split the problem:

• Every site fails → extension enablement, permissions, conflicts: not-working checklist.
• Only some hosts fail → never-translate list, language mismatch, page type: not-translating guide.
• Incognito-only or SPA-after-route failures while static pages and engines work → Incognito & SPA permissions / refresh timing.
• Only one custom engine fails while built-in works → stay on key / quota / reachability for that API.

Order: short static page + built-in → short static page + custom → problem site. Change one variable at a time so you know which step fixed it.

Engine choice and privacy boundaries

Public web pages on common online engines are usually fine; contracts, unpublished papers, and internal tickets should assume text leaves the device. A custom engine is not automatically safer—it only points traffic at the vendor you chose.

For stricter control: use a local/enterprise path if your settings expose one, or redact before translating. Keep installs and updates on the download page—avoid unknown “cracked engine” packages.

FAQ

An engine I saw online is missing—is Immersive Translate broken?

Not necessarily. Visible options follow your current settings page. Configure what actually appears as built-in or custom entries on your device.

DeepL key saved, still errors—what should I check?

Full paste, matching service type, console quota/key status, and a short-page retest. Do not confuse page-structure limits with key failures.

Quota exhausted—can Immersive Translate still translate?

The key-bound custom engine fails; a built-in path with remaining allowance usually still works. Renew or replace the key, then switch back.

Are custom-engine failures the same as whole-page “not translating”?

No. Key/quota is the engine side; disabled extension, never-translate, and conflicts are the extension/page side. Split the tracks.