How should Creative Commons licence data be embedded in a file?

Embed a URI or hyperlink to the material, a copyright notice, a notice referring to the licence, a warranty disclaimer, and identification of the creator and any designated attribution parties. Then add machine-readable fields in XMP, HTML and site-specific fields. If the licensor requests removal, you must take that attribution down where reasonably practicable. Before embedding anything, open the original source page, record the creator, source URL, exact licence and version, displayed notices, exclusions and the date checked, then confirm your intended activity against the ND and NC conditions.

Place The Notice Where A Person Sees It

Start with what a human sees on the file itself. For an image, put the licence notice in the caption, in an adjacent text file, or in a metadata panel the application displays by default. The notice must name the work, identify the creator, include a copyright notice and a notice referring to the licence, and provide a URI or hyperlink to the material where reasonably practicable. Under 4.0, you must also link or refer to the licence and indicate modifications, retaining earlier modification notices. A PDF supports text layers, so place the notice on the first page or in a credits section. For video, overlay a brief licence credit in the opening or closing frames and include the full notice in the video description.

Do not assume a single line of text satisfies the condition. The 4.0 legal code requires that you retain, when supplied, all of the following: identification of the creator and designated attribution parties, a copyright notice, a notice referring to the licence, a warranty disclaimer, and a URI or hyperlink to the material. The version 4.0 FAQ clarifies that the work's title is not separately required. Including it is good practice and older versions may require it when supplied. The failure case here is omitting the link to the licence or the indication of modifications. A text credit without a URI has not fully met the attribution condition.

Audio And The Removal Exception

For audio files, a spoken credit at the start or end is reasonable only if it includes the licence reference and a way to locate the original. A written notice in the file's ID3 tags or embedded fields is the more durable approach. The decisive exception applies if the licensor requests removal: you must remove attribution where reasonably practicable. Keep a screenshot or copy of the request.

XMP, the Extensible Metadata Platform, is the standard way to embed licence data inside image, audio, video and document files. The XMP field for the licence URI is dc:rights or cc:license. The Dublin Core rights element holds the work's copyright notice or a reference to the licence. Creative Commons recommends using the cc:attributionName and cc:attributionURL fields alongside the cc:license field. These fields survive file conversion better than visible text because they are part of the file structure, not a rendered layer.

Most image editors, including Adobe Photoshop and Lightroom, write XMP fields on export. A PDF can embed XMP in its document information, accessible under File Properties. The failure case is that many online services strip or ignore XMP when a user uploads the file. The service re-encodes the file and drops the embedded fields, leaving only the original visible notice on the source page. For a file that will be redistributed directly, XMP is reliable. For a file uploaded to a social service, treat the XMP as a backup that may or may not survive.

The 4.0 legal code requires that attribution information be retained where reasonably practicable. If a service strips the XMP but the visible notice remains on the source page, the reuser is still responsible for supplying the attribution in a reasonable manner for that medium. Check current terms for whether they preserve embedded fields. YouTube and Flickr have retained some fields in the past, but verify each service's current help page rather than assuming it still works.

For web pages, the licence data lives in the HTML <head> and in structured data markup. The <link> element with rel="license" inside the page's <head> points to the licence deed. Google and other search engines read this for snippet display. The <meta> element with name="description" can include the licence terms. RDFa, a W3C standard for embedding structured data in HTML, marks up the attribution data directly in the page's visible content. The Creative Commons chooser generates an RDFa snippet that includes the author, licence, work title and source URL.

Schema.org markup with the CreativeWork type and the license property provides a machine-readable alternative that major services recognise. The failure case is incomplete markup: a rel="license" link without the corresponding <meta> elements may not be picked up by all services. The 4.0 FAQ states that the URI or hyperlink to the material should be where reasonably practicable. A page without a visible link but with HTML fields only is not compliant if the reuser must supply a URI to the material. For a simple webpage, include both the visible text credit and the HTML structured data.

Video, Photo And Audio Services

Each service maps Creative Commons licence conditions onto its own publishing and credit fields differently. For YouTube, the built-in CC option has been CC BY in the past, but verify its current help page before assuming. The video description must still include the creator name, source URL, exact licence and version, and an indication of any modifications. Content ID is a private system; proof of a valid licence supports a dispute but does not guarantee the outcome. The failure case is that YouTube's CC option applies only to the video file itself, not to music, clips or other components that may have separate terms.

For Flickr, the licence dropdown on the upload page sets a visible notice on the photo page and populates the photo's API fields. The attribution credit in the photo description is separate from the automated licence field. Include both. For SoundCloud, the licence field is part of the track's metadata panel and appears below the player. The 4.0 legal code requires that attribution information be supplied where reasonably practicable. A service that hides the credit behind a click-through or a collapsed field may not satisfy the requirement. Check the service's current terms and test the view from a logged-out incognito browser.

File Hosting And The DRM Conflict

For a dedicated file hosting service like the Internet Archive, the form includes fields for creator, date, collection and licence. Fill every field that maps to the attribution conditions: creator, source, licence URI and any warranty disclaimer supplied. The failure case is a service that imposes exclusive sublicensing terms or download restrictions. The 4.0 legal code states that a recipient may not impose additional legal terms or effective technological measures that restrict another recipient's exercise of the licensed rights. A service with DRM or a requirement to accept non-CC terms creates a conflict. Do not assume a CC badge on that service resolves the conflict. Check the service's current terms of service.

A service that requires users to agree to exclusive sublicensing terms or that applies digital rights management to downloads may violate the 4.0 licence. The 4.0 legal code prohibits imposing effective technological measures that restrict a recipient's exercise of the licensed rights. DRM that prevents copying, printing or redistribution of a CC-licensed file is a conflict. A CC licence badge on the service does not override the terms of service. Check the service's current terms before uploading a CC-licensed work to it.

If a service's terms grant it a non-exclusive licence to display the work but also require the user to waive the right to redistribute the file outside the service, the 4.0 conditions may still apply to the uploaded file. The licence operates between the original licensor and downstream recipients. The service is not a party to that licence. Choose a service whose terms do not restrict the exercise of the CC permissions. For works you intend to share directly, a service that preserves the original file without DRM is necessary.