If the goal is to rename a GGUF metadata key, a safe implementation can treat it as an atomic add-new-key + delete-old-key operation while preserving the original value type. GGUF metadata is a key/value structure, so this also gives the UI a chance to reject duplicate destination keys before rewriting the file. The current Hugging Face announcement describes the built-in editor as updating metadata fields such as the chat template, but does not mention key renaming: GGUF Metadata Editor
As a workaround, the open-source gguf-org/editor
package documents support for inspecting metadata and adding/deleting keys. That allows a local rename by adding the new key with the same type/value, deleting the old key, and saving a new file: gguf-org/editor · Hugging Face I would keep the original GGUF as a backup and validate the renamed file in the target runtime. Standardized keys are consumed by s, so an arbitrary rename can make metadata invisible even when the file remains structurally valid.