A useful starting point
The quick answer
- Archive a small sample of the public site.
- Extract the ZIP and open the domain folder in a text editor.
- Use manifest.json to match original addresses to saved files.
Understand the source you are saving
| File | What it tells you | Where it comes from |
|---|---|---|
| HTML | Document content, links and markup | The public response sent by the server |
| CSS | Layout, typography and visual rules | Referenced stylesheets and inline styles |
| JavaScript | Browser-side behavior | Public script files referenced by pages |
| Backend project | Templates, database logic and configuration | Your repository, host or platform export |
Save the public files
Use the download form with a modest page limit. Keep linked documents selected if your review also needs brochures or downloads. After extraction, open index.html in a browser to check appearance, then in a text editor to inspect the saved markup.
Zipasite updates references for local browsing. A saved HTML file therefore represents an offline adaptation of the public response. Keep the source address and download date with your notes when a review requires a clear record of where the material came from.
Trace a stylesheet or script
Inside the domain folder, find assets/ and manifest.json. Saved asset names include a hash to distinguish original URLs. Search the manifest for the source address, then open the matching local file. A .bin extension can appear where the original address supplied little filename information.
For a layout review, begin with a visible heading or navigation element in the HTML. Follow its class names into the saved CSS. For behavior, inspect the referenced scripts and identify calls to remote services. Minified files are production output; readable source files and build configuration belong in the original development project.
Prepare a rebuild or code review
Use your repository for authored components, tests and build scripts. Use a platform export or hosting backup for databases and configuration. An offline page helps compare wording and appearance during a rebuild, while the original project supplies the pieces needed to operate the application.
- Record the original URL and capture date.
- Keep the HTML and assets folder together during inspection.
- Check the manifest for failed files before drawing conclusions.
- Use your own code or licensed material when creating a new implementation.
Common questions
Does the download include PHP or database files?
Zipasite saves the public responses and linked files it reaches. PHP application code, database contents and private configuration stay on the original server.
Can I edit the downloaded HTML?
You can edit a working copy in a text editor and open it locally. Keep the original archive intact so you can compare your changes.