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.
See who opened it, and whenLock it with a passwordPrint or share it as a QR code
Drop your file here
Drop several at once and they become one album link
Files up to 250 MB free·
FreeNo sign-up to view250 MB freeWorks in your browser, nothing to install
ImagesPDFsVideoAudioSlidesCodeSites
How do I host a static website from a ZIP?
To host a static website, zip your site's built files, or your framework's dist/, build/, or out/ output, and drop the ZIP in the uploader above. We unpack it safely, find your index.html, and serve every page and asset under one clean, shareable URL. Relative links and assets resolve exactly as they did on your machine, no server, no build pipeline, and no account required to view it.
Live in seconds, no deploy pipeline
If your site is already built, plain HTML/CSS/JS or a static framework's output, there's no host to pick, no build to configure, and no nameservers to wait on. Zip it, upload it, and it's live at a URL you can share by text.
Multi-page, relative links that work
A real site is index.html plus about.html plus a /css folder, an /images folder, and a /js bundle. 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 should.
Your own domain, automatic SSL
On Pro, point a domain or subdomain at your site and we provision the HTTPS certificate automatically, so visitors see yoursite.com in the address bar. No certificate wrangling and no renewal reminders.
When you tweak the copy, fix a bug, or regenerate your build, drop a new ZIP and the same address serves the updated site. The link you already shared keeps working and simply shows the latest version, the closest thing to a one-click redeploy without a build server or a git push.
What static hosting does not do
No backend or server-side code. We serve static bytes only, no PHP, no server-rendered pages, and no .htaccess interpreting. If your site needs a running server behind it, use a full platform.
No database or environment variables. An app that needs stored data or server secrets is out of scope; this is for finished static output.
No executables or server-side scripts. They're refused on upload, and every file's type is derived from our own inspection, not trusted from the ZIP.
How it works
1
Zip your site's files
Select the folder with your index.html and everything it references, CSS, JavaScript, images, fonts, and compress it to a .zip. With a framework, zip the built output (dist/, build/, or out/), not your source. We detect that folder automatically.
2
Upload the ZIP
Drag the .zip into the box above. We unpack it safely, find your index.html at the root or inside a common build folder, and lay every file out under one site so relative links and assets resolve exactly like they did locally.
3
Open the live site, add a domain
Your site goes live at a clean, shareable URL with every page and asset served correctly. On Pro, connect your own domain with automatic SSL, and re-upload a new ZIP any time to update the whole site while 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.
Re-upload to update, keep the same link
Sites change. When you tweak the copy, fix a bug, or regenerate your build, you don't want a new URL and a broken link in everyone's inbox. Drop a new ZIP and the same address serves the updated site, the link you already shared keeps working and simply shows the latest version. It's the closest thing to a one-click redeploy without a build server or a git push.
Static bytes only, safe by design
We serve your files as static bytes with the correct content type and nothing more. There's no server-side execution, no PHP, no server-rendered pages, no interpreting an .htaccess, so the security surface stays small and predictable. Executable and script files are refused on upload, and every file's type is derived from our own inspection, not trusted from the ZIP. The result is a host that's a great fit for finished static output and honest about what it won't do: it won't run a backend for you.
Who this is for, and who should look elsewhere
Great fit: anyone with a built static site, a hand-coded multi-page site, a framework's exported dist/ folder, a documentation build, a landing page, a portfolio. Not the right fit: an app that needs a database, server-side rendering, environment variables, or a backend API you control. Static hosting means we serve exactly the files you built; if your site needs a running server behind it, use a full platform. If your only blocker was 'I just need this built site live somewhere,' that's precisely the blocker this removes.
Set an end date or a view cap and the link stops on its own. Send a quote that expires Friday, or a preview that closes after five opens, without remembering to delete it.
Put a client's built site live at a clean URL, then a custom domain with SSL on Pro.
Designers & studios
Ship a hand-coded portfolio or landing page, relative links and assets intact.
Developers
Upload your framework's dist/ or build/ output and get it live without a deploy pipeline.
Events & courses
Host an event site or a course handout as one shareable link anyone can open.
What people say
In their words
“The admin interface is incredibly intuitive and set up exactly how a user actually thinks. My students all said it was easy to use and worked perfectly.”
JJasonTeacher · shares class materials
“The app is genuinely nice and easy to handle. I keep all my different app links in one place, my App Store and Play Store screenshots, and I organise my images and PDFs into albums with tags. The big storage means everything just lives here.”
EEvelynApp developer
“I handle contracts, invoices and legal files for several different organisations, so almost everything I send is password protected. Link in Seconds makes that simple, and I run my portfolio on a custom domain. It is easy to use and genuinely affordable.”
GGuy HenryFreelancer · contracts and invoices
Every link feature is free. Pro adds room and website hosting.
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. Without one, the site lives on its own linkinseconds 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.
Yes. If your site uses client-side routing (React Router, Vue Router, and the like), turn on the single-page-app option so unknown paths fall back to your index.html and deep links resolve instead of 404-ing.
Static-site hosting is a Pro feature. Pro sites can hold up to 500 files at up to 100 MB total; Lifetime raises that. Each site is served from its own isolated space so your JavaScript never touches the app.
Executables and server-side scripts are refused on upload, and every file's type is derived from our own inspection rather than trusted from the ZIP. We serve static bytes only, no server-side execution, which keeps the whole thing safe and predictable.
Your static site, live at a clean URL, in seconds
Zip your site's files, drop the ZIP, and get a live multi-page website with SSL. No account needed to view, and your link stays the same every time you re-upload.
