Host a static websitefrom a ZIP
Zip up your site's files — or your framework's built output — drop the ZIP here, and get a live, multi-page website at a clean URL. Relative links and assets just work.
Drop a document — or any file
Multiple files become one album link automatically
or
up to 100 MB on the free plan
Free: 20 links, up to 100 MB, never expire · Pro: unlimited, permanent links
Publish a static site in four steps
- 1
Zip your site's files
Select the folder that contains your index.html and everything it references — CSS, JavaScript, images, fonts — and compress it to a .zip. If you use a framework, zip the built output (the dist/, build/, or out/ folder), not your source. We detect that folder automatically, so a ZIP of the whole project usually works too.
- 2
Upload the ZIP
Drag the .zip onto the card. We unpack it safely on our side, find your index.html at the root or inside a common build folder, and lay every file out under one site — so href="about.html" and src="assets/app.css" resolve exactly like they did locally.
- 3
Open the live site
Your site goes live at a clean, shareable URL. Every page, every relative link, and every asset is served with the correct content type, so your CSS actually styles the page and your JavaScript actually runs. Open it and click around to confirm.
- 4
Add your own domain (optional)
On Pro, connect your own domain or subdomain with automatic SSL, so visitors see yoursite.com in the address bar. Re-upload a new ZIP any time to update the whole site — the URL stays the same.
A whole site live in seconds, not a deploy pipeline
The gap between 'my site works on my laptop' and 'my site is on the internet' is usually a pile of infrastructure: a host to pick, a build to configure, a domain to point, nameservers to wait on. If your site is already built — plain HTML/CSS/JS, or the output folder from any static framework — none of that should be necessary. Zip it, upload it, and it's live at a URL you can share by text. This is the fastest path from a finished static site to a real link, with nothing to install and no account required to view it.
Multi-page, with relative links that actually work
A single HTML file is one thing; a real site is index.html plus about.html plus a /css folder and an /images folder and a /js bundle, all wired together with relative paths. That's exactly what this handles. We keep your folder structure intact, so a link to "pricing/index.html" or an image at "assets/logo.svg" resolves against your site's own root — the way relative URLs are supposed to. If your ZIP has a single top-level wrapper folder (the kind your OS adds when you compress a folder), we see through it and serve from the real root.
Your own domain, with automatic SSL
A hosted site on a random URL is fine for a quick share, but for anything you're proud of you want it on your own domain. On Pro you can point a domain or subdomain at your site and we provision the HTTPS certificate automatically — no certificate wrangling, no renewal reminders. That turns this from 'a place to park a build' into a genuine home for a small site: a docs page, a landing page, an event site, a portfolio, a course handout.
Frequently
asked
questions
Your site's built files — an index.html plus the CSS, JavaScript, images, and fonts it references. If you use a framework, zip the built output (dist/, build/, or out/), not your source code. We detect that folder automatically and serve from your site's real root.
Yes. We preserve your folder structure and serve every file with the correct content type, so relative links like about.html and asset paths like assets/app.css resolve against your site's own root exactly as they did on your machine.
Yes, on Pro. Connect a domain or subdomain to your site and we provision the HTTPS certificate automatically, so visitors see your domain in the address bar. On Free your site lives on a linkinseconds.com address.
Upload a new ZIP and the same URL serves the updated site — the link you already shared keeps working. There's no build server and no redeploy step; replacing the ZIP replaces the whole site.
Yes — every asset is served with the correct MIME type (text/css, text/javascript, and so on), which is exactly what browsers require to apply styles and run scripts. Client-side JavaScript works; there's no server-side code execution, so a backend or server-rendered pages are out of scope.
Your link is 10 seconds away
Upload a file and share one clean, trackable link — free, no sign-up to start.