gemma-4-E4B-it-MLX-4bit
Try browser chat with a small demo model (a separate model; device support is checked before loading).
AtomicChat/gemma-4-E4B-it-MLX-4bitQuick answer: compatibility and sources
Can I run gemma-4-E4B-it-MLX-4bit on my computer?
It depends on your memory, processor, file format and runtime. Hugging Bay offers 7 hosted files; check the file list for the exact selection. A file-size fit is an estimate, not a successful run or speed promise. Read the license before use.
gemma-4-E4B-it-MLX-4bit is an open-weights language model for text generation. Model weights are learned parameters; a runtime loads them. A hosted file is an individual file Hugging Bay can serve. SHA-256 identifies exact file bytes. The availability date above applies to this file record, not the upstream metadata update date.
As of the recorded file availability check on .
Recorded SHA-256 for model.safetensors: 851ff79844d99f48e081fa631900809154abc2ee78111e42a509521f34afd984. Exact file evidence · Machine-readable source facts · Run evidence and any recorded receipts. A checksum fingerprints only the named file bytes; it does not prove safety, quality, a complete multi-file selection or a successful run.
Updated · Page-copy source revision 8871bab84e1cf80aea1686a944ec335078a6c036 · Source files: apps/web/lib/model-page-template.mjs, apps/web/lib/model-page-v3.mjs, apps/web/lib/aeo-page.mjs · Full revision record
Model metadata: As of at the model source. Popularity counters are source-reported, not measured by Hugging Bay. Availability checked .
Key facts
- Catalog record
- Summarizes upstream metadata; it is not itself a download or run receipt.
- File evidence
- Lists exact filenames, availability and any recorded SHA-256 for individual files.
- Run evidence
- Reports measured results only when a receipt exists for named file bytes and a setup; otherwise unmeasured.
- Checksum scope
- SHA-256 fingerprints one file’s bytes; it does not prove safety, quality or a multi-file bundle.
Evidence you can inspect (plain text)
- This page’s quick answer names the file record for hf-model-atomicchat-gemma-4-e4b-it-mlx-4bit.
- Open /artifact/hf-model-atomicchat-gemma-4-e4b-it-mlx-4bit/files for this exact filenames, availability and any recorded SHA-256.
- Open /evidence/artifacts/hf-model-atomicchat-gemma-4-e4b-it-mlx-4bit for run-readiness evidence tied to that record; absent receipts stay unmeasured.
- Open /api/artifacts/hf-model-atomicchat-gemma-4-e4b-it-mlx-4bit/card.md for machine-readable source facts (not a runtime test).
- A matching checksum on this page fingerprints only the named bytes shown in file evidence.
Unmeasured states are stated explicitly; this page does not invent run scores or compatibility guarantees.
Which date applies to which fact
- File availability check:
- Committed page-copy sources:
- Upstream model metadata: Dates on artifact records when shown; not implied by page-copy revision
- Run receipts: Only on /evidence pages when recorded; otherwise unmeasured
Page-copy revision (Updated line above) identifies committed text sources, not upstream model edits or test outcomes.
7 hosted of 14 listed
Hashes recorded. Date not recorded.
| File | Tamaño | SHA-256 | Origen | Descargar |
|---|---|---|---|---|
| Weights | ||||
model. | 5.15 GB |
| Hosted | Descargar |
| Tokenizer & config | ||||
config. | 6.63 KB |
| Hosted | Descargar |
generation_ | 208 bytes |
| Hosted | Descargar |
hero. | 185.7 KB |
| Upstream only | File metadata |
model. | 241 KB | — | Upstream only | File metadata |
pill_ | 23.4 KB | — | Upstream only | File metadata |
pill_ | 24.2 KB | — | Upstream only | File metadata |
pill_ | 19.5 KB | — | Upstream only | File metadata |
chat_ | 18.6 KB |
| Hosted | Descargar |
processor_ | 1.34 KB |
| Hosted | Descargar |
tokenizer. | 32.2 MB |
| Hosted | Descargar |
tokenizer_ | 3.73 KB |
| Hosted | Descargar |
| Docs | ||||
. | 1.61 KB | — | Upstream only | File metadata |
README. | 4.67 KB | — | Upstream only | File metadata |
Comprobar una descarga
In the folder where you saved config.json, run:
shasum -a 256 -- 'config.json'
sha256sum -- 'config.json'
Get-FileHash -LiteralPath 'config.json' -Algorithm SHA256
Compare the result with the recorded SHA-256.