Is it legal to copy a section of a website into your page builder?

The whole answer in three lines

• Structure is generally free. Column counts, spacing, section order, a three-plan pricing table. Nobody owns those.
• Everything inside it usually is not. Text, photos, icons, logos, brand colours. Assume it all belongs to somebody.
• So: keep the shape, replace the contents. That single habit avoids almost every problem in this post.

Not legal advice. We build a conversion tool, not a law firm, and copyright works differently in the US, the EU, the UK and everywhere else. If real money or a real client is riding on it, ask a lawyer where you are.

The rest explains why the line sits there, and the five cases where it gets more complicated.

First, are you breaking into anything?

No. When you open a public page, the server sends your browser the HTML, the CSS and the images, and your browser draws them. Reading what your own browser already received is what View Source and the DevTools inspector have done for twenty years. wpgraft measures the page that is already on your screen.

Two things that does not settle:

• Whether you may publish it. Different question, and the one that matters.
• What the site's own terms say. Some sites forbid extracting their content in their terms of use, and agreeing to those terms is a separate promise from copyright. Worth a look if the site is a competitor or a commercial product.

A page is five things, not one

Each is treated differently. This is the part worth remembering.

1. Text, images, video

Assume every word and every photograph is protected and that you have no right to republish it. Marketing copy, product photography, illustrations, icon sets, stock images the site licensed for its own use: none of it becomes yours because it arrived in a paste.

Replace all of it. Always. This one rule keeps most people out of trouble.

One practical detail: when a copy contains images, your own WordPress site downloads them from the source server into your media library. They physically end up on your host, and fetching them puts load on somebody else's. Another reason to swap them out early.

2. Logos, brand names, distinctive look

This is trademark, and it is stricter than copyright. The problem is using someone's mark in a way that suggests you are connected to them or confuses a customer, and you can cause it without copying a single line of code.

3. Layout, structure, spacing

This is the part you are actually after, and it has the most room.

"A hero with the headline left and the product shot right." "Three pricing plans with the middle one raised." "Cards with a 16px radius and a 24px gap." These are conventions. They are everywhere because they work, and no one owns the general idea of a pricing table.

The room is not unlimited. Copy one site's arrangement so completely and so distinctively that yours is recognisably a knock-off, and you have a different problem. In the EU and the UK there is also an unregistered design right that can protect the look of something for a few years after it appears, so a layout launched last month is not the same risk as one that has been around for five.

Rule of thumb: avoid a layout so particular that people would name the original on sight.

4. Fonts

Easy to miss, and it catches people who meant no harm. A licensed webfont is licensed to the site that bought it. Copying the files across does not bring the licence with them. Swap in your own type, which you were going to do anyway, because keeping their font means keeping their brand.

5. Other people's personal data

Some pages carry information about real people: names and photos in testimonials, staff details, contact details, and occasionally much more sensitive things. Copying a page that displays somebody's health information, financial account details, government ID numbers or private messages is not a copyright question at all. It is a data protection one, and it has regulators attached rather than lawyers.

Do not copy those pages. Our Terms prohibit it outright.

What about the HTML and CSS themselves?

Code can carry copyright. In practice the risk is lower than people expect, for two reasons.

Most page markup is functional, largely dictated by the job it does, and functional expression is thin ground for a claim. And a converted page is not a copy of the source markup anyway: wpgraft reads the computed result and writes new elements in your builder's own vocabulary. A Bricks section that came from an Elementor page shares no markup with it.

Where to stop and check: a site built on a licensed premium theme or template. That is the next section, because it is the question we get more than any other.

The one that trips people up: premium templates

A premium template does not stop being licensed because its demo page is public.

The demo exists so you can evaluate the product. The product is still sold under a licence, and almost every such licence forbids reproducing the design without buying it. Rebuilding that demo instead of paying for it is exactly what the licence exists to prevent, whatever tool does the copying.

Three things people say, none of which help:

• "It's a different builder now." The licence attaches to the design, not the file format.
• "I changed the colours." Still the same design.
• "The HTML was public anyway." Public is not free.

If you would have had to buy it to use it, you still have to buy it.

Where you have bought the licence, wpgraft is an ordinary way to move that design into the builder you prefer, subject to what the licence says about client work, multiple sites and derivative use. Read it, and keep the receipt.

Pages behind a login

Everything above assumed a public page. If a page is behind a login, a paywall or a members area you are not authorised for, do not copy it. That includes course material you bought, a client area belonging to someone else, and anything you reached by working around a restriction.

Nothing in the browser stops you, which is exactly why the rule has to be a rule. Our Terms forbid it.

The checklist

On any page you copy:

• Your own words in every heading, paragraph and button.
• Every image, icon and logo replaced with yours or something you licensed.
• Your own colours and your own fonts.
• Not a direct competitor copied so closely a customer could confuse you.
• Not a premium theme or marketplace template you did not buy.
• Not behind a login, and not displaying other people's personal data.

Six ticks and you are doing what designers have always done: studying a structure that works and building your own thing on it.

Where it is plainly fine

Three cases come up constantly and none are close calls.

Your own sites. Moving a section between two properties you own, off a platform you are leaving, or out of a builder nobody maintains any more. Most of the work this tool does is this.

Client sites you are engaged to work on. With the client's authority, on their own material.

Reusing your own work. Build a section once, use it across your projects. Nothing to worry about, because it was yours from the start.

Where it is plainly not

Republishing somebody's article, gallery or product catalogue. Rebuilding a competitor's site under your own name. Passing another company's branding off as yours. Redistributing a premium theme's templates as your own work.

None of these become acceptable because the copying was fast.

What we will not pretend about

We cannot tell you what is legal in your country, and we do not review what anyone converts: pages are transformed in memory and never stored, so we could not review them if we wanted to. What you paste, and what you publish, is your call and your responsibility.

What we will say is that this tool exists for the boring, obviously legitimate case: moving structure you have every right to move, faster than rebuilding it by hand.

More detail: Acceptable use has the full list of what you may and may not copy. Responsible use covers what the product does on our side. If work you own has been copied, the Copyright complaints page is the fastest route to us.