clip-matching is an open-weight model from Freja Andersson, released under MIT License. It has 33,088 parameters and a 512-token context. At 16-bit it needs about 0 GB of GPU memory, which fits on 1x MI300X from $1.85 an hour, at the lowest prices in the SAVRN Index.
This is an experimental CLIP codebase for Matching. It keeps the large setup intentionally manageable so architecture changes can be inspected before a full training run. - The Python file contains the model and runnable example or training entry point.
Runs On
What it takes to serve clip-matching (33,088 parameters): the memory its weights need at each precision, and the cheapest way to rent enough data-center GPUs to hold them.
| Precision | Weights | Memory needed | Cheapest setup | Per hour | Also fits |
|---|---|---|---|---|---|
| 16-bit | 0.0 GB | 0.0 GB | 1x MI300X (192 GB) Vultr |
$1.85 | 1x H100 $1.99 · 1x MI325X $2.00 |
| 8-bit | 0.0 GB | 0.0 GB | 1x MI300X (192 GB) Vultr |
$1.85 | 1x H100 $1.99 · 1x MI325X $2.00 |
| 4-bit | 0.0 GB | 0.0 GB | 1x MI300X (192 GB) Vultr |
$1.85 | 1x H100 $1.99 · 1x MI325X $2.00 |
Memory is the weights at that precision plus 20% for the runtime and a short context; a long context needs more. Prices are the lowest on-demand hourly rates in the SAVRN Index, read Oct 18, 2026.
clip-matching on every accelerator the SAVRN Index prices, at every precision
Model Card
By Freja Andersson, published under mit, revision 940e0d8deddd.
This is an experimental CLIP codebase for Matching. It keeps the large setup intentionally manageable so architecture changes can be inspected before a full training run. - The Python file contains the model and runnable example or training entry point. - config.json records the generated architecture settings. - trainingargs.json records the default experiment recipe. - model.safetensors is a valid initialization checkpoint for smoke tests; it is not presented as a trained benchmark checkpoint. - No benchmark score is claimed in this repository. The included configuration uses adamw with a constant warmup schedule. These are starting values in the script, not evidence of a completed run.…
Read Freja Andersson's full model card
CLIP for Matching
Overview
This is an experimental CLIP codebase for Matching. It keeps the large setup intentionally manageable so architecture changes can be inspected before a full training run.
Repository status
- The Python file contains the model and runnable example or training entry point.
config.jsonrecords the generated architecture settings.training_args.jsonrecords the default experiment recipe.model.safetensorsis a valid initialization checkpoint for smoke tests; it is not presented as a trained benchmark checkpoint.- No benchmark score is claimed in this repository.
Architecture
| Item | Value |
|---|---|
| Architecture | CLIP |
| Scale | large |
| Attention | multi query |
| Fusion | gated fusion |
| Activation | gelu |
| Normalization | groupnorm |
Default experiment recipe
The included configuration uses adamw with a constant warmup schedule. These are starting values in the script, not evidence of a completed run. For a meaningful evaluation, train all baselines with the same data exposure, tuning budget, and random seeds.
Quick check
python eval.py --help
Inspect the script's __main__ block for its generated smoke-test example. Because this is a custom implementation, generic automatic loading APIs require an explicit adapter before use.
Evaluation guidance
A useful first evaluation would use a paired validation set, report the task metric across at least three seeds, and include a matched-capacity baseline. Keep training logs and environment versions with any published result.
Limitations
The initialization checkpoint has not been trained or audited for robustness, fairness, or domain transfer. The implementation should be treated as an experimental starting point. Results from a future trained checkpoint must be documented separately from the defaults shipped here.
Files
eval.py— primary artifactREADME.md— this documentationconfig.json— architecture configurationtraining_args.json— default experiment settingsmodel.safetensors— initialization checkpoint
License
Released under mit. Review the source-data terms separately when this repository is used with external datasets.
Configuration
- Architecture
- CustomResearchModel
- Context length (tokens)
- 512
- Layers
- 6
- Hidden size
- 256
- Feed-forward size
- 1,024
- Attention heads
- 8
- Model type
- clip
Identity and Version
- Repository
- tonyliu5/clip-matching
- Publisher
- Freja Andersson
- Task
- Not stated by the source
- Modality
- Other
- Library
- Not stated by the source
- Parameters
- 33,088 parameters
- Languages
- Not stated by the source
- Revision
- 940e0d8dedddf273d146a075cf352a69398450e3
- First published
- 2026-10-02
- Last updated
- 2026-10-02
Files and Weights
6 files, 142.0 KB in total. The weights are 1 file totalling 132.8 KB in safetensors.
Every file
| File | Type | Size | SHA-256 |
|---|---|---|---|
| model.safetensors | Weights | 132.8 KB | e3990cda2590 |
| config.json | Configuration | 427 B | — |
| eval.py | Configuration | 4.6 KB | — |
| training_args.json | Configuration | 198 B | — |
| README.md | Documentation | 2.4 KB | — |
| .gitattributes | Repository | 1.5 KB | — |
License and Download
- License
- mit
- Access
- Open weights, no gate
- Download size
- 132.8 KB
Released by Freja Andersson through its official repository on Hugging Face. Read the license.
Memory Requirements
| Precision | Weights in memory |
|---|---|
| As published | 132.8 KB |
| 16-bit | 0.0 GB |
| 8-bit | 0.0 GB |
| 4-bit | 0.0 GB |
Weights only, from the published parameter count; the key-value cache and runtime add to this.
Questions About clip-matching
How much GPU memory does clip-matching need?
About 0 GB at 16-bit and 0 GB at 4-bit: the weights (33,088 parameters) plus a working margin. A long context needs more.
What is the cheapest GPU to run clip-matching on?
At 16-bit, 1x MI300X from $1.85 an hour; at 4-bit, 1x MI300X from $1.85 an hour, at the lowest on-demand prices the SAVRN Index lists.
Can I use clip-matching commercially?
Yes. clip-matching is released under MIT License. The MIT License is a short permissive license. It permits commercial use, modification and redistribution, provided the copyright notice and permission notice are included.
What is clip-matching's context length?
512 tokens, from the maximum position embeddings in its published configuration.