The core answer
A contractor may put client work in a portfolio only if it passes two gates. The first is rights in the work itself, which depends on who owns the copyright or what the contract grants. The second is everything else attached to the work: confidentiality terms, the client's trademarks and logos, images or data of people shown in it, and information the client has not yet released. Passing the first gate but failing the second still means you cannot show it.
The general rule in Thai copyright law for commissioned work is that the person who commissions it is usually the copyright owner, unless the creator and the commissioner agree otherwise. That rule does not settle every case. Some work is done by someone hired to work on the client's direction, some is a contract to produce a result, and some contracts transfer or license rights in their own words. The safest practice is not to guess from the general rule. Write the right to display the work into the contract at the start, or get written permission before each posting.
This guide is not about who owns a brand or about moving work into a company. We have separate guides on those (see section 1). This one answers a single question: may work done for a client be shown in your own portfolio or website, and what should be agreed up front.
Information as of 21 November 2026. Check the current text of the law and your own contract before relying on this.
Who this is for and which sections to read
| Your situation | Sections to read |
|---|---|
| Not yet signed with the client | Section 2 on what blocks showing, section 4 on clauses to write, and section 9 checklist |
| Signed and working, or already delivered | Section 5 on written permission, section 6 on how to show the work, and section 7 if others helped |
| The client has objected, or there is a dispute over work you showed | Section 8 on a takedown request, and section 1 to check who holds which rights under the contract |
1. Who holds rights in the work, by law and by contract (short version)
This is only as much as you need to decide about portfolios. The rest is in related guides.
- Work by an employee in the course of employment: the Copyright Act's general rule is that the creator owns it, but the employer may publish it for the purpose of the employment, unless agreed otherwise.
- Work done on commission: the general rule is that the commissioner holds the copyright, unless the creator and the commissioner agree otherwise.
- Agreement changes the result: a contract saying the contractor keeps the copyright, or the client owns it, or the contractor only licenses the client, outweighs the general rule.
- Transfers need evidence: a transfer of copyright should be in writing signed by both sides. If the contract is unclear, read its actual wording and the current law.
Related guides you can read separately:
- If the question is who owns the company's trademark or brand, read Who owns the brand when you set up a company.
- If you are a freelancer or agency moving work into a company and worried about transferring contracts and copyright, read Moving a freelance or agency business into a company.
- If the work is software the client commissioned, read the source code section of software development contracts.
2. I own the copyright, so why can't I show it?
Copyright ownership tells you who controls copying and publishing the work itself. Real projects carry other things with them, and each can be a separate reason to say no.
| What may block it | Where it comes from | Example |
|---|---|---|
| A confidentiality agreement (NDA) or non-disclosure term in the contract | Your contract with the client, whoever owns the copyright | An unlaunched campaign, a client's internal system, sales figures |
| The client's trademarks and logos | The mark owner's rights and the client's brand-use rules | Showing the logo to suggest "our client" may be read as claiming a relationship |
| Personal data and images of people | The Personal Data Protection Act (PDPA) and rights in a person's image | Photos of staff or the client's customers, screens showing names and phone numbers |
| Information the client has not published | Business confidentiality and contract terms | A new product line, pricing plans, unreleased features |
| Third-party rights | Licences for stock images, fonts, music or models used in the work | A font or image licensed only for that project |
The last two are often missed. A stock image or font licence may cover use for the client but not display in the contractor's own portfolio, so read the licence terms.
On personal data in brief: an image or data that identifies a person needs a lawful basis and a purpose that matches the use. Consent the client collected for one campaign does not necessarily cover the contractor showing the same image. Look at the original consent, and read guidance from the PDPC or our PDPA checklist.
3. How do the risks differ by type of work?
| Type of work | Common problem | Usually safer route |
|---|---|---|
| Design (logos, packaging, web and UI) | The logo and brand identity belong to the client, and unreleased work is confidential | Show only work the client has launched, or show drafts without the logo |
| Photos and video | Faces, the client's premises, and arrangements with models | Check consent from people shown, and use images the client has already published |
| Software and web apps | Source code, business logic, data on screens, third-party or open-source code with conditions | Show screenshots with real data removed, or write a case study without exposing code |
| Ad campaigns and content | Budgets, numeric results, rights of media or platforms | Disclose only the figures the client agrees, or use broad ranges |
The common rule: the more real client information the work shows, the clearer and more written the permission should be.
4. What rights should be agreed at the start (the portfolio clause)
Keep it short and answerable. Points to include:
- Work that may be shown: by type or by item, for example "deliverables handed over under this contract"
- Channels: website, portfolio, social media, pitch decks, or only private pitches to other clients
- Start date: for example only after the client has launched the work publicly
- Client name and logo: whether they may be used, in what form, or whether to describe the business generically
- What must not be shown: confidential information, internal figures, personal data, source code
- Client review: send the draft portfolio page, and say what happens if there is no reply within a set number of days (do not write that silence means approval if the client will not accept that)
- Removal: when the client can ask for takedown and how many days the contractor has
- Link to ownership of the work: if the client owns the copyright, write the display right as a clear exception or permission
- Others' material in the work: stock images, fonts, libraries, and whether their licences cover showing the work
If the client will not accept the clause, there are still options: agree item by item after delivery, or show only versions that do not identify the client. Decide before signing, not after delivery.
5. How do you ask the client for written permission?
Where the contract is silent or unclear on portfolios:
- Identify the work: project name, item, delivery date
- State what will be shown: screenshots, design images, case study text, and attach the actual page
- State channels and duration: website, social, pitch decks, and for how long
- State whether the name or logo will appear: if not, say what you will write instead
- State what will be left out: confidential information, figures, personal data
- Ask for a written reply: an email saying yes is enough if the sender has authority, such as the contract signatory or someone the client has named
- Keep the record: save the email and a screenshot of the live page in the project file
If the client replies only "OK", ask which channels and which items it covers, and keep the answer.
6. What is the difference between anonymising, a case study and showing the real deliverable?
| Approach | How | Remaining risk |
|---|---|---|
| Real work the client has already published | Link or image of work publicly launched by the client | Still check third-party rights and the contract. It is not automatically safe |
| Real work not yet published | Showing items the client has not released | High risk. Always get written permission |
| Anonymise or redact | Remove logos, names and identifying details | The client may still be guessed from the nature of the work or the figures. Let the client review |
| Case study | Describe the problem, approach and result in prose, without showing the actual deliverable | Numeric results may be confidential, and too much detail can reveal secrets |
Working rules:
- Remove identifying data from images, text, file names and hidden file metadata
- For photos showing faces without a consent that covers this use, blur the faces or choose another image
- For result figures, ask the client first. If they say no, use qualitative wording
- Anonymising is not a licence. If the contract bars disclosure even without a name, you can still breach it
7. What changes when a team or subcontractor worked on it?
- If employees or freelancers helped, check who holds rights in their part. Without a written agreement the lead contractor may not have full right to show that part. See also long-term freelancer vs employee
- Have contributors sign a document that grants the right to display the work (or assigns rights) to the lead contractor, and binds them to confidentiality
- If a team member wants to put the same project in a personal portfolio, agree at the start who may show what, or the client's objection will land on the whole team
- Use the same confidentiality terms as the client contract as the base, and see the point about business information leaving with departing staff in customer lists and trade secrets after resignation
8. What if the client asks you to take the work down, or there is a dispute?
- Take it down before arguing. If the client says no, remove the work from the website and social media, and from pitch decks still in circulation. Acting quickly limits harm and shows cooperation
- Ask for the reason in writing. Which clause does the client rely on? Read its actual wording
- Gather what you have: any permission you asked for, the contract, the confidentiality agreement
- Do not reply only by claiming copyright. The client's objection may rest on confidentiality or trademark, which do not depend on who owns the copyright
- If damages are claimed or a demand letter arrives, gather the documents in section 9 and consult a lawyer before replying
9. Documents and steps to prepare
- The contract or purchase order, including clauses on copyright, licensing and disclosure
- The confidentiality agreement (if any) and the scope of what may not be disclosed
- The portfolio clause, or per-item written permission
- Licences for stock images, fonts, music and libraries used in the work
- Consent from people appearing in images or video
- Agreements with employees and subcontractors who worked on it
- The draft portfolio page sent to the client and the approving email
- A dated screenshot of the live page, kept in the project file
- An internal list of works that must not be shown, with reasons
10. Hypothetical example: a design studio wants to post a restaurant client's website
This example is invented to illustrate and is not a real case. The facts are illustrative.
A small design studio built a website for a restaurant group. The contract says the client owns the delivered work and includes a confidentiality clause covering business information. It has no portfolio clause. The studio wants to post screenshots with the logo and food photos, and say bookings rose by a stated percentage.
What the studio should do:
- Read the contract to see who holds the copyright and what disclosure is barred. Where the client holds the copyright, the studio should not assume it may show the work itself.
- Break the material into parts. The logo belongs to the group. The food photos may have been taken by another photographer under a limited licence. Photos showing diners need a check on consent. The booking figures are the client's business information.
- Send a permission email as in section 5, with the draft page showing the site, diners' faces blurred, results described in broad terms instead of numbers, and a question about whether the logo may appear.
- Post only after the client agrees in writing, and keep the email and a screenshot of the live page.
- For the next job, put a portfolio clause in the contract from the start, as in section 4.
If the client does not reply, the studio should not treat silence as approval. It can write an anonymised case study or wait for an answer.
Common misunderstandings
- "I did the work, so I can show it." Not always. Doing the work does not give the right. If the contract gives the copyright to the client, or bars disclosure, you still need permission.
- "Owning the copyright means I can disclose anything." Copyright does not cancel a confidentiality agreement, the client's trademark rights or personal data protection.
- "Removing the client's name makes it safe." Not always. If the client can still be identified, or confidential details remain, it can still be a breach.
- "If the client does not reply, they do not mind." Silence is not clear consent. Get a written reply.
- "Once the client has published it, anyone can show it." The client publishing it does not pass its rights to the contractor, especially for parts owned by third parties.
- "A case study needs no permission." It is lower risk, but if it contains confidential or identifying detail you still need to ask.
Further reading
- Who owns the brand when you set up a company
- Moving a freelance or agency business into a company
- Software development contracts and source code
- Long-term freelancer vs employee
- Customer lists and trade secrets after an employee resigns
- PDPA checklist for businesses
Owning the copyright does not give you the right to show the work, so write the display right, the channels and what must not be shown into the contract at the start, and get written permission before posting whenever the contract is unclear.
We help draft and review clauses on copyright, confidentiality and display rights, prepare permission requests and permission letters, review a contract you have received, and advise when a client objects or asks for takedown. We are not marketing or design consultants, and we cannot promise the outcome of a negotiation with a client. Fees depend on the stage of the matter and the work required. Send us the documents first, and we will give you the scope of work and fees in writing before we start. Call +66 92 254 2045 or send us the details. See also contracts and documents, trademark registration and intellectual property.
This guide is published by Suwanvara Law Firm — a Khon Kaen law firm established in 1986. General information only, not legal advice on a specific matter.

