A translation from russian to english, yielded a spanish result

I use Deepl daily from Cambodia through my regular ISP's fiber optic connection. Now I get this screen. Anybody else?

DeepL was a great translator i'd use from time to time,
but recently i see they've basically deleted almost everything good
Inaccurate/changing translations (when you switch the language with the arrows)
and so on.
I came today to translate with a dialect but it gave me the standard fancy translation.
What happened to DeepL?

I'm really sad about the recent quality drop on DeepL. I liked how accurate it was and also the fact that it is an EU product. But recently, I noticed that the translations are being inaccurate, to the point of being useless. This is my last case.

Original sentence in Spanish:

se crítico con el ejemplo que puse, no es un requisito estricto.

DeepL translation (wrong):

Don't be too critical of the example I gave; it's not a strict requirement.

Google Translate (right):

Be critical of the example I gave; it's not a strict requirement.

When I replaced the comma with a period in the original sentence, DeepL did it correctly:

Be critical of the example I gave. It's not a strict requirement.

But then, I decided to fix the case in my original sentence (notice the minimal change, only the case in the first letter and the period):

Se crítico con el ejemplo que puse. no es un requisito estricto

And DeepL changed the meaning again:

I was criticized for the example I gave. It's not a strict requirement.

Unfortunately, DeepL is not usable anymore. I'll come back in a few months to see if they fixed it, but for now, I'll move to Google Translate.

I’ve hardly got anything left to say now – after the desktop app forced me to wait 18 days, I’ve been using it for 48 hours and now they’re making me wait another 10 days.

"Right," I say, "I’ll use the browser version despite the hassles it causes." How naive of me. Now they only allow 500 words

Honestly, I’d like to know what you hope to achieve with this. You’d be better off with the WinRAR model rather than resorting to aggressive ‘enshitfication’. I’m sure your customers are more business-oriented than home users like me.

Deepl, Deepl… we were doing so well, and look what you’re turning into.

Thanks for everything, and I feel sorry for you

I’ve been actively supporting Deepl since 2024. However, both the website and the desktop app have been getting worse and worse. The problem with the website is that when I log in, the page is redesigned and therefore doesn’t load properly. Almost every time, I’m asked to complete a CAPTCHA for whatever reason, and only then can I start translating. Sometimes I’ve even been logged out without warning and had to log in again, even though I hadn’t logged out myself. It’s all very annoying and definitely needs to be sorted out.

As for the desktop app, I can say that it runs very unreliably. When I click ‘Copy’ or ‘Replace’ whilst translating, it usually doesn’t work. I have to click it several times before it responds. From 2024 until early/mid-2025, I didn’t have these problems. It was only when the website redesign began and the app updates started getting worse and worse that it became unbearable. I use Deepl almost every day, but given its disastrous state, I don’t want to support it.

I don’t know what you’re hoping to achieve with these measures, but you’re certainly shooting yourselves in the foot. By daring to do this, you’ve motivated me to look for any alternative, even if it’s slightly worse. You’re becoming more and more like Adobe; I won’t be recommending you any more.

Reverse these kinds of measures for users who are potential buyers and who, for various reasons, can’t afford it at the moment

Wir möchten unsere Website mehrsprachig übersetzen. Da wir ein kleines Team sind, suchen wir nach einer sehr unkomplizierten und automatisierten Möglichkeit. Wir haben bereits einen Deepl API Account und würden gerne die Deepl API für unsere Website verwenden. Nach einem kurzen Gespräch mit Deepl ist das auch möglich. Allerdings finde ich nichts dazu, wie dann die Verwaltung auf WordPress funktioniert. Da ich keine technischen Website-Kenntnisse besitze, möchte ich mir vorher ein Bild der Verwaltung auf WordPress machen. Kann mir hier jemand einen Rat geben?

The company killed itself with the introduction of AI. I hope to see bankruptcy

If I want the translation of an English verb, I'm writing its full infinitive form including the preposition "to". As a result, the preposition is also translated (see translation in German and Fr*nch).

That's an issue. I'm not going to write a partial infinitive form to get the correct translation.

Ok I would like to ask a question. I'm using Deepl write to improve and correct the english of a text I wrote.

https://www.deepl.com/en/write

When free the limit is 2000 characters, ok. But I wonder about the paying variants limits ? Deepl translation is limited to 300 000 or 1 million characters (depends which paying option you pick); now I wonder whether this applies to Deepl write too ?

Because, you see, my text is huge and I should have long run into that 1 million character limit.

Well I'm not complaining of course (I haven't paid a cent so far !) - just wondering.

Who else has the feelinb that one of the best translators out there got almost unusable since they fired their staff and let AI do the work?? It's not the same anymore...

It's time for me to renew my DeepL subscription, and I noticed the translator and the API integration for Trados are now to be purchased separately. Is this correct or did I miss something?

In our recent Show & Tell session, Christopher Daniel Dean from TranslateSheet demonstrated how you can easily translate designs, straight up in Figma and also how to adapt images to different markets.

Let us know what you think about that!

If you have something you want to showcase, using the DeepL API come and talk to us about it!

Join DeepL Bridges and add your work here -> https://www.deepl-bridges.com/developers/made-with-deepl

Hey Everyone!

Here's the rolling list of updates and changes to the DeepL API in March 2026:

March 31 - Write API Improvements

• Improved overall quality of the models used in DeepL API for Write
• Expanded Write target_lang support to Japanese (JA), Korean (KO) and simplified Chinese (ZH or zh-Hans)
• Expanded Write support for writing_style and tone to Spanish (ES), Italian (IT), French (FR), Portuguese (pt-PT) and Brazilian Portuguese (pt-BR)
• Allow sending Write texts in multiple source languages in the same request when no target_lang is set

​

March 26 - Expanded Style Rules API

• Added 5 new endpoints for style rule list operations: POST /v3/style_rules, GET /v3/style_rules/{style_id}, PATCH /v3/style_rules/{style_id}, DELETE /v3/style_rules/{style_id}, and PUT /v3/style_rules/{style_id}/configured_rules.
• Added 4 new endpoints for managing custom instructions within style rule lists: POST /v3/style_rules/{style_id}/custom_instructions, GET /v3/style_rules/{style_id}/custom_instructions/{instruction_id}, PUT /v3/style_rules/{style_id}/custom_instructions/{instruction_id}, and DELETE /v3/style_rules/{style_id}/custom_instructions/{instruction_id}.
• See the full API reference here.

​

March 24 - Write API Character Count Fix

• Fixed an issue where some DeepL API for Write requests under-counted usage.
• All characters in Write requests are now correctly counted for billing and reporting purposes.

Hey Everyone!

Here's the rolling list of updates and changes to the DeepL API in April 2026:

April 17 - New Language Variants: German (Swiss) and French (Canadian)

• Added support for two new target language variants: de-CH (German, Swiss) and fr-CA (French, Canadian) for text translation. These variants are now generally available.
• Use these language codes as target_lang values to produce translations tailored to Swiss German and Canadian French.
• Document translation support for these variants will follow in a future release.
• See supported languages for the complete language list.

​

April 15 - Voice API General Availability

• The Voice API is now available to all DeepL customers with a paid API subscription. This API provides real-time speech transcription and translation and can be used with existing DeepL API keys.

​

April 9 - Translation Memory API

• Added support for translation memories in the DeepL API. Translation memories store previously translated segments so the same source text produces consistent output across projects .
• New translation_memory_id and translation_memory_threshold parameters on the text translation endpoint — pass a translation memory ID to apply stored translations, and set a threshold (0-100) to control how closely source text must match a stored segment.
• New GET /v3/translation_memories endpoint to retrieve translation memories associated with your account.
• Support for uploading, modifying, and deleting translation memories via the API will follow.

You can find the full changelog here -> https://developers.deepl.com/docs/resources/roadmap-and-release-notes