Most alternative pages assume you are shopping. This one probably finds you in the middle of a small migration you did not plan, which is a different problem with a different order of operations. There are really three questions and only the last one is about choosing a host: whether you can still get the file back while the page loads, who is currently holding the old address and what happens to them, and only then where it should live next. Skipping to the third is how people end up doing this twice. It is also worth saying plainly that a host winding down is not a scandal — small tools close, and the ones that give notice are behaving well. What it does mean is that the link you handed someone is now on a clock you do not control, and that is the thing worth fixing rather than the thing worth being annoyed about.
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, password-protect them, and store more.
Get the artefact back first, while the page still loads. Open the live page and save it — if it is a single self-contained file, that save is the whole thing. If it pulls in styles, scripts or images, you want those too, which usually means saving the complete page rather than just the document. Do this before you compare anything: every option below is easier with the file in your hand, and none of them are available once the page has gone.
Then upload it here. A single .html file, or a ZIP of a built 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 string carrying a noindex meta tag and an X-Robots-Tag header, because a deliverable is not trying to be found. No account is needed to try it: an anonymous upload holds one file up to 3 MB for 7 days. With a free account you set the expiry deliberately or turn it off, and a password is free on every plan.
Set the clock on purpose this time, since that is the part that just cost you an afternoon. On Solo ($4.99/mo) and Studio ($14.99/mo) links do not expire unless you decide they should, and when the work changes you replace the contents at the same address — the URL, the password and the expiry all carry over, each upload kept as a numbered version. That is the property that makes the next migration, whenever it comes, a one-person job instead of an email to everyone who has the link.
Read the notice on their own site rather than trusting a summary here, including this one — the terms of a wind-down are exactly the kind of detail that changes, and the only copy that matters is theirs. What is worth doing regardless of the specifics is the same in every case: assume the page has a finite life from today, get the file back while it still loads, and treat any date you are given as the outside edge rather than the plan.
No, and no host can offer you that — the address belonged to their domain. This is the genuinely annoying part of any migration and it is worth being clear-eyed about: everyone holding the old link has to be told once. What you can do is make it the last time. A link you can replace the contents of means future revisions do not cost anyone a new address, and if the work matters enough, a custom domain on Studio means the next host change is invisible to the people reading it, because the address was yours all along.
Two axes, and they sort the field faster than a feature table. First, should the page be public or private — a portfolio piece wants to be found, a client proposal does not, and hosts are built around one answer or the other rather than treating it as a setting. Second, how long does the link have to work: an afternoon, a review window, or indefinitely. Answer those two and most of the field falls away, including us for the cases where we are the wrong shape.
Then a private-link host is the wrong tool and you should use a better one. For a public page you never want to think about again, GitHub Pages remains the best free deal there is, at the cost of a Git workflow. Netlify and Vercel both take a drag-and-drop folder and give you a permanent public URL. We are built for the opposite case — one deliverable going to named people, off search, on a clock you set — and if that is not your case you will be happier elsewhere.
Yes. Upload the folder as a ZIP and the bundle is unpacked with relative paths intact, so internal links and asset references resolve the way they did locally. The entry page is detected automatically: a root index.html wins if there is one, and otherwise the shallowest HTML file becomes the entry, with ties broken alphabetically so the result is predictable. If your zip tool wrapped everything in a containing folder, that common wrapper is stripped when every entry shares it.
Faster than it feels, for one specific reason: the recovery step depends on the old page still loading. Once it stops, you are reconstructing the file from whatever you have locally, and for anything generated rather than authored — an export, a build output, something an AI tool produced — that can mean regenerating it and getting a subtly different document. Saving the file takes two minutes and removes the deadline entirely. Choosing the new host can wait until afterwards.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.