Qwen3 1.7B VRAM requirements
Fine-tuning Qwen3 1.7B takes about 4.7 GB of GPU memory with QLoRA, 7.2 GB with LoRA on 16-bit weights and 35 GB for full fine-tuning, at 2,048 tokens per sequence. Running it takes 5.0 GB in 16-bit or 2.1 GB in 4-bit with a 8K-token context.
Fine-tuning memory
| Method | Weights | Training state | Activations | Total | Smallest single GPU | 80 GB GPUs needed |
|---|---|---|---|---|---|---|
| QLoRA (4-bit base) | 1.5 GB | 0.3 GB | 2.9 GB | 4.7 GB | RTX 3090 (24 GB) | 1 |
| LoRA (16-bit base) | 4.1 GB | 0.3 GB | 2.9 GB | 7.2 GB | RTX 3090 (24 GB) | 1 |
| Full fine-tuning | 4.1 GB | 28 GB | 2.9 GB | 35 GB | A100 40GB (40 GB) | 1 |
On a 24 GB card such as the RTX 4090: QLoRA: yes, about 4.7 GB at 2K tokens, batch 1, rank 16; up to 8K-token sequences at batch 1 or batch 6 at 2K, LoRA rank up to 512.
Inference memory
| Precision | Weights | KV cache at 8K | Total | At 32K context | Smallest single GPU |
|---|---|---|---|---|---|
| 16-bit (BF16/FP16) | 4.1 GB | 0.9 GB | 5.0 GB | 7.8 GB | RTX 3090 (24 GB) |
| 8-bit | 2.0 GB | 0.9 GB | 3.0 GB | 5.8 GB | RTX 3090 (24 GB) |
| 4-bit | 1.1 GB | 0.9 GB | 2.1 GB | 4.9 GB | RTX 3090 (24 GB) |
Which GPUs fit Qwen3 1.7B
One GPU unless a count is shown. Follow a GPU's name for its maximum sequence length, batch size, LoRA rank and rental cost.
| GPU | QLoRA | LoRA | Full fine-tuning | Run, fp16 | Run, int8 | Run, int4 |
|---|---|---|---|---|---|---|
| RTX 3090 24 GB | Yes | Yes | 2× | Yes | Yes | Yes |
| RTX 4090 24 GB | Yes | Yes | 2× | Yes | Yes | Yes |
| RTX 5090 32 GB | Yes | Yes | 2× | Yes | Yes | Yes |
| L40S 48 GB | Yes | Yes | Yes | Yes | Yes | Yes |
| A100 40GB 40 GB | Yes | Yes | Yes | Yes | Yes | Yes |
| A100 80GB 80 GB | Yes | Yes | Yes | Yes | Yes | Yes |
| H100 SXM 80 GB | Yes | Yes | Yes | Yes | Yes | Yes |
| H200 141 GB | Yes | Yes | Yes | Yes | Yes | Yes |
| B200 180 GB | Yes | Yes | Yes | Yes | Yes | Yes |
What's specific to Qwen3 1.7B
- The safetensors hold 2.03B parameters including the tied embeddings, more than the name suggests.
- Full fine-tuning (about 33 GB before activations) fits on one 48 GB card.
| Architecture | Qwen3 1.7B |
|---|---|
| Parameters | 2.03B |
| Layers | 28 |
| Hidden size | 2,048 |
| MLP width | 6,144 |
| Attention heads / KV heads | 16 / 8 (head dim 128) |
| Vocabulary | 151,936 tokens, tied embeddings |
| Context | 32K tokens |
| License | Apache 2.0 |
| Released | April 2025 |
Try other settings
Pre-filled for Qwen3 1.7B. Change the sequence length, batch, LoRA rank, context or GPU.
| Job | Memory | RTX 4090 (24 GB) | Smallest single GPU |
|---|---|---|---|
| QLoRA (4-bit base)2K tokens × batch 1, rank 16 | 4.7 GB | Fits | RTX 3090 (24 GB) |
| LoRA (16-bit base)2K tokens × batch 1, rank 16 | 7.2 GB | Fits | RTX 3090 (24 GB) |
| Full fine-tuning2K tokens × batch 1 | 35 GB | 2 GPUs | A100 40GB (40 GB) |
| Inference, 16-bit (BF16/FP16)8K-token context × 1 sequence | 5.0 GB | Fits | RTX 3090 (24 GB) |
| Inference, 8-bit8K-token context × 1 sequence | 3.0 GB | Fits | RTX 3090 (24 GB) |
| Inference, 4-bit8K-token context × 1 sequence | 2.1 GB | Fits | RTX 3090 (24 GB) |
A job fits when the estimate is within 90% of the card's memory. Training assumes gradient checkpointing and FlashAttention; multi-GPU counts assume the memory splits evenly (FSDP, ZeRO-3 or tensor parallelism).
How we estimate it
Every figure comes from the model's published architecture (layers, hidden size, attention and KV heads, vocabulary) rather than a rule of thumb, using the same functions as the calculator above. Sizes are in GB (10⁹ bytes).
- Full fine-tuning: 16 bytes per parameter for mixed-precision Adam (bf16 weights and gradients, fp32 master weights and two moments), as in the ZeRO paper.
- LoRA: frozen bf16 weights (2 bytes per parameter) plus 16 bytes per adapter parameter, rank 16 on every linear layer. For mixture-of-experts models, adapters go on attention only and the experts stay frozen.
- QLoRA: NF4 weights with double quantisation (4.127 bits per parameter); embeddings and the output head stay in bf16, as bitsandbytes leaves them.
- Activations: gradient checkpointing and FlashAttention. Each layer's bf16 input is kept, one layer is recomputed at a time, and the output logits take 8 bytes per vocabulary entry per token (fp32 values and gradients). Chunked cross-entropy, as in Unsloth or Liger kernels, cuts that last term.
- Inference: 2, 1 or about 0.56 bytes per weight (4-bit with group-wise scales), plus an fp16 KV cache of 2 × layers × KV heads × head dim × 2 bytes per token; sliding-window layers only cache their window.
- Fits means the estimate is within 90% of the card's listed memory; the rest covers the CUDA context, kernels and fragmentation. Multi-GPU counts assume memory splits evenly.
Frequently asked questions
- Can I fine-tune Qwen3 1.7B on a 24 GB GPU?
- On an RTX 3090 or 4090 (24 GB): QLoRA: yes, about 4.7 GB at 2K tokens, batch 1, rank 16; up to 8K-token sequences at batch 1 or batch 6 at 2K, LoRA rank up to 512. LoRA: yes, about 7.2 GB at 2K tokens, batch 1, rank 16; up to 8K-token sequences at batch 1 or batch 5 at 2K, LoRA rank up to 512. Estimates use gradient checkpointing and leave 10% of memory free.
- How much VRAM do you need to run Qwen3 1.7B?
- About 5.0 GB in 16-bit and 2.1 GB in 4-bit, at 8K tokens of context. The smallest single GPU here for 4-bit is the RTX 3090 (24 GB); for 16-bit, the RTX 3090 (24 GB).
- How many GPUs does full fine-tuning Qwen3 1.7B take?
- About 35 GB with mixed-precision Adam at 2K tokens, so at least 1 × 80 GB H100 with the training state sharded (FSDP or ZeRO-3). LoRA needs 7.2 GB and QLoRA 4.7 GB.
- How long a context can Qwen3 1.7B handle on an 80 GB GPU?
- Its KV cache costs 3.8 GB at the full 32K tokens (fp16 cache). On one 80 GB GPU: 32K tokens with 16-bit weights, 32K tokens with 4-bit weights.
Related
- Qwen3 0.6B VRAMAlibaba Qwen
- Qwen3 4B VRAMAlibaba Qwen
- Qwen3 8B VRAMAlibaba Qwen
- Qwen3 14B VRAMAlibaba Qwen
- Qwen3 32B VRAMAlibaba Qwen
- Qwen3 30B-A3B VRAMAlibaba Qwen
Terms used on this page: LoRA, QLoRA, KV cache, gradient checkpointing, quantization. For any model size, use the fine-tuning VRAM calculator; for the method in depth, the Academy lesson Memory first: what hardware can train what.
Sources
- Hugging Face. Qwen/Qwen3-1.7B config.json
- Alibaba Qwen. Qwen/Qwen3-1.7B model card
- Alibaba Qwen. Qwen3 Technical Report (arXiv:2505.09388)
- Dettmers et al., 2023. QLoRA: Efficient Finetuning of Quantized LLMs (arXiv:2305.14314)
- Hu et al., 2021. LoRA: Low-Rank Adaptation of Large Language Models (arXiv:2106.09685)
- Rajbhandari et al., 2019. ZeRO: Memory Optimizations Toward Training Trillion Parameter Models (arXiv:1910.02054)
- Korthikanti et al., 2022. Reducing Activation Recomputation in Large Transformer Models (arXiv:2205.05198)
- Chen et al., 2016. Training Deep Nets with Sublinear Memory Cost (arXiv:1604.06174)
Architecture read from config.json and parameter count from the Hugging Face safetensors metadata on 15 November 2026.
Find out if you need to fine-tune at all.
Kojen's prompt tuning and model search run for real on your own test cases, on hosted models. Measure the cheaper levers before you rent a GPU.
Start training free