Cloudflare Drop tested: a folder to a live site

What was tested

Tested: the path without a terminal: a built folder dragged to Cloudflare Drop, claimed, given its own domain, then updated once. On: this site (90 files, 2.6 MB), one evening, against a protocol written the day before. Result: live on ranthrice.com that evening, on the free plan, for the domain’s price; updating needs a terminal, so the path is partial.

What the test answered

The test answered five questions in one evening: whether Drop asks for an account before the upload (it does not), what happens after the preview, how long it takes to reach a domain (under six minutes between claiming the uploaded site and registering its domain), what the domain costs ($10.46 a year) and how a claimed site is updated.

Does Drop need an account? No. Nothing was asked before the upload. The account came at the claim step, after the site was already live on a preview URL.

What happens after the preview? The preview is stated to last one hour. Claiming it inside that window turns a temporary account into a permanent one. This site was claimed into an existing account.

How long from upload to a domain? Under six minutes from the claimed Worker to the registered zone, read from the account’s creation timestamps. Those timestamps are in UTC and fall late on 2026-09-06; in our time zone it was already past midnight, which is why the run carries the 2026-09-07 date. The domain payment was confirmed in the same minute.

What does the domain cost? $10.46 for the year, on the invoice in the account, dated 2026-09-06 in UTC. The same figure appears on our two other domains, bought on 2026-06-02 and 2026-06-26. The public pricing page had answered 403 two days before the run, so this is the first number we can stand behind.

Can a claimed site be updated, and how? Not by dragging again. The claim leaves you with a Worker holding your files. Updating it needs Node and a terminal on your own machine, and that deploy takes the domain over from the Drop worker, which then sits unused until you delete it. The steps are in the Kit’s annex.

What went wrong on our side

The first test shipped a broken archive, and the fault was ours, not the host’s. The homepage answered; every page one level down returned the homepage instead, with a 200 status, and the headers file was ignored. It was fixed the same night by uploading the folder instead of the archive.

The lesson that survives publication is the check, not the cause: a deployment is never proven by its homepage. Open a page two levels deep, a binary asset and a URL that should return 404, before believing any upload.

The mechanism, the tool that produces the fault, the script that detects it before upload and the rules that follow are entries in the Kit’s trap register, dated 2026-09-07.

What it cost

There is no second line to the hosting bill. The free plan carries the static site and the small worker behind the forms; the domain is the whole recurring cost, and it is the one figure that comes with an invoice.

Limits

One test, one person, one browser, one country. The site was 90 files and 2.6 MB. We did not test the expiry of an unclaimed preview, a claim into a brand-new account, or a domain already registered elsewhere. A second and third test on other sites are required before the kit describes this path as tested.

Proof package. No screenshot was taken during this test, a lesson for the second one. The readings above come from the account’s own records (Worker and zone creation times, invoice), kept in a dated audit folder and shared on request. There is therefore no downloadable package attached to this run, and this page says so rather than pretending otherwise.

This test is the annex of The Domain-Only Website Kit; the domain price and its timing sit on our figures page, in the rows of 2026-09-07.