Search for what to do when a host closes and nearly every answer assumes a full website: a database to export, a CMS to reinstall, DNS records and a domain to transfer, a weekend of downtime planning. If that is your situation, those guides are right, and the people to talk to are a proper host — Vercel or Netlify for anything with a build or an API, a managed host for WordPress and the like. This page is for the other, quieter case that ends up in the same search results: what you had on that host was a page. A report, a proposal, a portfolio piece, a single tool someone built for you, an AI-generated dashboard — one HTML file, or a folder of HTML, CSS, scripts and images with no server behind it. Moving that is not a migration project. It is three steps, and the only one with a deadline is the first.
Try it now
Drop a file — get a private link in seconds. No sign-up.
Drop an HTML, ZIP, PDF, PNG or JPEG file, or click to choose.
One file, or a ZIP bundle. Max 3 MB.
Up to 3 MB, link self-destructs after 7 days. Sign up free to keep links forever and store more.
Save the page while it still loads. If it is a single self-contained HTML file, saving it from the browser is the whole job. If it pulls in its own stylesheets, scripts or images, save the complete page or download the folder you originally uploaded, and zip it. This is the step with a clock on it: once the old host stops serving the page, getting the exact file back can mean regenerating it, and an export or an AI-built page regenerated from scratch is rarely quite the same document.
Upload it here. A single .html file, or a ZIP of the folder, where the entry page is detected automatically and relative paths to CSS, JavaScript, images and fonts keep resolving. You get a link back in seconds: a long unguessable address that carries noindex, so it stays out of search unless you choose otherwise. No account is needed to try it; an anonymous upload holds one file up to 3 MB for 7 days. You can add a password either way. A free account gives you one link that stays on, a password you can change on any link, and other links that expire after 7 days.
Send the new link once, and make it the last time. Nobody can keep the old address for you, because it belonged to the old host's domain. What you can change is what happens next time: on Solo ($4.99/mo) and Studio ($14.99/mo) links do not expire unless you set them to, and when the page changes you replace the file at the same address. On Studio the page can sit on your own domain, so a future change of host is invisible to the people holding the link.
Ask what happens when someone uses it. If people only look at it, scroll it, click tabs or play with charts that run in their browser, it is a page, even if it is a folder with fifteen files in it. If it saves anything people type, has a login, sends email, takes payments through its own server or reads from a database, it is an application, and it needs a host that runs code. That second kind is a job for Vercel, Netlify or your CMS's own hosting, and their migration guides are the right place to start.
Not if the address is on the old host's domain. It was theirs, and when they close it goes with them. Everyone holding the old link has to be told once. If you own a domain and the page was on that domain, you can point it at the new home and the address survives; on Studio you can attach your own domain here for exactly that reason.
Read the host's own notice rather than any summary, and treat whatever date it gives as the outer limit rather than the plan. The only time-critical step is saving the file while the page still loads. Everything after that — picking a new home, sending the new link — can happen on a calm afternoon.
Probably not. A private link is built for sending a page to people you choose, not for being found. For a public page you never want to think about again, GitHub Pages is still the best free option if you are comfortable with Git, and Netlify and Vercel both take a dragged-in folder and give you a permanent public address.
Zip the folder and upload the ZIP. It is unpacked with its relative paths intact, so the page finds its own stylesheets, scripts and images the way it did before. A root index.html is used as the entry page if there is one; otherwise the shallowest HTML file is, with ties broken alphabetically.
No card to try, no sign-up to get a link. Sign up free to keep links forever and store more.