On this page
AI-assisted design raises several questions that are easy to collapse into one: may you upload the source material, may you use the output, can you protect the result, and should you publish it? A provider's commercial-use permission does not settle all of those questions.
For working designers, the practical response is a documented review process rather than a blanket promise that generated assets are safe or unsafe. Separate legal rights, contractual duties and ethical judgement. This article offers a workflow, not legal advice; obtain qualified advice for consequential or disputed uses.
Separate the rights questions
Start with input permission. A client may own a photograph but still restrict where it can be processed. A licensed stock asset may have terms governing modification or machine-learning use. Internal access to a file does not automatically authorise uploading it to an external generation service.
Next examine output permission in the provider's current terms and the agreement covering your account. Commercial-use language, warranties, exclusions and indemnity provisions are not interchangeable. Record the applicable terms and review date instead of relying on a marketing page remembered from a previous project.
Then consider copyright protection for the finished work. This depends on jurisdiction and the nature of human contribution, not merely on paying for a tool. The US Copyright Office's AI resources explain its work on these issues. Do not treat US guidance as a universal rule for clients operating elsewhere.
Finally assess third-party rights. Permission from a generator does not establish that an output avoids protected expression, trade marks, publicity rights or other claims. These are distinct review tracks. An asset can be permitted under a service contract and still be unsuitable for a particular campaign.
Build originality from a brief, not an imitation
Translate references into design principles rather than asking for a living artist's signature style or a competitor's recognisable campaign. Describe composition, contrast, density, texture and audience needs. This creates a clearer design brief and reduces dependence on somebody else's distinctive creative identity.
For example, replace a request to reproduce a particular brand's landing page with a specification for a restrained editorial layout, generous spacing, asymmetric image placement and clear navigation. Those choices still require creative judgement, but they do not define success as resemblance to a named source.
Use the Tailwind palette generator to develop colour scales from approved starting colours, then document how you selected and adjusted the resulting palette. Palette generation is not an originality test or a rights clearance service. Review the whole visual system, including typography, imagery and composition.
The AI image tools directory can help you compare workflows, but evaluate source controls and editing options as well as visual quality. A tool that supports meaningful iteration and retained project history can be easier to govern than a generator that only returns a finished image with little context.
Keep evidence of human decisions
Maintain provenance records as you work: source assets, relevant licences, prompts, selected outputs, substantive edits and approval decisions. Avoid collecting sensitive data merely to make the record comprehensive. Store enough evidence to explain the process without turning the archive into a new confidentiality problem.
A short project record can follow this structure:
Purpose: supporting illustration for the onboarding guide.
Inputs: approved internal sketch and licensed reference assets.
Generation service: account and terms review recorded separately.
Human decisions: composition revised, figures redrawn, labels replaced.
Checks: similarity, brand, factual content and accessibility reviewed.
Approval: named owner, date and permitted publication channels.Describe human contribution accurately. Selecting an output, rewriting a prompt and substantially redrawing an illustration are different activities. Do not claim that a detailed prompt automatically establishes ownership of every generated element. If registration or a rights dispute matters, discuss the actual workflow with counsel.
Provenance also supports maintenance. If a licence changes, a source becomes disputed or a client expands distribution, the team needs to identify affected assets. A folder called “final images” with no source records makes that work slow and uncertain, regardless of whether AI was involved.
Review similarity and sensitive representation
Perform a similarity review before publication. Search for recognisable logos, characters, signatures, distinctive packaging and composition that appears unusually close to a known work. Reverse-image search can reveal useful leads, but a clean result is not proof of non-infringement. These tools have incomplete coverage and cannot resolve legal questions.
Trade mark concerns are not limited to exact logo copies. Context, product category and the likelihood of confusion matter. The WIPO trade mark overview is a useful introduction, not a replacement for jurisdiction-specific clearance on a major identity project.
Apply representation checks separately from rights checks. Look for stereotyping, misleading depictions of real people, fabricated documentary scenes and implied endorsements. A legally usable image may still be deceptive or harmful when presented as evidence of a real event or customer experience.
Ask who is missing from the review. Designers cannot reliably assess every cultural reference from their own perspective. Seek appropriate expertise for sensitive subjects, and give reviewers enough context to judge the intended use. Do not expect an automated bias score to replace informed discussion or affected people's perspectives.
Agree disclosure and delivery rules early
Set client expectations before production. Agree whether AI assistance is permitted, what types of content require approval and whether confidential materials can enter external services. Explain meaningful limitations without suggesting that human-made work carries no risk or that AI-assisted work is automatically unprotectable.
Disclosure should match the context. A generated decorative texture raises different concerns from a synthetic testimonial portrait or a fabricated product demonstration. Consider audience expectations, platform rules, contractual requirements and applicable law. Avoid presenting synthetic evidence as a genuine customer, event or tested product capability.
The NIST AI Risk Management Framework offers a broader structure for identifying and managing risks. Use it as a planning aid, not a certificate that a design is ethical. Assign owners for decisions and a route for raising concerns before publication deadlines make review perfunctory.
Connect rights review to the wider AI workflow and your Figma-to-code handoff. Deliver approved assets with source notes, permitted uses and outstanding restrictions. If the client later wants merchandise, advertising or resale, revisit the clearance rather than assuming the original web-use decision covers every new channel.
Key takeaways
- Review input permission, output terms, protection and third-party rights separately.
- Brief for design principles rather than recognisable imitation of another creator.
- Keep proportionate records of sources, edits, approvals and applicable terms.
- Assess similarity, representation and misleading context before publication.
- Agree client rules early and revisit clearance when the intended use changes.
Reach designers & developers at work
Put your product next to the tools people use every day. One sponsor per placement, no tracking pixels.
Become a sponsor