Restore a Website from a Zip: The Complete Beginner's Guide

You ran a restore, the job finished, and now there is a zip file sitting in your downloads folder. This guide is about the next ten minutes: turning that zip back into a live website. There are four good ways to do it, and none of them require you to be a developer. I will walk through each one with the exact clicks, tell you which buttons live where, and finish with a comparison table so you can pick the right path for your situation.

What you get when you restore a website from a zip

Open the zip and you are looking at your whole website as plain files. Every page the archive crawler captured is there as an .html file, and every image, stylesheet, and script those pages used is downloaded into folders next to them. Internal links were rewritten to point at the local files, which is why the site works even before you upload it anywhere: find the homepage (usually index.html) and double-click it. Your restored site opens in your browser, straight off your hard drive, no internet needed.

A few files in the zip are extras we added rather than pages from your old site. README-how-to-restore.md is a short version of this guide. webarchive-cms.php is our free single-file CMS. Ignore it for now, section five explains what it does. If you ticked the file-list option when ordering, you will also see __files.txt, __files.json, and __files.sqlite: three formats of the same manifest listing every file in the zip. They are reference material for you, not something the site needs to run.

One thing is deliberately missing: a database. A restore brings back what visitors saw, not the server code behind it. That turns out to be good news for you: static files are the cheapest, fastest, most hack-proof way to host a website, and every path below works without you creating or configuring any database at all.

Restore a website from a zip into WordPress

Here is the honest part: a restored site is static HTML, and WordPress cannot swallow a zip of HTML in one go. WordPress keeps content in its own database, so moving a restored site "into WordPress" really means recreating the pages inside a fresh WordPress install. It is absolutely doable, just know it is the one path on this list that takes real time.

1. Install WordPress on your hosting. cPanel and Plesk both have one-click installers ("Softaculous", "WordPress Toolkit").
2. For a small site (under ~20 pages), do it by hand: create a WordPress page for each page you want to keep, paste the text from the corresponding .html file, and upload the images through the Media Library.
3. For a bigger site, use an import plugin such as "HTML Import 2", which reads a folder of html files and creates matching WordPress pages.
4. Set up the menu under Appearance → Menus, pick a theme, and create redirects for any old URLs that matter, because WordPress will not reproduce your original URL structure by itself.

Rule of thumb: choose WordPress only if you need WordPress going forward: a blog you will post to weekly, a store, memberships. For everything else, static hosting or the Restorix CMS gets the same site online in a tenth of the time, hosts for free or nearly free, and cannot be taken down by a plugin update.

Restore a website from a zip on Cloudflare Pages (free)

If you have no hosting and no budget, start here. Cloudflare Pages is a free static-site host, and your zip is already 100% compatible with it, so there is nothing to convert, check, or configure. The only real decision is the project name.

1. Extract the zip on your computer first. On Windows: right-click the zip, "Extract All". On a Mac: double-click it. You want a normal folder of files.
2. Go to dash.cloudflare.com and create a free account. In the left menu open "Workers & Pages", click "Create", switch to the "Pages" tab, and choose the direct upload option ("Upload assets").
3. Pick a project name; it becomes your free address, your-project.pages.dev.
4. Drag the extracted folder (the folder itself, not the zip) into the upload area and press Deploy. Cloudflare uploads every file and puts the site live in under a minute.
5. To use your own domain: open the project, go to "Custom domains", add your domain, and follow the prompt. SSL is automatic and free. If your domain's DNS is already on Cloudflare, one click finishes it.

Updating the site later means repeating step 4: drag the folder again and Cloudflare creates a new deployment, keeping the old one as a rollback. There is no server to maintain, no PHP version to worry about, and the free tier covers normal sites comfortably.

Restore a website from a zip on cPanel or Plesk

If you already pay for shared hosting, your site can live there, and this works on cPanel, Plesk, DirectAdmin, and nearly every other panel because they all share the same idea: a web root folder where your homepage file must sit. The steps below name the cPanel buttons; Plesk differs only in labels.

1. Log in to your hosting panel. The address is in your host's welcome email, typically yourdomain.com/cpanel or yourdomain.com:2083 for cPanel, yourdomain.com:8443 for Plesk.
2. Open "File Manager" and enter the web root: public_html on cPanel, httpdocs on Plesk.
3. Click "Upload" and send the whole zip up. Uploading one zip is far faster than uploading hundreds of small files.
4. Back in File Manager, select the uploaded zip and press "Extract". A second later your files appear.
5. Check for the classic mistake: if extraction created a subfolder and your files landed inside it, open that folder, select everything, and use "Move" to bring it all up into public_html directly. index.html must sit in the web root itself, one level up from where it probably is now.
6. If the domain is not pointing at this hosting yet, change its nameservers to the ones in your host's welcome email. Then visit the domain: your restored site is live.

Prefer FTP? That works too, just slower: extract the zip on your computer, connect with FileZilla, and drag the files into public_html. Whichever way you upload, keep the folder structure intact, since pages find their images and styles by relative paths, so flattening everything into one directory breaks the design.

Edit it too: restore a website from a zip with the Restorix CMS

A plain static upload has one annoyance: changing a phone number means editing HTML by hand and re-uploading. The Restorix CMS fixes that, and it is already inside your zip as the file webarchive-cms.php. It is free, open-source (GPL v3), and runs on any hosting with PHP, which means every cPanel and Plesk host on the market. Details and feature list live on the Restorix CMS page.

1. Upload and extract the zip exactly as in the cPanel steps above, making sure webarchive-cms.php ends up next to index.html in the web root.
2. Visit yourdomain.com/webarchive-cms.php in your browser.
3. The first launch asks you to create your admin password. Choose a strong one and store it somewhere safe, as this is the only setup step that exists.
4. The CMS imports your pages by itself and keeps its data in a built-in SQLite file. You never create a database, never touch phpMyAdmin, never edit a config file.
5. From the admin panel you can click into any page and edit text and images visually, run search & replace across the whole site (useful for old phone numbers and emails), manage files, and roll back to backups.

The CMS runs on PHP 5.6 through PHP 8.x, and safe mode is on by default so you cannot break the site while learning the panel.

Other ways to put the zip online

• Netlify or Vercel: same idea as Cloudflare Pages: Netlify Drop (app.netlify.com/drop) takes the extracted folder by drag & drop on a free plan.
• GitHub Pages: push the files to a repository and enable Pages. Free and reliable, but you need basic git.
• Your own VPS: copy the files to /var/www/yoursite and point nginx at the folder. Cheapest raw hosting there is, if you are comfortable in a terminal.
• Nowhere: the zip also works as a permanent offline archive. Keep it, and the site is never truly lost again.

Which path should you pick?

Still unsure? Do the Cloudflare Pages upload now (it costs nothing and takes five minutes) and move to your own hosting later if you outgrow it. A restored site that is online somewhere beats a perfect plan sitting in your downloads folder.