Skip to main content
Use case

Best GPUs for Fine-Tuning

LoRA and QLoRA on one GPU, full fine-tunes on a node.

GPUs 7
Providers 61
From $0.140/hr

What this workload needs

Practical VRAM floor
24 GB
What to compare on
VRAM capacity · BF16 throughput · Memory bandwidth · Single-GPU cost

Recommended GPUs for Fine-Tuning

Ordered by suitability for this workload, not by price.

Sample Fine-Tuning GPU Pricing

ProviderPrice / hr
$0.580/hr
1×
$1.22/hr36mo
16×
$2.00/hr
1×
$2.60/hr
1×
Gcore logo
GcoreVirtual GPU
$2.70/hr
8×
$3.09/hr24mo
8×
Runpod logo
RunpodSecure Cloud
$3.49/hr
6×
$3.50/hr
1×
$4.65/hr36mo
8×

Showing 9 of 671 price points. Visit individual GPU pages above for full pricing.

How to choose a GPU for fine-tuning

Fine-tuning covers a wide range of memory requirements, and the method you choose matters far more than the model size. Full fine-tuning updates every weight and therefore carries the same optimizer-state cost as pretraining — several times the parameter count in bytes. Parameter-efficient methods train a small number of added weights instead, cutting the requirement to roughly the size of the frozen model plus activations.

LoRA freezes the base model and trains low-rank adapter matrices, typically a fraction of a percent of the original parameters. QLoRA goes further by holding the frozen base in 4-bit precision, which is what makes single-GPU fine-tuning of large models practical. In exchange you accept some quality ceiling relative to a full fine-tune, which for most task-adaptation work is not the binding constraint.

That splits the hardware decision cleanly. A QLoRA run on a 7B–13B model fits on a single 24 GB card. A LoRA run on a 70B model wants 48–80 GB. A full fine-tune of anything above about 7B needs a multi-GPU node with sharding and behaves like a training job — see the LLM training page for how to size that.

Because fine-tuning jobs are short and bursty compared with pretraining, they are a good fit for on-demand and spot capacity. Spot pricing is meaningfully lower but instances can be reclaimed, so checkpoint frequently enough that a reclaim costs minutes rather than hours. Compare on-demand and spot rates in the table below.

Related Reading

Frequently Asked Questions

Can I fine-tune a model on a single GPU?

Yes, with parameter-efficient methods. QLoRA on a 24 GB card handles models in the 7B–13B range; a 48 GB card extends that meaningfully, and 80 GB covers LoRA on most open-weight models available today. Full fine-tuning of models above roughly 7B still requires multiple GPUs with sharding.

What is the difference between LoRA and QLoRA?

LoRA freezes the base model and trains small low-rank adapters, holding the base weights at their normal precision. QLoRA additionally quantizes the frozen base to 4-bit, which cuts memory use enough to fit substantially larger models on one GPU. QLoRA is slower per step but often the only option on a single card.

Should I use spot instances for fine-tuning?

Spot capacity is cheaper but can be reclaimed with little warning, so it suits jobs that checkpoint frequently and tolerate restarts. Fine-tuning runs generally do. Use the pricing type filter above to compare on-demand and spot rates for the same GPU.

Related Use Cases

Browse Related Categories