A design asset can look free to download and still be unsuitable for a client project. This reusable license audit checklist helps you verify fonts, icons, photos, vectors, mockups, templates, and other creative assets before delivery, publication, or launch.
Overview
License checking is part of the production workflow, not a final administrative task. A file may be available at no cost while limiting commercial use, requiring attribution, restricting modifications, or allowing use only while a subscription remains active. The relevant question is not simply “Can I download this?” but “Can I use this specific file, in this specific project, for this specific audience and distribution channel?”
Before using any design resource, record five essentials: the asset source, the applicable license, the permitted project use, the evidence supporting your decision, and any future obligation. Keep the record with the project rather than relying on a browser bookmark or memory. Provider pages can change, files can be replaced, and subscription access can end.
This process applies to free design assets and paid creative assets alike, including stock photos for designers, free vectors, texture packs, icon packs, mockup templates, social media templates, UI kits, fonts, and branding resources. For a broader file-management system, see the design asset library organization guide.
License types at a glance
| License or condition | What to verify | Typical workflow question |
|---|---|---|
| Personal use | Whether business, client, promotional, or revenue-generating work is excluded | Is this project connected to a business, product, client, or paid campaign? |
| Commercial use | Which commercial applications are allowed and whether special exclusions apply | Can the asset appear in the final public-facing work? |
| Editorial use | Whether use is limited to news, commentary, education, or documentary contexts | Is this content promotional or intended to sell, endorse, or advertise? |
| Attribution required | Where credit must appear and what wording or link is required | Can the required credit be included in the website, caption, credits page, or packaging? |
| Modification allowed | Whether cropping, recoloring, combining, animating, or adapting is permitted | Will the asset be edited or incorporated into a larger design? |
| Redistribution restricted | Whether the original or an editable version may be shared | Will the client receive source files, templates, fonts, or downloadable assets? |
| Subscription-based | Whether use depends on an active subscription, registration, or project-specific download | Does the license cover the intended use after access or membership ends? |
These categories are practical review labels, not substitutes for the provider’s actual terms. When wording is unclear or the project carries substantial legal or financial risk, pause the work and request clarification or professional advice.
Checklist by scenario
Fonts
- Identify the exact font family, weight, file format, and download source.
- Confirm whether desktop design, web embedding, app use, video, advertising, and client transfer are treated differently.
- Check whether the license covers the number of users, devices, websites, or projects involved.
- Record whether the client needs the font file or only exported artwork.
- Keep the license file, purchase receipt, or terms-page capture with the project record.
Icons and UI assets
- Check whether individual icons and the collection have separate license terms.
- Verify commercial use, attribution, modification, and redistribution rules.
- Confirm whether icons may be bundled inside a website, app, design system, or downloadable product.
- List any required credit in the project’s documentation or credits file.
- Review the final export so a restricted source file is not accidentally included in a handoff package.
When evaluating UI icons, format and coverage matter alongside licensing. The commercial UI icon pack guide provides a related review framework.
Photos, vectors, and illustrations
- Save the original asset URL, creator name if listed, download date, and license version or wording.
- Distinguish commercial permission from editorial-only permission.
- Check restrictions involving recognizable people, logos, trademarks, locations, products, or sensitive subjects.
- Confirm whether substantial alteration is allowed and whether the file can be used in merchandise, advertising, or templates.
- Do not assume that a search result, social post, or repost is the original source.
For stock photos, use the same project-first approach described in how to choose and license stock photos for commercial design projects.
Mockups, templates, textures, and patterns
- Determine whether the mockup is for presentation only or may be included in a product, template, course, or downloadable pack.
- Check whether editable PSD, vector, font, or texture files can be transferred to a client.
- For texture packs and seamless patterns, verify whether the finished design and the underlying files have different permissions.
- Test the asset in the intended output, but do not treat technical compatibility as proof of licensing.
- Record replacement options if the asset cannot be cleared for the final use.
A tileable background may be suitable for a finished poster but restricted when redistributed as a standalone pattern. The seamless pattern resource guide covers that distinction in practical terms.
What to double-check before delivery
Use a simple asset register for every file that survives the design process. A spreadsheet, project-management table, or version-controlled text file is sufficient if it is maintained consistently. Include these fields:
- Asset ID and filename: Use a stable name that remains understandable after export.
- Type and role: For example, hero photo, display font, interface icon, logo mockup, or background texture.
- Source URL and creator: Record the direct page where the file was obtained.
- License evidence: Save a license document, receipt, permitted-use statement, or dated capture of the relevant terms.
- Project scope: Note the client, brand, campaign, media, territory if relevant, audience, and intended duration.
- Restrictions: Record attribution, modification, user-count, redistribution, editorial, or subscription conditions.
- Expiration or review date: Add one when the terms, subscription, registration, or project authorization may change.
- Decision and reviewer: Mark the asset as cleared, cleared with conditions, pending, or replaced.
- Replacement plan: Name an approved alternative or explain where a replacement can be sourced.
Then compare the register with the final delivery folder. Remove unused licensed files, restricted source files, and unapproved alternatives. If the client receives editable files, explain which assets may be edited, embedded, or reused and which must remain internal. The client brand asset handoff checklist can help structure those usage notes.
For websites and apps, perform a separate production check. Confirm that icons, images, fonts, and graphics in the build match the cleared versions. A visual QA pass is useful, but it should accompany—not replace—the license register. See the website UI asset QA checklist for a related launch review.
Common mistakes
- Relying on the word “free.” Free often describes price or access, not unrestricted use. Open the actual terms before placing the asset in a commercial design.
- Saving only the file. A downloaded asset without its source and license evidence is difficult to verify later.
- Assuming one license covers every use. A font, photo, or template may have different permissions for web, print, video, apps, merchandise, and redistribution.
- Confusing attribution with permission. Adding credit does not automatically make a restricted commercial or editorial asset suitable.
- Sharing editable source files without checking. A finished logo, poster, or interface may be cleared while the underlying font, photo, icon, or mockup is not transferable.
- Ignoring updates to provider terms. A library assembled months ago may contain old links, discontinued files, or changed conditions.
- Using a preview or repost. Preview images and third-party uploads may not carry the same permissions as the original download.
- Failing to plan a substitute. A replacement plan reduces delay when an asset cannot be approved at the final review.
When to revisit
Run this audit before a client handoff, campaign launch, website or app release, print order, public portfolio update, or sale of a template or product. Recheck the register when a project changes audience, channel, geography, duration, client ownership, or distribution method. A design cleared for an internal presentation may need a new review before it becomes a public advertisement or downloadable resource.
For ongoing libraries, schedule a quarterly review or use the beginning of each seasonal planning cycle as a trigger. Prioritize high-use assets: brand fonts, UI icon sets, stock photos, shared templates, texture packs, and files used across multiple clients or channels. Also review whenever your team changes its storage system, subscription providers, design tools, or handoff process.
Keep the routine practical: open the source link, confirm the current terms, compare them with the project scope, update the evidence, and mark the asset cleared, conditional, pending, or replaced. If the terms cannot be located or interpreted with confidence, do not quietly pass the file forward. Isolate it, choose a documented alternative, and note the reason in the asset register. That small pause protects the delivery workflow and makes future audits faster.