Granite 4.2 8B vs Baidu Unlimited-OCR-2

Granite 4.2 8B 92

Model card 17, Intended use (best for), limitations (ethical considerations and limitations), architecture, parameters (8B), context length (128K native) and 12 tested languages are on the card. Training data 20, IBM's disclosure file for the 8B lists the datasets used in pre-training and post-training as machine-readable metadata, and the card describes the three training stages. Last change 20, the last commit, on 20 October 2026, replaced model.safetensors.index.json (titled "granite-4.2 index file fix"), 21 days before this check. Responsiveness 20, Of the 5 discussions that aren't pull requests (13 September to 5 November 2026), 4 have a reply from an ibm-granite member. Version policy 5, Granite 4.1 8B stays in its own repository and 4.2 came out in new ones. File health 10, Config, template and card agree on the architecture, the 131,072-token context and the thinking switch. 17 + 20 + 20 + 20 + 5 + 10 = 92.

Baidu Unlimited-OCR-2 50

The card covers intended use and the new attention, and misses limitations, parameters, context length, languages and a cut-off (5). Training data is described by mix and labelling with no datasets named and no cut-off (5). The card changed on 2 November 2026 and the SGLang wheel on 29 October (20). Baidu's uploader replied in 1 of the 5 Hub discussions, a few (5). The first model stays in its own repository without a note pointing here (5), and the files agree with the card (10).

Granite 4.2 8B 95

Memory 30, IBM's own 4-bit MLX build granite-4.2-8b-q4-mlx is 4.95 GB, and 4.95 GB × 1.2 = 5.9 GB, within 8 GB. Its Q4_0 GGUF is 5.06 GB and Ollama's library build granite4.2:8b (5.3 GB) fits 8 GB too. Runtimes 25, Released versions run the granite architecture in llama.cpp (granite, b12242), vLLM (GraniteForCausalLM in the v0.33.0 registry), SGLang (granite.py at v0.5.23), Transformers (v5.22.2) and Ollama (its own granite4.2 library entry, 8b tag). Builds 15, IBM publishes FP8, MXFP4 and NVFP4 safetensors builds, a GGUF repository with Q4_0 to Q8_0 and BF16 files, and 4-bit, 8-bit and BF16 MLX builds, so quantised builds at two precisions or more. Terms 15, Apache 2.0, an OSI-approved licence, with no use policy or other terms added on the card. Download 10, the Hub API reports gated false for the BF16, FP8, MXFP4, NVFP4, GGUF and MLX repositories, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps one inference provider (DeepInfra, live), short of the two the line needs. 30 + 25 + 15 + 15 + 10 + 0 = 95.

Baidu Unlimited-OCR-2 55

Memory earns the full 30, since the only build is 6.69 GB of BF16 weights that need about 8 GB with the fifth added. Runtimes score 0. Released vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.1 know the first Unlimited-OCR but not the sparse attention this one adds, Baidu's own routes are remote code in Transformers and a customised SGLang wheel, llama.cpp b12111 has nothing for it, so Ollama has nothing either, and LM Studio couldn't be checked. Builds score 0, as Baidu publishes no quantised build (16 exist, all by others). Terms get 15 for MIT with nothing added. Download gets 10 for an ungated repository, and hosted too 0, with no inference provider mapped and the card's Baidu Cloud line unconfirmed.

Granite 4.2 8B 55

File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, the files sit in the ibm-granite organisation, which IBM's Granite docs and the GitHub README link to (10). Safety evaluation 0, no safety results on the card. Agent guidance 5, General cautions. Licence risk 15, Apache 2.0 has no use policy, field-of-use limit, threshold or change clause, and the card's licence link resolves. Security programme 5, www.ibm.com/.well-known/security.txt names IBM PSIRT, read for the 3B listing on 4 November 2026 (5). 15 + 15 + 0 + 5 + 15 + 5 = 55.

Baidu Unlimited-OCR-2 45

File safety gets 15, safetensors only but loaded with trust_remote_code or through a prebuilt SGLang wheel from the repository. Provenance gets 15 for files in Baidu's verified organisation, linked from its GitHub organisation, with hashes for every file. Licence risk keeps 15, since MIT has none of the deductions. Safety evaluation, agent guidance and the security programme score 0, with no safety results, no cautions about use and no security contact found.

Granite 4.2 8B 85

Chat template 20, chat_template.jinja in the repository, with roles, tools, tool responses, the thinking switch and low effort. Tool-calling format 25, the card has tool-calling sections for vLLM and SGLang, declares tools with OpenAI's function schema and names the parser to use, qwen3_coder, which both runtimes ship in the released versions read. Trained tool calling 20, the template loops over every entry in an assistant turn's tool_calls, so it renders several calls in one turn, and the card names tool calling and agentic workflows as what it's best for. Structured output 0, the card doesn't document JSON or JSON Schema output or how to ask for it. Reasoning control 10, the card documents thinking on by default, non-thinking and low-effort modes per request through the template (enable_thinking and low_effort), with the reasoning returned apart from the answer. Context 10, 131,072 tokens natively per the card and config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.

Baidu Unlimited-OCR-2 75

Read for a document parser, the tool-calling, trained tool calling and structured-output lines stand for what it takes and returns. Baidu documents the page images, the prompt, the request settings and the block output, and ships a converter for the server's output (25). It was trained to read many pages in one request (20). The block format with classes, boxes and HTML tables, and its conversion to Markdown, are documented with how to get them (15). The prompt is built in code, with no Jinja template in the repository (10). Reasoning control scores 0, and the context 5, trained at up to 64K tokens.