What It Is
A swarm of AI agents that rebuild a site for you
Normally, copying a website means a developer rebuilding it by hand: every font, every color, every section, and that takes weeks. The AI Website Cloner throws all of that out. It is a free template you open in your AI coding agent, and it ships with one command: /clone-website.
You give it a link. It screenshots the page, pulls every color, font, and image, writes a detailed spec for every section, and rebuilds the whole thing as real code. And it does not build it one piece at a time. It spins up a swarm of AI agents, each rebuilding a different section at the same time in its own isolated branch, then checks the finished result against the original to make sure it matches.
What you get out the other end is not a screenshot. It is a clean Next.js codebase (Next.js 16, shadcn/ui, Tailwind v4) you can edit, rebrand, and deploy to Vercel. Over 24,000 GitHub stars and climbing. Recommended agent: Claude Code, but it works with Codex, Cursor, Windsurf, Gemini CLI, Copilot, and a dozen others.
Step 1
Before you start (3 things)
Node.js 24 or newer
From nodejs.org. The project is built on Next.js 16, which needs a current Node. Check yours with node -v.
An AI coding agent
Claude Code is the recommended one (best results, especially on Opus). Codex, Cursor, Windsurf, Copilot, Gemini CLI, Cline, and more are supported too.
Browser automation (this is the one people miss)
The tool has to actually open the target site to inspect it. With Claude Code, launch it with claude --chrome. On other agents, connect a browser MCP (Chrome, Playwright, or Puppeteer). Without this, the clone cannot run at all.
Step 2
Set it up (about 3 minutes)
Make your own copy with "Use this template"
On the repo's GitHub page, click the green Use this template button, then Create a new repository. Name it, pick public or private, create it. Do not clone the template repo directly. This gives you your own project so your work stays in your account.
Open your new repo and install
Clone your new repository to your computer and install the dependencies.
Start your agent with a browser attached
Launch Claude Code with Chrome so it can inspect the live site.
Run the one command
Point it at a URL and let the swarm go to work.
Once you've made your own copy and cloned it, this is the whole install:
Terminal
git clone https://github.com/YOUR-USERNAME/YOUR-NEW-REPO.git cd YOUR-NEW-REPO npm install claude --chrome
Then, inside Claude Code, run the command with the site you want:
The one command
/clone-website https://the-site-you-want.com
That's it. It inspects the page, downloads the assets, writes specs, dispatches the builder swarm, assembles the page, and runs a visual QA pass against the original. On a different agent? Open AGENTS.md in the repo. Most agents pick it up automatically.
Read This First
Important things to know
Don't steal a whole site. Steal the vibe.
Flat-out copying someone's live site is their work and a bad look. Where this actually shines is a section, or just the feel, of a site you love that you want as inspiration for your own. Clone it, then make it yours.
"Use this template," never clone the template repo
This trips up almost everyone. Use the green button to make your own copy first. Cloning the template directly means your generated site fights with the original repo.
No browser, no clone
It literally opens and inspects the page to pull real CSS values instead of guessing. If you skipped --chrome or a browser MCP, it will stop and ask. That's your reminder.
It clones one page, not a whole site map
It rebuilds exactly what's visible at the URL you give it. Want the homepage and the pricing page? Pass both URLs, and it handles them in parallel.
The default is pixel-perfect emulation
Out of the box it matches colors, spacing, fonts, and animations exactly, with no changes. Customizing is a second step: match first, rebrand after. Or tell it what to change up front (see the prompts below).
Let the swarm finish
The agents build in separate branches at the same time, then everything gets merged and QA'd against the original. It's built to keep the app compiling at every step, so don't panic mid-run. Let it reach the visual diff.
The Sauce
The best prompts to start with (copy-paste)
The command takes plain-English instructions after the URL, and the tool honors your instructions over its defaults. That's the whole trick. Here are the ones worth stealing. Swap the brackets for your own site and content.
1. The straight clone (start here)
Your first run. Point it at one URL and watch the whole pipeline work end to end.
Prompt
/clone-website https://the-site-you-love.com
2. Clone just the section you love
The ethical, practical move. Grab the one part you actually want instead of the whole page. Faster, cheaper, cleaner.
Prompt
/clone-website https://the-site-you-love.com. I only want the hero section and the pricing table, as inspiration for my own project. Rebuild just those two, not the whole page.
3. Match the design, use my brand
Keep the layout, spacing, and animations of a site you love, but swap in your product, colors, and copy. This is how you make it yours in one shot.
Prompt
/clone-website https://the-site-you-love.com. Match the layout, spacing, typography, and animations exactly, but rebrand it for my product: primary color #6C5CE7, my product name is [Name], and replace the headline copy with "[your headline]".
4. Clone two pages at once
Pass multiple URLs and it processes them in parallel, keeping each site's assets in its own folder.
Prompt
/clone-website https://the-site.com https://the-site.com/pricing
5. Rough it in fast (skip mobile for now)
When you just want the layout blocked out quickly. Tell it to skip the responsive passes and you'll get there faster.
Prompt
/clone-website https://the-site.com. Desktop only for now, skip the mobile responsive pass. I just want the layout roughed in so I can see it fast.
6. After the build: fix what doesn't match
Run this once the clone finishes. It re-checks your version against the original and repairs the drift.
Prompt
Take screenshots of my clone and the original side by side at 1440px and 390px, compare them section by section, and fix anything that doesn't match. Focus on spacing, fonts, and hover animations.
7. Make it yours, then ship it
Once the design matches, gut the placeholder content and wire in your real stuff, then deploy.
Prompt
The design matches now. Keep the layout identical, but replace all placeholder content with my real content: [paste your headline, features, and CTA]. Then run the build and tell me how to deploy it to Vercel.
Pro Tips
The stuff that makes it sing
Use Claude Code on Opus for the best clone
The template is tuned for Claude Code, and the harder the site, the more the top model matters. Other agents work, but this is the recommended path.
Smaller sites clone cleaner
A tight landing page comes out near-perfect. A giant, animation-heavy marketing site is more work and more tokens. Start with something simple to feel how it works.
It catches interactions, not just looks
Scroll effects, hover states, sticky navs, tab switches, smooth scrolling. It inspects behavior on purpose, which is why the clone feels alive instead of looking like a dead screenshot.
The specs are auditable
Every section gets a written spec file before it's built. If something looks off, you (or the agent) can open the spec and see exactly what it extracted, then fix it there.
You own real code at the end
This isn't a locked builder. It's a clean Next.js repo. Edit it, extend it, connect a backend, and deploy it to Vercel like any other project.