Ir para o conteúdo principal

AI models that run on this device.

Two small chat models run in a computer’s browser here; every other model is a file you download.

AtomicChat

gemma-4-E4B-it-MLX-8bit

Try browser chat with a small demo model (a separate model; device support is checked before loading).

AtomicChat/gemma-4-E4B-it-MLX-8bit
Model details
text generationLicense: apache-2.0SHA-256 recorded for 10 of 15 filessafetensors

Content controls: not assessed.

The catalog lists this model for having conversations. Catalog sources: license, cardMetadata.license, tags, task, cardMetadata.pipelineTag.

Quick answer: compatibility and sources

Can I run gemma-4-E4B-it-MLX-8bit on my computer?

It depends on your memory, processor, file format and runtime. Hugging Bay offers 9 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-8bit 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-00001-of-00002.safetensors: d5690742b9ca473a16b74ad756fa0b931837b07b506e62b1ab85d2a5ca3d9029. 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-8bit.
  • Open /artifact/hf-model-atomicchat-gemma-4-e4b-it-mlx-8bit/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-atomicchat-gemma-4-e4b-it-mlx-8bit for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-atomicchat-gemma-4-e4b-it-mlx-8bit/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.