Who Owns UI Design Copyright?

Before final payment, a client asks, “Will the font files be included?” Only then does the designer realize the fonts use a personal subscription license. After development begins, the team discovers that some icons come from a paid component library and cannot be transferred directly. Both sides thought “complete handover” was clear, but they were discussing different assets.

A UI project should distinguish at least four matters: how final design deliverables may be used, whether editable source files are delivered, whether third-party assets can transfer with the project, and whether the vendor retains portfolio-display rights. Each should be defined separately in the contract and handover checklist.

01 Distinguish Usage Rights, Copyright, and File Handover

Receiving rights to use interface pages does not necessarily transfer every copyright. Receiving copyright does not automatically include design-process files. Receiving a Figma file does not mean every font, image, and plugin inside can be freely resold.

The contract should define the payment conditions that trigger rights transfer, covered media and regions, whether modification and sublicensing are permitted, and the format of source-file delivery. Qualified legal professionals should confirm the specific legal arrangement for the project.

02 List Project Deliverables by Asset Type

A UI design may include brand assets, page layouts, original icons, illustrations, photography, fonts, open-source components, and third-party templates. Each category has a different source and license. Saying “all copyright belongs to the client” may not cover third-party assets the vendor has no right to transfer.

03 Define Where and in What State Figma Source Files Are Delivered

A read-only link may stop working when the vendor account closes. Copying files to the client’s team space may break component links, fonts, and plugins. The contract should define who holds the final file, whether component libraries, explorations, and version history are included, and when transfer occurs.

Usually there is no need to deliver every rejected concept or internal working file, but final approved pages, critical states, components, styles, interaction notes, and necessary assets should remain editable. Both parties can define this before the project starts.

04 Fonts Are the Most Commonly Overlooked Licensing Risk

System, open-source, commercial, and platform-subscription fonts have very different licenses. A designer’s personal account may permit proposal use without allowing the client to use the font long term in a website, APP, or advertising, or to receive the font file directly.

A more reliable approach is a font inventory recording the source, licensee, permitted media, and alternative. If the client must purchase its own license, explain this before the direction is confirmed to avoid replacing the font immediately before launch.

05 Track Sources for Images, Icons, and Generated Assets

Stock licenses may limit print quantities, advertising, template resale, or sensitive uses. Images of people can require model releases. Icon libraries may require attribution or restrict distribution of source files.

Assets created with generative tools should not automatically be declared “completely free of copyright risk.” Record the tool, input assets, human modifications, and usage scope, and avoid imitating a specific living artist or using unlicensed brand assets. Legal counsel should assess important commercial projects.

06 Component Libraries and Code Have Separate Rights

Open-source components, commercial design systems, and vendor-owned components used in UI design may be licensed only for this project. Copyright in development code, open-source dependencies, and deployment rights should be agreed separately. Delivery of design source files does not automatically transfer all code.

If the vendor retains general-purpose components and methods, define which deliverables are project-specific and which are reusable foundational capabilities. This prevents the client from later believing its assets were used in a competitor’s project.

07 Portfolio Rights and Confidentiality Can Coexist

Design teams usually want to show work after launch, while clients may have confidentiality, regulatory, or release-timing requirements. The contract can define when work may be shown, whether it must be anonymized, which pages and data require treatment, and whether the client may withdraw permission in specific circumstances.

“The vendor may publish anything forever” and “publication is prohibited forever” may both be overly absolute. Boundaries based on project sensitivity are easier to agree.

08 Define at Least Eight Items in the Contract

Specific wording should follow the project and legal advice, but at the business level the agreement should address at least the following.

• Distinguish final deliverables from third-party assets;
• Payment conditions and timing for rights transfer;
• Permitted media, regions, term, and modification scope;
• Delivery state of Figma and other editable source files;
• Licensing responsibility for fonts, stock assets, icons, plugins, and templates;
• Treatment of rejected concepts and the vendor’s general-purpose components;
• Portfolio display, attribution, and confidentiality boundaries;
• Infringement notices, replacement options, and allocation of responsibility.

09 Create an Asset Register at Handover

An asset register need not be complex. Each row can record name, type, source, license, file location, owner, and renewal date. When design or development teams change years later, it is far more reliable than chat history.

Copyright and licensing are not legal formalities for the final project day. They should be considered while selecting the direction because changing a font, image, or component can directly alter the design.

Frequently Asked Questions

Does copyright automatically transfer to the client after all design fees are paid?

There is no universal answer. Applicable law and the contract govern. The project should define the type of rights, transfer conditions, and permitted scope.

Can a client require Figma source files?

It depends on the contract and quote. Define whether they are delivered, their scope, account ownership, and timing before the project starts.

Can commercial font files be sent directly to the client?

Not necessarily. Many font licenses prohibit file transfer, and the client may need to purchase website or APP rights in its own name.

Can the designer include the project in a portfolio?

Follow the contract, confidentiality, and release-timing terms. Options include delay, anonymization, or hiding sensitive information.

Are open-source icons always available for commercial use?

Review the specific license, including attribution, modification, distribution, and sublicensing conditions. Do not rely only on a “free” label.