Remake clones a website pixel by pixel and lists what to replace

Keeping the design of a site you like usually means rebuilding it from screenshots. The copy drifts in ways nobody can measure. Ruben Hassid writes a newsletter called How to AI. He has released an open-source tool called Remake. Remake copies the original's own HTML, CSS and scripts. It replays them against a frozen clock. It then scores the copy pixel by pixel on every screen.

Remake is on GitHub as rubenhassid1/remake, under the MIT licence. The repository had 148 stars at the time of this item. It runs as a Claude Code plugin or a command-line tool.

How the copy is made

The engine visits the page once at desktop size and once at phone size. It keeps every file the page loaded. From then on it replays everything from that recording. Addresses are rewritten so every file loads from the user's own copy. Trackers are stripped out. A small runtime answers the original API calls from the recorded data.

Hassid says this is where other cloners stop and Remake does not. A live page never looks the same twice. A video autoplays from a different frame. A hero animates in. A random headline rotates on every load. Remake stops the page's clock before the first script runs. It feeds every call for a random number the same seed. It holds every video on its first frame. It steps time forward itself in exact amounts. Load the same page twice this way and the pixels match.

What passes and what does not

The gate for a passing copy is 98 percent of stable pixels per screen. Each motion frame has to reach 95 percent. Page heights have to be within four pixels of the original. The engine scores up to 40 screens per page across desktop and phone. It also scores 24 frames of a scroll. Anything that changes between two loads of the original is left out of the score. A clock or a live map is marked in blue on the proof page.

Each project goes to a private GitHub repo. A Vercel deployment follows, behind a passcode, hidden from search engines. The engine then checks from the outside that the passcode gate holds. Only then does it say the remake is complete.

What it will not do

The engine refuses to copy sign-in, checkout or banking pages. It stops when it sees password or card fields. A copy of those pages is a phishing kit. There is no proxy, no stealth browser and no CAPTCHA solver. When a host blocks the visit, Remake stops asking it. A swap board inside each project lists every piece that still belongs to the original. The groups are copy, photos, videos, logos, fonts, colours, links and forms.

For a team moving a site off an old platform, the useful part is not the clone itself. It is that every piece of the result can be scored. There is a number for how close the copy is. There is a list of what the team has not yet made their own.

Source

• rubenhassid1/remake, the GitHub repository and README
• How to AI, Ruben Hassid's newsletter