Base44 Rate Limit Exceeded? Here's How to Fix It (2026)

Start Here: Which Limit Are You Hitting?

Before anything else, check status.base44.com for an active incident. Rate limits and credit limits are normal, expected behavior, not an outage, so the status page will usually show nothing: that itself tells you the limit is real and not a platform problem.

Error 1 - "429" or "Too Many Requests" in a Short Time

What you see: a 429 status code, or "too many requests", right after doing the same thing several times quickly: reconnecting a domain, resubmitting a form, or calling an API, a backend function or an automation in a tight loop.

Why it happens

Base44 documents this as a temporary, per-person protection against sending too many requests in a short window, separate from any credit balance. It applies to actions in the dashboard and to API, backend function and automation calls alike.

How to fix it

1. Stop and wait a short time before retrying. Don't click the same button repeatedly if it doesn't respond right away.
2. Look for patterns that send many requests at once: data that refreshes on a timer, a search box that queries on every keystroke, or a list that loads records one by one instead of in a batch. In Discuss mode, ask the AI to point out which pages or automations do this before you let it change anything.
3. Space out writes instead of firing them together, and add a short debounce to search-as-you-type fields so they query once the user stops typing.
4. If your own backend function calls an API, add retry logic that waits before trying again after a 429, instead of retrying immediately.
5. If a 429 shows up during normal, non-repetitive use, contact Base44 support with the time it happened and what you were doing.

What you should see: the action succeeds on the next try, with no 429 in the browser console, once requests are spaced out.

Error 2 - Emails, Uploads, Image Generation or AI Features Stop Working

What you see: a feature that calls one of Base44's built-in services fails with a generic error for your users. If you repeat the same action yourself as the app owner, Base44 tells you plainly that you have used all your integration credits.

Why it happens

Integration credits are a separate, monthly balance from the request rate limit above. They're spent by Base44's own built-in integrations: Invoke LLM, SendEmail, SendPushNotification, UploadFile, GenerateImage and ExtractDataFromUploadedFile, plus backend function invocations (roughly 1 credit per 100 calls) and workflow steps (roughly 10 steps per credit). AI chat prompts draw from a different balance, message credits, so running out of one doesn't affect the other.

How to fix it

1. Check your balance first: open the workspace name at the bottom left, then Settings → General → Credit usage (or click the Base44 logo at the top left of the editor). If integration credits show 0, that's your answer.
2. Audit which pages or automations call a built-in integration on every page load, on a timer, or once per row in a list, instead of once when actually needed. Ask the AI in Discuss mode to list them before changing anything.
3. Cut the calls that don't need to happen every time: cache results that don't change often, batch emails or notifications instead of sending one per record, and trigger image generation or file extraction only on user action, not automatically.
4. Wait for the monthly reset, or upgrade your plan if the usage is genuine and growing.
5. If a backend function calls an external API using your own API key, that external call itself doesn't spend integration credits, only the function invocation does, so moving logic into fewer, batched function calls helps more than switching providers.

What you should see: Credit usage shows integration credits above 0, and the feature that failed works again without a manual retry.

What Actually Counts Toward Your Integration Credits (and What Doesn't)

An older version of this guide said reading and writing data through Supabase was the biggest driver of Base44's integration limit. That's wrong on two counts, and worth correcting directly because it sends people fixing the wrong thing.

• Base44 doesn't run on Supabase. It has its own backend: database, authentication, file storage, backend functions and hosting, with row-level security built in. Supabase only enters the picture if you connect an external Supabase project yourself from a backend function.
• Reading and writing your app's own database does not use integration credits. Base44's billing documentation says this explicitly. A dashboard that loads records from five tables on every visit doesn't touch your integration balance at all.
• Calling an external service with your own API key doesn't use integration credits either. Only the built-in integrations listed above do, plus the backend function invocation that makes the call.
• Manual edits in the visual editor, like dragging elements or changing text, don't use credits of any kind.

In short: if a feature is failing, look at how often it calls Invoke LLM, SendEmail, SendPushNotification, UploadFile, GenerateImage or ExtractDataFromUploadedFile, not at your database or at outside APIs you call directly.

Free Plan and Paid Plan Limits, and Where to Check Usage

• Free plan: up to 5 combined credits a day, capped at 25 a month, resetting at midnight in the workspace owner's time zone.
• Paid plans: message and integration credits reset monthly, on the same day of the month you subscribed.
• Where to check: workspace name (bottom left) → Settings → General → Credit usage, or the Base44 logo at the top left of the editor.

If you're consistently close to your monthly cap before the reset date, that's a usage pattern to fix (see Error 2 above), not something a single optimization will solve for good.

When It Isn't a Bug

• Hitting these limits as your app grows is expected, not a defect. Base44 sets both limits deliberately to manage shared infrastructure, and neither one is a sign your app is broken.
• Repeated integration credit exhaustion despite trimming unnecessary calls usually means the app's real usage of built-in services (email, AI, image generation) has outgrown what a Base44 plan covers cheaply. At that point the honest options are upgrading, moving the heaviest of those calls to an external service you control from a backend function, or moving that part of the app off Base44 entirely if it depends on features Base44 doesn't rate-limit the same way, such as scheduled jobs run from GitHub Actions or n8n that write results your Base44 app then just reads.

What to Include When You Ask for Help

Whether you write to Base44 support or to a developer, include:

• the exact error text or status code, and whether it happened once or repeatedly;
• the time it happened and what action triggered it;
• a screenshot of your Credit usage panel, so it's clear whether credits were actually at 0;
• which integration (email, AI chat, image generation, file upload, a specific backend function) was involved;
• your plan (free or paid), since the free plan's daily cap changes the likely cause.

If the problem isn't a limit at all, like a stuck editor, a blank screen or a domain that won't connect, see the full guide to the most common Base44 errors.

Frequently Asked Questions

Still broken after this guide?

If your Base44 app keeps failing in ways this guide doesn't cover, the AppStuck Master Prompt gets your AI builder to write up the problems in your app, so you can see what's wrong before you change anything else. It's free. Get the Master Prompt.

Sources

Checked on September 28, 2026, except where noted:

• Base44 docs: Credits
• Base44 docs: Troubleshooting issues
• Base44 docs: Using integrations
• Base44 docs: Backend features (checked September 16, 2026)
• Base44 status page