📑 Quick Navigation 7 sections
IntroductionThe ProblemThe SolutionStep-by-Step GuidePro TipsFAQRelated Guides

✅ Quick Summary

Push44 automates 100% white-labeling for Base44 live sites: it inspects your app's sandbox files, instructs Base44's AI engine to inject high-specificity CSS rules (#base44-edit-badge { display: none !important; }) into src/index.css, and triggers a production redeployment via POST /api/apps/:appId/deploy. The live Vite bundle is rebuilt, suppressing the badge permanently across all browsers.

The Problem

When Base44 serves live deployed sites, its backend server injects /static/js/badge.js into the HTML <head>. When loaded, this script mounts a high-priority div element with ID #base44-edit-badge at zIndex 999999. Base44 locks badge removal behind an expensive monthly subscription tier in their project settings.

How Push44 Solves It

Push44 automates 100% white-labeling for Base44 live sites: it inspects your app's sandbox files, instructs Base44's AI engine to inject high-specificity CSS rules (#base44-edit-badge { display: none !important; }) into src/index.css, and triggers a production redeployment via POST /api/apps/:appId/deploy. The live Vite bundle is rebuilt, suppressing the badge permanently across all browsers.

Step-by-Step Guide

1

Connect your Base44 account in Push44

Open Push44 (push44.vercel.app) and enter your Base44 API token or email/password in Settings. Push44 validates your credentials and auto-discovers all your active Base44 apps.

💡 Pro Tip
You can find your API token in your Base44 profile settings under API Keys.
2

Select your Base44 app on the Push page

Go to the Push page in Push44 and select your Base44 project. Push44 displays your app name, live published URL (e.g. https://push44.base44.app), and the 1-Click Badge Removal card.

💡 Pro Tip
Make sure your Base44 project has been deployed at least once so it has an active live URL.
3

Click 'Remove Badge from Live Base44 Site'

Click the 🛡️ Remove Badge from Live Base44 Site button. Push44 automatically verifies current CSS rules, prompts Base44 AI to apply the blocker rules, and calls the deployment endpoint.

💡 Pro Tip
The live rebuild and deployment typically takes 10–20 seconds.
4

Verify on your live deployed domain

Click 'View live site' to open your *.base44.app URL in a new tab. Hard-refresh (Ctrl+Shift+R or Cmd+Shift+R) to bypass browser cache — the floating edit badge is 100% removed and invisible.

💡 Pro Tip
The removal is permanent in your deployed build and persists across all client visits.

Pro Tips

  • Hard-refresh your live site after removal to bypass local browser cache
  • Push44 uses your active API token to deploy directly to Base44 edge servers
  • You can re-run badge removal anytime if you make new prompts in the Base44 editor

Common Mistakes to Avoid

⚠️ Watch Out For
  • Paying for expensive enterprise tiers just to hide a watermark
  • Trying to block the script locally in your browser instead of fixing the live deployment
  • Forgetting that the blocker must be injected into the compiled entry stylesheet (src/index.css)

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

Does this remove the badge on the live *.base44.app URL?
Yes! Unlike local ad-blockers, Push44 updates the live stylesheet and triggers a production deploy, so all visitors see a clean, badge-free website.
Do I need a paid Base44 subscription?
No. Push44 uses Base44's standard API endpoints and AI builder, which are available to all account tiers.
Will my custom logic or database be affected?
Not at all. Push44 only injects non-destructive CSS rules targeting #base44-edit-badge and .base44-badge. All pages, entities, and backend functions remain identical.
What if I edit the app again in Base44?
If you send new chat prompts in Base44, simply click 'Remove Badge' in Push44 again to redeploy the clean version.