Practical guide · Reviewed November 5, 2026

How to check an asset license before you use it

Finding a useful image, font, icon, sound, 3D model, code sample, or AI model is only the first step. Before you put it in a website, video, app, or product, confirm that the exact file and your intended use are covered by clear terms. A search result that says “free”� is not a license.

1. Start from the original item page

Open the page for the individual asset—not just a search listing, collection page, social post, or download mirror. Record the creator or publisher, the asset title or identifier, the original URL, and the license shown on that page. If the page does not identify a license or permission, do not assume that downloading means you may reuse the work.

Check that the license applies to the actual file you want. A site may host contributions from different people under different terms, and a single creator may publish some assets under one license and other assets under another. Save the item's own license link or a copy of the license text as it appeared when you obtained the asset.

2. Match permissions to your planned use

Write down what you intend to do: personal project, client work, commercial product, social post, template distribution, or modification. Then check the license for the permissions and conditions that match that plan.

These are different questions. Permission to display an image in a finished project does not necessarily mean you can repackage the image as a downloadable stock asset.

3. Check rights that a copyright license may not cover

An asset license may not grant every permission needed for a particular use. A photo can include an identifiable person, a private location, artwork, a product logo, or a trademark. A 3D scene can contain separately licensed textures or branded objects. Check for model releases, property permissions, trademark rights, privacy requirements, and third-party material when those issues matter to your project.

Be especially careful with sensitive or misleading contexts. Permission to use a photo is not permission to imply that a real person endorses a product, has a particular medical condition, or is involved in an event.

4. Treat software, fonts, media, and AI models separately

There is no single “open source”� license that covers every kind of resource. Software licenses such as MIT or Apache-2.0 may require you to retain notices or satisfy other conditions. A project can also depend on packages with different licenses, so review the dependency list and license files when you distribute software.

Font licenses apply to the font software and can have specific rules for embedding, redistribution, or modification. Read the license attached to the exact family and files you use. Audio and video platforms commonly attach terms to individual recordings or asset types; confirm whether synchronization, commercial projects, edits, and redistribution are permitted.

For AI workflows, check the software license, the model's license, dataset terms, and hosted service terms separately. A tool being open source does not automatically make every model, dataset, input, or generated output unrestricted. Review the model card and terms for the exact version, including any limits on commercial use or redistribution.

5. Keep a small asset record

Use a simple record for assets that matter to a project. It helps you reproduce credits, answer client questions, and revisit terms later.

If a license is unclear, the asset page conflicts with the license text, or the intended use is high-risk, choose a clearly licensed alternative or ask the rights holder for written permission.

6. Write attribution from verified details

When a license requires attribution, use the creator's requested wording if provided. Otherwise, a useful starting draft often identifies the work, creator, source, and license, and notes whether you changed it. Some licenses require additional details; your draft must follow the actual license rather than a generic template.

Example structure: “[Work title] by [creator], source: [original URL], licensed under [license and link]. Modified from the original.”�

Use the attribution-note builder

Read the commercial image-source comparison

Examples to think through

A photograph in a company homepage

Check the photo's item page and the provider's license. Confirm commercial use is allowed, and review whether identifiable people, logos, or sensitive subject matter require additional permission. Save the source and license record even if credit is optional.

An icon inside a downloadable UI kit

Check whether the icon license covers redistribution inside a template or icon pack, not only use inside a finished interface. Keep any required license and copyright notices in the kit's documentation or distribution files.

A font bundled with a web app

Read the license for that exact font family and confirm the way you embed and distribute the font is allowed. Keep required notices and do not assume that the repository's software license also covers its bundled fonts.

Use the original source as the authority

Our Open Library directory is a discovery aid. Providers can update their catalogs and terms, and descriptions can become outdated. Always use the current license and rights information attached to the specific asset you plan to use.

This guide is general educational information, not legal advice. License interpretation can depend on your project and jurisdiction; consult a qualified professional when needed.