How do common tools identify a model file (sha256, A1111 short hashes, ComfyUI/Hugging Face identifiers), and which identification survives renaming or re-saving?
Identifiers fall into three kinds. Name-based: ComfyUI prompts/workflows use the file name (ckpt_name), A1111's title includes the name. Whole-file content hashes: A1111 sha256 (short form = first 10 hex chars, used as 'Model hash'), InvokeAI and ComfyUI's asset store BLAKE3 ('blake3:<hex>'), Hugging Face LFS sha256 (also the ETag for LFS files) plus git blob ids and Xet hashes. Partial hashes: A1111's legacy 8-char hash (64 KiB at offset 1 MiB) and the kohya 'addnet' hash (data region after the header). Renaming keeps every content hash; any re-save that changes bytes (header/__metadata__ edit, different writer/ordering, dtype conversion) changes whole-file hashes; the addnet hash survives header-only edits only. None of the inspected tools defines a layout-independent tensor-content hash.
Structured fields
{
"citations": [
{
"url": "https://github.com/AUTOMATIC1111/stable-diffusion-webui",
"note": "see curator disposition"
},
{
"url": "https://github.com/comfyanonymous/ComfyUI",
"note": "see curator disposition"
},
{
"url": "https://github.com/invoke-ai/InvokeAI",
"note": "see curator disposition"
},
{
"url": "https://github.com/huggingface/huggingface_hub",
"note": "see curator disposition"
},
{
"url": "https://github.com/huggingface/safetensors",
"note": "see curator disposition"
},
{
"url": "https://docs.comfy.org/development/api-development/workflow-api-format",
"note": "see curator disposition"
}
]
}Evidence claims
- [sourced_fact] Identifiers fall into three kinds. Name-based: ComfyUI prompts/workflows use the file name (ckpt_name), A1111's title includes the name. Whole-file content hashes: A1111 sha256 (short form = first 10 hex chars, used as 'Model hash'), InvokeAI and ComfyUI's asset store BLAKE3 ('blake3:<hex>'), Hugging Face LFS sha256 (also the ETag for LFS files) plus git blob ids and Xet hashes. Partial hashes: A1111's legacy 8-char hash (64 KiB at offset 1 MiB) and the kohya 'addnet' hash (data region after the header). Renaming keeps every content hash; any re-save that changes bytes (header/__metadata__ edit, different writer/ordering, dtype conversion) changes whole-file hashes; the addnet hash survives header-only edits only. None of the inspected tools defines a layout-independent tensor-content hash. · locator: see curator disposition source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |
Linked records
- cites → https://docs.comfy.org/development/api-development/workflow-api-format
- cites → https://github.com/automatic1111/stable-diffusion-webui
- cites → https://github.com/comfyanonymous/comfyui
- cites → https://github.com/huggingface/huggingface_hub
- cites → https://github.com/huggingface/safetensors
- cites → https://github.com/invoke-ai/invokeai