NDA for Freelance Designers: 5 Clauses That Can Kill Your Career
Your portfolio is your business. It's how you get the next client, justify higher rates, and demonstrate a body of work that builds over years. For most freelance designers, it took dozens of projects and thousands of hours to create.
Some NDAs take it quietly. Not with dramatic language about ownership or seizure — with a clause near the end of a standard confidentiality agreement that prohibits disclosure of any information related to the engagement, undefined and unlimited. Under that language, you can't show the app you designed. You can't include the brand system in your portfolio. You can't even list the company as a client on LinkedIn without potentially breaching the agreement.
Portfolio restriction is the most common NDA risk for freelance designers, but it's not the only one. Designers also face hidden traps around tool and asset ownership, non-compete scope, attribution rights, and IP claims on pitch work that was never shipped. Here's what to find and what to request before you sign.
Clause 1 — Portfolio Rights (The Big One)
A standard NDA prohibits disclosure of confidential information. The problem for designers is that "confidential information" in most client NDAs is defined broadly enough to cover everything you produced: the visual designs, the brand system, the UI components, the user flows. All of it is "proprietary information related to the Company's products and services" — which is exactly what your portfolio is made of.
The clause doesn't have to say "you can't use this in your portfolio." It just has to define your work product as confidential information and prohibit disclosure. The effect is the same.
What makes this clause particularly dangerous for designers specifically — more so than for developers or consultants — is that designers' work is entirely visual and presentational. A developer can describe the architecture they built without showing proprietary code. A consultant can reference the engagement type without sharing strategic details. A designer's portfolio by definition shows the work. You can't partially disclose a visual design the way you can partially describe a technical implementation.
What to look for: Any clause that defines "Confidential Information" to include work product, deliverables, or materials created during the engagement — combined with a prohibition on disclosure to third parties. Read these two provisions together. Separately they may seem reasonable. Combined, they prohibit your portfolio.
What to request:
Portfolio carve-out:
"Notwithstanding the foregoing, Designer retains the right to display visual work product created under this Agreement in Designer's professional portfolio, website, and case studies, provided that (a) no financial, strategic, or operational confidential information of the Company is disclosed, (b) the display does not occur until [90 days / the product's public launch, whichever is earlier], and (c) Designer notifies Company at least 14 days before any such display to allow for reasonable review."
This language gives the client real protection — strategic and financial information stays confidential, and there's a delay to accommodate pre-launch sensitivity — while preserving your ability to build a portfolio from your own work. Most clients will accept this framing because it addresses their actual concern (confidential business information) rather than blanket-prohibiting work attribution.
Clause 2 — Tool and Asset Ownership
This clause affects designers more than almost any other freelancer type because design work is created with specialized, proprietary toolsets — Figma libraries, icon sets, component systems, typography collections, motion templates — that designers build and carry across engagements.
The risk: a broadly written IP assignment clause doesn't distinguish between assets created for this engagement and assets you brought to it. "All intellectual property created in connection with the services" can reach backward into your existing toolkit if you used it during the project.
Here's the specific scenario: you have a Figma component library you've refined over three years and forty projects. You use it to accelerate delivery on a new client's design system, customizing components for their brand. The client's IP clause assigns them ownership of all design assets created during the engagement. Are your original components — now modified — theirs?
The answer depends on how the IP clause is drafted, how much the original components were modified, and which jurisdiction governs. You don't want to find out the hard way.
A secondary issue: design systems and component libraries are typically built iteratively. The system you build for one client may become the foundation for systems you build for others. If an IP clause assigns the client ownership of the system architecture — not just the brand-specific implementation — you may be contractually prohibited from reusing structural decisions you'd normally carry into future work.
What to request:
Pre-existing tools and assets carve-out:
"The IP assignment in this Agreement applies only to works created specifically and exclusively for Company under this Agreement. Designer retains all right, title, and interest in and to: (a) all tools, libraries, components, and assets owned or developed by Designer prior to this Agreement ('Pre-existing Works'); (b) any improvements, modifications, or derivatives of Pre-existing Works made during this engagement; and (c) general design processes, methods, and know-how developed independently of Company's Confidential Information."
Clause 3 — Non-Compete Covering Adjacent Industries
Non-compete clauses are a common risk across all freelance NDAs, but they hit designers in a specific way: design skills are inherently cross-industry. A UX designer who works in fintech will inevitably apply those skills to healthcare, e-commerce, or SaaS. A brand designer who works for a consumer goods company will work for other consumer goods companies. An industry-level non-compete doesn't just limit where you work — it limits whether you can work at all in your area of expertise.
The risk is compounded by how "industry" and "competitor" are defined in startup and early-stage client NDAs. A company whose NDA defines "competitive business" as "any company offering products or services that compete with any product or service offered by the Company" at a company that is still exploring its product-market fit can expand that definition retroactively as the company's direction evolves.
A UX designer who signed an NDA with a fintech startup may find that eighteen months later, the startup has pivoted into healthcare payments — making healthcare a "competitive industry" under a clause they signed before that expansion happened.
What to request:
"The restriction in this Section shall not apply to Designer's work for companies in industries or verticals that are not direct competitors of Company's primary business as of the Effective Date of this Agreement, or to design work that does not involve Company's core product category. For purposes of this Section, 'direct competitor' means a company offering substantially the same product or service to substantially the same customer segment as Company's primary offering."
The "as of the Effective Date" language is the critical addition — it locks the definition to what the company actually is when you sign, not what it might become.
Clause 4 — Attribution Rights on Resume and LinkedIn
Most designers assume they can at least list a client as a past client. That assumption is wrong in some NDAs.
Confidentiality clauses that cover the "existence of the relationship" — not just the work product — prohibit you from mentioning the engagement at all. You can't list the company on LinkedIn. You can't reference it in a job application or to a prospective client. The engagement effectively disappears from your professional record.
This matters most for high-profile clients. Working with a well-known brand or tech company is a significant credential — it signals to future clients that you operate at a certain level. Being prohibited from mentioning it doesn't just affect your portfolio; it affects your professional positioning.
Even NDAs that don't explicitly cover the existence of the relationship can create ambiguity: if "confidential information" includes all information related to the Company, does identifying yourself as a former vendor on LinkedIn count as disclosure? The client may say yes when it suits them.
What to request:
"Notwithstanding any other provision of this Agreement, Designer may identify Company as a former client in Designer's professional resume, LinkedIn profile, and client references, provided that no Confidential Information is disclosed in connection with such identification. Designer may describe the general category of services performed (e.g., 'brand identity design,' 'product UX') without disclosing specific deliverables, strategies, or financial terms."
This is a modest request that most clients will grant — they're not trying to make you unemployable, they're trying to protect their strategic information. The carve-out separates the legitimate concern from the overreaching consequence.
Clause 5 — IP on Exploratory and Pitch Work
This is the clause designers encounter before an engagement even starts — and often miss entirely because they're focused on winning the project.
Many clients ask designers to do exploratory work as part of the proposal process: a few concept directions, rough wireframes, a mood board, initial brand directions. This work is done before any contract is signed. But sometimes, immediately after a client likes the direction enough to proceed, they send an NDA that assigns IP for "all work created in connection with the potential engagement" — which includes the pitch work you already produced.
If you don't proceed (you don't win the project), the client now owns the exploratory designs you created during the sales process. They can use the concept you showed them, hire someone else to execute it, and you have no recourse.
Even when you do proceed, pitch work that didn't make it into the final deliverable — rejected concepts, alternate directions you explored and discarded — may fall under a broadly written IP assignment. The client owns not just what they approved but everything you created in the process of arriving there.
What to request:
"The IP assignment in this Agreement applies only to final deliverables expressly approved by Company in writing. Exploratory concepts, rejected alternatives, and preliminary work created prior to the execution of this Agreement or not included in the final approved deliverables remain the property of Designer. Designer retains the right to display such exploratory work in their professional portfolio provided it does not reveal Company's Confidential Information."
If the client pushes back on retaining exploratory concepts, offer to embargo them (not show them publicly) for a fixed period — say, twelve months — rather than permanently assign them. That's usually enough to address the client's real concern, which is preventing their strategic directions from appearing in competitors' pitches before launch.
Counter-Language Designers Should Ask For
Here's a consolidated view of the five requests, formatted for easy reference when you're reviewing an NDA:
1. Portfolio rights:
"Designer retains the right to display work product in professional portfolio and case studies, provided strategic and financial confidential information is excluded and display occurs after public launch or 90 days, whichever is earlier."
2. Pre-existing assets:
"IP assignment applies only to works created specifically for Company. Designer retains all right, title, and interest in pre-existing tools, libraries, and components, including any modifications made during the engagement."
3. Non-compete scope:
"Non-compete restrictions apply only to direct competitors of Company's primary business as of the Agreement's Effective Date and do not restrict Designer's work in adjacent or unrelated industries."
4. Attribution:
"Designer may identify Company as a former client on resume and professional profiles and describe the general category of services performed without disclosing Confidential Information."
5. Pitch and exploratory work:
"IP assignment applies only to final approved deliverables. Exploratory and rejected work, and work created prior to Agreement execution, remains Designer's property."
You don't need to request all five simultaneously — read the specific NDA first and identify which clauses are actually present and problematic. For a complete understanding of how IP assignment clauses work in NDAs, read our guide on NDA IP clauses. For a broader view of the clauses that create the most risk across any NDA, see NDA Red Flags.
FAQ
Can I show password-protected portfolio work to prospective clients even if my NDA prohibits portfolio use?
This depends on how the NDA defines "disclosure." If it prohibits any sharing with third parties, showing work under password protection to a prospective client may still constitute a breach — you're disclosing it to a third party, just a controlled one. The safer approach is to negotiate an explicit carve-out for confidential portfolio sharing under a mutual NDA or written permission. Don't assume access controls substitute for contractual permission.
What if the client's NDA doesn't mention portfolio rights — am I free to use the work?
Not necessarily. If the NDA defines work product as confidential information and prohibits disclosure to third parties, that may implicitly cover portfolio use even without explicit language. Read the definition of confidential information and the permitted use restriction together before assuming you're free to use work not explicitly mentioned. When in doubt, ask the client directly and get their answer in writing.
Should I send my own NDA instead of signing the client's?
This is increasingly common among experienced designers and is entirely legitimate. Your own NDA template, drafted with your interests in mind, won't have the portfolio, attribution, or IP problems described above — because you wrote it with those protections included. Some clients will insist on using their own form, but sending yours first establishes your expectations and gives you negotiating leverage on the terms. It also signals professionalism.
Is unpublished design work protected by copyright without an NDA?
Yes — original creative work is automatically protected by copyright from the moment of creation under US law and most international equivalents. But copyright protection doesn't address the contractual restrictions that NDA clauses impose. Even if you own the copyright, a contract can restrict how you use the work. NDA review and copyright protection are separate issues that work together — not substitutes for each other.
What's the difference between an NDA and a design services contract for IP purposes?
An NDA governs confidentiality — what you can say about the engagement and to whom. A services contract or SOW governs ownership — who owns the work product created during the engagement. Many client packages bundle both: an NDA covering confidentiality and a services agreement with an IP assignment clause. Read both documents carefully, because IP assignment terms in the services contract interact with the confidentiality obligations in the NDA. A portfolio carve-out in the NDA means nothing if the services contract prohibits display of work the client now owns.
Before signing your next design NDA, get a clause-by-clause risk score in 60 seconds. Upload it to NDA Guard and know exactly which clauses to push back on.