翻译 Ukrainian 至 Spanish 自由

Ukrainian → Spanish translation on Free.ai runs through NLLB-200(Meta的200种多语言多语言模式)作为主要路线,马德拉德-400覆盖长尾和代码转换输入. Quality on Ukrainian → Spanish depends on how much overlap the training corpus had for this pair — high-resource directions read fluently, low-resource directions can drift on idioms or rare named entities. The form on this page lets you paste up to ~10,000 characters; for longer text upload a file or use the /v1/translate/ API. If a passage looks off, regenerate — the engine samples differently each run and the second pass often catches a missed nuance.

是 — —Ukrainian _ Spanish% 翻译对大部分正常使用是免费的。匿名用户得到每个IP每天的集合;注册的免费账户得到更大的每日集合(~50,000个字符/日)加上10,000个签名牌。除此之外,顶级启动启动时间为$1 (750,000个标牌), <Ukrainian% 的~ 150,000个字符 — 没有订阅,没有每月最低的签名 。

西班牙语有非正式的 tú 和 正式的 usa 。 引擎默认为中性登记册, 默认在多数情况下自然读取; 对于正式信件, 将您文本前缀为“ 正式翻译 : ”, 模型会倾向于使用用户格式 。

Yes. /translate/ accepts DOCX, PDF, TXT, MD, SRT (subtitle files), and JSON (i18n catalogs). Drop the file on the upload zone and pick Spanish (es) as the target — the translated file downloads with the same layout, fonts, and (for DOCX/PDF) inline images preserved in place. JSON keys are kept; only values are translated. SRT timestamps are preserved exactly.

Ukrainian → Spanish runs on NLLB-200(Meta的200种多语言多语言模式)作为主要路线,马德拉德-400覆盖长尾和代码转换输入. These models are self-hosted on Free.ai GPUs — your text never leaves our infrastructure for the default route. Premium routes (GPT-4o, Claude, Gemini) are available for pairs and contexts where the frontier model materially beats the open-source engines; those route through the upstream provider under our DPA. The route used for any given request is shown in the API response under "model".

Yes. Paragraph breaks, list bullets, and inline punctuation survive the Ukrainian → Spanish round-trip. Trailing whitespace and tab indentation are normalized; if you need byte-perfect fidelity for code or YAML, use the /v1/translate/ API with preserve_whitespace=true.

Free.ai的翻译成本是每个输入字符的~ 5个符号。 $ 1 购买 750 000 个符号, 大约包含 $150,000 个字符的 $FREEI_ PH_ rc_ name_ 输入( 约 25 000 字, 或 50 页文件) 。 5 美元顶上覆盖 ~ 750 000 个字符 。 免费账户的每日集合量为~ 500 000 个字符/ 每天, 外加 10,000 吨签名奖金, 因此中短文件一般是免费的。 费用按 $FREEI_ PH_ rc_ name_ 输入长度计算 —— FREEI_ PH_ tgt_ name_ 输出长度不影响计费。

Yes — drop an .srt file on /translate/ and pick Spanish (es) as the target. The translator preserves every cue number and timestamp exactly; only the dialogue text is rewritten. For long films, the file streams through chunk-by-chunk so a 2-hour movie subtitle file still finishes in well under a minute. If you need to dub the translated track as audio, pipe the output into /voice/tts/ — pick a Spanish voice and you get a synced narration. For the reverse flow (audio file → translated subtitles), use /transcribe/ first, then this translator.

Idioms are the honest weak spot. Common ones ("piece of cake", "break a leg") usually map to the Spanish equivalent because they appear in the training corpus; novel or regional slang often gets literal-translated. If accuracy on idioms matters (marketing copy, fiction dialogue), drop a footnote in your prompt — "translate idiomatically, prefer natural Spanish" — and the model will look harder for an equivalent expression instead of a word-for-word rendering. For legal, medical, or code-heavy text, the engine is conservative on purpose — proper nouns and technical terms are left as-is or rendered in their conventional form.

是的, POST 到/v1/ translate/ with source="uk", 目标="es", 和文本="在 JSON 体中, 加上您的旁观符号。 回复返回“ 翻译 ” : “... ”, “ 检测来源 ” : “... ”, “ 模版 ” : “... ” 。 对于长的文件, 发送文件_ url= 而不是文本, API 将抓取、 块和缝合结果。 完整引用和 SDK Spets at/ api/ 。

Yes — the reverse direction lives at /translate/es-to-uk/ and uses the same engine routing in the opposite direction. Quality can differ asymmetrically: one direction may read more naturally than the other because the training corpus is rarely balanced. If you need a round-trip sanity check (translate Ukrainian → Spanish → Ukrainian again), do it manually in two passes — automatic round-trip is intentionally not exposed because it tends to mask errors rather than catch them.

诚实回答 : 在 Google Translate 和 DeepL 几个 BLEU 点内的 Free.ai NLLB-200 路由土地上, 谷歌翻译和 DeepL 在大多数公共基准中几个 BLEU 点内有Free.ai NLLB-200 路由 。 Google 因其更大的网络索引, 仍然对稀有的命名实体( 中层品牌、 特殊地名) 拥有优势 ; DeepL 经常因其文件级别限制而赢得长欧洲语言文件 。 Free.ai 的好处是: 上传文件没有字符上限, 没有签名用户的每日申请配额, 真正的API没有节流, 以及 SRT/ DOCX/ PDF 支持没有企业计划。 试试这两段中的同一段, / Translate/ never charge you to 。