MedGemma FineTuned needs about 4.1 GB of memory at Q4_K_M (a 2.5 GB file) with an 8K context window, so it fits on a 6 GB GPU. This repository has 3 quants, from 2.5 GB (Q4_K_M) to 7.8 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 4.6 GB.
MedGemma FineTuned – 3.88B parameter vision model
MedGemma FineTuned is a 3.88B parameter vision model based on google/medgemma-4b-it. It has been fine‑tuned for medical image tasks and supports an 131072 token context window. The model is released under the Apache‑2.0 license.
Good at
- Vision tasks
- Image‑to‑image pipelines
- Fine‑tuned medical content
Limits
- No non‑vision capabilities
- Requires 8k context for memory estimates
- Apache‑2.0 license
Best for
- Medical image analysis
- Clinical image generation
- Research on medical vision models
Who it’s for. Developers building medical vision applications and researchers needing a fine‑tuned gemma3 model for image‑to‑image tasks.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 2.5 GB | 4.1 GB | Fits | Get file → | |
| Q8_0 | 4.1 GB | 5.8 GB | Fits | Get file → | |
| F16 | 7.8 GB | 9.4 GB | Too big | Get file → |
For 8GB VRAM, the Q4_K_M quant (~4.1GB at 8k context) is suitable. With 12GB VRAM, Q8_0 (~5.8GB) works well. If 16GB VRAM is available, F16 (~9.4GB) can be used. Memory estimates are approximate.
What GPU do you need for MedGemma FineTuned?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: no quant fits at an 8K context.
- 6 GB VRAM: the best quant that fits is Q8_0 (4.1 GB file, about 5.8 GB in use).
- 8 GB VRAM: the best quant that fits is Q8_0 (4.1 GB file, about 5.8 GB in use).
- 12 GB VRAM: the best quant that fits is F16 (7.8 GB file, about 9.4 GB in use).
Which MedGemma FineTuned quant should you choose?
Q4_K_M is the usual starting point for MedGemma FineTuned: it balances file size and quality well. Here it is a 2.5 GB file.
The Q8_0 file is 4.1 GB, about 1.7 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about MedGemma FineTuned
How much VRAM does MedGemma FineTuned need?
About 4.1 GB at Q4_K_M with an 8K context window. That is the 2.5 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run MedGemma FineTuned on an 8 GB GPU?
Yes, with Q8_0: the 4.1 GB file needs about 5.8 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of MedGemma FineTuned GGUF?
It depends on the quant: Q4_K_M is 2.5 GB, Q8_0 is 4.1 GB, F16 is 7.8 GB.
What context length does MedGemma FineTuned support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 1.1 GB at 8K and 4.6 GB at 32K.
Where can I download MedGemma FineTuned GGUF?
The files are on Hugging Face in the Aakash010/MedGemma_FineTuned repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does MedGemma FineTuned use?
Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run this model on 8GB VRAM?
Yes, the Q4_K_M quant uses about 4.1GB at 8k context, fitting within 8GB.
Does it support text‑only tasks?
No, it is vision‑only.
What license does it use?
Apache‑2.0.