PageDrop alternatives: where to move your page before it goes (2026)

PageDrop is winding down. If you published something there, this is the practical version: what the notice actually commits to, how to get your file back while you still can, and how to choose where it goes without just picking the next drag-and-drop box in the list.

What the notice actually says

Straight from pagedrop.io, checked again on 10 September 2026 — the wording has not changed since we first quoted it on 22 August:

New sales and open uploads have ended. Existing Creator Passes can be redeemed until 31 October 2026, 11:59 PM SGT; unused uses then expire without refund. PageDrop will remain online until the last existing page reaches its stated expiry.

Three separate facts sit in there, and they have different consequences:

Open uploads have ended. The upload box on the homepage now reads "New uploads require an existing Creator Pass during PageDrop's wind-down", and new passes are no longer sold. So unless you already hold a pass with uses left, whatever you were planning to publish there has to go somewhere else — and even with one, that route closes on 31 October.

Passes are redeemable until 31 October 2026. If you hold unused pass credit, that is the last date it is worth anything. After it, unused uses expire without refund. This is the only hard calendar date in the notice.

The site runs until the last page expires. This is the one people misread. It is not "the site closes on 31 October" — it is "the site closes when there is nothing left to serve." Because every PageDrop page carried an expiry chosen at publish, your pages are individually on borrowed time and were always going to be. The wind-down does not shorten your page's life; what it takes away is the ways of lengthening it. The homepage now says "New pass sales and paid TTL extensions have ended", so the one extension route left is an existing Creator Pass, which can still be applied to a page until 31 October.

Numbers and dates above are quoted from PageDrop's own site as of 10 September 2026 (the notice itself, first quoted 22 August, is unchanged; the two homepage lines about Creator Passes and extensions were read on 10 September). They set their own terms and can change them — check pagedrop.io before acting.

First: get the file back, while the page still loads

Do this before anything else, because it stops being possible the moment a page expires.

If a page still opens, the HTML is being served to your browser, which means you can have it. Open the link and use Save Page As (or View Source, select all, paste into a text file with a .html extension). PageDrop only ever hosted a single self-contained HTML file — CSS and JavaScript inline, no asset folder — so saving the page normally gets you the entire thing in one file, which is exactly the shape you need to upload somewhere else.

Two things to check on the saved copy before you trust it:

• Open it from your desktop, disconnected if you can. If it renders and the interactive parts still work, it is genuinely self-contained. If something is missing, the original pulled from an external URL and that dependency is still out there — fine, but now you know.
• Check the file size. Anything you plan to re-host has to fit the next host's upload cap, and those vary a lot.

If you never kept the local original and the page has already expired, there is nothing to recover. That is worth sitting with for a second, because it is the actual lesson here — see the last section.

Second: work out what the old link owes people

This is the step that gets skipped, and it is the one your clients notice.

Ask where that URL currently lives. If it only ever existed in a chat message from four months ago, let it go. But if it is in a sent email, a proposal PDF, a printed QR code, a calendar invite, or a thread someone might scroll back to, then somebody can still click it — and when they do, they will get nothing. From their side that does not read as "the host shut down." It reads as your work vanishing.

The fix is one message with the new URL and one line of context. Send it before the page expires, not after, so the old link and the new one are alive at the same time and nobody has to ask you what happened.

If this is a recurring problem for you — links you sent that later needed to change — that is a property of the host, not of your filing. Whether a free link will still work next year goes through how to tell in advance which hosts will do this to you.

Third: the alternatives, compared

PageDrop bundled three things that most hosts hand out separately. That is why "what's the PageDrop alternative?" has no single answer — the honest one is which third of it did you come for?

Here is the shortlist against those three jobs. The columns are each host's default posture, not a feature checklist, because defaults are the part that does not go stale when someone ships an update:

Only one row there brings the community half with it, and it is not a like-for-like. Neocities runs a genuine public browse feed — sites sorted by views, by recency, by tag, pages of them — so if Explore was what you came for, that is the nearest live equivalent, and it is a better answer than pretending the need has no home. What it is not is a drop box: Neocities is a personal-homepage community you keep a site on, not a place you fling one file and leave. Nothing else on this list runs a gallery at all.

For the current file-size caps, visit limits and prices across the free tiers, the full free-hosting survey keeps those in one dated table — they change often enough that repeating them here would just create a second copy to go stale.

Now the long version of each row:

You were there for instant, account-free, public publishing. Start with Cloudflare Drop, because it is the one row that reproduces PageDrop's actual feel: no sign-up, drop a folder, get a live URL — and, like PageDrop, the deployment lapses on its own unless you claim it. If you liked that a page you made in ten seconds also disappeared on its own, that is the same bargain. Netlify Drop, Tiiny.host and Static.app are the next shapes over — drag a file, get a public URL, no git — and all three are public-by-default and indexed, which is what you want if the point was reach. Pick between them on upload cap and how much of a site you intend to grow: one file, or a folder that keeps getting bigger. If you would rather never revisit the decision, GitHub Pages is the one that has outlasted every host on this list, at the price of a git workflow and a repo other people can read.

You were there because expiry was a feature. This is the one with no like-for-like replacement, and it is worth being clear about why: PageDrop made the deadline the product. Everywhere else, an expiry is a setting on a host that is otherwise built for permanence — you pick a date per page, and nothing about the host pushes you toward letting it die. Functionally you get the same outcome; culturally it is a different tool. If a self-destructing private link is the job, that setting is what you are shopping for.

You were there for Explore, the community gallery. No drop-box host runs one, and that is the honest headline — but "there is no replacement" would be too strong, so here is the real answer: Neocities has a public browse feed with sites sorted by views, recency and tag, which is the same social loop Explore ran. The catch is that it is a homepage community rather than a file drop. You keep a site there, edit it, and accumulate followers; you do not upload one HTML file, harvest likes, and move on. If discovery was genuinely the point, that is the platform shape you are looking for, and it is worth accepting the change of habit rather than settling for another URL vending machine.

Your page was never really static. If it signs people in, writes to a database, or runs anything server-side, it was never a fit for a drop-box host and it is not a fit for the next one either. Vercel and Netlify host the whole app with its server side intact, and that is the honest destination.

Where a private-link host fits

If the page was private — a client deliverable, a draft, a report for named people — then the replacement question is about control, not reach. That is the slot miinideck is built for: drop the HTML file you just recovered, get a link that is noindex by default behind an unguessable URL, with free password protection on any tier.

The free tier gives you unlimited links, a 10 MB file cap, and links that self-destruct after 7 days by default — with one always-on permanent link you choose. Solo ($4.99/mo) makes every link permanent and raises the file cap to 25 MB; Studio ($14.99/mo) adds a custom domain, white-label, and a 50 MB cap. The part that matters most for a migration: the same URL can serve a new version, so the link you send this time does not have to be replaced the next time the file changes — which is exactly the thing PageDrop's immutable-page design ruled out. Where the two designs actually differed walks that trade in full.

If the harder part is the link you already sent out — who has it, whether it will break, and what to tell them before it does — moving a page off a host that is winding down takes that side of it step by step.

The part worth keeping

A free host is a dependency, and dependencies end. That is not a knock on PageDrop, which was a coherent, well-executed product doing something genuinely different — and which is, to its credit, winding down with a notice, a redemption window, and pages that run out their stated life rather than vanishing overnight. Plenty of services have done worse.

The habit to take away is smaller than "self-host everything." It is this: the copy on the host is not your copy. Keep the original file somewhere you control — a folder, a repo, a drive — and treat every hosted link as a rendering of it rather than the thing itself. Do that, and the next time a host winds down, the whole migration is re-uploading a file you already have and sending one message. Skip it, and you are doing what most people are doing this month: opening old links one at a time to see which ones still load.