Skip to content
Model infoModelsSnapshot: 15 Oct 2026

DeepL / Classic translation generation

DeepL Classic

Historical translation generation compared with DeepL’s next-generation LLM in its 2024 announcement. A current API parameter does not reliably pin these original weights.

historicalClosed weightsText translation
Official documentation (opens in a new tab)Reviewed 13 Oct 2026
2 of 16 specification fields collected
Context windowNot collectedAwaiting source review
Maximum outputNot collectedAwaiting source review
Input billingNot collectedDeepL Translator · historical
Output billingNot collectedNo inferred price

Specifications

Provider-documented facts. “Not collected” means we have not verified that field yet, not that the feature is unsupported.

Context / input limit
Not collected
Maximum output
Not collected
Reasoning
Not collected
Tool calling
Not collected
Structured output
Not collected
Streaming
Not collected
Batch processing
Not collected
Fine-tuning
Not collected
Knowledge cutoff
Not collected
Release date
Not collected
Parameters
Not collected
Architecture
Not collected

The reviewed announcement distinguishes the classic model from the next-generation LLM without specifying an exact original architecture or parameter count.

Languages
Not collected
Context caching
Not collected

Access & pricing

Prices belong to an endpoint and billing tier. A provider listing does not guarantee access for every account or region.

DeepL Translator · historical

Provider source (opens in a new tab)
API model ID
Not collected

No public fixed model/checkpoint selector is documented.

Access
Historical Translator generation documented in the July 2024 comparison. A currently accessible exact checkpoint has not been established.
Regions
Provider-managed; contractual residency options, no universal region pin

Endpoint pricing has not been collected. Check the provider for applicable rates.

Data & enterprise terms

Current terms are linked for context; the exact original release agreement and retention configuration were not collected.

Read the service policy (opens in a new tab)

Caching

Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.

01 / INITIAL INPUTProcess & retain

The system processes eligible input and retains reusable state.

02 / LATER REQUESTCheck available state

Reuse depends on matching input, session state and the cache policy.

03 / CACHE HITReuse & generate

Reusing state can reduce repeated work. Any charges follow the billing rules below.

DeepL Translator · historical

Not verified

No discounted prompt-cache contract collected. Glossaries, translation memories, retained files and reconnectable sessions are not proof of model prompt caching.

How it works
Not collected

No discounted prompt-cache contract collected. Glossaries, translation memories, retained files and reconnectable sessions are not proof of model prompt caching.

Minimum reusable input
Not collected

No discounted prompt-cache contract collected. Glossaries, translation memories, retained files and reconnectable sessions are not proof of model prompt caching.

Lifetime & refresh
Not collected

No discounted prompt-cache contract collected. Glossaries, translation memories, retained files and reconnectable sessions are not proof of model prompt caching.

How to enable it
Not collected

No discounted prompt-cache contract collected. Glossaries, translation memories, retained files and reconnectable sessions are not proof of model prompt caching.

Usage fields
Not collected

No discounted prompt-cache contract collected. Glossaries, translation memories, retained files and reconnectable sessions are not proof of model prompt caching.

Billing rules
Not collected

No discounted prompt-cache contract collected. Glossaries, translation memories, retained files and reconnectable sessions are not proof of model prompt caching.

Limits & data boundaries
Not collected

No discounted prompt-cache contract collected. Glossaries, translation memories, retained files and reconnectable sessions are not proof of model prompt caching.

No verified cache rate for this endpoint. An empty rate is not a zero charge.

What the measurements say

No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.

Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.

The record behind the model

Why it is included

DeepL terms identify proprietary models and restrict copying or reverse engineering of the service. This is a documented proprietary generation or explicitly identified managed/research family, not a claim that every hosted partner component is a DeepL checkpoint. Public model weights are not provided by the cited release or API documentation.

Classification evidence (opens in a new tab)

Sources reviewed