Skip to content

Replit

A live coding space others open in the browser, run with one click, and copy into their own — nothing installed, ever. Share a link and they're in your real, running app in seconds.

Reach for it when people should run and tinker with a real multi-file app with zero setup — a workshop, a demo a teammate copies and tweaks. Skip it when you just want them to view a finished thing (a website or Artifact is lighter) or to own the source long-term (that's a GitHub repo).

Last verified: 2026-06-07 · Confidence: high on the in-browser run, the copy-to-own flow, and the public-only free tier; per-tier seat counts from Replit's pricing page.

It allows you to

  • Hand over a running app, not files. One link opens your real project, already running in their browser — the whole environment travels with it, so if it works for you it works for them.
  • Build together live. Several people edit the same project at once, cursors and all — the multiplayer move almost no other share here makes. (Paid; see Who can get in.)
  • Let them copy it to their own. Remix — copy the whole app into their account to change freely — in one click; yours stays untouched.
  • Open it to anyone or keep it named. Public is link-open to all; invited is named people only. → Who can get in.

Ideal for

  • A small app a teammate copies and tweaks — an ops dashboard or a survey-scoring tool someone remixes into their own account, changes the inputs, and runs — with no setup walk-through from you.
  • A live pair-build in a workshop — you and a fellow in the same project at once, both typing, fixing the bug together on screen, the way a shared Google Doc works but for a running app. (Paid; multiplayer needs a seat.)
  • A template a group builds off — like the public apps in Replit's Gallery, where a community-made project shows its remix count and anyone copies it to start their own version.

Who can get in

  • Public — anyone with the link runs and remixes it, no account. No sign-in to view, run, or read the code. [confirmed]
  • Invited — named editors who sign in. Invite by Replit username or email; each joins with full edit access. Live co-editing (multiplayer) is paid. [confirmed]
  • Cut someone off. Remove them and their next load is blocked; a remix they already made is their own copy and keeps working — true everywhere. [estimate]
  • Free tier is public-only. Private projects and multiplayer are paid, so a free account shares only in the public state. [estimate]

Which rungs it can hold. Named people (invited, paid) or the whole internet (public); no clean org-only short of Enterprise, and the free tier holds only the public rung. → Who can see it? [estimate]

Handing data to the host. Replit holds your code and whatever the app stores, on US servers; a public project is MIT-licensed for anyone to copy and may train Replit's models. [confirmed] Going private is the off switch — the training clause is scoped to public Apps, so we read private as not-trained, though Replit doesn't say so in those words. [estimate] Pick public-vs-private before you add data — full pricing & access fine print. → Can you trust the company? (Replit's entry)

What you do to set it up

Replit is its own web editor — you do the clicking. Your agent can write or fix the code, but creating the project, hitting Run, and sharing the link are yours.

  • Build or paste in the app, then click Run — it's live at a replit.com/@you/project URL straight away. [confirmed]
  • Share it: click Invite / Share — copy the public link for anyone, or invite named people by email (paid). [confirmed]
  • One-time: create a Replit account (~3 min once).

Full walkthrough in Share and run on Replit. Prefer to keep the source yourself? Build in Claude Code and hand over a GitHub repo — but then the recipient sets it up locally, which Replit avoids.

What the other person does

  • Just run it: click the link → the app's already running. ~5 sec, no account, nothing installed. [confirmed]
  • Copy it to change: click Remix, edit freely — needs a free Replit account (~3 min once). [confirmed]
  • Edit alongside you: accept your invite and they're in the same live project — but that runs on your paid plan, not theirs. [confirmed]
  • Pay: nothing to view, run, or remix a public app. [confirmed]

Other ways to share

  • It should just run for a non-technical viewer — no editor, no remix, no account? → a deployed website opens in any browser as a finished thing, not a space to tinker in.
  • It's one notebook to press play on, not a live multi-file app to co-edit? → a Google Colab notebook is the lighter press-play option.
  • They're ready for the real source — every file, full history, changes approved before they land? → a GitHub repo; Replit is about running and copying in-browser, not careful version history.

Sources

Good to know

  • A free published app goes down after 30 days. On the free Starter plan the published link "will automatically go down after 30 days" — re-publish it, or move to Core ($20/mo) for an always-on link. [confirmed] (Starter plan, checked 2026-06-07)
  • Free tier is public-only, one app. Starter gives 1 published app and no collaboration seats; private projects and live multiplayer are both paid. [confirmed] (collaboration-seat cutoff [estimate]) (Starter plan)
  • Per-tier seats: Core ($20/mo) gives 5 collaborators, Pro ($95/mo) gives 15. Re-check live before counting on a figure → replit.com/pricing. [confirmed]