What GPU do I need to run MuScriptor/muscriptor-large?

1.4B parameters, published in F32. View on Hugging FaceGated

1.4B
Parameters
F32
Native precision
Unknown
Architecture
text-generation
Pipeline

muscriptor-large is published by MuScriptor on Hugging Face, with 5,345 downloads and 377 likes to date. It's a unlisted-architecture model built for text-generation, published natively in F32, and gated: you'll need to accept the model's terms on Hugging Face before downloading weights.

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)
FP325.1 GB6.1 GBQuadro M40001$0.046/hr
FP8 (quantized)1.3 GB1.5 GBRTX 5060 Ti1$0.145/hr
INT4 (quantized)0.6 GB0.8 GBRTX 30701$0.088/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 muscriptor-large at its published (F32) precision: 1× Quadro M4000, at $0.046/hr per GPU ($0.046/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

muscriptor-large: common questions

Does muscriptor-large fit on a 8 GB GPU?

Yes. At FP32 it needs 6.1 GB of VRAM, so an 8 GB card holds it with 1.9 GB to spare. A 6 GB card is not enough for it at FP32.

Do I need approval to download muscriptor-large?

Yes. MuScriptor gates this repository on Hugging Face, so you have to accept its terms with a signed-in account before the weights will download. It does not change the 6.1 GB the model needs once you have them.

Can muscriptor-large run in 16-bit instead of FP32?

Yes. Its published weights are FP32, 5.1 GB, or 6.1 GB once inference overhead is added. Loading the same weights in 16 bits halves that to 2.5 GB, or 3.1 GB with overhead. That moves it onto a 6 GB card instead of an 8 GB one. How much accuracy the cast costs is model-specific and is not measured here.

What is the least VRAM muscriptor-large can run in?

0.8 GB, at INT4 (quantized), which fits a 6 GB card, against 6.1 GB at FP32. That row assumes an INT4 checkpoint has actually been published for this model, so check its Hugging Face page before planning around it.

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

MuScriptor models

More on muscriptor-large

Related reading: H100 pricing and specs, How much VRAM you need for LLMs, and What AI inference is.

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.