Skip to content

Creative Commons License

A standardized public copyright license that gives every downstream recipient a direct, irrevocable permission grant for specified reuse while expressing attribution and selected ShareAlike, NonCommercial, or NoDerivatives conditions through interoperable legal, human-readable, and machine-readable layers.

Version
v2 · 2026-09-06 · History
Domain-specific #
1582
Origin domain
copyright licensing
Subdomain
standardized public licenses

Core Idea

A Creative Commons license is one member of a standardized suite of public licenses by which a person or institution authorized to license copyright and certain similar rights gives the public advance permission to use identified material under stable terms. Instead of asking the rights holder for a separate grant each time, a prospective user identifies the license and version, tests the contemplated act against its permissions and conditions, and either proceeds in compliance, relies on an independent exception or limitation, or seeks separate permission.[1][2]

The current Version 4.0 suite has six licenses: CC BY, CC BY-SA, CC BY-NC, CC BY-NC-SA, CC BY-ND, and CC BY-NC-ND. They are generated from four named elements: Attribution (BY), ShareAlike (SA), NonCommercial (NC), and NoDerivatives (ND). Attribution appears in every current license. ShareAlike conditions the sharing of adapted material on use of the same or a designated compatible licensing regime. NonCommercial limits exercise of the licensed rights to noncommercial purposes as defined by the selected legal code. NoDerivatives permits production and reproduction of adaptations under Version 4.0 but withholds permission to share adapted material.[3][4][5][6]

The locked identity is authorized licensor + identified material subject to copyright or similar rights + a named CC license and version + a worldwide, royalty-free, non-exclusive, non-sublicensable, irrevocable public grant for the license term + direct downstream offers from the licensor + attribution and the selected SA/NC/ND conditions + prohibition on added downstream restrictions + legal-code, deed, and machine-readable representations → reusable permission without per-user negotiation, bounded by the chosen license and unlicensed rights.[7][8]

“Creative Commons License” therefore names an autonomous licensing architecture, not Creative Commons as an organization, not a generic aspiration to share, and not one undifferentiated permission. The choice among six instruments changes what downstream users may do. The version matters because prior suites and jurisdictional ports remain legally relevant when attached to material. Version 4.0, published in 2013, is the current and recommended international suite; it was designed to operate worldwide without the earlier porting model and expressly addresses sui generis database rights, limited treatment of some other rights, and automatic reinstatement after timely cure of a violation.[9][10]

This entry is explanatory rather than legal advice. Actual compliance depends on the particular legal code, material, jurisdiction, facts, and rights involved.

Structural Signature

  • the licensor — an individual or entity that owns or controls the copyright and similar rights it purports to grant;
  • the licensed material — clearly identified work, database, performance, recording, or other protected material, with third-party or excluded content marked separately;
  • the baseline legal perimeter — the copyright and similar rights that would otherwise require permission, including applicable sui generis database rights in Version 4.0;
  • the selected instrument — one of the six CC licenses, identified by element combination, version, and, for older material, any port or jurisdiction designation;
  • the public license grant — standing permission offered to the public rather than negotiated with one named counterparty;
  • the common scope — in Version 4.0, a worldwide, royalty-free, non-sublicensable, non-exclusive, irrevocable license for the term of the licensed copyright and similar rights, subject to conditions;
  • the downstream-offer mechanism — each recipient receives an offer from the original licensor under the public license rather than depending on a private sublicense chain;
  • the Attribution condition — when sharing, retain supplied creator identification, copyright and license notices, warranty-disclaimer notice, and source URI where reasonably practicable; identify the license and indicate modifications;
  • the optional element logic — SA governs licensing of shared adaptations, NC restricts licensed uses to noncommercial purposes, and ND withholds permission to share adapted material;
  • the no-added-restrictions condition — recipients may not impose different terms or effective technological measures that restrict exercise of the licensed rights in the licensed material;
  • the independent-rights boundary — exceptions and limitations remain available; patent and trademark rights are not licensed; third-party, privacy, publicity, and moral-rights issues can remain;
  • the persistence and compliance rule — the licensor may stop distributing or offer the material on other terms without terminating existing CC grants, while a noncomplying licensee's rights terminate subject to the selected version's reinstatement rules;
  • the three representations — legally operative Legal Code, human-readable Commons Deed, and machine-readable rights expression;
  • the attribution and provenance trail — the marking links material, source, creator where supplied, modifications, and the exact license URI so later users can evaluate the grant.

Every role is load-bearing. A “CC” icon without an exact license or version can leave conditions unclear. A valid-looking notice applied by someone who lacks the relevant rights cannot grant what that person does not control. A deed is a useful summary but not the legally operative text. A compatible act outside copyright—such as a use authorized by fair use or another exception—does not depend on the license and is not narrowed by it.[7][2][8]

What It Is Not

A CC license is not a transfer of copyright ownership. The grant is non-exclusive, and the licensor can simultaneously offer the same material under other terms. Nor is it a waiver of every right: the Version 4.0 legal codes do not license patent or trademark rights and treat moral, privacy, publicity, and related rights only to the limited extent stated.[7]

It is not CC0 or the Public Domain Mark. Creative Commons explicitly describes CC0 as a public-domain dedication, not a license; it attempts to waive rights as fully as possible and supplies a fallback license where necessary. The Public Domain Mark labels material believed to be free of known copyright restrictions. The six licenses instead operate on protected material by retaining copyright and granting selected permissions under conditions.[11][2]

It is not generic “open content.” CC BY and CC BY-SA are highly permissive of reuse, but NC licenses restrict commercial use and ND licenses restrict sharing adaptations. Whether a license satisfies an external Open Definition, free-culture definition, repository policy, or funder mandate is a separate classification question. “Creative Commons” names provenance of the instrument; “open” is not a sufficient substitute for reading its elements.

It is not a bespoke contract, terms-of-service policy, confidentiality agreement, or permission email. Those can authorize use, but they lack the suite's fixed element grammar, canonical URI, public downstream offer, and three-layer rights expression. A modified legal text is not automatically an official CC license; Creative Commons' legal code and trademark policy distinguish the canonical instrument from unauthorized modifications.[7][8]

It is not technical access control. A paywalled file may carry a CC license; a freely downloadable file may be “all rights reserved.” Technical reachability and legal permission are separate. It is also not a warranty of accuracy, noninfringement, or fitness. Version 4.0 contains broad disclaimers and limitations of liability to the extent permitted.[7]

Scope of Application

CC licenses are designed for copyrightable works and other material within their legal scope: photographs, text, music, video, educational resources, scholarly works, cultural-heritage reproductions where rights exist, government information, and databases are common settings. Version 4.0 includes applicable sui generis database rights within “Copyright and Similar Rights,” subject to its detailed database section.[2][7]

The framework spans individual and institutional licensing. A photographer can license a single image; a university can license course materials; a journal can license articles; a museum can mark institution-created metadata or images; a government can license reports and datasets; a platform can offer a license choice to uploaders. The exact material boundary must remain visible when a page combines differently licensed or third-party components.

Creative Commons does not recommend its licenses for software or hardware. Software carries patent, source-code, compatibility, and warranty conventions handled more directly by established free and open-source licenses; hardware has different legal components. A CC license can also be inappropriate when the material is already in the public domain, when the purported licensor lacks rights, when collective-management obligations conflict, or when confidential or personal data cannot lawfully be made public.[2]

The current architecture is international, but it is not timeless or versionless. Material remains governed by the license actually applied. Earlier 1.0 through 3.0 licenses, unported forms, and jurisdictional ports can differ in attribution, database-rights, termination, and governing-law treatment. A user should not silently “upgrade” someone else's license simply because 4.0 is now recommended.[9][10]

Clarity

Five questions identify the operative structure.

First, who has authority over what? The licensor must own or control the rights, and the notice must distinguish material excluded from the grant. A platform user's assertion is evidence of a license choice, not proof of title.

Second, which exact license and version? “CC licensed” is incomplete because BY, SA, NC, and ND change permissions. The canonical URI is the reliable identifier.

Third, does the intended act require the licensed rights? If the use falls within the public domain or an exception such as fair use or fair dealing, the CC conditions are not triggered for that use. If copyright permission is needed, proceed to the license terms.[2][7]

Fourth, is the act sharing, adaptation, commercial use, or some combination? BY allows sharing and adaptation, including commercially, with attribution. SA adds a reciprocal license condition to shared adaptations. NC limits the licensed rights to noncommercial purposes. ND permits private production and reproduction of adaptations under 4.0 but not sharing them. Technical format changes necessary to exercise the rights do not by themselves create Adapted Material under the 4.0 codes.[4][5][6]

Fifth, are attribution, marking, downstream, and other-rights duties satisfied? Appropriate credit is contextual rather than one rigid citation format, but supplied notices, the license, modification indication, and source link should be retained as reasonably practicable. No-added-restrictions prohibits placing legal or effective technological barriers on licensed material that prevent downstream exercise. Privacy, publicity, trademark, patent, and third-party copyright may still require separate analysis.

Manages Complexity

The suite converts an open-ended drafting and negotiation problem into a recognized decision matrix. A licensor answers two major policy questions—whether commercial use is permitted and whether adaptations may be shared, with ShareAlike available for shared adaptations—and selects a stable instrument. A reuser reads the short identifier and URI, then consults the legally operative code rather than locating the licensor for every ordinary reuse. The result scales a permission decision across unknown future recipients.[3][1]

Standardization also compresses communication. The license name and icons give humans a rapid signal; the deed provides an accessible summary; the legal code fixes operative terms; machine-readable metadata lets software and search systems recognize rights information. These layers address different interpreters without pretending that a summary or icon replaces the law.[8]

The downstream-offer structure reduces chain fragility. Because recipients receive an offer from the licensor, permission does not depend on an intermediary possessing sublicensing authority. The no-added-restrictions rule helps preserve the licensed permission surface as copies travel. ShareAlike can preserve reciprocal terms for adaptations, but it introduces a compatibility problem: a downstream adapter must select an allowed same-elements or designated compatible license. This is managed through published compatibility rules, not by assuming all “open” licenses compose.[4][12]

The architecture does not eliminate complexity; it locates it. Questions about ownership, adaptation, commercial purpose, attribution, mixed material, version differences, moral rights, privacy, data protection, patents, and license compatibility remain. The suite makes those questions enumerable and exposes which one blocks a proposed use.

Abstract Reasoning

The principal reasoning move is a permission pipeline:

  1. identify the material and the party claiming to license it;
  2. isolate the relevant copyright or similar right and ask whether an exception already authorizes the use;
  3. resolve the exact CC license, version, and scope marking;
  4. classify the intended conduct as reproduction, public sharing, adaptation, commercial or noncommercial use, or database extraction/reuse;
  5. apply BY and any SA, NC, or ND element;
  6. preserve notices and indicate modifications in a reasonable form;
  7. check additional rights and third-party content outside the grant;
  8. verify downstream terms, technological measures, and compatibility.

This pipeline licenses concrete predictions. If a user shares an adaptation of BY-SA 4.0 material, the adapter's license must be BY-SA with the same elements in the permitted version range or a designated compatible license. If the material is BY-ND 4.0, a user may make an adaptation privately but cannot rely on that license to share it. If use of BY-NC material is commercial within the legal code's definition, separate permission is required unless an independent exception applies.[4][6][5]

It also distinguishes irrevocability from immunity to breach. The licensor cannot withdraw the public license from compliant recipients merely by changing its mind, although it can stop distributing or offer other terms. A particular licensee's rights terminate automatically upon noncompliance; Version 4.0 provides automatic reinstatement when the violation is cured within thirty days of discovery, or reinstatement by express permission. Remedies for the violation may remain.[7][2]

Compatibility reasoning is directional. A general resemblance between two licenses does not authorize relicensing. The applicable SA legal code and Creative Commons' compatibility list determine permitted adapter-license paths; some listed compatibility is one-way.[12]

Knowledge Transfer

Exact transfer occurs across media. A photograph, textbook chapter, recording, research article, video, and database can occupy the Licensed Material role; creator, publisher, university, museum, or government can occupy the Licensor role; the same element grammar and downstream logic survive. The format of attribution changes with medium, but its legal role does not.

Transfer also occurs across distribution systems. A license notice can accompany a physical book, appear beside a digital image, live in a repository record, be embedded in webpage metadata, or be generated by a platform. The three-layer design anticipates legal, human, and machine readers. The exact marking technique varies, while the link among material, license, creator information, and changes remains.

The broader lesson—publish standing permission terms so strangers can coordinate without bilateral negotiation—transfers beyond CC and is already captured by prime:license_as_coordination. What does not transfer is the CC-branded six-license matrix, the BY/SA/NC/ND grammar, canonical license URIs, Version 4.0 definitions, CC deeds, and CC Rights Expression Language. Those features keep this node domain-specific.

Examples

  1. CC BY 4.0 educational diagram. A university marks a diagram with creator, source, and CC BY 4.0 URI. A teacher adapts labels, includes it in a commercial textbook, credits the creator, links the license, and indicates the change. The use fits BY because commercial reuse and adaptation are permitted subject to attribution.[13]
  2. CC BY-SA 4.0 translation. A translator shares a translation of a licensed essay. Translation is Adapted Material under the legal code, so the translator preserves attribution and applies BY-SA 4.0 or another allowed same-elements or designated compatible license to the contribution.[4]
  3. CC BY-NC 4.0 reuse boundary. A nonprofit-status label alone does not decide whether a use is NonCommercial; the legal definition concerns whether the use is primarily intended for or directed toward commercial advantage or monetary compensation. A publisher planning a paid product must analyze the concrete use or seek separate permission rather than inferring permission from the word “educational.”[5]
  4. CC BY-ND 4.0 private adaptation. A researcher translates a licensed work for private study. Version 4.0 permits production and reproduction of Adapted Material but not sharing it under the ND license. Publishing the translation requires separate permission or another legal basis.[6]
  5. Mixed-media webpage. A page footer says most original text is CC BY, while a third-party photograph carries a separate all-rights-reserved notice. The license applies only to the marked scope; the footer does not absorb the photograph into the grant.
  6. Database reuse. A CC BY 4.0 database provider licenses applicable copyright and sui generis database rights it controls. A reuser extracting and sharing a substantial portion follows attribution and database provisions, while rights in individual contents and privacy law remain separate.[7]
  7. CC0 nonexample. A rights holder applies CC0 to waive copyright and database rights as fully as possible. This serves public-domain placement, not the retained-rights plus conditional-license structure of the six CC licenses.[11]
  8. Gratis download nonexample. A creator posts a film online without a license. Anyone can view or download it technically, but public reachability alone does not give CC permission to redistribute or adapt it.

Structural Tensions

  • Simplicity versus legal precision. Icons and deeds make the choice legible, but only the legal code is operative. Diagnostic: does the user follow the URI to the correct version rather than treating the icon as exhaustive?
  • Advance permission versus retained control. A licensor gains reach by making an irrevocable public grant, while NC and ND retain selected controls. Diagnostic: choose the instrument based on downstream acts the licensor is prepared to authorize permanently, not on a vague wish to “share.”
  • Standardization versus factual heterogeneity. One license can cover many media, but ownership, third-party content, privacy, moral rights, and collective-management rules differ. Diagnostic: map the licensed-material boundary and rights inventory before applying the standard form.
  • ShareAlike continuity versus interoperability. Reciprocal licensing preserves an open terms lineage but can block combination with incompatible material. Diagnostic: check the exact adapter-license and compatibility path before merging works.
  • NonCommercial intent versus ambiguous edge cases. NC supplies a recognizable boundary yet commercial advantage can be fact-dependent. Diagnostic: analyze the actual purpose and transaction under the selected legal code or seek separate permission rather than relying on organizational labels.
  • NoDerivatives integrity versus translation and accessibility. ND can protect an unaltered public version, but translation, remix, synchronization, or other changes may become unshareable adaptations. Diagnostic: distinguish permitted technical modifications from legally material adaptations and obtain permission when sharing crosses the boundary.
  • Irrevocable reliance versus compliance enforcement. Recipients need durable permission; licensors need conditions to matter. Diagnostic: separate withdrawal, which does not terminate compliant grants, from a licensee's breach, which triggers termination and the version-specific cure rules.

Structural–Framed Character

Creative Commons License is precise but deeply framed. Its causal and inferential roles are stable: authorized licensor, protected material, public grant, element-specific conditions, direct downstream offer, attribution, term, termination, and three representations. Yet none exists independently of a legal order recognizing copyright, licensing authority, exceptions, public sharing, and remedies.

Institutional origin, human-practice dependence, traveling legal vocabulary, and import-versus-recognize therefore score fully framed. Evaluative weight is slightly lower because the suite permits a range from permissive BY to restrictive BY-NC-ND and the entry does not endorse one. Still, the architecture was designed to promote voluntary sharing, so its normative orientation is not zero. The aggregate is 0.96, correctly classifying a repeatable institutional instrument rather than a substrate-neutral law.

Structural Core vs. Domain Accent

The portable core is a rights holder publishes standing terms for a class of future users, allowing reliance without repeated bargaining. That core is exactly license_as_coordination. Contract, Commitment, Access Control, Attribution, and Compatibility describe adjacent operations.

The domain accent is constitutive: Creative Commons authorship of canonical public licenses; the six-instrument suite; BY, SA, NC, and ND elements; versioned canonical URIs; the direct-offer and no-added-restrictions language; the 4.0 treatment of database rights and cure; and the Legal Code–Commons Deed–machine-readable stack. If those are removed, what remains is a public license in general. Because this vocabulary and legal machinery do not recur literally across unrelated substrates, Creative Commons License is domain-specific rather than prime.

License as Coordination is the minimal strict parent. A CC license is a canonical instance of replacing per-use permission bargaining with published standing terms that an indefinite public can inspect and rely on. The proposed DAG contains one review-only child-to-parent subsumption edge to prime:license_as_coordination.

Contract is related but not a universal parent. The 4.0 legal code expressly addresses how the license may be interpreted as a contract, while public licenses can also operate as permissions under copyright without fitting every jurisdiction's bilateral-contract model. The safer genus is License as Coordination.

Access Control is a boundary, not a parent: access is technical availability, while the license is normative permission after or independent of access. Open Availability and Open Publication for Interoperability are neighboring governance bundles. They require findability, access, reuse-ready form, or nonrestrictive derivative permissions that a CC license alone—especially an NC or ND license—does not guarantee. Commons Governance is broader collective stewardship and not entailed by applying one license.

Relationships to Other Abstractions

Local relationship map for Creative Commons LicenseParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.CreativeCommons LicenseDOMAINPrime abstraction: License as Coordination — is a kind ofLicense asCoordinationPRIME

Current abstraction Creative Commons License Domain-specific

Parents (1) — more general patterns this builds on

  • Creative Commons License is a kind of License as Coordination Prime

    License as Coordination is the minimal strict parent.

Hierarchy paths (5) — routes to 4 parentless roots

Neighborhood in Abstraction Space

Creative Commons License sits in a sparse region of the domain-specific corpus (100th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (1565 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08

Not to Be Confused With

  • Creative Commons: the nonprofit organization that publishes the legal tools. It is generally not a party to licenses between a licensor and public users.[7]
  • CC0: a public-domain dedication and fallback mechanism, expressly not one of the six CC licenses.[11][2]
  • Public Domain Mark: a marking tool for works believed to be free of known copyright restrictions, not a permission grant.
  • Copyright: the background exclusive-rights regime. A CC license selectively authorizes acts within that regime without transferring the underlying ownership.
  • Open Availability: a resource-governance posture requiring findability, access, explicit terms, and substantive reuse. A CC license can be one legal component, but an inaccessible file or an ND-licensed resource does not satisfy the whole posture.
  • Open-source software license: a software-specific legal instrument. Creative Commons recommends established software licenses rather than CC licenses for software and hardware.[2]
  • Free use or fair use: statutory exceptions and limitations can authorize conduct without the license; CC conditions do not narrow them.
  • Terms of service: platform rules governing an account or service relationship, which may coexist with but cannot silently rewrite the CC grant to downstream recipients.
  • A license deed: the human-readable summary. The deed is not the license; the legal code is the operative layer.[8]
  • A “CC” badge without scope and version: incomplete marking that may fail to tell a reuser which terms govern which material.

References

[1] Creative Commons, “About CC Licenses,” official overview. registry ↩a ↩b

[2] Creative Commons, “Frequently Asked Questions,” official FAQ. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i

[3] Creative Commons, “Creative Commons Licenses,” official six-license and four-condition overview. registry ↩a ↩b

[4] Creative Commons, “Attribution-ShareAlike 4.0 International — Legal Code,” canonical legal code. registry ↩a ↩b ↩c ↩d ↩e

[5] Creative Commons, “Attribution-NonCommercial 4.0 International — Legal Code,” canonical legal code. registry ↩a ↩b ↩c ↩d

[6] Creative Commons, “Attribution-NoDerivatives 4.0 International — Legal Code,” canonical legal code. registry ↩a ↩b ↩c ↩d

[7] Creative Commons, “Attribution 4.0 International — Legal Code,” canonical legal code. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j

[8] Creative Commons, “Legal Code Defined,” official explanation of the legal-code, deed, and machine-readable layers. registry ↩a ↩b ↩c ↩d ↩e

[9] Creative Commons, “License Versions,” official version history and suite roster. registry ↩a ↩b

[10] Creative Commons, “What's New in 4.0,” official Version 4.0 explanation. registry ↩a ↩b

[11] Creative Commons, “Public Domain,” official CC0 and Public Domain Mark explanation. registry ↩a ↩b ↩c

[12] Creative Commons, “Compatible Licenses,” official BY-SA compatibility list. registry ↩a ↩b

[13] Creative Commons, “Attribution 4.0 International — Deed,” official human-readable summary. registry ↩