A useful starting point
The quick answer
- Extract the whole ZIP and open its index.html.
- Check that the assets folder stays beside the HTML files.
- Match a missing image or stylesheet with its manifest entry.
Match the symptom to a first check
| What you see | First check |
|---|---|
| Most styling is missing | The stylesheet path and the extracted assets folder |
| One image is missing | Its saved status and original address in the manifest |
| Text appears in another font | Font download notes and stylesheet references |
| Content appears after a click online | A possible live JavaScript dependency |
Start with a fresh extraction
Extract a fresh copy into a new folder and open index.html from that copy. Keep the domain folder’s HTML files, assets and supporting files in their original relationship. This is especially useful after individual files have been moved or renamed.
If that fresh copy looks correct, compare its folder structure with your working copy. Fix the moved file or reference in the working copy, and retain the original ZIP for another clean extraction.
Trace one missing file
Open manifest.json in a text editor and search for the image name, stylesheet path or source host. Check the saved status and related issue. A successful file entry points you toward a local-reference problem; a failed request points you toward retrieval or source availability.
In our quotes.toscrape.com sample, twelve font requests returned HTTP 404. That example illustrates why download notes matter even when the archive completes. It identifies specific missing resources; it says little by itself about whether the text you need is readable.
Check the original reference
While connected, compare the same page on the original site. A broken source URL may also fail there. For your own site, correct the source reference and create a fresh archive. For a temporary network error, retry a small sample after the source is available.
If the image is inserted by JavaScript, scrolling or a gallery action, use the JavaScript checklist. If the asset lives on another host, review the notes for that host’s access rules as well.
Confirm the repair
Open the corrected page locally and repeat the offline check. Inspect both the homepage and an inner page, because their references can differ. Record the exact file and change if you are handing the archive to someone else.