Skip to main content
Branches let you try new ideas, features, or redesigns without affecting your app. Each branch has its own chat and its own live preview, and you can work on several branches in parallel, then merge each one into your app when you are happy with the result.
The branch menu listing several branches next to an app preview

Work on several branches alongside your main app

Ways to use a branch

  • Test a redesign. Try a new look for your app and compare it with the current version. If you change your mind, leave the branch behind.
  • Keep your live app ready. When a small fix comes up mid-project, fix and publish it from main right away. Your bigger work in progress stays safely on its branch.
  • Build a feature that launches later. Work ahead of a release and keep the feature on a branch until launch day.
  • Work in parallel. Build on several branches at the same time, and work with your team on different ideas at once, each on their own branch.
Branches work alongside a GitHub connection. Base44 keeps each branch as a real branch in your repository, and you can also build on a branch that is already there.

​
How branches work

Your app’s main version is called main. When you create a branch, Base44 starts a separate line of work from the current state of main. Each branch keeps its own chat, live preview, and copy of your app’s design and pages, so changes you make stay on the branch until you merge them. A branch also builds on its own and keeps its own version history, so branches run in parallel and you can return to any earlier point without touching main. Some things stay shared across main and every branch. Your app’s data is the same live records everywhere, and record changes happen on main. Your connections and automation, including integrations, secrets, automations, workflows, and in-app agents, are shared too, along with your app’s settings, domains, and published version.
A branch uses your real, live data.
  • Records you add, change, or delete while previewing a branch affect the same data your app uses everywhere.
  • To experiment without touching your live data, switch your preview to test data while you work. Test data is available on the Builder plan and higher. Learn more about testing your app with test data.

​
Creating a branch

Describe what you want to build, and Base44 creates the branch, names it from your first message, and starts building right away. Branch names are short, 3 words or fewer, and always in English, whatever language you write in. The name is set automatically, and a branch cannot be renamed.
Before you begin: If your app was built a while ago, you may need to make one change on main before you can create your first branch. If that applies to your app, Base44 tells you when you try.
To create a branch:
  1. In the app editor, click your app’s logo or name at the top of the chat panel.
  2. Click Create new branch.
  3. Pick one of the suggestions, or type what you want to build in the chat box.
  4. Send the message.
The branch menu open under the app name, showing Main chat and a Create your first branch panel with the Create new branch button highlighted

Creating your first branch from the branch menu

Branches always start from main. If you create a branch while you are on another branch, the new branch still starts from main.
Branches work on your phone as well, both in a mobile browser and in the Base44 app. The branch menu appears at the top of the editor as soon as your app has a branch, so create your first branch from a desktop browser, then switch between branches, build, and merge from your phone.

​
Importing a branch from GitHub

When your app is connected to GitHub, you can build on a branch that already exists in your repository. Base44 works on that branch itself, so your changes and Base44’s go to the same branch in your repository. To import a branch from GitHub:
  1. In the app editor, click your app’s logo or name at the top of the chat panel.
  2. Click Import from GitHub.
  3. Search for the branch you want, then select it.
  4. Click Import.
You import from the repository your app is connected to. A branch you create in Base44 gets a new branch in that same repository.

​
Working on a branch

While you are on a branch, the branch’s name replaces your app’s name at the top of the chat panel, and a spinning icon shows when the AI is working. You build on a branch the same way you build on main: describe what you want in the chat. Selecting an element and making a visual edit saves to the branch you are on too, the same as your chat changes. A few things work differently on a branch:
  • Merge to main replaces the Publish button. You publish changes from main after merging.
  • The preview shows the branch’s version of your app.
  • The page URL includes the branch, so you can share a link that opens the app editor on that branch.
Branches run in parallel. Send a request on one branch, switch to another, and keep building there while the first one finishes. Your app runs up to 5 builds at the same time, so you and your team can move on several ideas at once, each on their own branch.The branch menu shows which branches are building, so you can check on them as you go.

​
Actions that happen on main

You do most of your building on a branch, but some actions affect your whole app, not just one branch. Those always happen on main, even while you are working on a branch:
  • Publishing your app
  • Creating or changing secrets, connectors, automations, workflows, and in-app agents
  • Editing code directly in the code editor
  • Changing your app’s theme settings
  • Undoing a message in the chat, or editing and resending one
  • Adding a page from Figma
  • Asking the AI to add, change, delete, or import records
If you ask for one of these on a branch, Base44 asks you to do it on main or merge the branch first.

​
Entities on a branch

You can create entities and add fields to entities you already have on a branch, and both are live in that branch’s own preview right away. On an entity you create, you set everything, including its data permissions. On an entity that already exists, additions apply, so keep a new field optional, because your existing records do not have it yet. Removing an entity or a field, changing an existing field’s type or whether it is required, and changing data permissions happen on main. Make the change there and your branch picks it up right away, with no merge or update needed. Records are your app’s live data, shared with main, so ask the AI for record changes on main rather than on a branch. Adding, changing, or deleting records yourself while previewing a branch works as it always does, and it changes the same data your app uses everywhere.

​
Backend functions on a branch

You can add and change backend functions on a branch. The branch gets its own copy of each function you touch, along with the shared files those functions import, so you can update a helper and the function that uses it together. The branch preview calls the branch’s version, and merging the branch deploys it to main. If your app cannot do this yet, Base44 asks you to make backend changes on main.

​
Using version history on a branch

Every version saved on a branch is listed in that branch’s own version history, so you can look back at how the branch developed and return to any earlier point. Restoring a version changes that branch only, and main stays exactly as it is. A merged branch keeps its version history readable, and you can restore while a branch is still active. To restore an earlier version of a branch:
  1. On the branch, click the Version history icon at the top of the chat panel.
  2. Click a version in the list to load it in the preview.
  3. Click the More options icon next to that version.
  4. Click Revert to this version.
Restoring brings the branch’s pages, design, entities, and backend functions back to that version, and the branch’s chat returns to the message that created it. Your records are shared with main, so they stay as they are. Your later versions stay in the list, so you can move forward again whenever you want.
Restoring and publishing from a branch:
  • Publish this version is available on main only, because publishing always ships your main app. To release work from a branch, merge it into main and publish from there.
  • Restore a version once the branch has finished building and any update from main is complete. If the branch is busy, Base44 tells you so, and you can restore as soon as it finishes.

​
Switching between branches

You can move between main and your branches at any time, and every branch keeps its changes until you merge it. On a branch, you can also click the X next to Merge to main to exit back to main. To switch to another branch or back to main:
  1. Click the branch name at the top of the chat panel.
  2. Select a branch from the list, or select Main chat to return to main.
The branch menu open on a branch, showing Main chat above the list of branches

Switching between main and your branches

The icon next to each branch shows its current status. Hover over the icon to see the label:
You can switch branches while the AI is building, and it keeps working on the branch you left. Save or discard any edits on main first.

​
Updating a branch with changes from main

If main changes while your branch is open, a card appears above the chat box on the branch. It tells you how much changed on main and whether any of it overlaps with your branch. When you update, the AI combines main’s changes with your branch. If some changes overlap, the AI resolves them for you. If the two versions genuinely conflict, the AI asks you a question in the chat so you can decide what to keep. To bring main’s latest changes into your branch:
  1. On the branch, find the update card above the chat box.
  2. Click Update branch.
An update card above the chat box reading 1 new message on main, Nothing overlaps, Ready to update, with an Update branch button

The update card that appears above the chat box when main has changed

You can also start an update from the branch menu. Click the More actions icon next to a branch, then click Update from main.
If an update runs into a problem, Base44 rolls it back and your branch’s work stays unchanged.

​
Merging a branch into main

Merging brings everything you built on the branch into main. Your changes reach your app’s users only when you publish from main, so you decide exactly what goes out and when. After the merge, a summary of the branch’s changes appears in main’s chat, and the branch stays in your branch list as merged, so you can still read its chat history, but it becomes read-only. To merge a branch:
  1. On the branch, click Merge to main at the top of the editor.
  2. Review the confirmation, then click Merge to main.
The app editor on a branch with the Merge to main button highlighted in the top bar

Click Merge to main at the top of the editor, then publish from main when you are ready

You can also ask the AI chat to merge or update a branch. It adds a one-click card to the chat that runs the action for you.
You can also merge from the branch menu. Click the More actions icon next to a branch, then click Merge to main.
If the branch conflicts with changes made on main, Base44 asks you to update it first. Update the branch from main to resolve the conflicts, then merge again.

​
Deleting a branch

Delete a branch when you are done with an idea and want to clear it from your list. Your app and your other branches stay as they are.
Deleting a branch is permanent. It removes the branch and its chat, and this cannot be undone. To keep the work, merge the branch into main first.
To delete a branch:
  1. Click the branch name at the top of the chat panel.
  2. Click the More actions icon next to the branch you want to delete.
  3. Click Delete.
  4. Review the confirmation, then click Delete branch.
The branch menu with the More actions menu open on a branch, showing Merge to main, Update from main, and Delete

Opening the More actions menu on a branch

You can delete a branch once the AI finishes building on it and any update from main is complete. Merged branches stay in your list as a record of the work.

​
FAQs

Click a question below to learn more about branches.
No. Publishing always happens from main. On a branch, the Publish button is replaced by Merge to main. Merge the branch first, then publish from main.
There is no set limit. You can keep as many branches going at once as you want, and merge each one whenever it is ready.
Yes. Each collaborator can open a different branch and chat there, and each branch builds on its own. Your app runs up to 5 builds at the same time, and anything beyond that waits in the queue and runs in order.Creating a branch needs edit access to the app, so members with the Viewer role can open branches and read their chats. Learn more about roles in your workspace.
No. Building on a branch uses credits the same way as building on main, from the same credit balance.
Yes. Create a branch the way you would on any app, and Base44 adds the matching branch to your connected GitHub repository. To build on a branch that is already in your repository, use Import from GitHub.
Yes. Base44 adds your open branches to the repository when you connect, so there is nothing to merge or delete first. If a branch is building at that moment, wait for it to finish, then connect.
Yes. An app you migrated from another platform works with branches from the same branch menu as any other Base44 app.