index.html is at the top of your ZIP, file names match in upper/lower case, and no path starts with C:\, file:// or/Users/.How to see what is actually wrong
Open your live link in Chrome, Edge or Firefox, right-click the page and choose Inspect, then open the Console tab. Red lines that say 404 or Failed to load resourcename the exact file the browser could not find. Keep that list next to you while you go through the fixes.
1. The ZIP has an extra folder inside it
Symptom: the link shows "not found" or an empty page, even though the upload succeeded.
If you compressed the folder itself, everything sits one level down (my-site/index.html) and there is no index.html at the top. Re-zip by opening the folder, selecting all the files inside, and compressing those. The ZIP Inspectorshows the structure before you upload.
2. Upper and lower case do not match
Symptom: some images or styles load and others do not.
Windows and macOS usually ignore case, so <img src="Hero.JPG"> findshero.jpg on your laptop. Web servers treat them as two different files. Rename the file or fix the reference so they match letter for letter. Using only lowercase names avoids this for good.
3. Paths point to your own computer
Symptom: images work for you (on the same laptop) but not for anyone else.
Search your HTML and CSS for file://, C:\ or /Users/. Some editors insert these when you drag an image in. Replace them with paths relative to the HTML file, such as images/photo.jpg.
4. Paths start with a slash
Symptom: the home page works, but sub-pages lose their styling (or the other way round).
/css/style.css means "from the root of the domain", while css/style.css means "next to this page". Both work on Droply when your site is at the root of its link, but mixing them between pages in sub-folders often goes wrong. Pick relative paths and use ../ to go up a folder.
5. You uploaded the source, not the build
Symptom: a blank white page, and the console mentions main.jsx,.tsx or "unexpected token".
Browsers cannot run JSX, TypeScript or Vue single-file components directly. Run your build command (often npm run build) and upload the folder it produces, usually dist,build or out. With Vite, also set base: "./" invite.config so asset paths are relative.
6. The page needs a server
Symptom: forms do nothing, or you see raw <?php code.
Static hosting serves files exactly as they are. PHP, server-side forms and databases do not run. For forms, use a form service that gives you an HTML snippet (Formspree, Tally, Google Forms embeds), or use Droply's built-in email capture on the Plus plan if you just need visitors' email addresses.
7. You are looking at an old version
Symptom: you updated the files, but the old page still shows.
Your browser may be holding on to the previous copy. Do a hard refresh (Ctrl+Shift+R, or Cmd+Shift+R on Mac) or open the link in a private window. Also check that you used Update on the existing project rather than creating a new one with a different name.
Still stuck?
Our helpdesk covers the most common upload problems. If none of it fits, email us the link and what you expected to see. A screenshot of the console helps a lot.