Publish an HTML, CSS and JavaScript website for free

Folder checklist before you upload

How should you structure folders, links and routes?

When you move from your computer to a live server, every file path becomes case-sensitive. Your computer might let style.css load Style.CSS, but a live web server treats them as two different files. Keep all file names and folder names lowercase, and link them with relative paths instead of local file paths.

Multi-page sites work out of the box when you match your links to your file structure. A file saved as about.html opens at /about.html, while the shorter /about address works when you save the file as about/index.html. If you only have a single file with inline styles, see our guide on turning a single HTML file into a website or pasting raw HTML code.

If your JavaScript project is a single-page app that uses client-side routing, opening a route like /about works after a visitor starts on the homepage, but opening or refreshing /about directly returns a 404 error because ship.page has no single-page-app fallback. Switch your router to hash routes like /#/about so every link works on direct load, or use Netlify, Cloudflare Pages or Vercel if you need the server to rewrite every path to index.html.

• Supported static files: HTML, CSS, JavaScript, images, fonts, audio, video, WebAssembly and JSON.
• No server code: PHP, Node.js, Python, databases and WordPress do not run here.
• Contact forms: connect your HTML form tag to a third-party form service.
• Uncompressed files only: files are served with no Content-Encoding, so turn off .br or .gz pre-compression or include a JavaScript decompressor.

How do GitHub Pages and Netlify compare when you have an account?

If you only want a live link right now without creating an account, ship.page publishes your folder in seconds with no password gate in front of your visitors. When you want to compare other ways to publish, GitHub Pages and Netlify are the two main routes that require an account.

GitHub's web uploader (under Add file, then Upload files) lets you drag in up to 100 files at a time and 25 MiB per file in the browser with no Git installed. You then open Settings, click Pages, and pick a branch to publish your site at username.github.io/repository a few minutes later. Pick GitHub Pages when you already keep your code in a GitHub repository and want commits to update the live site.

Netlify Drop (at app.netlify.com/drop) accepts a folder, ZIP or single HTML file in the browser without signing in first, and its documentation notes that deploys under 50 MB work best while single files over 10 MB may get stuck. However, a site dropped without signing in stays behind a temporary password until you claim it with a Netlify account, and Netlify's blog states that an unclaimed drop expires on its own.

Tip: If your project is already packed as an archive, read our guide to hosting a ZIP file online, or start from scratch with how to make a web page.

When do you need a free account or the $4/month Pro plan?

You can publish to ship.page without an account, and the free plan has no bandwidth limits, no ads and a small "Hosted on ship.page" badge that visitors can close. Signing in with Google or an email link (no credit card) lets you claim your upload to manage it from a dashboard, though a free page cannot be updated in place and a new upload gets a new link.

Pro is $4 a month (billed monthly, cancel anytime, no yearly plan). On Pro, pages don't expire while you're on Pro (or you can pick any expiry from 60 seconds), you can re-upload or edit a page and keep the same link, and the badge is removed. Pro also adds password protection, raises limits to 100 MB ZIPs (400 MB unpacked), 10,000 files per upload and 120 deploys a minute, and includes up to 5 custom subdomains like yourname.ship.place that you can point at any of your pages.