Build an offline copy of your website
A website can appear permanent in a browser while its underlying parts quietly change. Images move to a new content delivery network, a publishing plugin replaces templates, and old pages begin returning errors. A local snapshot freezes the version you can see now, providing a dependable reference when a server fails, a redesign removes content, or the internet becomes unavailable.
An offline copy is more than a saved home page. It may contain HTML, stylesheets, scripts, images, fonts, documents, and internal links arranged so they still work without a server. A lighter preservation copy might hold only articles and images, while a complete mirror can capture a whole site. The right scope depends on why you need the material and how long you expect to keep it.
Connection quality makes this practical rather than theoretical. A fixed-line NBN connection in Sydney or Melbourne may handle a large download comfortably, while an operator in regional or remote Australia may rely on a 4G or 5G hotspot with uneven coverage. A controlled crawl, resumable downloads, and an off-site second copy reduce the risk of losing everything to a dropped connection.
This guide covers preparing a site, running a local crawl, comparing preservation methods, checking downloaded files, and storing the result safely. Treat the copy as an archive rather than a disposable backup, and record what it contains so another person can restore it years later.
Define the scope of your copy
Begin with a written purpose. Decide whether the copy is for emergency recovery, legal evidence, research, education, or long-term access. A recovery copy should include the current site and its essential assets. An archive may also need earlier versions, original media, metadata, and a record of missing or redirected pages.
Choose between a focused collection and a full-site mirror. A focused collection might cover one section, such as a project archive or newsroom. A mirror follows approved internal links and attempts to retrieve supporting files. It can consume considerable space, especially when video, high-resolution photography, downloadable reports, and old attachments are included.
Community material can be just as significant as corporate pages. A collection might contain a community archive profile alongside interviews, photographs, or local history, with each item linked to the pages that give it context. Capturing those relationships is often more useful than storing isolated files without navigation.
Check permission and prepare the source
Only archive material you own or have permission to copy. Review the site’s terms, access rules, and robots directives, and avoid disabling those controls without explicit authorisation. Third-party text, photographs, fonts, and software may remain protected even when the surrounding website belongs to you.
Australian privacy obligations can still apply to stored information. The Privacy Act 1988 and Australian Privacy Principles may govern personal information held by covered organisations. Keep unnecessary contact details, customer records, and administrative data out of a public-facing archive, and encrypt sensitive backups with controlled access.
Inventory the website before downloading it. Identify its content management system, main domains, asset hosts, downloadable files, forms, search functions, and pages that require authentication. Make a separate export of the database if you operate a WordPress, Drupal, or similar system; a collection of HTML files will not preserve unpublished posts or configuration settings.
Run a controlled local crawl
A command-line crawler can create a static mirror on Linux, macOS, or Windows through WSL. Replace the placeholders below with your approved domain and starting address:
wget --mirror --convert-links --adjust-extension --page-requisites \
--no-parent --domains your-domain.example "$SITE_URL"
The --mirror option recurses through pages, while --page-requisites retrieves commonly needed assets. --convert-links rewrites downloaded links for local use, and --restrict-file-names avoids problematic characters on Windows. Add only approved asset hosts to the domain list, and begin with a small test section if the site is large.
Some content cannot be captured by ordinary link crawling. Pages generated entirely by JavaScript may appear empty, while contact forms, comments, searches, logins, shopping baskets, and dashboards depend on live server code. Use a browser-based crawler for important rendered pages, export content through the CMS, and record these functions as limitations rather than assuming the static copy is complete.
A news area provides a useful test because it combines dated entries, navigation, images, and many cross-links. The archived news pages can help you assess how a crawler handles deep paths and older material. Look for duplicated files, broken redirects, inconsistent templates, and pages that appear only in the live site’s search results.
Compare the main preservation methods
Different tools suit different needs. Choose based on the site’s technology, the required level of context, and the amount of technical work you can maintain.
| Method | Best suited to | Main strength | Common limitation |
|---|---|---|---|
| Wget mirror | Static sites and technical users | Repeatable, scriptable, inexpensive | Dynamic features and forms remain unavailable |
| HTTrack | Visual crawling on a desktop | Friendly interface and useful filters | Bundled assets can be incomplete or inefficient |
| CMS export | WordPress, Drupal, and similar systems | Captures posts, media, taxonomy, and metadata | Does not preserve the exact public-facing design |
| Browser save | A single important page | Quick and simple | Usually misses scripts, styles, and linked media |
| WARC or replay archive | Long-term institutional preservation | Retains source data, metadata, and replay information | Requires specialist tools and more storage |
For Australian buyers, compare local support and Australian-dollar billing with lower-cost international object storage. Check data residency, retrieval fees, and what happens to the archive if the provider changes its service. A downloadable folder is convenient, but a professional format offers stronger evidence of when and how the content was captured.
For most owners, a static mirror is the best starting point. Add a CMS export when unpublished content matters, a WARC-style archive when provenance is important, and a document archive when reports or media need preservation in their original formats. Store several related outputs together so readers can use the convenient local copy without losing the more detailed preservation record.
Check the copy and record its contents
After the crawl, open several downloaded pages with the network disconnected. This reveals missing images and scripts that appear normal while a browser quietly retrieves them from the internet.
Files to confirm:
- Open the home page, a deep article, an archive page, and a downloadable document.
- Check that stylesheets, images, fonts, and media appear correctly.
- Follow internal links and confirm that they point to downloaded files.
- Compare the offline collection with the site’s main navigation and section list.
Create a manifest for the archive. It should identify each source address, its saved location, the download time, and any errors encountered.
Details to record:
- Record the crawl date, time zone, tool version, and list of approved domains.
- Note redirects, missing pages, blocked resources, and pages requiring authentication.
- Store file counts, folder sizes, and SHA-256 checksums for critical files.
Keep the manifest in plain text or CSV so it remains readable if specialist software becomes unavailable. Store credentials separately, and never place them inside the same archive containing the website. A clear inventory turns a folder of files into a managed collection that another person can understand and restore.
Store and test the archive safely
Follow a simple storage rule: keep one working copy, one copy on separate local media, and one encrypted copy away from the building. An external drive, NAS, cloud object store, or trusted institutional repository can provide the off-site copy. Test that the chosen service makes it easy to retrieve the entire archive, not merely individual files.
Environmental risks make redundancy especially important in Australia. Fire seasons, flooding, and severe storms can affect equipment kept at home or in a nearby office, while heat and humidity can damage poorly stored drives. A second copy in a different physical location protects against the same incident. Label media with the site name and a date such as 23/09/2026, following the familiar day-month-year format.
Generate checksums for critical files and test a sample extraction in a new folder. Confirm that a machine without your usual browser extensions can open the pages, and that the collection can be understood without access to the original CMS. The case for maintaining this evidence over time is set out in why website archives matter: a saved file gains value when its source, date, and context remain attached.
Keep the offline collection current
An offline copy becomes stale as soon as the live site changes. Schedule a refresh after every major redesign and at least annually for a stable site. Compare page counts, URLs, file sizes, and checksums, then preserve the replaced version rather than overwriting it. Versioned copies show how a site’s content and design evolved.
Treat the domain as another part of the preserved system. Record the registrar, renewal date, nameservers, hosting account, publishing administrator, and recovery methods. For an Australian business, include local support contacts and account recovery details, while storing administrator information in a password manager with multi-factor authentication. For a public resource hub such as Papajohn Phillips, a concise stewardship note can also explain which historical sections are preserved and how visitors can enquire about the domain.
When someone says, “no worries, it’s only a backup,” give the collection a proper squiz and check that it can actually restore the site. Choose one site you own, create a dated mirror today, open it with the network disabled, and store it with its manifest and a short recovery guide. Start with that first verified snapshot, then repeat the process when the site changes.