Treat “personal” as a use case, not a permission slip
A mood board, practice website, or self-initiated brand concept may not have a paying client, but it can still be seen by other people. Once you post it on a portfolio, social platform, or public repository, you are distributing work that may contain someone else’s images, fonts, or design assets. Being unpaid does not automatically make that use permitted.
Start by listing the outside materials your project uses: photographs, illustrations, icons, textures, templates, fonts, audio, and mockups. For each item, ask where it came from and what permission covers your intended use. A file being easy to download—or appearing in a search result—is not evidence that you can reuse it.
Match the license to what you plan to publish
Read the terms attached to the specific asset, rather than relying on a site-wide label such as “free.” Check whether the license allows public display, modification, redistribution, and commercial use. Think beyond the project’s first version: you might later put it in a portfolio, sell prints, offer a template for download, or adapt the design for a client. A license that works for a private experiment may not cover those later uses.
Pay attention to limits on how an asset can appear. For example, some licenses allow an image in a finished design but do not allow you to pass along the original file in a downloadable template. A mockup or icon pack may also have restrictions on resale as a stand-alone asset. If the terms are unclear, choose an asset with clearer permissions or request permission from the rights holder.
“Royalty-free” usually describes a licensing arrangement; it does not mean an asset has no conditions. Likewise, a Creative Commons license may require attribution or limit commercial use or adaptations. Read the particular license version and follow its conditions. Exceptions to copyright, such as fair use, depend on context and location, so they are not a reliable blanket plan for an ordinary portfolio piece.
Give images and fonts their own checks
With images, check both the permission to use the image and what it depicts. A photographer’s license may not answer every question about a recognizable person, a logo, or private property shown in a photo. If you intend to use an image in a way that suggests endorsement or promotes a product, be especially careful. When in doubt, use imagery made for that purpose, obtain the needed permissions, or change the concept.
Fonts have separate licenses too. A font may permit installation on your computer for making static graphics while requiring different permission to serve font files on a website, include them in an app, or package them in an editable template. Before publishing, check how the font will be delivered—not just how the final design looks. Keep the font’s license information alongside your project files so a future update does not accidentally change how it is used.
Credit creators where required—and keep evidence
When a license requires attribution, follow its instructions for what to include and where to place it. Depending on the project, a credits page, caption, or accompanying description may be more practical than squeezing a credit into the artwork itself. Credit is a way to meet a license condition or acknowledge a creator; it is not a substitute for permission when the license does not allow your use.
Keep a small asset log with the creator’s name, the asset title or filename, where you obtained it, the license or permission you relied on, and any attribution wording. Save a copy of the relevant terms or permission message with the project. This makes it easier to update credits, replace an asset, or check the rules again before changing how you publish the work.
Make the final review part of publishing
Before you share a project, review the actual deliverable. A flattened portfolio image, a live website, and a downloadable source file expose assets in different ways. Remove unused files from public folders, confirm that required credits are present, and check whether any license prohibits the format you chose.
If an asset fails the check, you do not have to abandon the project. Replace it with something you created, find an alternative with suitable terms, or seek permission. Building this review into your workflow lets you experiment freely while keeping the published version clear, documented, and easier to reuse.
