All guides

Is It Legal to Copy a Website's Design? A Practical Guide

October 27, 2026Pluck Team5 min read
  • guide
  • design

We make a tool that copies components out of live websites, so we get this question a lot. The short answer: using a website as a reference is normal, long-standing design practice, and the law mostly agrees with that. Shipping a near-identical copy of someone else's site under your own name is not, and the law agrees with that too. Most real cases sit between those two, and this post is about telling them apart.

One thing up front: this is general information from a product team, not legal advice. Rules differ by country, and if money or a brand is on the line, talk to a lawyer who knows your jurisdiction.

Ideas and layouts versus expression

Copyright, in most jurisdictions, protects expression, not ideas. A three-column pricing table with the middle plan highlighted is an idea. So is a hero with a headline on the left and a screenshot on the right, a sticky navbar with a logo and four links, or a dark footer with columns of links. Nobody owns these patterns. Thousands of sites use them, and you can too.

What copyright does protect is the specific creative work on the page:

  • Copy. Headlines, body text, product descriptions, microcopy with any originality to it.
  • Images and illustrations. Photos, icon sets drawn for the brand, custom illustrations, hero artwork.
  • Code, in the sense of the actual source files, which is usually not what you are after anyway.
  • Sometimes the overall look and feel when it is distinctive enough and copied wholesale, which varies a lot by country and is where cases get argued.

Separately, trademark law protects the things that identify a company: its name, logo, and sometimes a signature colour or shape when it has become strongly associated with the brand. The question there is confusion, not copying. If a visitor could think your site is theirs, or endorsed by them, you have a problem regardless of how the design was made.

A rule of thumb that holds up

Ask what a visitor would experience. If someone who knows the original lands on your page and thinks "this is a different product that clearly learned from the same ideas", you are in reference territory. If they think "this is the same site" or "these must be the same company", you have gone too far.

In practice this means:

  • Borrow the structure: section order, grid, spacing rhythm, where the call to action sits.
  • Borrow the techniques: a particular hover effect, a card treatment, how a table collapses on mobile.
  • Write your own copy, use your own images, and use your own brand marks and name.
  • Do not reuse their logo, their illustrations, or their product screenshots.
  • Be careful with a signature combination such as their exact typeface plus their exact colour plus their exact layout. Any one of those is fine. All three together on the same kind of page starts to look like impersonation.

What Pluck captures, and what that means

When you pluck a component, Pluck copies its structure and computed styles: layout, spacing, colours, typography, borders, shadows, breakpoints, plus a screenshot and the image references on the element. That is a very accurate reference. It is also, by design, everything, including the parts you should replace.

So treat a pluck the way you would treat a saved screenshot in a moodboard, except more useful. When you paste it into Cursor, Claude Code or Lovable, your one-line instruction is where you draw the line. "Recreate this pricing table using our plan names, prices and brand colours from theme.css" keeps the layout and swaps the expression. "Recreate this exactly" does not, and you should only say that for your own site.

The same applies on a board in Pluck Studio. Connecting a competitor's hero as a reference and asking for "a hero in this style for our product" is reference use. Connecting it and asking for "this exact hero with our logo" is a copy with the serial numbers filed off.

Common situations

Redesigning your own site

Plucking your current site, or your old one, is the cleanest case. You own the expression. Pluck everything, paste it anywhere, keep what you like. This is also the main reason the Pluck a Pricing Table and Rebuild It in Tailwind workflow is so useful: most teams are rebuilding something they already have.

A client sends you a link and says "make it like this"

Clients do this constantly. Treat the link as a brief about taste, not a spec. Pluck the sections to understand the structure and rhythm, then build with the client's content and brand. If the client insists on something that would read as a copy, say so in writing. It protects them as much as you.

Studying a component library or design system

Plucking a button or a modal from a public design system to see how it is built is study. Most of those systems are open source anyway. Shipping their components under their brand name without the licence's attribution is a licence question, not a design one, so read the licence.

Pages behind a login

Being able to see a page does not change who owns it. Plucking the dashboard of a SaaS tool you pay for, in order to study its information design, is reference use. Reproducing that dashboard as your competing product is not, and the terms of service you agreed to probably say so too. We cover the mechanics in Pluck Your Own App: Capturing Dashboards and Pages Behind a Login; the title says where the main use case is.

Templates and themes you bought

Licensed templates come with their own terms. Plucking from a theme demo to study it is fine. Rebuilding the whole theme from the demo to avoid paying for it is the kind of thing licences exist to prevent.

A checklist before you ship

  • Is every word on the page ours?
  • Is every image, icon and illustration ours or properly licensed?
  • Is our name and logo the only brand on the page?
  • Would a visitor who knows the reference think this is a different product?
  • If we used their typeface and colours, did we also change the layout enough that the combination is ours?
  • For anything behind a login, did we read the terms of service?

If every answer is yes, you are doing what designers have always done, just faster.

Why we think about this

Pluck exists because describing a design to an AI in prose loses the details, and a screenshot loses the structure. Giving your tools the real thing is better for everyone, including the people whose work you learned from, because the result ends up being yours rather than a blurry imitation. We built the extension for reference, study, redesign and iteration. Use it that way and the law is very much on your side.

If you want to put this into practice, install Pluck and start with your own site. Then read How to Build a Moodboard from Real Websites, Not Screenshots for a workflow built around references done right.

Use Pluck with your stack

Go pluck something nice.

Free to start. No credit card.

The Pluck duck