Can you export code from Bubble?

No. Bubble’s support article puts it directly: it doesn’t support “on-premise self-hosting or code exports at this time” (Bubble support, updated July 2026). A Bubble app isn’t compiled into code that you could take away; it’s a description of your app that Bubble’s own engine interprets when someone opens a page.

That’s also true of Bubble’s new AI features: Agent 2 and the Bubble MCP build elements, workflows and data types inside Bubble, not code.

Bubble’s data export article confirms the CSV and API routes. Two things never come out: runnable code and user passwords — Bubble stores passwords separately and doesn’t release them, so any move ends with users choosing a new password once.

The export is a large JSON document. It contains:

• Pages and reusable elements — every element with its type, position and layout settings, styles, conditionals and visibility rules.
• Workflows — every event and action, with their conditions and expressions as structured data (not text).
• Backend workflows — API workflows, recurring events and database triggers.
• The data model — data types, fields and their types, option sets with attributes, and privacy rules.
• Styles, colors, fonts and app texts — including translations, if your app has several languages.
• Settings — installed plugins and their settings, API Connector calls, domain and SEO settings.

It does not contain your database records, your users or uploaded files (files appear in your data as URLs).

1. The app: in the Bubble editor, open the Settings tab and use Export application. You get a .bubble file.
2. The data, as files: in the Data tab, open a data type’s records and export them as CSV — one type at a time.
3. The data, completely: in Settings → API, enable the Data API, tick each data type, and create an API token. Tools (and deBub) can then read all records, users and file URLs page by page — and read them again later to sync changes.

Menus in the Bubble editor change from time to time; if a label differs, Bubble’s manual has the current location.

Because the export is precise, it’s a starting point for every realistic route:

Rebuild by hand from the export

A developer uses the app and its export as a specification. You get exactly what they build, at agency or freelance rates, in weeks to months.

Ask an AI tool to rebuild it

AI coding tools can help a developer rebuild faster. Fed the raw export and asked for “the same app”, they tend to guess at the parts that matter most — conditions, privacy rules, edge cases — without telling you which parts were guessed.

Compile the export

The export can be read the way Bubble reads it and written out as code, deterministically. That’s what deBub does: your .bubble file becomes a Next.js + TypeScript + Supabase project with the same pages, workflows, data model and privacy rules, and a report that lists anything it couldn’t translate exactly. Your data, users and files are copied through the Data API when you launch. See what maps to what.

Stay on Bubble

If you don’t need code, you don’t need to leave. The October 2026 changes explain what Bubble’s new AI features cost.

A useful test for any route: once you’re done, could you…

• run the app on hosting of your choice, without the tool that produced it?
• hire any developer — or use any AI coding tool — to change it?
• keep it running if the vendor disappeared tomorrow?

A Bubble export passes none of these; a standard Next.js codebase in your own GitHub, with a database in your own Supabase account, passes all three. Ready to plan the move? Read How to migrate from Bubble to code.