世
Fox  Translator
Drop a course · translate · re-export
{{ st.n }}
{{ st.label }}

Translate a course or document in minutes

Drop a SCORM package, Word doc or PowerPoint deck. We'll pull out every piece of text, translate it with a glossary you control, let you review it against a live preview, and hand back a ready-to-use file in its original format.

!{{ error }}
{{ u.icon }}
{{ u.title }}
{{ u.body }}
📦
{{ pkgName }}
{{ pkgSummary }}
Translate into
Source detected as English. Pick a target language.
Master glossary
{{ glossHint }}
●{{ glossSaveNote }}

Translating into {{ targetName }}…

{{ progressLabel }}
{{ progressCount }}
{{ activeLabel }}
{{ activeSub }}
✓{{ validationBadge }}
Original
Translated
{{ it.kind }} {{ it.original }}
Live preview
Text scale {{ fontScale }}%
{{ exportNote }}
How to use this tool
✕
1
Connect a translation engine (first time only). Click the ⚙ icon, pick your provider and paste your API key. The key stays in your browser — it's never uploaded anywhere except to the provider itself. Everything except the auto-translate step works without a key.
2
Drop in your file. A SCORM .zip (Storyline, Rise or standard HTML), a Word .docx, or a PowerPoint .pptx. The tool pulls out every piece of translatable text — slide copy, quiz feedback, menus, alt text, speaker notes.
3
Pick the target language and check the glossary. The master glossary keeps brand names and key terms consistent — leave a term's translation blank to keep it exactly as-is in every language. It saves automatically and is reused for every file; use Import/Export to share it with your team as a spreadsheet.
4
Translate, then review side-by-side. Original text on the left, translation on the right — edit anything. The live preview shows the translated text at real size and flags boxes the translation has outgrown; the text-scale slider helps longer languages fit.
5
Optional: send to a validator. "Send for validation" downloads a single review file — your validator opens it in any browser (no account, no software), edits, clicks Validate with their name, and sends back the results file. "Import results" merges their edits and stamps the project validated.
6
Export. You get back the same format you dropped in — a ready-to-upload SCORM zip, Word doc or PowerPoint deck, with fonts extended so accents and Japanese/Korean render correctly.
Not translated: text baked into images, audio or video. Storyline courses must be published for Web/LMS (HTML5) — a raw .story file won't work.
Translation engine
✕
Provider
Uses the built-in Claude AI. No key needed here — but this only works inside this design environment. For a copy hosted on your webserver, pick another provider.
API key
From console.anthropic.com. Calls go straight from the browser to Anthropic. The key is visible to anyone who can view this page's source — use only on an internal or password-protected page; for a public URL use the Company proxy instead.
API key
Model
Endpoint override (optional — for a company relay)
Browsers may block direct calls to api.openai.com from a hosted page (CORS). If translation fails with a network error, route through a small relay and set its URL here.
Endpoint
Deployment name
API key
Ask IT for an Azure OpenAI resource with a GPT-4o deployment. Azure allows direct browser calls, so no proxy is needed and data stays in the company tenant.
Proxy URL
A small server-side script that holds the API key (the deploy folder includes translate-proxy.php for GoDaddy). Safest option for a shared web copy — no key ever reaches the browser.
Settings are stored only in this browser (localStorage). Keys are sent only to the provider you chose, and only to translate. Upload, review, glossary and export never need a key.