SmolLM2 360M Instruct Text 2 JSON needs about 1.1 GB of memory at Q4_K_M (a 0.3 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 4 quants, from 0.3 GB (Q4_K_M) to 0.8 GB (F16).
SmolLM2 360M Instruct Text 2 JSON – lightweight calendar event parser
SmolLM2 360M Instruct Text 2 JSON is a fine‑tuned version of SmolLM2-360M-Instruct-bnb-4bit. It extracts structured calendar event information from natural language text. The model is based on a 0.409 billion parameter llama architecture and supports 8192 context tokens.
Good at
- Parsing natural language event descriptions
- Extracting scheduling entities
- Outputting structured JSON
Limits
- No vision support
- Requires 8192 context tokens
- Apache‑2.0 license
Best for
- Calendar application integration
- Personal assistant scheduling systems
- Meeting summarization tools
Who it’s for. Developers building scheduling or calendar features that need quick, on‑device parsing of event descriptions into JSON. The model is suitable for lightweight applications with limited GPU memory.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 0.3 GB | 1.1 GB | Fits | Get file → | |
| Q4_K_M | 0.3 GB | 1.1 GB | Fits | Get file → | |
| F16 | 0.8 GB | 1.7 GB | Fits | Get file → | |
| F16 | 0.8 GB | 1.7 GB | Fits | Get file → |
For 8 GB VRAM, use the Q4_K_M quantized file (0.3 GB, ~1.1 GB memory at 8k context). If more memory is available, the F16 quantized file (0.82 GB, ~1.7 GB memory) provides higher precision.
What GPU do you need for SmolLM2 360M Instruct Text 2 JSON?
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: the best quant that fits is F16 (0.8 GB file, about 1.7 GB in use).
Which SmolLM2 360M Instruct Text 2 JSON quant should you choose?
Q4_K_M is the usual starting point for SmolLM2 360M Instruct Text 2 JSON: it balances file size and quality well. Here it is a 0.3 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about SmolLM2 360M Instruct Text 2 JSON
How much VRAM does SmolLM2 360M Instruct Text 2 JSON need?
About 1.1 GB at Q4_K_M with an 8K context window. That is the 0.3 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 SmolLM2 360M Instruct Text 2 JSON on an 8 GB GPU?
Yes, with F16: the 0.8 GB file needs about 1.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of SmolLM2 360M Instruct Text 2 JSON GGUF?
It depends on the quant: Q4_K_M is 0.3 GB, Q4_K_M is 0.3 GB, F16 is 0.8 GB, F16 is 0.8 GB.
What context length does SmolLM2 360M Instruct Text 2 JSON support?
The GGUF header lists a trained context length of 8,192 tokens (8K). The KV cache grows with the context you use: about 0.3 GB at 8K and 0.3 GB at 8K.
Where can I download SmolLM2 360M Instruct Text 2 JSON GGUF?
The files are on Hugging Face in the pramodkoujalagi/SmolLM2-360M-Instruct-Text-2-JSON repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does SmolLM2 360M Instruct Text 2 JSON 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 8 GB VRAM?
Yes, the Q4_K_M quantized file uses about 1.1 GB memory at 8k context, fitting within 8 GB VRAM.
What context length does the model support?
The model was trained with 8192 context tokens and can handle that length.
Is the model licensed for commercial use?
It is released under the Apache‑2.0 license, which permits commercial use.