Two ways to do this. The first keeps you right here — you connect your own Netlify account in a popup and your files go straight over. The second is a drag-and-drop on Netlify's own website, and you can try it without even signing up first.
Build your project here, go to the Ship step and choose "Deploy to Netlify from here". You authorise your own Netlify account in a popup, and the files go from your browser straight to Netlify — we have no server in between, and the authorisation token is used once, in that tab, and never stored. Netlify names the new site at random; you can rename it, or point a domain at it, from its settings. Deploying again updates that same site instead of creating a second one.
Download the ZIP from the Ship step and unzip it. Open app.netlify.com/drop and drag the unzipped folder onto the page — the folder itself, not the ZIP and not the files inside it. Netlify puts it online and hands you a .netlify.app address straight away. No account is needed to try it, though you will want one to keep the site.
app.netlify.com/dropWhen someone opens a link straight to an inner page — or just refreshes one — Netlify goes looking for a file there, doesn't find it, and shows a "not found" error. We fix this for you: at the Ship step, pick Netlify as your host before you download, and the fix goes in automatically.
/* /index.html 200The free .netlify.app address works and already has HTTPS, so this step is optional. When you do want your own domain, it lives under Domain management in the site settings — Netlify tells you which DNS records to add and issues the certificate itself.
Drop your ZIP into the builder. It runs the real build in your browser, and when something breaks it points at the line that matters instead of handing you the whole log.
Open the builder