Free AI Tools in Persian
فارسی
ISO Code: fa
Available Tools in Persian
Persian AI Capabilities
Free.ai supports Persian 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 Persian (Qwen3 30B MoE)
- Translation to and from Persian (Madlad — 419 languages)
- Persian speech-to-text transcription (Whisper Large v3)
- Persian text-to-speech with natural AI voices (Kokoro / Piper / MeloTTS)
- Persian prompts work for image, video, and music generation
Språkdetaljer
| Språk | Persian |
| Inhemsk beteckning | فارسی |
| ISO-kod | fa |
| Tillgängliga verktyg | 31 |
| Pris | Avgiftsfri |
Bläddra bland språk
Visa alla språkVanliga frågor
Persian (فارسی) has broad coverage on Free.ai. AI chat, translation, transcription, TTS, and writing tools all support it. Image and video generation accept Persian prompts but render best from English (or Persian-to-English via /translate/ first). 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 Persian prompts and replies in Persian. 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 Persian is roughly the same as English on modern multilingual models — no language surcharge.
Yes — append `?lang=fa` to any URL (e.g. /?lang=fa or /chat/?lang=fa) and the Free.ai chrome (menus, buttons, tooltips, footers) renders in Persian. The selection persists via cookie. Hreflang tags in <head> tell Google to serve the Persian version to Persian-speaking searchers. AI model output itself follows whatever language you write your prompt in — independent of the UI setting.
TTS for Persian is available via the multilingual engines (MeloTTS and the premium providers) at /voice/fa/. The smaller monolingual engines (Kokoro, Piper presets) may not have a Persian voice — the picker on /voice/fa/ greys those out. Premium engines give the most natural prosody.
Yes — /transcribe/fa/ uses Whisper-large. WER on Persian is typically higher than on English (often 10-20% on normal audio) because Whisper saw less Persian training data. Clean audio + pinning `language=fa` via the API (`/v1/transcribe/?language=fa`) helps. Output: TXT, SRT, VTT, JSON with 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-fa/ for English→Persian or /translate/fa-en/ for Persian→English (where available). The API endpoint is `/v1/translate/?target=fa` — POST your source text in the request body. There is no per-character minimum; short strings and full documents both work.
Yes, with a caveat. /image/generate/ accepts prompts in Persian, but every major open and commercial image model (Flux, SDXL, Seedream, Ideogram, etc.) was trained primarily on English-captioned images. Persian prompts work, but the tightest prompt-following comes from English. If quality matters, run your prompt through /translate/ first (or use /v1/translate/?target=en in the API) and feed the English version to /image/generate/. Rendering Persian text inside images requires Ideogram or a similar text-aware model — most other models will produce gibberish glyphs.
Yes — Persian is right-to-left and Free.ai handles that. UTF-8 + bidi rendering means Persian text shows correctly in chat (/chat/), transcription output (/transcribe/fa/), and TTS input boxes. When you switch the UI to Persian via /?lang=fa, the entire chrome (sidebar, menus, buttons) flips to RTL via the CSS `dir="rtl"` attribute. Honest caveat: a few admin-only screens and the Code tool still render LTR — these are on the fix list.
Yes. /write/blog/, /write/essay/, and /write/email/ all accept a topic in Persian and produce output in Persian. Under the hood these route to the same chat models, so anything /chat/ does in Persian the writing tools also do. SEO tools (/seo/, /write/title/) generate Persian-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. Persian input and output tokenizes at roughly the same rate as English on modern multilingual tokenizers (BPE / SentencePiece), so a Persian 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 Persian input transparently — `/v1/chat/` takes a `messages` array in any language and replies in the same one. For translation, POST to `/v1/translate/?target=fa` with the source text. For transcription, pin the language with `/v1/transcribe/?language=fa` so Whisper does not autodetect wrong on short audio. For TTS, POST to `/v1/tts/` with `language=fa` 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 Persian) lists which surfaces currently support it.