Data as of November 18, 2026 · How the score is built
Qwen-VL-OCR
Decision readingQwen-VL-OCR is tracked, but not publicly ranked yet. The profile exposes 0 sourced benchmark rows and leaves unsupported fields blank until a published record exists.
Email me when its price, rank or availability changes.
Lineage
The sequence follows explicit supersedes links. Each score is estimated for that model; a relative can inform a sparse estimate but never sets a floor, so a newer release can score below an earlier one. Scores and prices remain blank when the corresponding public row or first-party rate is unavailable.
Base entry
Spec sheet
Each documented value carries its source. Missing fields stay visible as not sourced or not published, rather than disappearing from the page.
- API model ID
- Not published
- Context window
- Not disclosed
- Maximum output
- Not sourced yet
- Knowledge cutoff
- Not sourced yet
- Input modalities
- Not sourced yet
- Output modalities
- Not sourced yet
- Parameters
- Not disclosed by the provider
- Availability
- Available through Alibaba Cloud Model Studio as qwen-vl-ocr, the stable alias of the qwen-vl-ocr-2025-11-20 snapshot. The older qwen-vl-ocr-latest, qwen-vl-ocr-2025-04-13 and qwen-vl-ocr-1028 IDs were retired from the international Model Studio on October 10, 2026. The default maximum output is 4,096 tokens.
- Cloud regions
- Not tracked yet
- Lifecycle
- Established
- API capabilities
- Tool calling, structured outputs, and batch support are not tracked yet
- Prompt caching
- Not documented in the pricing record
- Self-host
- Weights are not published
- Rate limits
- Not tracked yet
How to read this profile
The visual layer above carries the decisions. These notes preserve the model, ranking, coverage, and family context behind the numbers.
We track Qwen-VL-OCR, but no weighted text-model benchmark result is published on the site yet. This page shows the metadata and separate protocol evidence we can verify now; a BenchLM score will appear only if compatible public evaluations land.
Qwen-VL-OCR is a proprietary model with a Not disclosed context window. No explicit reasoning mode is documented in this profile.
Available through Alibaba Cloud Model Studio as qwen-vl-ocr, the stable alias of the qwen-vl-ocr-2025-11-20 snapshot. The older qwen-vl-ocr-latest, qwen-vl-ocr-2025-04-13 and qwen-vl-ocr-1028 IDs were retired from the international Model Studio on October 10, 2026. The default maximum output is 4,096 tokens.
Qwen-VL-OCR is Alibaba's text-extraction model built on the Qwen3-VL architecture. Model Studio documents built-in tasks for document parsing, high-precision text localization, key-information extraction, table parsing, formula recognition, general text recognition and multilingual recognition, plus image rotation correction. Alibaba now recommends qwen3.5-ocr for new work. Alibaba publishes no benchmark values for this model, so the row has no scored fields.
The profile has no source-displayable benchmark row yet.
Last updated November 18, 2026. Runtime fields remain blank until a sourced snapshot exists.
Questions
How does Qwen-VL-OCR perform overall in AI benchmarks?
Qwen-VL-OCR does not have any source-displayable benchmark rows yet, so this profile does not assign a public score or rank. Documented specifications remain visible, while score-led charts and claims stay unavailable until a published evaluation can be attached to the exact model.
Does Qwen-VL-OCR have full benchmark coverage on BenchLM?
No. Qwen-VL-OCR currently has 0 source-displayable rows. The profile exposes published, non-generated evidence and leaves missing categories blank until an exact evaluation is available. Coverage describes how much was measured; it is not a penalty added to an individual benchmark result.
What is the context window size of Qwen-VL-OCR?
Qwen-VL-OCR has a reported context window of Not disclosed in the exact-model catalog record. The value stays visible, but the profile marks its source link as unavailable instead of presenting it as directly documented. Maximum output length remains separate because providers often publish a different limit.