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.

QuantFactory

state-0-GGUF

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

QuantFactory/state-0-GGUF
Model details
text generationLicense: mitSHA-256 recorded for 14 of 16 filesGGUF

Content controls: not assessed.

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

Quick answer: compatibility and sources

Can I run state-0-GGUF on my computer?

It depends on your memory, processor, file format and runtime. Hugging Bay offers 1 hosted file; 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.

state-0-GGUF 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 state-0.Q4_K_M.gguf: e9d91168fe65944d7188b46bccec5606000e73b84e8532ea40b9b800af480e73. 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-quantfactory-state-0-gguf.
  • Open /artifact/hf-model-quantfactory-state-0-gguf/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-quantfactory-state-0-gguf for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-quantfactory-state-0-gguf/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.

1 hosted of 16 listed

Hashes recorded. Date not recorded.

FileTamanhoSHA-256OrigemBaixar
Weights
state-0.Q4_K_M.gguf Default4.92 GB
e9d91168…af480e73e9d91168fe65944d7188b46bccec5606000e73b84e8532ea40b9b800af480e73
HostedBaixar
state-0.Q2_K.gguf3.18 GB
74de81a4…56d6508c74de81a4ff34cd2799d78d7613aa63c5533017020aabb6a7e255ca2b56d6508c
Upstream onlyFile metadata
state-0.Q3_K_L.gguf4.32 GB
846de39b…762bd41d846de39b5ad0465f5644fd3cee0352cd07aa5dec925946e69db4425d762bd41d
Upstream onlyFile metadata
state-0.Q3_K_M.gguf4.02 GB
3d31439c…decb1e2e3d31439c2fb5694eb3934c72e661880951189fdcd89f2aa5c34f6449decb1e2e
Upstream onlyFile metadata
state-0.Q3_K_S.gguf3.66 GB
c78743aa…71bd2e9ac78743aab9baa9d19408355ef146cdcb128daf23a15f0cbfc86270f971bd2e9a
Upstream onlyFile metadata
state-0.Q4_0.gguf4.66 GB
d5327e8e…39c7ed3ad5327e8e970e5b984820053064b42248083764768564b4316bd8d71e39c7ed3a
Upstream onlyFile metadata
state-0.Q4_1.gguf5.13 GB
e45ded9c…a3ae1ce6e45ded9ca11834aacb8f011ca438037db1168d3d09b7011dfd6fcb59a3ae1ce6
Upstream onlyFile metadata
state-0.Q4_K_S.gguf4.69 GB
0971efe3…f473b8f00971efe38d38f3b8e37da4e854bd74e4d9a09cbc28644666bd9d1a71f473b8f0
Upstream onlyFile metadata
state-0.Q5_0.gguf5.6 GB
56f4d245…dc160f6c56f4d2458dc627288bba8871e7d4858d9e264ec3094e6cce6e636adddc160f6c
Upstream onlyFile metadata
state-0.Q5_1.gguf6.07 GB
a6c1fb32…af1b456ca6c1fb32ea4b510b3116443edd3031ff0cd1c025d0a7c16a7c164d3caf1b456c
Upstream onlyFile metadata
state-0.Q5_K_M.gguf5.73 GB
f6f86b8b…e5391aa2f6f86b8b5490af17df83b44b10282d5ec718d3e5045fa067438849a4e5391aa2
Upstream onlyFile metadata
state-0.Q5_K_S.gguf5.6 GB
6623ca6e…446b4d706623ca6e71e203c6b115bca98bf59d666e64bd9a52aced160db85f89446b4d70
Upstream onlyFile metadata
state-0.Q6_K.gguf6.6 GB
fa553e26…e9bdcd17fa553e26b1a37b3c4f637b8d04ee9df46ae664a5a2f0f076df3c1824e9bdcd17
Upstream onlyFile metadata
state-0.Q8_0.gguf8.54 GB
2fe5798a…523cfd8b2fe5798a15aedd58bc05a80954e4b20d4c7901d4d2235ec0bfb0e414523cfd8b
Upstream onlyFile metadata
Docs
.gitattributes2.29 KB—Upstream onlyFile metadata
README.md8.03 KB—Upstream onlyFile metadata

Verificar um download

In the folder where you saved state-0.Q4_K_M.gguf, run:

macOS
shasum -a 256 -- 'state-0.Q4_K_M.gguf'
Linux
sha256sum -- 'state-0.Q4_K_M.gguf'
Windows
Get-FileHash -LiteralPath 'state-0.Q4_K_M.gguf' -Algorithm SHA256

Compare the result with the recorded SHA-256.