To host a website made with Replit means putting the app you built in Replit on a server so anyone can open it at a stable HTTPS address. On Replit's free Starter plan you get one published app, and that link goes down after 30 days unless you republish it (Replit: Starter plan); deed.page's Free plan holds 25 sites of up to 25 MB each, with no account and no expiry (pricing).
This guide covers when Replit's own publishing is the right call, which Replit projects a static host can serve, and how to publish one with curl or through MCP. Every deed.page command here was run against production on November 22, 2026, and the test sites were then deleted.
How do I host a website made with Replit?
The short answer: click Publish in Replit, or download the project as a zip, run its build, and upload the folder of HTML, CSS and JavaScript it produces to a static host.
Replit's docs, checked November 22, 2026, say publishing is available on every plan and gives the app a .replit.app address (Replit: Publish your app). Starter apps show a "Made with Replit" badge, and more published apps need Core or Pro (Starter plan). Replit's Static deployments have free hosting and charge $0.05 per GB of data transfer (Deployment pricing). If your app needs a running server, stay on Replit or another server host. Host it yourself when it is plain front-end files and you want a link that does not lapse, or an agent that keeps updating it.
Check which kind of Replit project you have
Replit offers Autoscale, Reserved VM, Scheduled and Static deployments. Its docs say Static deployments are not compatible with apps created by Replit Agent, because Agent builds full-stack apps that need a backend server (Replit: Deployment types). The same rule applies on any static host:
- Plain HTML, CSS and JavaScript, or a front end with a
vite buildscript, produces files a static host can serve as-is. - An Express, Flask or other server, API routes, or secrets read on the server need a host that runs code. A static host only serves files.
- A full-stack Agent app can move only if its front end works on its own, calling an API that stays online somewhere else.
To get the code, open the three-dot menu at the top of the file tree and choose Download as zip. If that fails on a large project, Replit suggests running zip -r project.zip . in the Shell and downloading project.zip (Replit: Projects and files).
Build it and publish it with one curl
Unzip the project, build it, then upload the output folder (dist for a default Vite setup; check build.outDir in vite.config if yours differs):
npm install && npm run build
tar -C dist -czf site.tar.gz . && curl -T site.tar.gz "https://deed.page/v1/sites?slug=tide-tables-replit-q3x7&spa=1&ref=blog"
Our test was a React + TypeScript Vite app. The dist folder had 8 files and the tarball was 92 KB. The reply had "url": "https://tide-tables-replit-q3x7.deed.page/", "version": "v1", "files": 8, "expires_at": null, and a deed_tok_… owner token shown once. Keep that token; it is the only credential. Pick your own suffix, since that slug is only an example. A stranger sending the same request got 409 slug_taken with the suggestion tide-tables-replit-q3x7-2 (choosing a slug).
spa=1 sends unknown paths to index.html, so a deep link such as /harbors/monterey returned the app with status 200, while the CSS file still served as text/css and the script as text/javascript (SPA mode). Send spa=1 on every publish.
To ship a new build, send it with the token:
curl -T site.tar.gz -H "Authorization: Bearer $DEEDPAGE_TOKEN" \
"https://deed.page/v1/sites?slug=tide-tables-replit-q3x7&spa=1&ref=blog"
An identical tarball returned "unchanged": true and no new version; a changed build returned "version": "v2" at the same URL. Bigger builds go up in parts (large sites).
Publish through MCP instead
If an agent such as Claude or Cursor holds the built files, it can publish through deed.page's MCP server at https://deed.page/mcp (docs). The call looks like this:
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"publish_site","arguments":{"slug":"tide-tables-replit-mcp-v8k2","spa":true,"files":{"index.html":"<!doctype html><title>Tide tables</title><h1>Tide tables, built in Replit</h1>"}}}}
It returned ok: true, version: "v1", the subdomain URL and a token, and a client route like /stations/santa-cruz served the page. update_site with that token gave v2 at the same address; without the token it refused with unauthorized. The MCP walkthrough covers the rest.
FAQ
Can I host a Replit site for free outside Replit?
Yes, if it builds to static files. deed.page's Free plan is $0 for 25 sites of 25 MB each, with 10 GB of transfer a month per owner; Hobby at $3 a month raises that to 100 GB (pricing).
Will my Replit database and sign-in still work after I move the site?
Only the parts the browser can reach directly. Server code, secrets and anything that ran in the Replit backend do not travel with the built files, so keep that backend running or move it to a server host.
Will the site disappear if nobody visits it?
No. deed.page sites do not expire unless you send X-Ttl for a throwaway page (TTLs). Free sites show a small "Published with deed.page" link; Hobby removes it.