✅ Quick Summary

Push44 uses the Base44 public API (the same API that powers their own editor) to read all your project files. It then uses the GitHub Tree API to push every file in one atomic commit. The entire process takes under 2 minutes and requires only your Base44 API token and a GitHub Personal Access Token — both free to obtain.

The Problem

When you build an app on Base44, your source code lives on Base44's servers. You can preview and edit it inside their platform, but downloading your full project as a GitHub repository requires either a paid plan or manual copy-paste of individual files. Most developers want to own their code, version-control it, and not be locked in.

How Push44 Solves It

Push44 uses the Base44 public API (the same API that powers their own editor) to read all your project files. It then uses the GitHub Tree API to push every file in one atomic commit. The entire process takes under 2 minutes and requires only your Base44 API token and a GitHub Personal Access Token — both free to obtain.

Step-by-Step Guide

1

Get your Base44 API token

Open Base44 in your browser and navigate to your profile settings. Find the 'API Keys' or 'Access Tokens' section and generate a new token. Copy it — you'll paste it into Push44 in the next step. This token is what gives Push44 read access to your project files.

💡 Pro Tip
Your token starts with a long alphanumeric string. Keep it safe — treat it like a password.
2

Open Push44 and add your credentials

Go to push44.vercel.app and click 'Launch App'. On the credentials screen, select 'Base44' as your platform. Paste your API token into the Base44 token field. Then add your GitHub Personal Access Token (create one at github.com/settings/tokens with 'repo' scope).

💡 Pro Tip
If your Base44 account uses Google login, use the API token tab instead of email/password.
3

Select your Base44 project

After connecting, Push44 loads your list of Base44 apps. Click on the project you want to export. Push44 will fetch all files from that project — typically 20–60 files for a full-stack app. You'll see a file count as it loads.

4

Configure your GitHub repository

Enter the GitHub username and repository name where you want to push the code. You can choose an existing repo or type a new repo name — Push44 will create it automatically if it doesn't exist. Select the branch (defaults to 'main').

💡 Pro Tip
For a private repo, make sure your GitHub PAT includes the 'repo' scope, not just 'public_repo'.
5

Review the diff and push

Push44 shows you a diff view: which files are new, which are modified, and which are unchanged. Review the changes, then click 'Push to GitHub'. Push44 creates the GitHub tree, commit, and branch update in a single API call — your repo is updated atomically.

Pro Tips

  • Run Push44 after every major Base44 session to keep your GitHub repo in sync.
  • Use GitHub branches to track different versions of your app (e.g., 'base44-export-v1', 'base44-export-v2').
  • Push44 never modifies your Base44 project — it's read-only access to your files.
  • If you have multiple Base44 apps, repeat the process for each one with separate GitHub repos.

Common Mistakes to Avoid

⚠️ Watch Out For
  • Using a GitHub token with insufficient permissions — make sure 'repo' scope is selected, not just 'public_repo'.
  • Forgetting to copy the entire Base44 API token — they are long strings and browsers sometimes cut them off.
  • Trying to push to a GitHub repo you don't own or don't have write access to.

Ready to Export?

Push44 is free, open source, and takes under 2 minutes to set up.

Start Exporting Now → View on GitHub

Frequently Asked Questions

Can I export Base44 code for free?
Yes. Push44 is completely free and open source. There are no paid plans, no subscription required, and no file limits. You can export unlimited Base44 projects.
Does Push44 modify my Base44 project?
No. Push44 only reads your files via the Base44 API. It never writes to Base44 or changes your project in any way.
What if my Base44 project has images or binary files?
Push44 handles all file types that Base44 stores in your project, including images and other assets. They are pushed to GitHub as binary blobs.
Can I export to a private GitHub repository?
Yes. As long as your GitHub Personal Access Token has 'repo' scope (not just 'public_repo'), Push44 can push to private repositories.
How often should I export my Base44 project?
We recommend exporting after every significant change — at least daily if you're actively developing. This gives you a complete version history in GitHub.
Does my Base44 account need a paid plan?
No. Push44 uses the Base44 API which is available to all Base44 users. You only need a valid API token from your account settings.