Home / Compare builders / SPOE vs Replit / How to export from ReplitHow to export your code from Replit, and keep it runningReplit downloads a project as a ZIP from the three-dot menu at the top of the file tree, or syncs it both ways with GitHub. The database comes out separately with pg_dump, secrets are copied by hand, and uploaded files are downloaded from App Storage. Its copy steps are written for moving to another Replit account: running the app outside Replit is documented only for Enterprise, in early access.From Replit's own docs, read 2026-10-22. Every step links to the page it is from.Download a ZIP

In the project, open the three-dot menu at the top of the file tree and choose Download as zip. (source)

If that fails, open a Shell and make the zip yourself, leaving out the folders Replit can rebuild and its .cache folder, which holds cached secret values (Replit says to always leave it out of a zip you make by hand): zip -r project.zip . -x ".cache/*" "node_modules/*" ".venv/*" "venv/*" ".pythonlibs/*" "build/*" "target/*" ".next/*" "__pycache__/*" (source)

Then find project.zip in the file tree, open its three-dot menu and select Download. (source)

Push to GitHub

Link your GitHub account from your account's connected services, then open the Git tool in the project and connect the repository. Turn on auto-sync in the Git pane for two-way sync. (source)

Commit and push. Use a private repository unless you want the code public. (source)

Or in the Shell: git remote add origin with the repository's address, then git push origin and your branch, with a personal access token for GitHub.com. (source)

Your data, secrets and files

In the Shell, run pg_dump -Fc "$DATABASE_URL" --no-owner --no-privileges -f backup.dump. As written, this exports the development database. (source)

For your live data, open the Database tool, select the production database, copy its connection string from Settings and use it in place of "$DATABASE_URL", keeping the quotes. (source)

Download backup.dump from its three-dot menu in the file tree, and keep it out of GitHub. (source)

Or open the Database tool, select the database, then My Data and Database studio, and export the data to a file. (source)

Copy each secret by hand from the Secrets tool, deployment secrets included: their values do not travel with the code. (source)

In the App Storage tool's Objects view, download each file with the download icon to its right. A bucket belongs to its project and cannot be attached to another. (source)

Custom domain: in the old project, open Publishing → Domains and disconnect it. (source)

A domain bought through Replit moves to another registrar through Replit Support, and not until 60 days after purchase. (source)

What comes out

A ZIP carries everything on disk, uncommitted changes included, and the full history when it includes the .git folder. (source)

A web app comes with its front end and back end: Agent sets up API routes, a database and server-side logic as the app needs them. (source)

The database code is in the project: Agent adds an ORM. (source)

The sign-in wiring is in the code: Clerk Auth adds Clerk's React components and Express middleware. (source)

Replit's own config files come along, hidden by default: .replit, and replit.nix for Nix packages. (source)

The database is not in the code copy: Replit's copy guide moves its schema and data with pg_dump and pg_restore. (source)

Enterprise only, in early access: Image Exports turn Publish into a Docker image, a Terraform file and an SBOM. (source)

What stays behind, and needs replacing

Secret values stay in the Secrets tool and do not come with the code, but Replit's .cache folder holds cached copies of them, so leave it out of any zip you make yourself. (source)

The production database runs on Neon, billed through Replit. (source)

Replit Auth signs your app's users in with Replit accounts. (source)

If you do not name a sign-in system, Agent adds Clerk on Starter, Core and Pro, and Replit Auth on Enterprise. (source)

Clerk runs on a Clerk tenant Replit manages, and your app's users exist only in that tenant. (source)

App Storage files sit in Google Cloud Storage buckets that Replit's libraries sign in to for you. (source)

Replit AI Integrations run on provider credentials Replit manages. (source)

Connectors have to be connected again, one by one. (source)

Code can read environment variables Replit sets itself, such as REPLIT_DOMAINS and REPLIT_DEPLOYMENT. (source)

Agent chats and checkpoint rollbacks stay with the old project. (source)

Even Enterprise self-hosting means bringing your own sign-in and connectors. (source)

Cancel a paid plan and it runs to the end of the billing period, then the account moves to the free Starter plan: published apps may go offline, custom domain connections are removed and storage is reduced. Replit says to download anything you want to keep first. (source)

Repeated payment failures may suspend your published apps. (source)

After a billing hold is lifted, published apps do not restart on their own: you publish them again. (source)

Not on Replit's pages

How to run an exported app outside Replit, apart from Enterprise's early-access Image Exports.

Whether Download as zip includes the .git folder, or the .cache folder of cached secrets.

How SPOE differs

The whole project. A SPOE export is the whole project: the code, the Docker files that start it and, for a full-stack app, its database migrations, with a signed provenance manifest and the verifier inside. It starts with docker compose up, with nothing of SPOE inside, so there is nothing of ours to replace.

Signed and recorded. Every export is signed by SPOE: an Ed25519-signed provenance manifest, with a record of it on APIR's hash-chained log. spoe.ai/verify checks every file and that spoe.ai signed it, in your browser, so anyone can prove the code is exactly what was exported.

Yours for good. Your first payment of any size unlocks export permanently, whether or not you ever pay again. Locked or not, the code is always visible and copyable in the editor.

Coming from Replit. SPOE does not import a Replit project. If the app is live and you can show the site is yours, with a DNS record, a file on it or a tag in its pages, Bring your site copies the page at that address, with its styles and pictures, into a SPOE project to keep building; the data and the logic behind it are not copied. Otherwise, describe the app to SPOE and it is built as a Next.js, Fastify and Postgres project you hold. Keep your Replit export either way: it is yours.

SPOE vs Replit · Lovable vs Replit · Bolt vs ReplitExport guides for Lovable · Bolt · Base44 · v0How it works · Features · Models · Pricing · Docs · Blog · Handle checker · App ideas · Arcade · Compare builders · Verify an export · Developer API · Start freeThis page needs JavaScript to run the app itself. Everything above is a plain description of it.