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.

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.