What GPU do I need to run thinkingmachines/Inkling-Small?

266.0B parameters, published in BF16. View on Hugging Face

266.0B
Parameters
BF16
Native precision
InklingForConditionalGeneration
Architecture
image-text-to-text
Pipeline

Inkling-Small is published by thinkingmachines on Hugging Face, with 184,510 downloads and 392 likes to date. It's a InklingForConditionalGeneration model built for image-text-to-text, published natively in BF16.

VRAM required & cheapest live GPU fit

Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.

PrecisionWeight sizeRequired VRAMCheapest live fitGPUs neededEst. $/hr (full fit)
BF16495.4 GB594.5 GBRTX PRO 60007$9.63/hr
FP8 (quantized)247.7 GB297.2 GBAMD MI300X2$5.26/hr
INT4 (quantized)123.8 GB148.6 GBAMD MI300X1$2.63/hr
cheaper alt.RTX A50007$1.23/hr

A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.

INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.

Cheapest way to run Inkling-Small at its published (BF16) precision: 7× RTX PRO 6000, at $1.38/hr per GPU ($9.63/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

Inkling-Small: KV cache by context length

The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.

Grouped-query attention: every layer caches keys and values for a few shared KV heads. Cached per token: 172,032 bytes at 16-bit.

ContextKV cache, one sequence
4K0.66 GB
32K5.3 GB
128K21.0 GB
1M (model maximum)168.0 GB

Computed from the layer, head and window counts in the model's own configuration (thinkingmachines/Inkling-Small), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

Inkling-Small: common questions

Can Inkling-Small run on a single GPU?

No. At BF16 it needs 594.5 GB of VRAM, more than a single 32 GB desktop card holds. The cheapest capable card in the live feed is a 95.0 GB RTX PRO 6000, and it takes 7 of them.

How many GPUs do I need to run Inkling-Small?

7 at BF16. It needs 594.5 GB of VRAM and the cheapest capable live offer is a 95.0 GB RTX PRO 6000, so 7 of them come to $9.63/hr in total.

Does quantizing Inkling-Small lower the GPU bill?

Yes. At BF16 the cheapest live fit is 7 RTX PRO 6000 cards at $9.63/hr. At INT4 (quantized) it drops to one AMD MI300X at $2.63/hr, provided a quantized checkpoint exists for it.

Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.

More thinkingmachines models

All 2 thinkingmachines models: VRAM and GPU requirements

Alternatives at this size

Other models for image-text-to-text within about a third of Inkling-Small's 266.0B parameters, from other model lines.

More on Inkling-Small

Related reading: RTX PRO 6000 pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, and Best GPU for LLM inference.

Your own GPU cloud accounts

One console for the GPU clouds you already rent from. Your keys stay on your machine.

$20 a month, flat

Connect your accounts

One console for the GPU clouds you already use.

Connect your accounts for $20 a month, flat. Your provider bills the GPU.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.