Everything people ask

Drop the folder on the home page. It is listed back to you file by file, and nothing is uploaded until you confirm — after which the site is reachable over HTTPS on its own subdomain the moment the upload finishes. Nothing to install and no card — publishing is free, and the limits are the only restriction. Paid tiers exist for people who want more room, their own domain, or their pages without our link in the corner.

No, and that is not a launch offer: the free tiers stay free. They are not a trial, they do not ask for a card, and nothing you publish on one starts costing money later. If you do take a paid tier, it is a monthly or yearly subscription at the price on the pricing page, cancellable at any time — it then runs to the end of the period you paid for, which is not refunded, unless you are a consumer in the EU or the UK and it is within fourteen days of subscribing, where it comes back in full. A site that fits inside the plan you are on is never taken offline over money. While a payment is unsettled, publishing is paused until it goes through, and everything already published carries on being served. If it is never settled the account returns to the free tier and the dropto.run link comes back; if it then holds more than the free tier allows, you get a week's notice before the excess is put to sleep — oldest first, every file kept, and back on its own once there is room. The terms say this in full.

Anything that is already a folder of files: hand-written HTML, CSS and JavaScript, or the build output of a framework — React, Vue, Svelte, Astro, Next in static export mode, Hugo, Jekyll, Eleventy. Portfolios, landing pages, documentation, a CV, a client preview, a hackathon demo. A folder needs either an index.html at its top level or something readable — a .md file or a .pdf — and a 404.html beside the index becomes the error page with nothing to configure.

Anything that needs a server of its own: no PHP, no database, no rendering per request, no background jobs. If it runs after you upload it rather than in the visitor's browser, this is the wrong kind of hosting for it. Forms are the one exception, on the paid plans: mark a form with data-drop2run and what visitors send is collected for you, with no endpoint to sign up for. And where the server is one you already run, a site can call it: on the plans that include it, its /api/* calls go on to your API with the key attached on the way, so the key never reaches the page.

Your files sit on a global edge network and are served from data centres in 300+ cities, whichever one is nearest the visitor. Nothing is rendered per request and there is no origin server for the request to travel to and wait on — the nearest data centre already has the page and answers it directly. Somebody opening your site from another continent is served locally rather than from wherever you happened to upload it.

It keeps serving. Publishing and this dashboard are one system; serving your site is a separate one that runs entirely on the edge network and does not call us to answer a request. If our side is broken or offline, new deploys stop working and the site already published carries on being served as normal.

No. Your browser keeps a claim token for each site you publish, and that token is what lets you deploy to the same site again or attach it to an account later. Lose the token and you lose the ability to change that site — the site itself stays up until it expires.

Yes, once it is built. Run your build, then drop the output folder — dist or build — rather than the project. Links followed inside the app work immediately. For a route typed straight into the address bar to work as well, open the site's own page and set how it is served to Single-page app: the default is Static site, because on a plain static site a wrong URL should say so rather than quietly render the home page.

Yes. Drop a folder of .md files, or a single .pdf, and it publishes as a documents site: the page is rendered for reading, with tables, GitHub alerts, syntax highlighting, Mermaid diagrams and maths handled for you. More than one file gets a searchable file tree beside it; a single document is shown on its own. Nothing is generated and there is no index.html to write — a folder that already has one is published as an ordinary site instead, which is what output from a site generator should be. If that guess is ever wrong, the site's own page can set it by hand.

Every file also keeps its own URL: open it in a browser and you get the reader, fetch the same address with curl or from a script and you get the file itself. One link works for a person and for a tool, and that will not change.

The new version goes live in one step, so no visitor ever sees a half-updated site. The previous deploy stays on disk for as long as your tier keeps it.

No. Every response carries X-Robots-Tag: noindex, so search engines are asked not to index anything published here. That is deliberate rather than an oversight: one phishing page inheriting the reputation of a shared domain is enough to get every site on it flagged by browsers. If being found by search matters for what you are publishing, this is not the right host for it yet.

Yes, from the Starter tier up. Point the domain at us and the certificate is issued and renewed for you; how many domains a tier allows is on the pricing page. Every site also has a subdomain here, which it keeps and goes on being served on. Without an account that subdomain is assigned for you; with one you can choose the name.

Yes, on plans that include comments. The people you share a site with — or anybody signed in, if you choose — press C, click a heading or select a sentence, and write; the comment stays pinned there, everyone reviewing sees it appear without reloading, and you get an email. It works on Markdown, code and text files in a documents site too. You answer on the page, or let your AI agent read the threads, fix what they point at and answer for you. Commenters sign in with a Drop2Run account, which is how you know who said what. How comments work →

Yes, and it goes offline immediately. The subdomain is then retired rather than released: nobody else can claim a name whose old links are still being followed.

How many sites you may have, how much you may store, how large one publish and one file may be, how many new or changed files you may publish a month, how many calls your sites may send on to your own API a month, and how long a site is kept. Traffic to your pages is not one of them — it is neither metered nor billed. All of them, for every tier, are on the pricing page, which reads the same figures the service enforces.