Keep a Footage and Asset Permission Log Before You Publish
A permission log helps a creator answer a practical question: why can this particular asset appear in this particular piece? It should connect the file in your project to a source, a permission record and the intended use. This guide offers an original organisational workflow, not legal advice or a guarantee that a licence covers every situation. When the rights are unclear, seek clarification or choose material you can use with confidence before publication.
Photo: Hanna Pad · License. Illustrative stock photography.
Inventory the actual assets in the edit
List the photographs, footage, music, sound effects, fonts, graphics and outside contributions that appear in the final project. Include assets that came inside a template rather than assuming the template settles every embedded permission. Give each item an ID and connect it to its filename or timeline location. Distinguish material you made from client-supplied and third-party material. The list should reflect what is actually used, not every file you downloaded while exploring. That makes the final review manageable and helps locate an asset if a question arises later.
Record the source and the claimed permission
Use fields for asset ID, creator, original source URL, licence name and version, date checked, evidence location, intended use and restrictions. Save a relevant permission message or licence record using an appropriate method. A link alone can become unavailable, while a screenshot alone may omit the source identity or important conditions. Avoid relying on a reposting account's claim when the original creator is unknown. For commissioned contributions, record the agreed use and ask a qualified professional when ownership or contractual questions need interpretation.
Read the licence rather than the word free
Creative Commons offers different licences with different conditions, including attribution, noncommercial restrictions or limits on adaptations. The CC label is not one universal permission. Check the specific licence and whether it fits your proposed use, edits and distribution. Do not assume a crop, translation or remix is automatically acceptable under every licence. The same practical caution applies to stock libraries: a downloadable preview is not necessarily the licensed production asset. If the terms do not clearly cover your situation, resolve the question before building the piece around the material.
Keep music permissions separate from visual permissions
A clip may include a recognisable song even when you have permission from the person who filmed it. Record the soundtrack as a separate item and inspect the intended platform use. YouTube's Audio Library provides tracks with licence information, and some require attribution. Preserve the attribution text when it applies. Do not assume permission for one platform extends to paid advertising, another platform or a downloadable client file. If you cannot establish the required use, replace the track or publish without it rather than hiding it beneath narration.
Write credits from the record
Create the credits from the log after the edit is stable. Match names, titles and licence details to the actual assets, and include modification notes when the applicable terms require them. Put the credit where the permission arrangement calls for it, rather than in a private document nobody receives. An original row example is: A07 | desk photograph | photographer name | original URL | licence/version | cropped | attribution in description | record saved at __. Replace every placeholder before publication and avoid copying credits from an unrelated project.
Recheck the final use and archive the evidence
Compare the final export with the asset list and remove unused rows from the publication checklist while preserving your internal research record. Check whether the piece has become sponsored, moved platforms or added a new distribution format, because the intended use may have changed. Save the log with the matching video version. YouTube notes that its reused-content monetisation review is separate from copyright permission; having a log does not promise platform approval. Its purpose is to keep decisions traceable and help you identify unresolved material before an audience or client sees it.
Your working checklist
Checkmarks stay in this browser when storage is available. They do not submit a form or complete a booking.
Put it into practice
- Inventory the assets actually used and assign IDs that connect to filenames or timeline locations. Include music, embedded template assets and outside contributions.
- Record creator, source, specific permission, intended use and restrictions for each item. Resolve uncertain ownership or licence conditions rather than relying on a general free label.
- Build the final credit text from the log and compare it with the edit. Check platform, advertising and adaptation uses against the relevant permission arrangement.
- Archive the log and evidence with the matching publication version. Revisit permissions when you reuse the material in a different project or distribution setting.
Before you finish
- Every outside asset in the final piece has a traceable source.
- The actual licence conditions were read rather than inferred.
- Music and visual permissions are considered separately.
- Required attribution matches the used asset and intended placement.
- No permission record is presented as guaranteed monetisation approval.
Common questions
Is credit enough to use another person's clip?
Credit and permission are different questions. Determine the applicable permission or lawful basis for use; do not assume that adding a name makes any reuse acceptable.
Can I use a Creative Commons asset commercially?
It depends on the particular licence and situation. Some CC licences permit commercial use, while others restrict it. Read the specific terms and any relevant rights limitations.
Does a client's supplied folder prove all rights are cleared?
No. Ask the client to identify sources and the agreed use. Record their information, and flag uncertainty before publication rather than treating file access as a complete permission record.