If you share Llama 3 or a modified version with others, you must give them a copy of this license, clearly mark any files you have changed, and keep all existing notices in the model files.
This analysis describes what Meta's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This clause establishes that the license terms, including all restrictions such as the competitive use prohibition and Acceptable Use Policy, flow through to all downstream recipients, creating a chain of obligation across every redistribution of Llama 3 or its derivatives.
Any developer or organization that receives a redistributed version of Llama 3 or a derivative model is legally bound by the same terms as the original licensee, including restrictions on competitive use and compliance with the Acceptable Use Policy.
Cross-platform context
See how other platforms handle Redistribution Requirements and similar clauses.
Compare across platforms →Monitoring
Meta has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.
"If you distribute or make available the Llama Materials (or any derivative works thereof), you will (i) provide a copy of this Agreement to any recipients of the Llama Materials; and (ii) cause any modified files to carry prominent notices stating that you changed the files; and (iii) retain in the Llama Materials and in all copies of derivative works all notices that are present in the Llama Materials.— Excerpt from Meta's Llama Community License Agreement
(1) REGULATORY LANDSCAPE: Redistribution requirements in software and model licenses are governed by contract law and copyright law. EU AI Act transparency requirements may independently require disclosure of underlying model lineage in distributed AI systems, which may overlap with or reinforce this provision. (2) GOVERNANCE EXPOSURE: Medium. Organizations managing large-scale model distribution pipelines must implement technical and procedural controls to ensure license documents are included with every distribution, modified files are marked, and existing notices are preserved. (3) JURISDICTION FLAGS: Open source license compliance obligations have been litigated in EU jurisdictions under GPL and similar frameworks; while the Llama 3 license is not an open source license in the OSI sense, analogous compliance obligations apply and similar enforcement risks exist. (4) CONTRACT AND VENDOR IMPLICATIONS: Vendor agreements and API distribution contracts built on Llama 3 must include provisions requiring downstream recipients to comply with this agreement, and should specify the version of the license in effect at distribution. (5) COMPLIANCE CONSIDERATIONS: Legal teams should implement a license compliance checklist for all model distribution workflows, including automated notice preservation checks and documentation confirming that each redistribution event included the required agreement copy.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Watcher: 10 platforms + same-day alerts. No credit card required.
Professional Governance Intelligence
Need to monitor specific governance provisions?
Professional includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
This clause establishes that the license terms, including all restrictions such as the competitive use prohibition and Acceptable Use Policy, flow through to all downstream recipients, creating a chain of obligation across every redistribution of Llama 3 or its derivatives.
Any developer or organization that receives a redistributed version of Llama 3 or a derivative model is legally bound by the same terms as the original licensee, including restrictions on competitive use and compliance with the Acceptable Use Policy.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Meta.