惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

阮一峰的网络日志
阮一峰的网络日志
雷峰网
雷峰网
Last Week in AI
Last Week in AI
T
Tailwind CSS Blog
V
Visual Studio Blog
Jina AI
Jina AI
博客园 - 司徒正美
The Cloudflare Blog
Hugging Face - Blog
Hugging Face - Blog
博客园_首页
S
SegmentFault 最新的问题
博客园 - 三生石上(FineUI控件)
有赞技术团队
有赞技术团队
小众软件
小众软件
V
V2EX
Apple Machine Learning Research
Apple Machine Learning Research
美团技术团队
博客园 - 【当耐特】
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
IT之家
IT之家
WordPress大学
WordPress大学
爱范儿
爱范儿
月光博客
月光博客
大猫的无限游戏
大猫的无限游戏

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
What I learned testing AI translation tools in 2026 (Deep...
Auke de Haan · 2026-05-28 · via DEV Community

Auke de Haan

Translation used to be a settled question. DeepL was best at European languages, Google Translate was best at coverage, and you picked whichever fit your stack. In 2026 the picture is more interesting, because the big LLMs (Claude, ChatGPT, Gemini, Mistral) now match or beat the specialised tools on the same prompt, with one important catch.

I spent a couple of weeks pushing translation tasks through six tools, in five language pairs (Dutch, German, French, Spanish, Polish, all paired with English). Here is what actually shifted.

DeepL still wins for raw translation, but the gap shrunk

For a clean source-to-target translation with no instructions, DeepL still produces the most native-sounding output in European languages. Compound nouns, idioms, register choice, it gets these right more often than the LLMs. That has not changed.

What has changed: the gap is now small. On EN to NL, EN to DE and EN to FR, Claude and GPT-5 are within shouting distance. For most marketing copy you would publish the LLM output without editing.

The thing LLMs do that DeepL cannot

DeepL translates. It does not adapt. If you ask DeepL to translate a US blog post for a Dutch audience, you get a literal Dutch version, references to American cultural artefacts intact, dollars not euros, the lot.

Ask Claude or GPT-5 the same thing with a one-line instruction ("adapt for a Dutch audience, replace US-specific references, keep tone friendly but direct") and the output is a Dutch blog post, not a Dutch translation. References get localised, examples are swapped, tone shifts.

For anything you actually publish, that is a much bigger productivity win than the small quality edge DeepL holds on raw fidelity.

When to use which

My current default after the testing:

  1. Short, neutral, high-fidelity translation (legal text, product descriptions, UI strings). DeepL.
  2. Long-form content that needs to feel native and adapted (blogs, emails, marketing). Claude with explicit instructions about audience and tone.
  3. Bulk volume on a tight budget. Mistral Le Chat. Cheaper than the US LLMs, surprisingly competitive on FR and IT.
  4. Rare or low-resource language pairs. Gemini, which seems to have benefited most from large-scale multilingual training in the last year.

Two non-obvious gotchas

A pair of things that bit me during testing:

  • LLMs hallucinate brand names. If your source mentions a specific product, an LLM will sometimes "correct" it to a more famous similar product. DeepL never does this. Worth catching with a glossary or a post-translation diff.
  • Privacy matters more than people remember. Pasting a client contract into a US LLM is not the same as running it through an EU-hosted DeepL Pro account. For regulated content (legal, HR, medical) the hosting story still matters in 2026.

I compiled the full hands-on comparison, including how each tool handles Dutch specifically and what the real GDPR position looks like, in this 2026 AI translation tool guide. Curious how others here are mixing LLMs and dedicated translation tools, especially for less-common language pairs. What is winning in your stack?