Fix missing CSS, images or fonts

Check what is missingCopy Anchor Link

If the page has text but no styling, start with the stylesheet URL. If one image is missing, inspect its src. Publishing the same unchanged ZIP repeatedly will not fix a path that does not exist.

Find the failed requestCopy Anchor Link

Open the published page, open your browser’s developer tools and select Network. Reload the page and find the failed image, stylesheet or font request. Open its URL directly. A 404 means the requested resource was not found; a blocked request, a login page or a script error needs a different diagnosis.

Compare the requested URL with the paths actually inside your package. Check the public page separately from the isolated editor preview. If a resource returns an HTML page instead of the expected image or stylesheet, check the path and routing rather than assuming a successful HTTP response means the resource is correct.

Match the package exactlyCopy Anchor Link

<link rel="stylesheet" href="./assets/style.css">
<img src="./assets/photo.webp" alt="Your project photograph">
<script src="./assets/app.js" defer></script>

Make sure each referenced file exists in the uploaded package. File names are case-sensitive. Photo.webp and photo.webp are different. Include fonts and image files referenced from CSS, too.

Understand relative pathsCopy Anchor Link

./ starts at the current document's directory; ../ goes one directory up. A leading / starts at the website root. Test a nested HTML page directly, not only by navigating from the homepage.

Replace local file paths and temporary object URLs with files in the package or intentional public HTTPS URLs. A blob: URL from another session is not a durable hosted image.

Check external resourcesCopy Anchor Link

Open preview diagnostics and look for a failed resource or blocked request. External servers can require authentication, disallow cross-origin use or become unavailable. The preview cannot reveal every detail of a cross-origin error.

Try the external-library workflow. After correcting the files, publish an update and reopen the same URL outside your workspace. See ZIP packaging for a complete folder example.

Try a small reproducible exampleCopy Anchor Link

These are original browser-only review-page examples. They use sample content and do not save responses:

• Working website ZIP: the HTML requests assets/preview.svg, which is included.
• Intentionally broken image-path ZIP: the HTML requests assets/Preview.svg, but the included file is named preview.svg.

In the broken package, change Preview.svg to preview.svg in index.html, then publish the corrected files to the same project. Reopen the image URL and confirm that it returns the image. Re-uploading the original unchanged package does not repair it or extend a Free site’s lifetime.

Both packages contain an index.html, CSS, JavaScript and the same original SVG illustration. The broken sample demonstrates a missing resource; it is not a model of every possible hosting failure. Keep these as test content rather than overwriting a project you need.

For the complete packaging workflow, read how to host a ZIP website.

For HTML image paths, external stylesheets and response-type diagnosis, read images missing after publishing HTML.