Granite 4.2 30B vs Bonsai Image Binary 4B
At a Glance
| Compare | Bonsai Image Binary 4BPrismML | |
|---|---|---|
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | $0.16Deepinfra ↗ · Sep 22, 2026 | Not reported |
| Output priceFrom · USD / 1M tokens | $0.65Deepinfra ↗ · Sep 22, 2026 | Not reported |
| Context windowMaximum documented tokens | 131K | Not reported |
| Model facts checked | Sep 2, 2026View model evidence → | Sep 18, 2026View model evidence → |
Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →
Available Benchmarks
Side-by-Side Facts
| Field | Granite 4.2 30B | Bonsai Image Binary 4B |
|---|---|---|
| Developer | IBM | PrismML |
| Family | Granite 4 2 | Bonsai Image 4b |
| Model | Granite 4.2 30B | Bonsai Image Binary 4B |
| Version | Granite 4.2 30B | Bonsai Image Binary 4B |
| Lifecycle | active | active |
| Released | 2026-08-25 | 2026-05-18 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text | Text |
| Output modalities | Text | Image |
| Context window | 131K | Unknown |
| Total parameters | 29.3B | 4B |
| Active parameters | Unknown | Unknown |
| License | apache-2.0 | apache-2.0 |
| Open weights | Yes | Yes |
| API available | Yes | No |
| Self-hostable | Yes | Yes |
| Provider access | Deepinfra (Standard) | Unknown |
| Capabilities | chat, generation, reasoning, structured_outputs, tools | generation |
| Base model | Unknown | FLUX.2 Klein 4B |
| Default resolution | Unknown | 512 × 512 |
| Transformer size | Unknown | 0.93 GB |
| Weight format | Unknown | Binary weights with FP16 group scales |
Granite 4.2 30B Capabilities
Bonsai Image Binary 4B Capabilities
Primary Evidence
Sources and Freshness
Questions
Granite 4.2 30B vs Bonsai Image Binary 4B FAQs
Is Granite 4.2 30B or Bonsai Image Binary 4B better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Granite 4.2 30B and Bonsai Image Binary 4B, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Granite 4.2 30B or Bonsai Image Binary 4B?+
Only Granite 4.2 30B has a directly sourced input price: $0.16 per million tokens. Only Granite 4.2 30B has a directly sourced output price: $0.65 per million tokens.
Which has a larger context window, Granite 4.2 30B or Bonsai Image Binary 4B?+
Neither model has a larger sourced context window in this comparison. Granite 4.2 30B is 131K and Bonsai Image Binary 4B is —.
Which performs better in benchmarks, Granite 4.2 30B or Bonsai Image Binary 4B?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Granite 4.2 30B or Bonsai Image Binary 4B be self-hosted?+
Both models have the same recorded self-hosting status: supported. Granite 4.2 30B is open weight; Bonsai Image Binary 4B is open weight.
Can Granite 4.2 30B and Bonsai Image Binary 4B understand images?+
Granite 4.2 30B is not documented with image input; Bonsai Image Binary 4B is not documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Granite 4.2 30B or Bonsai Image Binary 4B?+
Neither has a larger sourced maximum output. Granite 4.2 30B is — and Bonsai Image Binary 4B is —.
Do Granite 4.2 30B and Bonsai Image Binary 4B support reasoning and tool use?+
Granite 4.2 30B: reasoning and tool calling. Bonsai Image Binary 4B: none of these features are definitively sourced. Feature support does not establish relative quality.
Which is available from more inference providers, Granite 4.2 30B or Bonsai Image Binary 4B?+
Granite 4.2 30B has 1 sourced provider route; Bonsai Image Binary 4B has 0, so Granite 4.2 30B has broader tracked availability.
Which offers better value, Granite 4.2 30B or Bonsai Image Binary 4B?+
There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.