unsloth

gemma 2 2B

Text generation

This receipt records checks for this exact file; it does not prove safety or that it will run on your device. Read the receipt

Model details
text generationLicense: gemmaSHA-256 recorded for 7 of 9 filessafetensors
Quick answer: compatibility and sources

Can I run gemma-2-2b on my computer?

It depends on your memory, processor, file format and runtime. A download is not confirmed by the current file evidence; inspect the file record before trying it. A file-size fit is an estimate, not a successful run or speed promise. Read the license before use.

gemma-2-2b 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: 40f7727761523db40b475358377c9a9b0f0d8fcf7ef8b869e71ae4f0ef12a555. 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-unsloth-gemma-2-2b.
  • Open /artifact/hf-model-unsloth-gemma-2-2b/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-unsloth-gemma-2-2b for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-unsloth-gemma-2-2b/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.

Requirements and source record

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

unsloth/gemma-2-2b

Content controls: not assessed.

The catalog lists this model for generating text. Catalog sources: license, cardMetadata.license, task, cardMetadata.pipelineTag.

Download availability is being checked.

Hashes recorded. Date not recorded.

FileSizeSHA-256SourceDownload
Weights
model.safetensors5.23 GB
40f77277…ef12a55540f7727761523db40b475358377c9a9b0f0d8fcf7ef8b869e71ae4f0ef12a555
Download availability is being checked.File metadata
Tokenizer & config
config.json891 bytes
e7fd1f56…5285aa11e7fd1f5621e3956cc2795c3e69d775da31b04a5aae436fa892ab2fe75285aa11
Download availability is being checked.File metadata
generation_config.json190 bytes
4ebdb544…0df227984ebdb5448f194666939265b988d4e8f6437d970dcb271e6f3133ccb70df22798
Download availability is being checked.File metadata
special_tokens_map.json636 bytes
baec30ea…e1351351baec30ea10906f16adb8c18af7a34023002c1746542612b8b41c9f09e1351351
Download availability is being checked.File metadata
tokenizer.json17.5 MB
3f289bc0…41be49223f289bc05132635a8bc7aca7aa21255efd5e18f3710f43e3cdb96bcd41be4922
Download availability is being checked.File metadata
tokenizer.model4.24 MB
61a7b147…e1d4c8e261a7b147390c64585d6c3543dd6fc636906c9af3865a5548f27f31aee1d4c8e2
Download availability is being checked.File metadata
tokenizer_config.json46.4 KB
380c8e59…67837c69380c8e594ecb8ca2b219d7ef355d6f424343eb1c5bd391251b558dbf67837c69
Download availability is being checked.File metadata
Docs
.gitattributes1.57 KB—Download availability is being checked.File metadata
README.md3.58 KB—Download availability is being checked.File metadata

Check a download

In the folder where you saved config.json, run:

macOS
shasum -a 256 -- 'config.json'
Linux
sha256sum -- 'config.json'
Windows
Get-FileHash -LiteralPath 'config.json' -Algorithm SHA256

Compare the result with the recorded SHA-256.