Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
This page describes what the document states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability may vary by jurisdiction. Methodology
These guidelines tell anyone publishing a model on Hugging Face what they must include in their model card and how to set key metadata fields. You are required to document your model's intended uses, limitations, biases, training data, training details, and evaluation results. Metadata like the license, pipeline tag, and library name are not just labels—they control what gets displayed on your model page and how other users can find and interact with your model.
The Hugging Face Model Card Guidelines establish mandatory disclosure and metadata requirements for models hosted on the Hugging Face Hub. Creators are required to include in the model card: intended uses and potential limitations (including biases and ethical considerations), training datasets, training parameters and experimental information, and evaluation results. Metadata fields—including license (with custom licenses requiring an 'other' value plus a name and link), pipeline tag, and library_name—carry direct functional consequences: the pipeline tag controls the interactive widget and underlying APIs, structured evaluation results are parsed and rendered as a Hub widget, and the license is publicly displayed and used as a filter. For model repos created after August 2024, explicit declaration of library_name: transformers is required, as automatic detection no longer applies.
For a user browsing or downloading models on Hugging Face, these guidelines mean that model pages are required to disclose intended uses, limitations, biases, ethical considerations, training datasets, and evaluation results—giving users structured information to assess a model before using it. When a creator adds the not-for-all-audiences tag, Hugging Face automatically displays a warning on that model's page. Users can filter models by license, which is drawn directly from the metadata the creator is required to provide.
Which mapped governance frameworks each document engages, tied to the specific provisions that engage them.
10 important changes detected
11 versions captured · Last updated: July 2026
Hugging Face updated its Model Card Guidelines on July 2, 2026 by adding navigation references to agent-related documentation sections. The change added two new entries to the documentation index: 'Session …
View change record →On June 30, 2026, Hugging Face modified its Model Card Guidelines documentation by adding a reference to 'S3 Compatibility' in the Storage Buckets section of the Hub documentation navigation. This …
View change record →Hugging Face updated its Model Card Guidelines documentation on June 22, 2026. The change added a new navigation item labeled 'Serve Models' to the documentation sidebar under the Jobs section. …
View change record →Hugging Face updated their Model Card Guidelines on June 13, 2026 by adding 'Service Accounts' to the navigation menu in their hub documentation. This is a formatting and organizational change …
View change record →On June 9, 2026, Hugging Face updated its Model Card Guidelines by adding a 'Hardware' section to the documentation navigation menu. This addition expands the structural guidance available to model …
View change record →Hugging Face's Model Card Guidelines were updated on June 4, 2026. The change involves a modification to one sentence within the documentation. The document now includes a reference to 'OpenEnv' …
View change record →Hugging Face updated its Model Card Guidelines documentation on May 31, 2026 by adding a single reference to 'Agent Traces' in the Datasets section of the documentation navigation. The change …
View change record →The detected change involves a minor reorganization of navigation elements in Hugging Face's Model Card Guidelines documentation. The 'Blog Articles' link was moved from its original position in the upper …
View change record →Every distinct legal provision identified in this document. Featured provisions appear above with analysis.
Hugging Face has updated this document before. Monitor includes same-day alerts, structured change summaries, and monitoring for up to 20 platforms.
Need provision-level monitoring and regulatory mapping? Insight includes governance timelines, drift analysis, and full provision tracking.
Cross-platform context
See how other platforms handle not-for-all-audiences tag gates model page display and similar clauses.
Compare across platforms →Governance Monitoring
Structured alerts for policy changes, governance events, and provision updates across 352+ platforms.