Free AI Tools in English
ISO Code: en
Available Tools in English
English AI Capabilities
Free.ai supports English across 31 tools, powered by state-of-the-art open-source models (Qwen3, Whisper, Madlad). Pick a tool above to start.
- AI chat and text generation in English (Qwen3 30B MoE)
- Translation to and from English (Madlad — 419 languages)
- English speech-to-text transcription (Whisper Large v3)
- English text-to-speech with natural AI voices (Kokoro / Piper / MeloTTS)
- English prompts work for image, video, and music generation
Ibimenyetso by'ururimi
| Ururimi: | English |
| Izina ry'idosiye | English |
| Inyandikoporogaramu | en |
| Ibikoresho | 31 |
| Agaciro: | Kigenga |
Gushakisha Ururimi
Ururimi:Ibibazo bizwa kenshi
English is a full-coverage language on Free.ai. Every public tool accepts English: AI chat at /chat/, translation at /translate/, audio transcription at /transcribe/en/, text-to-speech at /voice/en/, writing tools at /write/blog/ and /write/email/, image generation at /image/generate/ (prompts in English work but English prompts produce best results), and code generation at /code/. Currently active surfaces: chat, search, assistant, write, summarize, paraphrase, grammar, humanizer, detect-ai, expand, simplify, rewrite, email, cover-letter, resume, essay, story, poem, code, coder, translate, image, image/anime, image/logo, image/poster, image/meme, image/wallpaper, video/generate, music/generate, transcribe, tts.
Yes — /chat/ accepts English prompts and replies in English. Free signups get 10,000 tokens immediately plus a daily refill pool (resets every 24 hours) that covers normal conversational use. When the daily pool runs out, paid tokens start at $1 = 750,000 tokens; a $5 top-up adds 200,000 tokens at the entry tier. Per-message cost in English is roughly the same as English on modern multilingual models — no language surcharge.
Yes — append `?lang=en` to any URL (e.g. /?lang=en or /chat/?lang=en) and the Free.ai chrome (menus, buttons, tooltips, footers) renders in English. The selection persists via cookie. Hreflang tags in <head> tell Google to serve the English version to English-speaking searchers. AI model output itself follows whatever language you write your prompt in — independent of the UI setting.
It varies by engine. Free.ai exposes multiple TTS engines at /voice/en/ — Kokoro and Piper for fast on-device-quality synthesis, Chatterbox for expressive long-form, and MeloTTS for multilingual coverage. For English, MeloTTS and the premium engines give the most natural prosody; the smaller models trade naturalness for speed. Paste a sample on /voice/en/ and the page renders the same text across engines so you can pick by ear.
Yes — /transcribe/en/ runs Whisper-large on English audio. Word error rate (WER) on clean studio audio is typically 5-12%; noisy phone calls or heavy regional accents push WER higher. The API endpoint `/v1/transcribe/?language=en` lets you pin the language so Whisper does not autodetect wrong on short clips. Output formats: TXT, SRT, VTT, JSON with word-level timestamps.
Yes — /translate/ does both directions. Free.ai uses a mix of NLLB-200 (Meta's 200-language model) and premium models depending on the pair. Popular pairs have dedicated landing pages — try /translate/en-en/ for English→English or /translate/en-en/ for English→English (where available). The API endpoint is `/v1/translate/?target=en` — POST your source text in the request body. There is no per-character minimum; short strings and full documents both work.
Yes — image generation models (Flux, SDXL, Seedream, Ideogram, and the rest at /image/generate/) were trained on English caption pairs and produce their cleanest results from English prompts. You can mix English with proper nouns from any language (place names, brands, character names) and the model handles them.
Yes. English uses the Latin script with locale-specific diacritics, and Free.ai serves UTF-8 end-to-end — chat, transcription output, TTS input, /write/ exports, and PDF/DOCX downloads. Accented characters and locale-specific glyphs render without substitution.
Yes. /write/blog/, /write/essay/, and /write/email/ all accept a topic in English and produce output in English. Under the hood these route to the same chat models, so anything /chat/ does in English the writing tools also do. SEO tools (/seo/, /write/title/) generate English-language titles and meta descriptions when you set the target locale.
Same rates as every other language. $1 buys 750,000 tokens; a $5 top-up gets 200,000 tokens at the entry tier; free signups receive 10,000 tokens immediately plus a daily free pool that covers everyday chat and translation. English input and output tokenizes at roughly the same rate as English on modern multilingual tokenizers (BPE / SentencePiece), so a English chat costs about the same as the equivalent English chat. No language carries a surcharge.
Yes. The same endpoints used by the web UI accept English input transparently — `/v1/chat/` takes a `messages` array in any language and replies in the same one. For translation, POST to `/v1/translate/?target=en` with the source text. For transcription, pin the language with `/v1/transcribe/?language=en` so Whisper does not autodetect wrong on short audio. For TTS, POST to `/v1/tts/` with `language=en` to pick the right voice automatically. Auth: Bearer token from /api/. See /api/ for SDK snippets and rate-limit details.
Free.ai supports 100+ languages with dedicated landing pages at /languages/. The full list covers every language Whisper, NLLB, and the major chat models handle — including all official EU languages, every major Asian language, Arabic and Hebrew, and a growing roster of African and Indigenous languages. Each language page (like this one for English) lists which surfaces currently support it.