A useful starting point
The quick answer
- Choose a text page and a representative interactive page.
- Create a small archive and inspect the saved result.
- Use an owner export for application data and a backup for restoring the service.
Separate the three layers
| Layer | Example | Offline question |
|---|---|---|
| Initial HTML | An article heading and body | Is the text present in the saved page? |
| Client-side behavior | Tabs, menus and galleries | Do the required scripts and assets work locally? |
| Live data or actions | Search results, checkout and account details | What service supplies the data or action? |
Run a representative test
Choose a page containing the main reading material and another that uses the interaction you care about. Archive a small sample, extract it and open both pages locally. Compare visible text, images and navigation with the source while you still have access.
Then temporarily disconnect your device and repeat the same journey. A page that works only while connected has a remaining live dependency. Record that dependency so the archive’s reader knows which tasks belong on the original site.
How Zipasite collects content
Zipasite reads public HTML and referenced files, follows discovered pages and updates saved references. Downloading a script preserves a file; executing an application may require additional data, a compatible browser origin or a live service.
The crawler can inspect certain references in source files, but content created through user actions or remote application calls may stay with the live site. A small sample is the useful compatibility check for a specific website.
Choose an owner-controlled route
If you own the application, a static export or a dedicated offline build can package the intended routes and data more deliberately. Review the framework and platform documentation for that project. Keep private information within the approved export process.
For documentation, look for an official downloadable HTML collection, PDF or versioned source release. For a full service restore, keep the repository, database and deployment configuration. Each output solves a different part of the preservation task.
Describe what the copy supports
- List the pages and interactions you tested.
- Record the device and browser used.
- Identify content that still loads from the live web.
- Keep the download notes with the archive.
- Repeat the check after an important source-site change.