Cloudflare Drop alternative: a public link with no account and no claim step

Cloudflare Drop, announced in July 2026, puts a static site on Cloudflare's network by drag and drop, with no account required to start; an unclaimed drop stays live for 1 hour. BrewPage covers the same moment differently: nothing to claim, a link that stays up for the days you choose, up to 30, and pasted HTML or Markdown as well as files. This page compares the two, including when Cloudflare is the better fit.

Cloudflare Drop vs BrewPage at a glance

Cloudflare details come from its Drop page and developer documentation as of October 2026. Limits change, so check the linked sources before you decide.

QuestionBrewPageCloudflare Drop
Account to publishNone: each publish returns an owner tokenNo account required to start
How long it stays up1–30 days, as you choose, then deleted with no recoveryA temporary live preview that stays live for 1 hour unless you claim it
Keeping itNothing to claim: the owner token updates or deletes the pageClaim within 60 minutes by signing in or creating an account; new accounts verify their email first
What you can publishPasted HTML or Markdown, a single file, a folder or a ZIPA folder or .zip of a static site (HTML, CSS, JS), or a single .html file with any filename
Addressbrewpage.app or a BrewPage subdomainA workers.dev URL
SizeOne HTML page up to 5 MB; a site up to 20 MB (200 files, 5 MB each)After claiming, on Workers Free: up to 20,000 static asset files per Worker version, 25 MiB each
Own domainNot offeredAfter claiming: connect an existing domain or buy a new one
PriceFree, with no payment stepClaimed sites can run on Workers Free; Workers Paid has a minimum charge of $5 USD per month
AutomationFree REST API with no key, OpenAPI spec, MCP server and GitHub Actionwrangler deploy --temporary creates a temporary account and prints a claim URL to use within 60 minutes

Cloudflare prices and limits as of October 2026, per their developer documentation.

Where BrewPage differs

Both put a static page online from the browser without signing up first. They differ in what happens after the first hour, what you can publish and how ownership works.

  • No claim, no email. Cloudflare's changelog calls an unclaimed drop “a temporary live preview that stays live for 1 hour”. Keeping it means signing in or creating a Cloudflare account, and a new account verifies its email address first. On BrewPage nothing needs claiming: the link stays up for the days you pick, up to 30, and the owner token from each publish updates or deletes it.
  • Paste text, not only files. Cloudflare Drop's page lists a folder, a .zip or a single .html file. BrewPage takes those too, plus pasted HTML or Markdown, so a page an AI assistant wrote in a chat can go online without saving it to disk first.
  • Markdown is first-class. A .md file or pasted Markdown is rendered as a styled, readable page. See Markdown hosting.
  • Agents get a lasting link without a claim URL. Both let an agent publish without logging in: Cloudflare's Wrangler deploys with --temporary, creating a temporary account and a claim URL to use within 60 minutes. BrewPage's REST API publishes with one curl request and no key, and returns the link and an owner token with no claim deadline. There is an OpenAPI spec, the brewpage-mcp server, a GitHub Action and an llms.txt.
  • A password without an account. Cloudflare offers access control once a site is claimed. On BrewPage any publish can carry a password of at least 4 characters, no account needed.

When Cloudflare Drop is the better choice

BrewPage is built for sharing something now, not for running a website. Cloudflare is likely the better tool if one of these matters to you:

  • You want to keep the site long term. Claim it into a Cloudflare account and it is yours to keep and grow. Every BrewPage publication is deleted within 30 days.
  • You want your own domain. After claiming, you can connect an existing domain or buy a new one. BrewPage does not offer custom domains: pages live on brewpage.app or a BrewPage subdomain.
  • The site is larger. On Workers Free a claimed site can hold 20,000 static asset files per version, 25 MiB each. A BrewPage site is capped at 200 files and 20 MB.
  • You plan to build on Cloudflare. Claimed sites can add observability, Markdown for Agents and access control, and static asset requests are free and unlimited.

Publish on BrewPage in three steps

  1. 1Open the editor on the homepage. Paste HTML or Markdown, or drop a .html or .md file. For a site with its own CSS, JavaScript and images, drop the whole folder or a .zip.
  2. 2Choose who can find it. Public, the default, can appear in the gallery and in search; Private gives an unlisted address. Add a password if readers should enter one, and pick how many days the page stays online, up to 30.
  3. 3Press Publish, copy the link and keep the owner token: it is what lets you replace or delete the page later.

Scripts and agents can skip the editor. Each request below returns the link and the owner token as JSON:

Publish a ZIP of a static site for 15 days

curl -X POST "https://brewpage.app/api/sites?ttl=15" \
  -F "archive=@site.zip"

Publish a single HTML file

curl -X POST "https://brewpage.app/api/html?ttl=15" \
  -H "Content-Type: text/html" \
  --data-binary @index.html

The site opens at the file named by the entry parameter, else a root index.html, else the shallowest HTML file. The full reference is on the API page and in llms-full.txt.

What to know before you switch

Lifetime
Content expires within 30 days: you pick 1 to 30 days, and the editor suggests 30 for public pages. Expired content is deleted for good. Updating a page keeps its original expiry; publish again to start a new period.
Attribution
Published pages show a small BrewPage badge.
Domain
No custom domains. Pages live on brewpage.app or a BrewPage subdomain.
Visibility
Public pages without a password may be listed and indexed. An unlisted address is not secret: anyone with the link can open it. Use a password when readers should have to enter one.
Ownership
No accounts: the owner token is the only way to update or delete. A lost token cannot be recovered, and the page then simply expires.

Cloudflare Drop alternative — FAQ

Is BrewPage a free alternative to Cloudflare Drop?

Yes. Publishing and reading on BrewPage cost nothing, with no signup, API key or payment step. It suits short-lived sharing: every page expires within 30 days.

Do I have to claim my page within an hour?

No. There are no accounts, so there is nothing to claim. The link works as soon as you publish and stays up for the days you choose, up to 30. Keep the owner token to update or delete the page.

Can I drop a whole folder or a ZIP?

Yes. Drop a folder or a .zip with up to 200 files and 20 MB in total, 5 MB per file. Relative links between the files keep working.

How long does a BrewPage link stay online?

Between 1 and 30 days, as you choose. Public pages from the editor default to 30 days, API publishes to 15. After that the page is deleted and cannot be recovered.

Can an AI agent publish to BrewPage?

Yes. Agents can call the free REST API without a key, or use the brewpage-mcp server from MCP-compatible tools. The answer includes the link to share and the owner token.

Can I use my own domain?

No. Pages live on brewpage.app or on a BrewPage subdomain. If you need your own domain, a claimed Cloudflare site or another host with custom domains fits better.

Sources

Cloudflare facts were checked in October 2026 on these pages. They may have changed since; Cloudflare's own pages are authoritative.

BrewPage facts come from the current API reference and llms-full.txt.