EZ Website Backup
Back up a site
🤖
EZ Website Backup / Blog
Advanced

How to Rip a JavaScript / React Site That Normal Rippers Miss

Modern sites build their pages in the browser, so classic crawlers save blank shells. Turn on JavaScript rendering and capture what a real browser sees.

Advanced · July 3, 2026 · 6 min read

One rule before you start: only back up sites you own or are explicitly authorized to archive — your own server, a client site you manage, or content you have written permission to copy. Downloading a site you don't control can violate copyright, terms of service, or computer-misuse law. EZ Website Backup asks you to confirm this before every new domain, and ties each job to your account.

Here's a nasty surprise people hit with older website rippers: they download a React or Vue site and every page is nearly empty. That's because the raw HTML those sites serve is a near-blank shell — the real content is assembled by JavaScript after the page loads. If your crawler doesn't run that JavaScript, it saves the shell.

The fix: render the page first

EZ Website Backup has a Render JavaScript toggle in Advanced options. Turn it on and each page is loaded in a real headless browser, given a moment to build itself, and only then captured — so the saved HTML contains the actual text, images and links a visitor would see.

Step by step

  1. Open the app and paste the URL of the JavaScript-heavy site you own.
  2. Open Advanced options and switch on Render JavaScript (for React/Vue & other SPAs).
  3. Because rendering is slower, keep Max pages sensible on the first run and raise a Politeness delay if the site is delicate.
  4. Run the crawl. Pages now come back fully populated, and the crawler can follow the links that JavaScript generated.
How to tell if you need it: do a quick normal crawl first. If the saved pages look empty or are missing their main content, re-run with Render JavaScript on.

The trade-off, stated plainly

Rendering runs a full browser for every page, so it's noticeably slower and heavier than a plain fetch. Leave it off for classic server-rendered sites (most WordPress, static, and plain HTML sites) — you won't need it. Turn it on specifically for single-page apps and dashboards where the content only appears after scripts run.

What still won't come across

Rendering captures the built DOM, not live interactivity. Infinite-scroll feeds, data behind a login you haven't supplied cookies for, and content that only loads on a click may still be partial. For member areas, combine rendering with the authenticated-crawl cookie field.

Back up your site in the next minute

Point EZ Website Backup at a URL you own, watch the file tree fill in, and download exactly what you need.

Open the app →

Create a free account

Keep reading